● Customer Success · Model · v1.2
The Customer Journey
The story of how a company delights its customers, written as forty-two moments — each with the signal that starts it, the outcome that ends it, the one team that owns it, and the milestone it touches. The manual, and the workbook that is the map.
Why it matters
The Operating Model says how a Customer Success organization is built. This model says what it does to a customer, in order: every step from the first lead to the renewal, written down with the signal that starts it, the outcome that ends it, and the one team that owns it. It is the spine the plays hang from — every play on this shelf is a moment on the map, and every moment touches one of the Operating Model’s twelve milestones. It rests on one claim: finis origine pendet, the ending depends upon the beginning. Churn is baked in during Hypercare, the ninety days after onboarding, and a customer lost inside the payback period never paid for themselves.
What’s inside
A journey starts with a vision. The company’s vision, the customer’s vision inherited, and Customer Success as the steward of the journey; the engagement model and the operating framework as the two halves of one journey.
Why map it. Three causes of churn, all controllable; where churn is baked in; the legacy model against the engagement model; what a lost customer costs, read as payback.
Four stages. Acquisition, Onboarding, Adoption, Expansion — a definition each, and Success’s principles inside it; early and ongoing adoption; the challenge lanes; the channel-partner variant.
The moment, and the two vocabularies. The story, the signal, the outcome, the codes, and the milestone it touches. One owner per moment; any number held to account for a defined part of it; four rules for writing them. The twelve milestones are what the organization does; the moments are what the customer experiences.
The map on one page. All forty-two moments, each with its milestone, the two gates and the four plays in place.
Onboarding, adoption, the lanes and expansion. The success plan and the trainers; the Value Workshop at thirty days and graduation at ninety; seven challenge lanes and exactly when Success is pulled in; renewal nurture on a trigger, not a date; offboarding; five traits of a successful partnership.
Who does what, and building your map. The counts by function; ninety days from a blank workbook to a map every team has agreed to; the checklist.
How to use it
Read the manual once. Open the workbook and rewrite the Map tab for your company: delete what you don’t run, add what you do, and give every row exactly one owner and the milestone it touches. Check the Milestones tab: none of the twelve should be left untouched. Walk the map with each function, one column at a time. Set renewal lead times by tier on the Settings tab. Load every account into the Tracker with its go-live and renewal dates, and review the overdue gates every Monday.
Provenance
Built three times: in 2017 as Senior Director of Customer Success at a hospitality-software company in the Vista Equity portfolio — forty-nine moments across eight functions; in 2018 as Vice President of Customer Success at a managed file transfer and network management software company; and in 2019 as Vice President of Customer Success at a financial services software company, where the 2018 map carried over almost whole. Merged and rewritten here as a Juan.co model: forty-two generic moments, each mapped to the Operating Model’s twelve milestones, every product-specific step generalized away, renewal nurture made trigger-based, and the workbook built with an owner check and a per-account tracker.