When I follow a stalled B2B SaaS marketing program back to its constraint, I usually arrive at the same place: a shortage of customers willing to say on the record what the product did for them. The fix is a customer reference program: a standing system that finds customers willing to speak, gets their participation approved before anyone needs it, and spreads the requests so no account is worn out.
It shows up as four separate problems, which is why, in my experience, it rarely gets diagnosed as one.
The press program can't place proof stories because reporters want a named user. The analyst program comes up short at the point where analysts check with your customers. The review profile is stale because nobody asks systematically. And sales keeps requesting references for the same three accounts until those accounts stop answering.
Four teams, four complaints, one missing asset.
Key takeaways
- Forrester asks every vendor in a Wave evaluation for reference customers and interviews or surveys them; in evaluations that started on or after July 1, 2024, customer feedback replaced market presence on the Wave graphic.
- Gartner's Magic Quadrant FAQ, published in 2021, says its analysts won't ask vendors for customer reference names, except mainly for one-time surveys when Gartner expands into new markets, and points vendors to Peer Insights reviews instead.
- A standard logo-rights clause, such as the one in Common Paper's cloud service agreement, lets a vendor identify the customer by name and logo; have your legal team check what a quote, a case study or an interview would need.
Why are customer references so hard to get?
Getting a customer to go on record is genuinely hard, and most of the difficulty sits on the customer's side.
Their legal team may need to approve it. Their communications team has views about which vendors they're associated with. The individual who loves your product may not be senior enough to authorize it, and the person who is may not care. Security-conscious buyers often have policies against confirming what's in their stack. And the person who championed you internally changes jobs, taking the relationship with them.
Often the contract settled the question before anyone asked. Software agreements can grant publicity rights or restrict public announcements, and in my experience enterprise customers often negotiate those terms. Common Paper's free standard cloud service agreement, for example, lets the vendor list the customer's name and logo by default, notes that some customers remove that right, and offers replacement language barring either side from announcing the deal without written approval. A logo-rights clause like Common Paper's covers identifying them as a customer. Before you ask the customer, ask your legal team what your own agreement permits and which further approvals a quote, a case study or an interview would need.
I've seen it more than once: the technology is phenomenal, but the customer is a Fortune 500 company that won't sign off on a case study. In a competitive space there's also the Moneyball problem. A team that's winning with something has no reason to help a rival by talking about it. What works is getting language into the contract before the deal starts, saying that if things go well they'll give quotes and talk to media, because asking afterward is almost always a no.
None of that is solved by asking harder. It's solved by starting earlier and treating it as a program.
The reframe that works
A reference request works better as an offer than as an extraction: something the customer gets value from.
The customers who say yes are usually the ones who get something out of it: visibility for their own team's work, a speaking slot, a case study they can use internally to justify the purchase, recognition in front of their peers. A practitioner who solved a hard problem with your product often wants credit for solving it.
The ask that works isn't "will you be in our marketing." It's closer to "would you be interested in talking about what your team built."
In my experience, that distinction does more for the yes rate than any process improvement.
How do you build a customer reference program?
A customer reference program starts at onboarding, tracks each customer through approval stages, offers several levels of participation, and spreads the requests so no single account carries them.
Start at onboarding, not at need. The moment to identify a future reference is when someone is delighted, which is usually early and rarely when your press program needs them. Flag them then.
Track it as a pipeline with stages. Identified, willing, internally approved, legally cleared, actively available. Many of the companies I see have a spreadsheet of names with no idea which stage each is at, and discover the clearance problem the week a reporter asks.
Get the approval before you need it. Legal review can take weeks. Doing it under deadline is how opportunities get missed.
Give people tiers of participation. Not everyone will do a press interview. Some will do a quoted case study, some a review, some an anonymous metric, some a private reference call. In my experience a tiered ask gets more yeses than a binary one, and a customer who says yes to something small often says yes to more later. Ask again before you expand what they've agreed to.
Rotate deliberately. Reference fatigue is real and it burns your best relationships. Track how often each account is asked and protect the ones doing the most.
Follow the champion when they leave. Your advocate moving to a new company is a lost reference and a warm lead simultaneously. Most companies I've seen handle it as neither.
What does one reference customer unlock?
One customer relationship can support a press interview, an analyst reference, a conference talk, a written case study, a review, and a sales reference. Record which of them the customer and their employer have actually approved.
Launch coverage shows it plainly. When Campaign Monitor announced its 1-to-1 Email Marketing product at the end of October 2017, a launch we ran, MediaPost's write-up featured a named customer, Flight Centre, with its results and a quote from its email marketing manager. Arrange that kind of participation early, so the customer's approval doesn't hold up a launch interview.
I plan partnership news the same way. In my experience an announcement gets one story. A second needs results, so we go back once there's something to report, such as what was built and who it helped, and brief the reporter with the company and the customer on the same call. That call needs a customer who has already said yes.
We've watched this play out across a decade-long client program. Its best year for coverage wasn't driven by its biggest announcement. When we audited that year afterward, the three things we found missing were customers willing to talk, more than one spokesperson, and proprietary data to publish, and those were precisely the gaps limiting everything else.
The pattern generalizes. In my experience, programs that look like they have a communications problem often have a customer-reference problem wearing a communications costume.
Do analysts still call customer references?
Forrester still interviews reference customers for its Wave evaluations, but Gartner mostly stopped asking vendors for them for its Magic Quadrants. Forrester asks every vendor in a Wave evaluation for reference customers and its analysts interview or survey them; in evaluations that started on or after July 1, 2024, customer feedback replaced market presence on the Wave graphic, and vendors with strong feedback get a more prominent marker. Forrester also says it doesn't name reference customers in the report unless that's agreed in advance. Gartner no longer asks vendors for customer reference names for its Magic Quadrants, outside a one-time survey when it opens a new market, and points vendors to its Peer Insights reviews instead. Those reviews show the reviewer's role, industry and company size, not their name or employer.
That's the tier system working in your favor. A customer whose employer won't let you name them publicly may still be able to take a private analyst reference call or write a Peer Insights review, which Gartner verifies but publishes without the reviewer's name or employer. They still need whatever approval their employer requires for that. In my experience it's a smaller ask, and it gets a yes more often.
Where to start
Pick three customers you believe are genuinely happy. Ask them what their team accomplished, not whether they'll be in your marketing. Find out what would make participating worthwhile for them. Then start the approval process before you have a use for it.
It's the least glamorous item on any marketing plan, and in my view it's the one that most limits what the rest of the plan can achieve.
Common questions
What is a customer reference program? A standing system for finding customers willing to vouch for your product, getting their participation approved by their employer in advance, and matching each request to the right customer without overusing anyone. The requests range from sales reference calls and reviews to case studies, conference talks, press interviews and analyst evaluations.
What is customer marketing? Marketing to existing customers to support adoption, retention, expansion and advocacy. Case studies, references, reviews, speaking opportunities and press participation are its advocacy side. Where it sits varies by company, between marketing and customer success.
How do you get customers to agree to a case study? Lead with what they get, such as recognition for their team's work, visibility and material they can use internally, rather than with what you need. Start the conversation when they're happiest, usually shortly after a successful implementation.
Why do customers say no? Usually for reasons on their side: legal review, a publicity clause in the contract, communications policy, security posture, or the enthusiastic user lacking authority to approve. Starting early and offering smaller forms of participation helps with much of it, but some customers will stay unavailable whatever you offer.
How many customer references does a B2B SaaS company need? Enough to rotate. Asking the same few customers again and again can cause reference fatigue and leave you without an available reference when you need one. A working program keeps several accounts cleared at different participation levels.
What's the connection between customer references and PR? Close, in my view. Reporters want a named user, Forrester interviews or surveys reference customers for its Wave evaluations, Gartner may use Peer Insights reviews as one of many inputs, and review sites run on customer voice. Each asks something different of the customer, and all of them start with customers willing to take part.
Sources
- Forrester, The Forrester Wave Methodology, accessed November 8, 2026
- Gartner, Gartner Magic Quadrant: Frequently Asked Questions, 2021
- Gartner, What Is Peer Insights?, Gartner Peer Insights vendor resources, accessed November 8, 2026
- Gartner, FAQ: Gartner Peer Insights, accessed November 8, 2026
- Common Paper, Cloud Service Agreement, Version 3.0, accessed November 8, 2026
- Common Paper, Remove Logo Rights, accessed November 8, 2026
- Jess Nelson, Campaign Monitor Launches 1-1 Email Marketing, MediaPost, November 1, 2017
Salient PR builds customer advocacy and reference programs alongside earned media for B2B SaaS and enterprise technology companies.
About Salient PR
Salient is a B2B tech PR agency. We help startups become the story — landing tier-one coverage, building executive visibility, and turning attention into pipeline.
Senior team. No hand-offs. Radical transparency. If you’re ready to talk, reach out.
