At a glance
A customer advocacy programme should give customers several ways to contribute, make permissions specific and track participation so the same advocates are not overused. Useful stories answer real buyer questions without overstating influence.
Customer advocacy programmes can quickly overuse their most generous participants. A customer who has already joined a webinar, taken reference calls and approved a case study may still be asked to appear on another panel, even when the next request adds little value for them.
A durable programme treats advocacy as a relationship, not an asset-production target. It gives customers practical choices, protects consent and time, and focuses every request on evidence another buyer can actually use.
Offer a choice of ways to contribute
Some customers enjoy speaking publicly. Others are happy to take a private reference call but cannot discuss results on a website. Some want to share operational lessons rather than promote a supplier.
Build a range of options: a short written contribution, a peer discussion, a recorded interview, a reference conversation or a more detailed case study. Explain the time involved, the audience and the approval process.
TrustRadius’s 2026 B2B buying research found that easier access to peers with product experience was a change buyers wanted in the purchasing process. That supports the value of credible customer perspectives, but it does not mean every customer should become a sales reference.
Ask at a sensible moment
Work with the account team to understand the relationship. A recent successful milestone can create a good opportunity. An unresolved support issue or difficult renewal usually calls for service, not a publicity request.
Explain why this person’s experience is relevant. “We would like to share how your team handled regional rollout” is more considerate than “We need a customer logo for a campaign”.
Keep participation separate from the standard of service the customer receives. Saying no should be easy and should not create awkwardness in the commercial relationship.
Make the story useful to another buyer
A strong customer story explains the starting situation, the decision, the work involved and what changed. Include trade-offs and conditions. A polished quote about a seamless transformation often tells a prospective buyer very little.
If the story includes numbers, establish the source, period and calculation. Distinguish a customer’s estimate from a measured result. Do not imply that another buyer should expect the same outcome.
For a technology implementation, explain what the customer contributed: data preparation, training, process changes and internal ownership. That makes the story more credible and helps future customers prepare.
Keep permission specific
Agree which name, logo, quotes, images and results may be used, in which channels and for how long. Give the customer a clear review process and record the approved version.
A private reference call does not imply permission to quote the conversation in an advertisement. A case study approval does not automatically cover a new claim assembled from old material.
Make withdrawal or correction requests easy to route. Public customer information deserves the same maintenance discipline as product information.
Track the relationship, not just the asset count
Keep a shared record of requests, participation and preferences so different teams do not repeatedly approach the same person. Watch whether the programme depends on a handful of generous customers.
Recognise the contribution in a way that suits the participant and any relevant employer policies. That might mean professional visibility, useful peer connections or simply a well-run experience that respects their time.
Use clean CRM records to keep these preferences accurate. For account-based work, connect the request to the accounts and buying situations where the experience is genuinely relevant.
Measure whether the evidence helps
Ask sales which stories answer real buyer questions. Ask participants whether the process was worthwhile. Track use and influence carefully without assuming every deal that encountered a case study was caused by it.
A good advocacy programme leaves customers feeling respected and buyers feeling better informed. If it produces a large asset library by exhausting the same few people, it needs a different operating model.
