AM Marketing Group Inc.
Customer Lifecycle
& Expansion
Playbook
Carry the promise from the sale into customer value, renewal confidence, and relevant opportunities to grow.
01 / Find the disconnect
What did the customer buy, and what did users receive?
A signed agreement does not mean the team using the solution understands the promise or is ready to implement it. Compare the buying conversation with onboarding and actual use. Identify the intended outcome, success measure, commitments, limits, users, and implementation owner.
Value question
What customer outcome should improve, and what observable event would demonstrate progress?
Ownership question
Who is accountable on the customer side and on your team for removing obstacles and reviewing the outcome?
Start with one ICP segment and a defined customer cohort. Compare similar use cases and time since onboarding. A new account and a mature account should not be judged against the same adoption window.
Review the benefit the customer actually received.
Build onboarding, renewal, and expansion messages around the outcome the customer wanted and the improvement they experienced. Usage and delivered assets are evidence to interpret. Ask what became easier, faster, more reliable, or more valuable for the customer and which buying role cares about that change.
Message test: “Your team used 12 reports” records activity. “Your managers used the reports to identify the blocked handoffs before the customer review” explains a benefit, when customer evidence confirms it. Tie any savings or performance figure to a documented baseline and comparison.
From benefit to prescribed solution: Confirm the customer’s problem and baseline, connect the relevant capability to the desired improvement, and support the claim with a dated source, comparable context, measured result, and limits. Recommend a specific scope, then agree on the success measure, owner, and next evaluation step. Keep the customer’s evidence distinct from external benchmarks and illustrative scenarios.
02 / Map the journey
Design each stage around a customer decision.
| Stage | Customer question | Action and signal |
|---|---|---|
| Promise | What will change, and what are we committing to? | Record the agreed use case, buyer/KDM expectations, users, success criteria, and limits. |
| First value | Can we achieve an initial useful outcome? | Resolve setup and access, support the core task, and record time to first value. |
| Adoption | Is this useful enough to repeat? | Measure the intended workflow and outcomes; investigate friction and uneven participation. |
| Renewal | Does the continuing value justify the commitment? | Review value with users and the renewal owner; confirm approval process, budget path, risks, and dates. |
| Expansion | Is there another valuable problem this offer can solve? | Validate additional need and fit, delivery capacity, role-specific value, and an agreed evaluation path. |
03 / Differentiate the roles
Users, renewal owners, and approvers need different evidence.
| Role | What matters | Useful communication |
|---|---|---|
| User / practitioner | Daily usefulness, quality, confidence, and support. | Task guidance, office hours, examples, and a direct route for reporting friction. |
| Buyer / renewal owner | Account performance, issue resolution, coordination, and contract process. | A clear outcome review, open action plan, responsibilities, and renewal timeline. |
| KDM / budget approver | Business value, risk, alternatives, and future investment. | A concise evidence-based business review with full costs, limitations, and a specific decision. |
| Champion / implementation owner | Internal credibility and the ability to make the program succeed. | Shareable proof, a realistic success plan, and support for stakeholder alignment. |
Reconfirm roles when people leave or responsibilities change. A satisfied user may influence renewal without controlling it. A supportive approver may not see adoption friction. Keep both views in the account plan.
04 / Use signals carefully
Separate a risk hypothesis from a confirmed problem.
| Observed signal | What to investigate | Appropriate next action |
|---|---|---|
| Expected workflow is not happening | Access, training, use-case fit, timing, or product quality. | Ask users about the blocked task and assign a resolution owner. |
| Champion leaves or the account goes quiet | New ownership, changing priorities, and unknown decision authority. | Rebuild the stakeholder map and confirm the success plan. |
| Usage or outcomes improve | Whether the intended benefit is real and valuable to the customer. | Validate the outcome with the customer and document approved evidence. |
| Another team asks about the offer | A genuine additional use case, capacity, funding, and buying path. | Explore the need with that team before proposing an expansion. |
A health score is a prompt for investigation. Confirm the customer’s situation before assigning risk or expansion intent. Review account history and individual usage in context; low activity can be normal for infrequent tasks.
05 / Worked example
Validate value before pitching expansion.
Illustrative example, not a client result: A customer’s managers use a reporting product every month, but the executive sponsor says its value is unclear. A second business unit has shown interest.
- Ask users which decisions the reports improve and which tasks remain difficult.
- Give the renewal owner an outcome review and an action plan for unresolved issues.
- Give the KDM evidence tied to the original business objective, with assumptions and limits explicit.
- Validate the second unit’s workflow, users, implementation capacity, and approval path separately.
- Propose an expansion only if the additional need and delivery fit are confirmed.
Public experience reference: AMG’s published McGraw Hill case discusses customer re-engagement and product-led upsell work. The reporting-product scenario above is a separate fictional example. McGraw Hill case study.
06 / Your customer growth canvas
Create one shared account plan.
These fields are for your working notes. They are not submitted to AMG or permanently saved by this page. Copy your answers before leaving or refreshing.
07 / Measure the right movement
Keep retention and expansion visible separately.
- Track eligible accounts reaching first value and median time to that milestone.
- Track repeated workflow use and customer-confirmed outcomes over an appropriate period.
- Calculate customer retention with a defined starting cohort. Record churn reasons and open recovery actions.
- For recurring revenue, separate contraction, churn, and expansion. Gross revenue retention excludes expansion; net revenue retention includes it. Both use a consistent opening cohort and time period.
- Treat expansion as a distinct qualified opportunity. Record its new use case, stakeholders, evidence, and decision path.
Continue the work.
Choose the resource that supports your next decision.
Is the problem starting before onboarding?
Review what the launch promised and the first value customers expected to receive.
Product Launch & Adoption →Recommended next: test whether fit holds within each segment.
Use retention, payment and customer outcomes to refine the market you choose to pursue.
Market Opportunity & Product-Market Fit →Found an expansion opportunity?
Coordinate the buying group, evidence and next commitment within the account.
ABM Account-to-Revenue →Connect your customer promise to the next stage of growth.
AMG connects positioning, lifecycle messaging, adoption support, and revenue coordination across the customer relationship.
Discuss your customer growth priorities →