First 90 Days: Validate Before You Scale

A 90-day plan is useful when it creates a sequence for learning, choosing and testing. It is not a promise that every new business should reach the same milestones in three months.

The useful question is:

What should be clearer after 90 days than it is today, and what evidence will make the next decision easier?

Start with the business as it exists, not the business you hope to build.

Document:

• who is buying or considering the offer;
• the problem they are trying to solve;
• what they use today;
• who decides;
• why the decision happens now.

Use recent customer behaviour wherever possible.

Record:

• current revenue and pipeline;
• cash position and committed outflows;
• delivery capacity;
• major operating constraints;
• important dependencies;
• decisions currently being delayed.

Write the five assumptions that could most seriously change the plan.

For each:

What we believe → evidence → what is missing → cheapest credible test

Do not spend the first month producing activity that leaves these assumptions untouched.

Turn the evidence into explicit choices.

Write a short decision memo covering:

Target customer: who deserves attention now?

Problem: which problem is urgent enough to solve?

Offer: what is the smallest useful version?

Distribution: how will the customer find or buy it?

Economics: what must be true about price, cost and payment timing?

Capacity: what can the current team actually deliver?

Stop list: what will you deliberately not do?

For every major choice, record the alternative you rejected and why.

Build, sell, deliver or improve only enough to produce evidence.

Choose tests that answer questions such as:

• Will the target customer pay?
• Can we deliver the promised outcome repeatedly?
• Which objections block purchase?
• Does the customer use the solution after the first interaction?
• Does gross contribution justify the delivery effort?
• What causes repeat or non-repeat behaviour?
• Where does the operating system break as volume increases?

Define the evidence before running the test.

Hypothesis: what must be true?

Test: what can we do now?

Measure: what behaviour or result will we record?

Review date: when will we decide?

Decision: continue, change customer/offer, or stop the test.

A busy 90 days can still teach very little.

Watch for:

• more features without more customer evidence;
• more meetings without decisions;
• more leads without better customer fit;
• more content without evidence of the intended business effect;
• hiring before the work and outcome are defined;
• revenue growth that creates a cash problem;
• dashboards that measure activity but not the constraint.

The right metric depends on the decision. A sales problem, delivery problem and cash problem should not all be managed with the same number.

At day 90, write one page.

What do we now know from observed behaviour or records?

Name the evidence, not just the conclusion.

Record the evidence and its limits.

Compare actual revenue, contribution, fixed costs, cash movement and payment timing with the assumptions used at the start.

Name activities that did not justify their cost or did not answer an important question.

Name the specific evidence that supports continuation.

Write one consequential decision, its owner, the next evidence required and the review date.

A 90-day plan is a planning structure, not a universal startup timetable. The right sequence depends on business model, customer buying cycle, stage, capital, team capacity and operating constraints. Change it when evidence changes.