How we build · Stage 07
Grow
Use evidence from real usage to decide what happens next.
- Typical duration
- Continuous
- Portal phase
- grow
- Stage
- 07 of 08
- CRM stages
- 2
What this stage is for
After launch the roadmap should be driven by what users actually do. We instrument, measure, experiment and prioritise against outcomes rather than a fixed feature list.
Your part
Agree the outcome measures, and let the evidence change the roadmap.
Activities
What happens
- Product analytics and funnel instrumentation
- Experimentation and A/B testing where volumes support it
- Conversion, retention and task-completion optimisation
- Roadmap delivery in continuing increments
- Ongoing accessibility and performance work
Outputs
What you get
- Outcome dashboards tied to the KPIs agreed in Shape
- Experiment results and the decisions taken from them
- A prioritised, evidence-backed roadmap
Exit criteria
We do not move on until
Written down so neither side has to rely on a feeling that things seem fine.
- The agreed outcome measures are being reported against
- Roadmap priorities are set from evidence rather than opinion
Behind the scenes
How this shows up in our systems
This is not a diagram made for a website. The stage you are reading maps onto literal values in our CRM and the phase label in your client portal.
- CRM pipeline stages
- Support / managed serviceRunning under an agreed service level.Expansion / renewalA further engagement or a renewal is in play.
- What you see in the portal
- Your project shows the phase "grow", with this stage's purpose and your part written on the project page.
Where it applies
Services that run this stage
Next step
Talk to us about grow
The Project Architect asks the questions this stage depends on, and tells you which stage your project should actually start at.