How to Set Your Startup's First Quarter Goals

Annual planning is a corporate ritual that doesn't work for early-stage startups. When you're pre-product-market fit, you can't predict what you'll be doing in 12 months. You might pivot twice. You might run out of money. You might discover your entire market has shifted.

90 days is the right timeframe. It's long enough to make meaningful progress on hard problems. It's short enough to adjust when you learn something new. Most importantly, it forces you to prioritize ruthlessly.

This guide covers how to set quarterly goals when you're just starting out, what metrics to track, and how to know when to change course.

The 90-day sprint isn't arbitrary. It's the sweet spot for several reasons.

Long enough to:

• Build and ship meaningful features
• Run experiments and see results
• Make progress on complex problems
• Establish new habits and processes

Short enough to:

• Adjust when you learn something unexpected
• Avoid sunk cost fallacy on the wrong priorities
• Maintain urgency and focus
• Celebrate wins and reset

What 90 days feels like:

• Week 1-4: Set direction, start building
• Week 5-8: Make progress, hit obstacles, adjust
• Week 9-12: Push to finish, evaluate results

At the end of each quarter, you'll know more than you did at the beginning. Your next quarter's goals should reflect that learning.

Two to three goals. Maximum.

This feels like too few. It isn't. Early-stage startups fail because they spread attention too thin, not because they focus too much.

Why limiting goals works:

• You can actually remember your priorities
• Your team (if you have one) can align around them
• You can go deep instead of making surface-level progress everywhere
• You'll finish things instead of having five half-built projects

What happens with too many goals:

• Everything becomes equally important (meaning nothing is important)
• You context-switch constantly
• You end the quarter with nothing completed
• You burn out without feeling accomplished

If you can't pick 2-3 goals: Everything on your list beyond #3 is either:

• A task, not a goal (break it down)
• A dependency of a bigger goal (combine it)
• Not actually important right now (cut it)

Be honest about what will actually move the needle this quarter.

Goals can measure inputs (what you do) or outputs (what happens as a result). Both matter, but they serve different purposes.

Output metrics (results):

• Revenue: $10,000 MRR
• Users: 500 active users
• Retention: 40% 30-day retention

Input metrics (activities):

• Customer calls: 50 user interviews
• Content: Publish 12 blog posts
• Outreach: Send 200 cold emails

When to use each:

Use output metrics when you have enough data to set realistic targets and when you can influence the outcome. If you've been growing 20% month-over-month, a revenue goal makes sense.

Use input metrics when you're early and don't have baseline data. If you've never done sales outreach, you can't set a conversion goal. But you can commit to 200 emails.

The trap: Input metrics feel safer because you control them completely. But inputs don't guarantee outputs. You can send 200 emails and get zero customers. Watch for input goals that don't produce results. They might mean your strategy is wrong, not just your execution.

Most early-stage startups have no baseline data. You can't set a 20% improvement goal when you don't know your current numbers.

Strategies for pre-data goal setting:

Milestone-based goals: Instead of "increase revenue by X%," set "reach $5,000 MRR" or "get first 10 paying customers." Milestones work when you're going from zero to something.

Learning-based goals: "Validate that restaurants will pay $200/month for this" is a goal. The outcome is a yes or no, not a number. Early-stage goals are often about answering questions.

Effort-based goals (carefully): "Talk to 50 potential customers" is achievable even with no data. But pair it with a learning objective: "and document their top 3 pain points."

Borrowed benchmarks: Look at what similar companies achieved at your stage. YC companies often target 5-7% week-over-week growth. Industry benchmarks for retention vary by category. Use these as starting points, not gospel.

The honest approach: "We don't know what's achievable. Our goal is to find out." That's a valid Q1 goal for a brand-new startup.

Pre-launch startup:

1. Ship V1 and get 100 users signed up
2. Complete 30 customer interviews and validate top 3 feature assumptions
3. Establish one repeatable acquisition channel (define what repeatable means)

Post-launch, pre-revenue:

1. Convert 10 free users to paying customers
2. Achieve 30% 7-day retention
3. Identify and double down on the highest-converting user segment

Early revenue ($1-10K MRR):

