Find the constraint before choosing tactics
Write your goal as a change in a business outcome: more retained customers, more delivered orders or more qualified opportunities. Work backward through the journey. If the business already receives suitable leads but loses them during evaluation, another traffic campaign can increase workload without fixing sales.
Separate a traffic problem from a conversion problem with counts, not impressions. Record how many people enter each stage, how many progress and how long progression takes. A large percentage drop is not automatically the best opportunity: the stage also needs enough volume and a change your team can influence.
Build a plan the team can execute
- Describe one customer situation, including the trigger that makes the problem urgent.
- Choose one primary outcome and define its denominator, reporting window and data owner.
- Write a hypothesis connecting a proposed change to a specific customer behavior.
- Assign an owner, a spending limit and a review date before launch.
- Add a guardrail such as refund rate, lead quality or retention so local improvement does not damage the business.
Treat content, ads, product work and sales follow-up as connected parts of the journey. Name the dependency that could block each task. A landing page cannot promise a capability that the product does not deliver, and a campaign cannot depend on sales capacity that does not exist.
Worked example: fix evaluation first
Illustrative example: a software company receives 100 qualified demo requests in a month, but only 40 attend. The immediate test is a clearer confirmation page and a reminder with a concrete demo agenda. The primary outcome is attended qualified demos divided by qualified bookings. Paid acquisition remains steady while the team evaluates attendance and eventual customer quality.
This plan answers a smaller question than “How do we grow faster?” It also creates a useful next decision: if attendance improves but purchase does not, investigate the demo and offer instead of buying more appointments.
A simple roadmap
| Workstream | Decision it should support |
|---|---|
| Customer research | Which buying situation deserves priority? |
| Journey measurement | Where do suitable customers stop progressing? |
| Focused experiment | Does the proposed change remove that obstacle? |
| Review | Expand, revise or stop based on outcomes and guardrails. |
What should you leave out?
Leave out initiatives with no clear customer problem, owner or measurement plan. Keep attractive ideas in a backlog rather than giving every department a parallel project. A narrow plan can expand after it produces useful evidence.
How long should the plan cover?
Use a short execution horizon and a longer business direction. A quarterly roadmap can contain several shorter learning cycles; the timing depends on purchase lag and the volume needed to observe outcomes.
Is a growth plan only for startups?
No. Established businesses also have constraints. The difference is that they often need more coordination, segmented reporting and protection for existing customers.
Put this into practice
Create a one-page brief containing the goal, customer, constraint, hypothesis, owner, budget and guardrail. If the team cannot explain why the first task should change the goal, rewrite the brief before launching it.
Primary-source reading for platform details: Paul Graham: Startup = Growth.
Related foundation: SaaS growth strategy: build acquisition around activation. How these guides are prepared.
Ayoub Mouhachtt
Growth & performance marketing. Explore the portfolio and working background.
Related portfolio work: eGrow. The worked examples in this guide are illustrative and are separate from the portfolio’s project evidence.