Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

B2B Marketing › B2B Demand

Customer References and Advocacy

How to run customer references and advocacy in B2B: a reference pool, matching references to deals, reviews and speakers, disclosure and reference fatigue.
Guideintermediate13 min readUpdated

Why business buyers ask for references

A consumer can read reviews and buy; if the product disappoints, the cost is theirs alone. A business buyer carries the decision into meetings with colleagues who will hold them to it. The buying committee wants evidence that the vendor delivered for an organisation like theirs, and the most persuasive evidence comes from a peer with nothing to sell. That is the job of social proof in business-to-business markets, and it is why requests for a reference call tend to arrive late in a deal, when the risk feels most personal.

Different roles look for different proof. A champion wants a peer who solved the same problem and can say what the first months were like. A finance approver wants outcomes in terms they recognise. An IT or security reviewer wants to speak to their counterpart at a customer about the implementation. Procurement may simply want a list of comparable customers. The sales content and training guide names references, reviews and case studies among the proof sales needs and explains what a good case study contains; the business-to-business content guide asks for customer outcomes with the customer's name on them. What neither covers is the programme that makes that proof available on demand without exhausting the customers who provide it.

When a reference cannot be found, deals wait. The diagnosis of a lengthening sales cycle lists reference customers by sector among the late-stage material whose absence stretches a cycle. A programme exists to make sure the right customer is available when the question arrives, rather than discovered after a week of asking around.

The reference pool and what each customer agreed to

The foundation is a record, kept in the CRM against the customer's account and the named contacts, of what each customer has agreed to do. Agreement is specific. A customer happy for their logo to appear on the website may not want to take calls; a champion who will speak to peers may need their communications team to approve anything published. Treating "a reference customer" as one category is how vendors end up using a logo without permission or sending a stranger to someone who only agreed to a quote.

FieldWhat it recordsWhy it matters
Customer and contactThe account and the named person who agreedAgreement belongs to a person, and people change jobs
Activities agreedLogo, quote, case study, reference call, review, speaking, advisory groupPrevents asking for something the customer never offered
Approved byWho on the customer's side approved, such as communications or legalMany organisations require internal sign-off before their name is used
Date of agreementWhen consent was given, and any expiry the customer setAgreements go stale as contacts and circumstances change
ProfileIndustry, size, use case, region, competitor replacedThe fields that make matching possible
Last asked and last usedDates and the opportunity each request servedEnforces the limit and shows who carries the load
Gifts, credits or discountsAnything given in returnNeeded for disclosure, as covered below
StatusActive, resting, withdrawnCustomers can step back at any time and the record must show it

Keep the agreement in writing, even if it is a short email the customer replies to. Review the pool on a regular rhythm the team sets, confirm that contacts are still in post and still willing, and remove anyone who has left or withdrawn. A pool that lists customers who agreed long ago and have since changed jobs is worse than none, because sellers stop trusting it. When the person who leaves was also the account's champion, the guide to a customer champion changing jobs covers closing their agreement, protecting the account they left and asking again at their new organisation.

Recruiting advocates at the right moment

The best time to ask a customer to speak for the product is soon after they have achieved something with it: a successful go-live, a measurable result, a renewal they chose gladly. Customer success managers and account managers see those moments first, so recruitment runs through them rather than through a marketing campaign. The expansion and renewal guide describes how marketing works with those teams after the sale; asking for advocacy belongs in the same working arrangement, with the account team deciding when to ask and marketing recording the answer.

Feedback programmes help to find candidates. The voice of the customer guide covers relationship surveys and open-text feedback; a customer who describes a clear result in their own words is a natural candidate for a case study, provided the account team agrees the timing. Customers at risk, those in a dispute and those whose renewal is uncertain are not asked, and a rising churn rate in a segment is a warning that its references may soon disappear too.

Advocacy is easier when it is reciprocal. The flywheel framework describes a business where satisfied customers do part of the marketing; the programme keeps that momentum by giving advocates something of value in return that is not payment: early access to new features, a voice in product decisions, introductions to peers, visibility for their own work. A customer who gains standing among peers from speaking at an event is more willing to do it again than one who was simply asked a favour. Where early access is offered through a formal programme, the tutorial on running a beta or early-access programme covers choosing participants, the terms they agree to and collecting their quotes with that access disclosed.

Matching a reference to a deal without wearing customers out

