Your happiest customers are your cheapest growth: proof, referrals, and expansion revenue, captured on a system instead of luck.
A customer succeeds, everyone celebrates, and the relationship goes quiet until the next purchase order or the next problem. No case study, no referral ask, no structured look at what else they could buy. The easiest revenue in the company is left to chance.
Your happiest customers are your cheapest growth: proof, referrals, and expansion revenue, captured on a system instead of luck. Built once, documented in your standard work, and run by your own team week after week.
Selling more to people who already trust you is the highest-margin motion in business, and almost nobody systematizes it. This playbook installs the loop: check-in cadences that surface expansion early, proof capture wired to project milestones, referral plays that feel natural, and customer language fed back into your positioning.
At any given time roughly 95% of your category's buyers are not in market. Your customers are the one audience you can stay close to between purchases, so when the trigger event hits, you are already in the room.
of a B2B buying group's total buying time is spent meeting with potential suppliers. A standing quarterly check-in is time in the room competitors cannot buy, earned by never turning it into a pitch.
An installed base left in silence does not hold still. Every quarter the loop is missing, the same five things quietly happen.
The Proximity Audit dates the silence across your top accounts and counts what it is leaving on the table. That is the point of starting there.
An install only sticks when it has owners. Here is who this playbook belongs to inside your company, and what each of them walks away with.
The owner or GM who wants growth without buying more cold pipeline.
OutcomeExpansion revenue at the lowest acquisition cost in the building.
Your marketing lead, who designs the cadence, the triggers, and the digest.
OutcomeA quarterly feed of verbatim customer language and fresh proof for every campaign.
The account owners and service managers who hold the check-ins.
OutcomeWarmer accounts, and openings surfaced before an RFP exists.
The keeper of your positioning source document, who reads and answers the digest.
OutcomeA message that stays current because the field keeps correcting it.
An illustrative composite drawn from real engagement patterns. Company details invented; the shape of the change is the point.
Loop design, triggers, and interview guides.
Customer conversations and capture.
Case studies captured, referrals generated, expansion revenue.
Expansion fails when the only post-sale contact is an invoice. Each week installs the part of the loop the next part depends on, so the sequence is fixed and the scope is too.
Every key account scored on health, headroom, and proof, with evidence; the post-sale silence dated; tiers set.
Why firstYou cannot run a loop on accounts you cannot see. The map decides who gets check-ins, asks, and rescues, in what order.
The quarterly value check-in that is not a sales call: six blocks, one rule, named runners, and a verbatim log.
Why before any askEvery later move rides on conversations the customer is glad to take. The check-in rebuilds the trust each ask spends.
Five project milestones wired to capture asks, scripts in the asker's voice, every capture routed to one register.
Why nowResults are most quotable while they are fresh. Triggers make the ask automatic instead of remembered.
The peer introduction, guest the customer, the reference bank, and the one-paragraph forwardable.
Why nowReferral asks land when the relationship is warm and the proof is fresh: exactly what the last two weeks built.
The expansion lens finds where the problem lives next; one-pagers built from each account's own results.
Why nowThe strongest argument an account can hear is its own numbers. The lens turns logged openings into specific small moves.
The quarterly voice-of-customer digest, verbatim, routed to the positioning owner with a reply loop; the Expansion Loop Manual assembled and owned.
Why lastThe loop ends where your message begins: field language flows back into the position, and the system gets a named owner.
Check-ins held, captures landed, referrals received, expansion conversations opened, all against the Week 1 baseline.
Why it mattersThe first counted cycle makes the loop visible, and tees up the annual audit that starts the next one.
Every week compiles into the Expansion Loop Manual: the named product your team owns, reruns, and defends long after the install ends.
This playbook lives in System 05: Expand, the part of the method that answers one question: Where does revenue actually happen? Most companies install it alongside one or two related playbooks in a 90-Day Install.
Share this page with your leadership team. If it names your problem, the Proximity Audit will tell you whether this playbook should be your first install or your third.
Installed on one product line first, then yours to rerun across every line you own. Not sure it's the right first move? Start with the Proximity Audit ($7,500, credited toward an install): all fifteen areas scored and a ranked roadmap.
Book a Proximity Audit Ask about this playbook →