30-60-90 Day Startup Plan: What to Focus on in Your First 90 Days

The first few months of a startup can disappear surprisingly quickly.

You start with a long list of things that need doing.

Build the product. Talk to customers. Set up the website. Post on social media. Find funding. Make sales. Hire someone. Fix the product.

Then another idea appears and gets added to the list.

By the end of the first month, you can be incredibly busy without being much closer to knowing whether the business is actually working.

That's where a 30-60-90 day startup plan can help.

The point isn't to predict everything that will happen over the next three months. Startups rarely cooperate with the plan anyway.

The point is to decide what matters now, test your assumptions and create clear points where you stop and ask what you've learned.

For a startup, the first 90 days aren't about completing a perfect checklist. They're about turning uncertainty into evidence.

What Is a 30-60-90 Day Startup Plan?

A 30-60-90 day startup plan breaks the next three months into three manageable stages.

Instead of trying to map out everything the business might do over the next year, it focuses on what needs attention now.

Each stage should have a clear objective, key priorities, actions, milestones and a way to measure progress. Where relevant, assign owners and deadlines, with a review point before moving into the next stage.

It's worth separating this from your business plan.

The two work together.

Your business plan sets the direction, while the 30-60-90 day plan turns that direction into near-term action.

If a business plan says:

"We will acquire our first 100 customers."

The 30-60-90 plan asks what needs to happen next.

By Day 30: What do we need to test or learn?

By Day 60: What evidence should we have?

By Day 90: What should be true, and what decision should we make?

That makes the 90-day plan less about filling a calendar and more about creating measurable progress.

Put the 90-Day Plan Into Practice

If you want to turn these ideas into something you can actually work through, download our free 30-60-90 Day Startup Plan Template.

It gives you a simple structure for setting priorities, defining what you need to learn and tracking progress across the next three months.

Don't Start With 90 Tasks. Start With One Question.

Before filling in a template, step back and ask one question:

What does this startup need to prove in the next 90 days?

The answer depends on where the business is right now.

Starting here stops the plan becoming a long list of tasks that feel productive but don't necessarily move the business forward.

One quarter. One primary question.

Everything else should support that question.

The 30-60-90 Startup Framework

The first 90 days shouldn't look the same for every startup.

An idea-stage founder has different problems from a business already generating revenue. What matters is the progression.

30 Days → Validate

What do we need to learn?

60 Days → Build & Test

What can we put in front of real customers?

90 Days → Measure & Decide

What have we proved, and what happens next?

This is more useful for a startup than the traditional 30-60-90 approach often used for employee onboarding.

A startup's plan needs to reflect uncertainty, customer feedback and changing assumptions.

Days 1–30: Validate

Main question: Are we working on the right thing?

The first month is about reducing uncertainty.

That could mean:

• Defining your target customer

• Speaking to potential customers

• Testing your value proposition

• Finding out what people currently use instead of your proposed solution

• Creating a prototype

• Testing a landing page

• Investigating pricing

• Defining the smallest version of the product worth building

You don't need to do all of these things.

The right activities depend on the question you're trying to answer.

The important thing is to finish the first 30 days knowing more about the customer and problem than you did at the start.

Activity vs Learning

It helps to separate activity from learning here.

Activity

"We completed 20 customer interviews."

Learning

"We now understand whether the problem is painful enough, who experiences it most and what they currently do about it."

The first is something you did.

The second is information that should shape what you do next.

Days 31–60: Build and Test

By the second month, the question changes:

Can we turn what we learned into something people will actually use?

For some startups, that means building an MVP.

For others, it could mean:

• Running a pilot

• Testing a prototype

• Starting to sell a service

• Putting a simple offer in front of potential customers

• Testing an early pricing model

The important word here is test.

Don't spend 30 days building simply because the calendar says Days 31–60 should be about building.

If the first month showed that customers don't understand the problem in the way you expected, building more of the original solution probably won't fix it.

This is where a good 30-60-90 plan differs from a rigid project schedule.

A good plan should create discipline without becoming a prison.

If customer conversations change your understanding of the problem, change the plan.

If an early test shows customers won't pay the price you expected, investigate it.

By Day 60, you should have something tangible to evaluate.

That could be:

An MVP · Paying customers · A tested offer · A pilot · Another meaningful piece of evidence

Days 61–90: Sell, Measure and Decide

By the final month, the question changes again:

What have we proved, and what should we do next?

This stage turns the experiments from the first 60 days into evidence you can use.

You might:

1. Convert a pilot into paying customers

2. Improve retention

3. Repeat a sales process

4. Refine pricing

5. Work out which acquisition channels are producing genuine interest

But scale isn't automatically the goal.

It can be the right next step when the evidence supports it, or it might not be.

A startup may discover that customers don't use the product enough, the pricing doesn't work, or the original customer segment isn't the right one.

That's still useful information.

At Day 90, review what you learned, which assumptions survived testing and what should happen next.

You may:

• Continue with the same approach

• Change the product

• Change the customer segment

• Change the route to market

• Pause the idea

The decision is part of the output.

A Real 90 Days: One Founder's Version

Here's what this can look like in practice.

Imagine a founder starts the first 90 days convinced the biggest risk is building the product fast enough.

By Day 30, customer conversations reveal something different.

The retailers being interviewed aren't short on inventory software. They already have three tools they half-use and don't fully trust.

The actual problem isn't building fast.

It's earning enough trust to become tool number four.

That single insight changes what Days 31–60 look like.