1. Reach $5,000 MRR
2. Reduce churn to under 8% monthly
3. Document and delegate one repeatable process (support, onboarding, etc.)

Post-funding:

1. Hit milestones committed to investors (be specific)
2. Hire first [role] and have them productive
3. Establish one scalable growth channel

Notice the pattern: each goal is specific, measurable, and focused on the biggest risk or opportunity at that stage.

Goals only matter if you track them. But tracking can become its own distraction.

The minimum viable check-in: Once per week, answer three questions:

1. What progress did we make on each goal?
2. What's blocking progress?
3. What will we do this week to move forward?

30 minutes, maximum. If you're spending hours on weekly reviews, you've over-complicated things.

What to track:

• Your 2-3 quarterly goal metrics (that's it for strategic tracking)
• Leading indicators that predict those metrics
• Obvious operational metrics (cash in bank, critical bugs)

What not to track weekly:

• Vanity metrics (social followers, page views with no conversion)
• Metrics you can't influence this quarter
• Dashboards someone told you to have but you never look at

Tools: A simple spreadsheet works. Google Sheets, Notion, or even a text file. Fancy analytics tools are for later. Right now, you need clarity, not comprehensive data.

Sometimes you'll be halfway through a quarter and realize a goal was wrong. Maybe the market shifted. Maybe you learned something that changes everything. Maybe you were just wrong.

Signs you should change the goal:

• New information makes the goal irrelevant
• You've achieved the underlying intent but not the specific metric
• External factors make the goal impossible
• You're making consistent effort with zero progress (after troubleshooting)

Signs you should persevere:

• It's hard but not impossible
• You're making progress, just slower than hoped
• You haven't actually tried your best ideas yet
• Changing the goal would just be avoiding discomfort

The honest test: If you hit this goal, would it meaningfully move your business forward? If yes, keep pushing. If no, why was it a goal in the first place?

How to change goals mid-quarter: Don't pretend the old goal never existed. Acknowledge the change, document why, and set a new goal for the remaining weeks. Changing goals isn't failure. Changing them without learning is.

At the end of 90 days, take an hour to review before planning the next quarter.

Questions to answer:

• Did we hit our goals? If not, why not?
• What did we learn that we didn't know 90 days ago?
• What worked that we should do more of?
• What didn't work that we should stop or change?
• What should our goals be for the next quarter based on this?

Be honest about results:

• If you hit a goal, did it actually matter? Did it move the business forward?
• If you missed a goal, was it the wrong goal or poor execution?
• What would you do differently if you could restart this quarter?

Involve the team (if you have one): Different perspectives reveal blind spots. The person doing customer support sees different patterns than the person writing code.

Document it: Write a brief summary of the quarter. Future you will find it useful. Patterns emerge over multiple quarters that you can't see in the moment.

• 90 days is the right planning horizon for early-stage startups. Long enough for progress, short enough to adjust.
• Set 2-3 goals maximum. More than that spreads focus too thin.
• Use output metrics when you have data, input metrics when you're establishing baselines.
• Early-stage goals are often about validating assumptions and learning, not hitting specific numbers.
• Check in weekly for 30 minutes. Track only what matters for your quarterly goals.
• Change goals mid-quarter if new information makes them irrelevant. Don't change them just because they're hard.
• Review honestly at quarter end. Learn from what happened before planning what's next.

What if we're so early that we don't know what to prioritize?

Your goal is to figure out what to prioritize. "Complete 30 customer interviews and identify the #1 problem we should solve" is a valid Q1 goal. Learning is progress.

How do we handle goals when the whole company is two people?

You don't need a formal OKR system. Write your 2-3 goals somewhere visible. Check in weekly over coffee. The process can be informal as long as it happens.

Should founders have individual goals or just company goals?

At early stage, individual and company goals should be the same. You're all working on the same 2-3 priorities. Personal goals come later when you have enough people to specialize.

What if my co-founder and I disagree on priorities?

That's what goal-setting is for. Have the hard conversation now. Disagreement about quarterly goals usually reflects deeper disagreement about strategy or vision.

How often should goals change based on investor feedback?

Investors have opinions. Not all of them are right for your situation. Consider their feedback, but don't let your quarterly goals ping-pong based on every conversation. You know your business better than they do.