Field notes / Strategy

What belongs in a 90-day growth plan

A useful growth plan makes decisions visible. It connects a business objective to the work, budget and evidence needed to move it.

Clay + Flint / November 17, 2026 / 4 minute read

A plan should make choices easier.

A list of campaigns is not yet a growth plan. Neither is a revenue target with a collection of tactics underneath it. A useful plan explains the business constraint, the work you will commit to and the evidence that will inform the next decision.

Ninety days is a practical planning window: long enough to build and use something meaningful, short enough to make tradeoffs visible. It does not guarantee that a long sales cycle or search investment will produce a measurable commercial result within the quarter.

1. Write the constraint in business language.

Begin with what is preventing progress. “We need more social posts” describes a possible output. “Suitable prospects do not understand when to involve us” describes a problem worth investigating. Review recent enquiries, sales conversations and operating records before selecting the answer.

Choose one primary audience, offer and business objective for this plan. That is a decision about the next quarter’s work, not a restriction on the businesses you may serve in the future.

2. Establish a baseline—or name the gap.

Record a metric, its definition, source, owner and date range. A qualified enquiry might mean a request in your service area for an eligible service, with a realistic timeframe. A form submission by itself may not meet that definition.

If nobody can produce a trustworthy count, write “unknown.” Add a measurement deliverable and the date when the team will review an initial baseline. A guessed number makes the plan look finished while hiding the work it needs.

3. Pick two workstreams that address the constraint.

A workstream is an ongoing area of focus with a defined result, such as “improve the estimate-request journey” or “make sales follow-up dependable.” Keep an explicit “later” list so every good idea does not become this month’s commitment.

WorkstreamExample deliverableCompletion evidence
Enquiry journeyOne priority service page and a shorter request formApproved copy, mobile and keyboard checks, a successful routing test.
Follow-upAn owner, qualification rules and a small set of response templatesTest records reach the right person; staff can explain and use the next-action process.

4. Make the first month concrete.

Give each deliverable one owner, a due date, a reviewer and an acceptance condition. Include the inputs the client team must supply. “Build a landing page” is open-ended; “publish the approved page for the priority offer, verify form delivery and record conversion events” is reviewable.

Account for approvals, software, media and production costs. A plan that uses every hour for creation has left no room for feedback, fixes or measurement. Confirm what fits before work is promised.

5. Separate completed work from business results.

Use three layers of evidence. First, delivery: did the agreed asset or workflow pass its checklist? Second, adoption: is the team using it and is the journey functioning? Third, commercial observation: what happened to qualified enquiries, accepted opportunities, bookings or repeat purchases?

These layers answer different questions. A delivered page is not proof of a sales increase. A lower enquiry count can still be useful if qualification improved. Review the full journey and explain the limitations of the available data.

A worked example

If the page attracts suitable visitors but the team does not respond, another campaign is unlikely to be the first useful investment. The plan should allow work to move toward the actual constraint.

6. Decide in advance when to change course.

  • Weekly: review deliverables, dependencies and the next owner action.
  • Monthly: review journey performance, customer feedback and capacity.
  • At day 90: decide what to continue, change, stop or investigate.
  • For each decision: record the evidence, its limits and the next review date.

A forecast describes what may happen. A plan records what you will do. Keep assumptions about traffic, conversion, cost and team capacity beside the plan so you can revise them without pretending the original forecast was a commitment.

Leave the meeting with five answers.

  • What is the one business constraint we are addressing?
  • Which two workstreams will receive attention?
  • Who owns the next deliverable and what counts as complete?
  • What evidence will we review, and where will it come from?
  • What would make us continue, change or stop?

Use the guided 90-day workbook to record those decisions, including a baseline, a priority scorecard and a monthly review.

Put the thinking to work.

Use the guided workbook to turn your business constraint into a measurable 90-day plan.

Get the free workbook More field notes

Your privacy preferences

Essential session cookies support sign-in. Optional first-party analytics count completed actions without advertising IDs, stored IP addresses or third-party tracking.