Turn happy customers into references, on purpose.
“Who among my customers has earned an ask for a reference, and how do I ask without burning them?”
Who to ask, the ask, the value exchange, and a pipeline of advocacy over time, without burning anyone out.
What this skill does
Turns your happiest customers into references, case studies, and referrals as a system, not a scramble the week before a launch. It finds who has earned enough goodwill to ask, matches each one to the right ask, sets a fair value exchange so it is not a favor, and runs the whole thing as a pipeline with stages, not a one-time beg. Advocacy is a program you build, not a mood you catch.
Inputs
- Works today with: what you can describe. Which accounts are happy, who the champions are, what results they have seen, and what you need (references, stories, referrals). Paste a list or describe your book.
- More powerful connected to a CRM: pulls account health, tenure, and value, so the ask goes to the right accounts.
- Sharper with a product-analytics tool: confirms a "happy" account is actually a deeply adopted one, not a quiet one.
- Sharper with a survey or feedback tool: adds satisfaction signals so you ask the people who already told you they are glad.
How it works
- 1Who to ask (earn the right)
Not every happy account is an advocate. Rank on three things: they are getting real results, the relationship has a named champion, and you have banked more goodwill than you are about to spend. Only then do you ask. Asking a shaky account for a public story is how you lose it.
- 2Match the ask to the relationship
Asks come in sizes. A quick review is light. A reference call is medium. A named case study is heavy. A referral is a favor with your reputation attached. Start light, earn the heavy ones. Do not open with the biggest ask on a new relationship.
- 3The value exchange
Advocacy is a trade, not a donation. Name what the customer gets: exposure to their market, access to your executives or roadmap, credits, a genuine thank-you that helps their own career. If you cannot name what they get, you are asking for a favor, and favors do not scale.
- 4The advocacy pipeline
Treat advocates like a pipeline with stages: Identified, Asked, Committed, Live, Nurtured. An advocate is not one-and-done. The customer who did a story this quarter is your reference next quarter, if you nurture them instead of disappearing.
- 5Cadence and no-burnout rule
Space the asks. The same three logos cannot carry your whole program, and over-asking a good advocate burns them out. Rotate. Keep a bench. One heavy ask per advocate per period, tracked.
Output format
ADVOCACY PIPELINE, one book
Need: 2 case studies, 3 reference calls, an intro to a similar buyer
Ready to ask
Account A champion strong, deeply adopted, renewed 2x
-> heavy ask: named case study. Exchange: conference speaking slot.
Account B champion strong, high survey score
-> medium ask: reference call. Exchange: early roadmap access.
Account C happy, newer relationship
-> light ask: a review. Exchange: a public thank-you + swag.
Not yet
Account D results good but no named champion. Build the relationship first.
Nurture
Account E did a story last quarter. Send the results it drove. Do not re-ask yet.
(Accounts and details are illustrative.)
Tips
- No ask to an account that is not both happy and stable. Verify the health signal first.
- The ask size matches the relationship strength. No heavy ask on a light relationship.
- Every ask names what the customer gets back. No naked favors.
- No advocate carries more than one heavy ask per period. Rotate the bench.
- "Happy" is backed by a real signal (renewal, adoption, survey), never a hunch.
Turn account data into a QBR that earns the renewal.
Value delivered, adoption vs stated goals, risks named first, the roadmap, and one outcome-tied expansion ask.
Build the plan that predicts the renewal a year out.
Translates the customer's goals into measurable outcomes, time-to-value milestones, and the leading indicators that flag risk early.