Instead of building a feature-heavy MVP, the founder builds the smallest possible integration with the one tool retailers already trust and leads every pitch with that.

By Day 90, the original idea hasn't necessarily been proven.

But a narrower, more useful version of the idea has.

And that can be exactly what the first 90 days were supposed to uncover.

This is close to the idea of validated learning associated with the Lean Startup methodology developed by Eric Ries. The approach centres on building, measuring and learning so entrepreneurs can test assumptions and adjust rather than simply spending months building against an untested idea.

The goal of the first 90 days isn't to prove that your original idea was right. It's to find out what the evidence is actually telling you.

What Should You Actually Put in the Plan?

Once you've worked out what the startup needs to prove, the plan itself can stay fairly simple.

You need enough detail to know what you're trying to achieve, what needs to happen, who's responsible and how you'll judge progress.

A Simple 90-Day Planning Table

The Assumption row is particularly useful for startups.

Traditional project plans tend to focus on what needs to be delivered. Startups also need to track what they don't know yet.

For example, you might assume small businesses will pay £50 a month for your product.

That assumption can become something to test during the first 30 or 60 days.

Writing it down makes it easier to challenge rather than quietly treating it as fact.

If you can't identify the assumption behind a goal, you may be treating a guess as a fact.

Don't Confuse Activities With Progress

A plan can look impressive when it's full of completed tasks.

That doesn't necessarily mean the startup has moved forward.

Activity

Publish 20 LinkedIn posts.

Progress

Generate 15 qualified conversations with target customers.

The activities aren't useless. You need to publish, build and have meetings to make things happen.

The problem comes when completing the activity becomes the goal rather than a means to one.

Before adding something to your plan, ask:

What will this help us learn, prove, improve or achieve?

If the answer isn't clear, reconsider the task.

A busy month and a useful month can look identical from the outside.

The difference only shows up in what you can say with confidence at the end of it.

Your Metrics Should Match Your Stage

Not every startup needs the same dashboard.

It's easy to copy a list of popular startup metrics and start tracking revenue, website traffic, followers, MRR, CAC and retention.

But a number is only useful if it helps answer the question your startup is currently trying to prove.

What to Measure at Different Stages

These aren't rules.

They're starting points.

The important thing isn't how many metrics appear in your spreadsheet.

Ask:

What number would actually tell us whether this 90-day plan worked?

That's the one worth paying attention to.

What Happens If the Plan Goes Wrong?

Something probably will.

The MVP might take longer than expected.

Customers might not care about the feature you thought would matter.

Your first marketing channel could produce almost nothing.

A key hire might fall through.

That's normal startup territory.

The mistake is treating the original 90-day plan as fixed when the evidence is telling you something has changed.

Instead, build review points into the plan.

Day 30

What did we learn?

Day 60

What changed?

Day 90

What should we stop, continue or start?

This turns the 30-60-90 plan into a learning loop rather than a document that becomes irrelevant after week three.

Building the Plan Is Only Part of It

Sometimes the hardest part of a 90-day plan isn't writing it. It's knowing what to change when things don't go as expected.

If you're working through a customer problem, testing an idea or deciding what deserves your attention next, join the Startup Networks Discord Community and connect with other founders who are figuring things out too.

Don't build your business alone.

Common 30-60-90 Startup Plan Mistakes

A 90-day plan can give a startup useful focus, but there are a few easy traps.

1. Trying to Do Everything

Three months is not long.

Choose the few things that matter most to the question you're trying to answer.

2. Setting Goals Without Evidence

"Get 1,000 users" sounds ambitious, but what would that number actually prove?

3. Measuring Vanity Metrics

Followers and impressions can look impressive while sales remain at zero.

4. Building Before Validating

Spending weeks building something nobody needs is an expensive way to learn.

5. Making Everything Urgent

If everything is a priority, the plan isn't prioritising anything.

6. Never Revisiting the Plan

Your assumptions should change when the evidence changes.

And don't copy another startup's roadmap.

A SaaS company, marketplace and local service business can have completely different priorities over the same 90-day period.

How the 30-60-90 Plan Fits With Your Other Startup Tools

A 30-60-90 day plan doesn't replace the other frameworks you might already use.

It gives them somewhere to go next.

Then comes the 30-60-90 day plan.

What are we actually doing next?

Think of it as the execution layer that turns broader strategy into near-term priorities, tests and measurable outcomes.

Download the 30-60-90 Day Startup Plan Template

You don't need another document to stare at.

You need somewhere to decide what matters over the next 90 days, turn those priorities into actions and give yourself a clear point to review what's actually happening.

The Startup Networks 30-60-90 Day Startup Plan Template is designed to take the framework in this article and turn it into a practical plan for the next three months.

Use it as a starting point rather than something to follow rigidly.

Your priorities may change as you speak to customers, test your idea and gather evidence.

📥 30-60-90 Day Startup Plan Template

Your Next 90 Days Should End With an Answer

The goal isn't to reach Day 90 with every task ticked off.

It's to reach Day 90 with more certainty than you had on Day 1.

Maybe you found your first customers.

Maybe you proved the problem was real.

Maybe you discovered your original customer wasn't the right one.

Or perhaps you were trying to solve five problems when customers only cared about one.

Those are all useful outcomes.

A good 30-60-90 day plan gives you a structure for testing assumptions, learning from the results and deciding what deserves your attention next.

So before you fill in your plan, ask yourself:

What's the one thing your startup needs to prove in the next 90 days?

Share your answer with the Startup Networks community and see what other founders are working towards.