A buyer wants the reference closest to their situation. The sales content guide makes the point for case studies: they need to be findable by industry, company size, use case and competitor replaced, and the same fields drive reference matching. A seller requests a reference through one route, states the opportunity, the stage and the question the buyer wants answered, and the programme owner proposes the best match from the pool. In an account-based marketing programme, the same fields let the team line up a likely reference for each named target account before anyone asks for one.

One owner and one route matter more than any tool. When every seller asks customers directly, the most helpful customers receive the most requests, nobody sees the total, and a valued customer can be asked by several sellers in the same month. The owner sees every request, checks the customer's record, asks the account team before contacting the customer, and briefs the customer on who will call and what they want to know.

Set a limit per customer per period as a team, and write it into what the customer agreed to. No outside figure fits every business, so the limit comes from the size of the pool, the length of a typical call and what customers say they are comfortable with. When a deal needs a reference that would breach the limit, the answer is to find another customer, offer a case study or a recorded interview instead, or recruit a new advocate in that segment. Reserve calls for deals where the buyer has asked for one and the opportunity is real, and thank the customer afterwards with a note on how the deal went, whatever the outcome.

Case studies, reviews, speakers and advisory groups

Reference calls are one form of advocacy among several, and each has its own way of running.

Case studies for business buyers. A case study for a committee should speak to more than the champion. Interview people in several roles at the customer where they are willing: the champion on the problem and the decision, a user on daily work, someone in finance or operations on the outcome, and IT on the implementation. Expect approval by the customer's own communications or legal team, and allow time for it. Tag each finished study by industry, size, use case and competitor replaced so sellers can find it. The craft of planning, interviewing and writing a single case study is the subject of the tutorial on writing a customer case study; the sales content guide covers what a good one contains. Announcing a contract or partnership with a customer to the press is a further use that needs its own agreement, and the guide to making a joint announcement with a partner covers naming the customer, a quote from each side and who answers journalists.

Reviews on software review sites. Buyers read independent reviews when they shortlist. When asking customers for reviews, ask every customer or a fair sample rather than only those expected to be positive, never make anything given in return depend on what the review says, and disclose any incentive, as covered below. The store reviews and social proof guide covers review collection for consumer purchases, and its points about selective asking and incentives apply to business reviews too.

Customer speakers. A customer presenting at an event, in a webinar or in an article carries more weight than any vendor slide. Brief them, offer help with the material, and let them say what they think, including what did not go well.

Advisory groups. A small group of customers who meet periodically to discuss the roadmap and the market is a source of product and messaging input first. It is not a sales event, and members who feel they are being sold to stop attending. The roundtables and customer events guide covers hosting those meetings, and the guide to running a customer advisory board sets one up as a standing programme with a charter, a member mix and a way of reporting back what changed.

Recognition throughout should come through thanks, access and visibility rather than payment. Paying for advocacy changes what the advocate is saying and how readers should weigh it.

Disclosure, incentives and honest claims

This section is educational, not legal advice. The rules vary by country and change over time, and the sources listed on this page are the authority.

A testimonial, a published quote, a review and a reference call are all forms of endorsement. As the SaaS industry guide and the professional services industry guide summarise from the FTC's endorsement guidance, endorsements must reflect the endorser's genuine experience, and a material connection between the endorser and the business, such as a payment, a gift or an incentive, should be disclosed clearly. A discount or credit given in exchange for a case study, a reference or a review is that kind of connection, which matters because the pricing and packaging guide lists a case study among the things a discount can be traded for. Record every such exchange in the reference pool so the disclosure can travel with the content, and give customers plain wording to use when they post a review. The referral programme guide makes the same disclosure point for customers who are rewarded for recommendations.

Claims need the same care. In the UK, the advertising codes administered by the Advertising Standards Authority require marketing claims to be substantiated and not misleading, as the SaaS guide states for comparison claims. A figure in a customer's quote becomes a claim the business makes once the business publishes it, so keep the evidence behind every outcome a case study states, publish results only in the words and figures the customer approved, and never edit a quote in a way that changes its meaning. The trust and proof guide covers permission records and honest sourcing for testimonials on a page; the same rules apply when a seller pastes the quote into a proposal.

Tracking references in the pipeline

Record each reference request against the opportunity it served: the customer, the type of advocacy, the date, the stage the deal was at and, once the deal closes, the outcome. Two readings follow.

