A 90-day startup plan: a founder's template

Start with a verifiable bottleneck

A founder may simultaneously want a new sales channel, a product launch, a management hire and new software. But if the current bottleneck is frequent late handovers, another channel may bring more customers into an unreliable experience. Priorities should begin with what limits results, not a list of activities that merely look growth-oriented.

Hypothetical scenario: a service startup has 20 customers, six of whom received deliverables late during the month. Investigate whether delays stem from information gathering, unclear scope or delivery capacity. Each cause leads to a different plan. These figures illustrate how to ask questions, not an industry assessment standard.

Choose priorities using four questions, not just a score

First: which outcome does this affect? Second: what evidence indicates that this is the right problem? Third: how much team time, money and attention are required? Fourth: if it goes wrong, how reversible is it? The answers help the group see trade-offs before choosing.

A scoring table can aid discussion but does not create certainty. Two ideas with equal scores may still differ in risk or dependencies. For hard-to-reverse decisions, clarify missing information instead of forcing a ranking through subjective numbers.

Add a list of things not to do in the next 90 days. If a new idea is added each week without removing anything, the plan becomes a wish list. Founders must protect priorities by refusing or deferring activities that do not yet serve the goal.

A one-page planning template for small teams

The table below describes a hypothetical effort to reduce late handovers. Targets must be adjusted for actual data, sample size and team capacity. A numerical goal is not automatically an appropriate goal.

Divide 90 days into three stages with decisions

First 30 days: measure the baseline, talk with people doing the work directly and test one small change. The required output is learning, not just written documentation. If the original assumption is wrong, revise the problem before investing further.

Days 31 to 60: expand scope when evidence supports it. Check quality, effort and side effects; a method that works when the founder closely follows every case may not hold up when assigned to the whole team.

Days 61 to 90: retain effective elements, document recurring work and decide the next period's priorities. These stages organize experimentation; they are not a mandatory calendar. Startups with long purchasing or implementation cycles should adjust review timing accordingly.

Interactive checklist: is the plan clear enough to discuss?

Check each item when you have found specific evidence or information for it. The checklist identifies gaps in a plan; it does not score business quality or predict success. Selections are processed only in your browser.

What should a one-page weekly report clarify?

Record new results, recent learning, risks and decisions requiring support. Separate confirmed facts from hypotheses. For small samples, include a few concrete situations to explain the figures rather than treating a week's rise or fall as an established trend.

Completed tasks with unchanged outcomes signal a need to revisit the solution. Do not continue solely because much effort has already been invested. If market conditions change, record what prompted a priority shift and which work will stop to release resources.

Move from planning to evidence-based decisions

After selecting an experiment, read the experiment-assessment article to define conditions for continuing, revising or stopping in advance. When additional capacity is needed, the hiring-versus-outsourcing article helps distinguish a long-term need from a task that can be contracted as a package.

A plan also needs its implementers to understand their roles. Use the 1:1 meeting template to hear each person's bottlenecks and the operational-overload case to check whether the growth plan exceeds service capacity.

Suggested actions