Working template
90-day SaaS growth plan
Use this template to plan one focused learning cycle across demand, conversion, lifecycle, and revenue intelligence. It is designed to make the next decision clearer—not to turn a quarter into a promise.
START WITH A CONSTRAINT
A useful plan connects a business question to evidence, accountable owners, and a decision that can change when new information arrives.
The planning cycle
Three phases, one connected operating system.
Days 1-30
Diagnose and align
- Write the one constraint this plan is intended to investigate, plus the buyer or revenue decision it affects.
- Document the current evidence: demand, conversion, sales, product, lifecycle, and data signals—along with what is unknown.
- Agree on the primary conversion event, lifecycle definitions, decision owner, working cadence, and the systems or people required for access.
Days 31-60
Run focused work
- Choose the smallest set of connected changes that can test the constraint. Avoid a channel backlog that cannot produce a useful answer.
- Record each hypothesis, required input, owner, expected signal, and the outcome that would change the next decision.
- Keep the destination, qualification path, sales handoff, and reporting context connected to any demand or conversion work.
Days 61-90
Review and decide
- Review results against the definitions set at the start, including data gaps, changes in context, and unintended trade-offs.
- Decide what to scale, stop, revise, or investigate next. Preserve the rationale so the next cycle starts from evidence rather than memory.
- Update ownership, measurement, and the next constraint before turning early signals into an annual plan or outcome claim.
Plan fields
What to make explicit on one page.
- Business constraint and decision to improve
- Target buyer, trigger, and current path
- Evidence available and material unknowns
- Primary conversion event and qualification definition
- Connected work across demand, conversion, lifecycle, and revenue intelligence
- Owners, inputs, approval rights, and operating cadence
- Hypotheses, expected signals, and stop/change conditions
- Reporting view, caveats, and next-cycle decision
Built for the working session
A template should make ownership visible.
Use the structure to bring customer context, a focused constraint, and the people responsible for the next decision into the same conversation.