The first is reference use per opportunity: how many deals asked for references, at which stages, and how those deals ended. Read it as association, not cause. Deals that ask for references are often larger, later or more competitive than deals that do not, so comparing their win rate with the rest says little about what the reference did. The useful questions are narrower: did deals wait for a reference, and did any lose because none was available?

The second is reference health: which customers are carrying most of the load, which are resting, which segments, sizes, use cases or competitors have no reference at all, and how many agreements are out of date. The gaps become a recruiting plan for the account teams, and overused customers are rested before they say no.

MeasureWhat it showsHow to act on it
Requests by stage and outcomeWhere in deals references are asked forPrepare proof for the stage before buyers ask
Requests unfilled or delayedDeals that waited or went withoutRecruit in the missing segments
Load per customerWho is asked most oftenRest overused customers; widen the pool
Coverage by segment and competitorWhere the pool has gapsSet recruiting targets with account teams
Agreements past reviewRecords that may be staleReconfirm or remove

An HR software firm's reference programme (illustrative)

Illustrative example — not a real result

Trellisbyte HR finds out who has been taking its calls

Trellisbyte HR is an invented company selling HR and payroll software to mid-sized employers. It has 160 customers, and until this year its sellers arranged references themselves, usually by messaging a customer they knew. The marketing manager builds a reference pool from the customer success team's notes and a short email to every customer contact the account managers judge to be in good standing. Thirty-four customers agree to something: 31 to a logo, 18 to a quote, 12 to a case study and 15 to reference calls. Each entry records what was agreed, who approved it at the customer and the date.

Reconstructing the previous twelve months from sellers' emails, the manager finds 47 reference calls, of which 29 were taken by four customers. One of them, a logistics firm, had taken 11 calls and told its account manager it was considering declining all future requests. Meanwhile the pool has nobody in retail or hospitality, two sectors where sellers had opened 14 opportunities in the year.

Trellisbyte routes every request through the marketing manager, sets a limit of two calls per customer per quarter, and rests the four busiest customers for a quarter. Customer success recruits three new advocates in retail and hospitality within two months, and one becomes a case study interviewed across its HR director, payroll lead and IT manager, approved by the customer's communications team. Two customers who received a renewal credit for case studies have the arrangement noted in the pool, and the published studies say so. The team records every request against its opportunity and reads the results each quarter as a check on coverage, not as proof that references win deals.

Common mistakes

  • Running references from memory. Without a pool, the same few customers carry every call and nobody sees the load until one of them says no.
  • Treating agreement as all or nothing. A customer who agreed to a logo has not agreed to take calls or publish a case study.
  • Letting every seller ask directly. One route and one owner are what make limits possible.
  • Asking at the wrong moment. A customer in a dispute or an uncertain renewal is not an advocate yet.
  • Asking only happy customers for reviews. Ask every customer or a fair sample, and never tie a reward to what the review says.
  • Hiding what was given in return. A discount, credit or gift exchanged for a case study, reference or review is a material connection to disclose.
  • Publishing claims nobody can support. Keep the evidence behind every outcome a customer story states.
  • Reading reference use as cause. Deals that ask for references differ from those that do not; read the numbers as association and use them to find gaps.

Frequently asked questions

How often can we ask the same customer to take a reference call?

There is no figure that fits every business, and this site does not give one. Set a limit per customer per period as a team, agree it with the customer when they join the pool, and record every request against their entry so the limit can be enforced. Customers who are busy, newly promoted or in the middle of a renewal may want fewer requests than the limit allows, so ask them rather than assuming.

Can we give customers a discount in exchange for a case study or a review?

Many vendors do, and the exchange creates what the FTC's endorsement guidance calls a material connection between the customer and the business. As the site's SaaS and professional services guides summarise that guidance, such a connection should be disclosed clearly, and testimonials and reviews must still reflect the customer's genuine experience. Record any exchange in the reference pool so the disclosure can travel with the content. This is educational, not legal advice; check the rules for each market with whoever handles compliance.

Should we ask only our happiest customers to write reviews?

For reviews, no. Asking only the customers expected to be positive gives buyers a distorted picture, and the site's professional services guide notes, from the FTC's endorsement guidance, that a firm should not ask only the clients it expects to be positive. Ask every customer, or a fair sample chosen without regard to how they feel. Reference calls are different: a reference is a customer who has agreed to speak for the product, and choosing a satisfied, relevant one is the point.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. FTC Endorsement Guides: What People Are Asking — Federal Trade Commission
  2. Advertising Standards Authority — ASA

Related