01 / Behind the approach
The decision behind the approach
Trigger messages from useful product context and distinguish upgrade revenue from other account changes.
02 / Behind the approach
The scope at a glance
- Diagnosis, Data Plumbing, and Deliverability
- Build the Six Expansion Flows
- Optimize Offers, Personas, and Send Logic
- Attribute, Improve, and Hand Over
01 / Fit
Explain who the product helps and why.
Start with the workflow and audience, then show what a useful evaluation involves. Make requirements and limitations visible before a visitor books time or starts an account.
- Choose product behaviours that plausibly indicate a need for more capacity, capability or support.
- Use real product information.
- Explain setup and integration dependencies.
- Separate demo requests from suitable opportunities.
The working decision
Explain who the product helps and why.
Use real product information.
02 / First value
Define the milestone beyond account creation.
Agree the action that signals an initial useful outcome. Inspect the steps, questions and dependencies between entry and that milestone with the team that owns the product.
- Explain the relevant feature or plan in context and avoid treating every active user as ready to upgrade.
- Confirm the event and eligible population.
- Make help available at the point of friction.
- Assign ownership of product changes.
The working decision
Define the milestone beyond account creation.
Confirm the event and eligible population.
03 / Continued use
Look for a continuing reason to use the product.
Review usage and customer feedback by a consistent cohort. Coordinate useful education, support and commercial communication without treating every reminder as a retention improvement.
- Review expansion, contraction, renewal and churn independently over a stated observation period.
- Keep usage and paid continuation distinct.
- Match messages to the customer’s situation.
- Review the period and limitations of the cohort.
The working decision
Look for a continuing reason to use the product.
Keep usage and paid continuation distinct.
03 / Behind the approach
How the approach fits together
1. Identify meaningful usage signals
Choose product behaviours that plausibly indicate a need for more capacity, capability or support.
2. Make the next step useful
Explain the relevant feature or plan in context and avoid treating every active user as ready to upgrade.
3. Separate account outcomes
Review expansion, contraction, renewal and churn independently over a stated observation period.
04 / Behind the approach
What to measure
- Expansion revenue: additional revenue from existing accounts under the agreed definition.
- Upgrade conversion: eligible accounts upgrading.
- Retention: account continuation over a stated period.
Report the observation period, the source of each measure and any changes to the way data was collected. Compare like with like before treating a difference as improvement.
Does an upgrade prove the email caused the expansion?
No. Product usage and sales activity may also contribute. Use a suitable comparison where possible and state attribution limits.
Send everyone to a demo?
Choose the route that fits the product and buying process. A complex evaluation may need a person; a straightforward use case may benefit from a direct trial.
Judge growth by registrations alone?
Track whether suitable users reach value and continue. Keep sign-ups, activation, paid conversion and expansion visible as separate stages.
Expansion revenue
additional revenue from existing accounts under the agreed definition.
Order and customer records, with cancellations, returns and the observation window stated.
Upgrade conversion
eligible accounts upgrading.
Customer, subscription and billing records for the defined eligible cohort and period.
Retention
account continuation over a stated period.
Customer, subscription and billing records for the defined eligible cohort and period.
05 / Behind the approach
What this example helps you evaluate
Use the approach to identify what needs to change, what your team must provide and how you would judge progress. The commercial outcome depends on the starting point, implementation and operating conditions.
06 / Behind the approach
When this approach is relevant
Use this as a starting point when the obstacle and operating conditions resemble your own. The first discussion should establish whether the underlying cause is similar and whether the required information and delivery capacity are available.
Use-case brief
The intended user, workflow and reason the proposed next step fits.
Evaluation path
The page, demo or trial route and the questions that need to be answered.
Activation map
The useful milestone, required events and product-team dependencies.
Cohort review
Continued usage, paid outcomes and feedback using a consistent starting group.
Before we start
Questions about the approach
How should I read this case study?
This is an illustrative composite scenario explaining a method. It is not a verified result for a single named client. Use it to understand the decisions and information the approach requires.
Does an upgrade prove the email caused the expansion?
No. Product usage and sales activity may also contribute. Use a suitable comparison where possible and state attribution limits.
Can the same approach work for our business?
The sequence may be useful, but it needs to fit your product, audience, systems and buying journey. We begin with the problem and the available evidence before proposing the scope.
What should we bring to the first conversation?
Your website, the target market and a short explanation of the obstacle are a useful start. Bring existing reports if available; access and any sensitive records can be discussed through the appropriate process.
