For B2B marketing and sales teams
Build a customer reference program that does not wear out your best customers
Every enterprise deal asks for a reference, and the same three happy customers get every call. Set up a program with the checklist below, keep track of who has been asked and for what in StoryProof, and give sales recorded stories so live calls are saved for the deals that need them.
- A setup checklist for the whole program
- Rules that stop advocates being overused
- A tag scheme to track every request
The problem, solved
How reference programs break down, and how StoryProof shores them up
The same three names
Sales asks whoever said yes last time. Your most generous customers get the most calls and eventually stop answering.
With StoryProof: Capture each advocate once on video, in an audio note or in writing, then point early-stage prospects to your Wall of Love so a live call is kept for late-stage deals.
Nobody knows what was agreed
One customer agreed to a quote on the website, not a call with a competitor’s customer. Without a record, someone will ask for the wrong thing.
With StoryProof: Store the agreed scope as a tag on that customer’s approved story, so any rep checking the library sees the limits before they reach out.
Our reference stories are years old
A reference from three years and two product versions ago can hurt a deal more than help it.
With StoryProof: Send the advocate a fresh collection request after a major release. The new version lands in your approval queue, and nothing from it is public until you sign it off.
The champion moves on
The person who agreed to be a reference changes job, and the next sales rep calls a successor who has never heard of the arrangement.
With StoryProof: Switch their status tag to retired the day you hear, and remove their story from whichever widgets carried it, since you pick each widget’s testimonials yourself.
Flip the switch to see how StoryProof handles each one.
Checklist
Set up your reference program
Work through this once to set the program up, then revisit the last group every quarter.
Runs in your browser. Nothing is saved.
A tag scheme for the reference pool
Tags on each approved story let anyone see who is available, for what, and how recently they were asked.
In StoryProof
Run the program in StoryProof
- You will need
- Your list of willing references
- A StoryProof workspace with seats for marketing and sales
- 1
Record a story from each reference first
Send each reference a collection link. A recorded video or written story answers most prospect questions without a call.
- 2
Approve and tag with the scheme above
Every story waits for approval. Tag it with scope, segment, role and status so sales can find the right one.
- 3
Give sales access to the library
Add your sales team to the workspace so they can find approved stories themselves. Brand spaces per account: Free 1, Starter 1, Pro 3, Agency 15. Seats per space: Free 1, Starter 3, Pro 5, Agency 10.
- 4
Share a Wall of Love link in deals
For early-stage prospects, a Wall of Love link shows every approved story on one page, with no call booked.
- 5
Thank people automatically
On a plan with automations, StoryProof can email a thank-you with a link to the published story after it is approved.
What happens next: Update the last-used and status tags after every live call, so the next request goes to someone who is rested.
Before you start
What StoryProof does not do here
It does not book reference calls
Live calls are arranged by your program owner. StoryProof holds the stories and the tags that show who is available.
Tags are kept up to date by people
Nothing updates a last-used tag on its own. Make updating it part of closing every reference request.
Your CRM may still be the system of record
If deals and contacts live in a CRM, keep the request log there too and use StoryProof for the stories themselves.
Incentives need care
Gifts or discounts for references can colour what a prospect hears, and some customers’ employers forbid accepting them. Check the customer’s policy, and tell prospects if a reference was rewarded.
FAQ
Questions people ask
Short answers to what usually comes up next.
How often can we ask a reference customer for a call?
Agree a limit with each customer, often one or two calls a quarter, and track it. Offering a recorded story first keeps the number of live calls down.
Who should own the reference program?
One person, usually in customer marketing, so sales has a single place to ask and customers are not contacted by several people.
How many references does a program need to start?
Enough to cover each main segment you sell into at least once, so no single customer carries every deal in that segment. Start small and recruit where the tag scheme shows gaps.
Should a reference customer know which prospect they are speaking to?
Yes. Tell them the prospect’s company, role and what the prospect wants to hear about before the call, and give them the chance to decline, especially if the prospect is a competitor of theirs.
What if a reference says something negative on a live call?
Treat it as useful feedback rather than a breach. Ask the reference what changed, fix the issue if you can, and rest them from calls until the account is healthy again.
Still have a question? Ask the StoryProof team or book a demo.
Give sales stories, and give your advocates a rest
Record a story from each reference once, tag it, and let sales find it themselves.
Last updated 2026-11-04.