Divide a 90-day growth plan into three jobs: establish the starting position, make a focused change and review the evidence before choosing the next step. You do not need to launch every channel at once. Start with one point in the customer journey that is holding back enquiries or sales.
Choose one growth goal
Traffic, followers and form completions are useful observations, but they do not all represent business progress. For a B2B service company, a meaningful outcome might be qualified opportunities reaching a discovery meeting. For a retailer, it may involve the contribution from fulfilled orders. A subscription business may need to focus on customers continuing to receive value after the first purchase.
Choose one primary outcome and identify the steps that influence it. Record operational constraints alongside the target. Generating enquiries the sales team cannot handle, or promoting products that cannot be fulfilled, creates a disconnected plan. Agree which offer matters, what a suitable customer looks like and who can approve spending and changes.
Days 1–30: check the data and customer journey
Review search visibility, campaigns, landing pages, contact channels and sales notes together. What question brings someone in? Which information helps them decide? What happens after they enquire? Mark missing information as unknown, rather than interpreting an absent measurement as no activity. Turn the important gaps into implementation tasks.
Google Analytics supports measuring meaningful actions as key events. Recording a successful form submission can be useful, but it does not establish that the enquiry is suitable or that a sale occurred. Define how website observations will be connected to sales assessment. Resolve obvious duplication and tracking errors before comparing channel performance.
| Period | Decision to support | Working output |
|---|---|---|
| Days 1–15 | Where are the gaps and uncertainties? | Baseline and measurement gaps |
| Days 16–30 | What should change first? | Priority bottleneck and experiment brief |
| Days 31–60 | What behaviour is changing? | Implementation log and sales feedback |
| Days 61–90 | What should continue, change or stop? | Decision note and next-period resources |
Narrow the bottleneck
Changing every channel and page at once makes interpretation difficult. Start with a commercially relevant service or product group. If interest exists but enquiries do not follow, investigate the offer, explanation and contact experience. If enquiries are unsuitable, examine targeting and expectations. If meetings do not progress, the proposal process and sales objections deserve attention.
Prioritise using expected impact, supporting evidence, delivery effort and dependencies. A content programme may be valuable, while a broken enquiry form still deserves earlier attention. Scoring can structure the discussion, but it cannot turn a weak assumption into evidence. Make the reasoning visible so the team can revise it when new information arrives.
Days 31–60: try one focused change
Illustrative experiment: a custom software provider receives many price enquiries for work it does not offer. The team clarifies suitable project types on the page and adds “What do you need to build?” to the form. It then reviews lead suitability without simultaneously changing ad targeting and pricing messages.
Do not compare form counts alone. Does the team need extra calls to collect missing information? Which project types arrive? Can sales route them correctly? With limited traffic or enquiries, treat the observations as tentative and use conversation notes to choose the next change.
- Before: classify enquiries as suitable, out of scope or missing key details.
- Change: add project examples and the question that captures the need.
- Track: record enquiry volume, suitability and missing information.
- Next: improve unclear copy, or fix follow-up if suitable leads remain unanswered.
Track delivery and customer feedback together
Content, advertising, development and customer follow-up may sit with different people. Give every task an owner, an acceptance condition and visible dependencies. Record when a page, campaign message or form changed. Without that context, the team may compare periods that represent very different customer experiences.
Use weekly reviews to examine customer questions and poor-fit enquiries alongside performance data. Ask sales which expectations were wrong, which objections repeated and which explanations helped. When traffic is limited, a small number of conversions cannot support a confident statistical claim. Continue learning through conversations, usability observations and operational records while acknowledging the uncertainty.
Days 61–90: review and choose the next step
Separate what you observed, what remains an assumption and what the team will do next. Account for seasonality, overlapping campaigns and the time customers need to buy. A before-and-after comparison alone does not establish causation. For a long sales cycle, opportunities generated during the period may not reach a final outcome until later.
Assign resources to the work you will continue. Give a reason for changing or stopping other activities. The strongest outcome of the first 90 days is a better operating system for growth: customer evidence informs the offer, design, content and project priorities, rather than a calendar encouraging the same activity indefinitely.