The favor call
An account manager is close to signing a new deal. The prospect wants to hear from someone who already uses the solution. So the account manager calls a satisfied client and asks for a favor: could you connect with one of my prospects and share your experience?
In B2B, this happens every day. Sellers have direct access to happy clients, and a peer conversation is often what moves a prospect from interest to decision. It accelerates the sales cycle and multiplies win rates, which is exactly why it is so common.
References are one of the two most common ways to start with customer advocacy. The other is producing customer stories and case studies. This article covers references: how they typically work within a company, why they need to be formalized, and the first steps to do so.
What informal references quietly cost
When references rely on individual sellers, three problems may arise.
Nobody is counting. No one controls how many times a client is asked for a reference. The same satisfied customer can be approached every week by different people, and nobody sees it until the client is overwhelmed.
Access is uneven. Not every seller has the same opportunities. Some have relationships with the big logos; others don't. Some can't find a client who fits their prospect. The sellers who ask for references get better results, and the rest of the team is left behind.
Other teams collide with sales. References are the most requested tactic, but they are not the only one. The brand or field marketing team may need a client to speak at an event. Sales or customer success can help identify a happy client, but that client may have already supported several references over the last quarter. Now the company is asking for extra effort on top of that.
Once these problems start appearing, informal references have usually reached their limit. When you see them, it is time to formalize a program and centralize every request, whether it is a call, an event speaker, or anything in between.
What formalizing looks like: the reference program
A reference program consolidates all reference requests from sales and marketing in one place. Customer-to-customer calls, event speakers, online peer reviews, logo approvals, and standalone quotes — all of it goes through the same door. The team matches each request with the right advocate and secures their participation.
The program has three jobs.
Protect your customers. The program tracks how often each advocate participates and which activities they are willing to support. Clear participation limits prevent the same clients from being approached too often and help keep reference fatigue under control.
Give every seller the same chance. The best reference should not depend on who a seller happens to know. A smaller customer with the same use case, industry, or company profile may be far more useful to a prospect than the biggest logo in your database.
Show the difference a reference makes. With every request recorded, the team can compare deals where a reference was involved with deals where it was absent. References can accelerate the close and increase the average deal size. The program is what makes that visible.
To make that comparison possible, decide what you will measure before the first request comes in. Tag every deal that receives a reference from day one, ideally in your CRM. Record your current average sales cycle and deal size as a starting point. Without that baseline, the impact can't be reconstructed later.
Where reference programs usually get stuck
Launching a reference program comes with predictable friction. Each first step answers a challenge you are likely to face.
Adoption: sales does not want another process
The biggest resistance comes from sales. Before, a seller could pick up the phone and ask a client for a favor. Now they need to submit a request to a new team, and that team may suggest a different client than the big logo they wanted. For sales, the old way felt more beneficial.
Two things help. First, executive sponsorship: sales leadership needs to back the rule that every request goes through the program, not directly to clients. Second, a process designed to take as little effort as possible.
Start with the tooling you have. If you have a CRM in place and a team to help implement a ticketing flow there, that is the best practice — requests, deals, and outcomes live in the same environment. If that is not an option, a form or a dedicated channel works to start.
Either way, every request should include the same information:
-
the prospect's company size and industry;
-
the deal the seller is trying to close;
-
context on what the prospect wants to learn from the call — integrations, a previous experience with a competitor, implementation, or revenue metrics.
Those details are what allow the team to find a reference that actually fits the prospect. But fit alone is not enough. For sellers to adopt the process, it also has to move at the pace of the deal.
Speed: deals move fast
A new process can't slow down a deal. Sales needs to know one thing immediately: if I submit a request today, when will I hear back? An SLA answers that question and also tells sellers how much notice the reference team needs.
Demand exceeds supply: you have more request than advocates
When advocate capacity is limited, the program needs clear criteria on two fronts.
Which customers qualify as references. Agree on the criteria with customer success, so no one is asked during an escalation or a renewal at risk.
Which deals get priority. For example, when requests compete for the same advocates, the larger deal takes priority, so the biggest opportunities get the strongest matches.
Overuse: everyone wants the same customers
Every seller hopes to connect prospects with the most well-known brands. That creates constant demand for a few advocates and low interest in others — great clients get left out for having a more traditional use case or a smaller implementation, while the in-demand ones get overused.
Usage limits protect the most requested advocates. Recruitment solves the root cause. By analyzing the requests received and how many were fulfilled, the team can identify gaps in product, industry, and country coverage, and run targeted campaigns to recruit new participants.
Advocate experience: give advocates a reason to participate
A common view is that a reference program is transactional and that advocates need to be nurtured elsewhere. We see it differently. Being a reference connects your clients with peers in the same field who face similar challenges. It extends their network.
You can also add benefits for participating:
-
gift cards;
-
a gamified experience — points for every reference, redeemable for branded merchandise once they reach a threshold;
-
early access to new features;
-
exclusive sessions with your engineers to share feedback.
And close the loop. Tell the advocate how the deal ended. It costs nothing, and it is one of the strongest reasons they will say yes the next time.
When to move to a platform
A manual reference desk is a first trial. Once it runs and shows results, the signs of scale appear: request volume grows, matching clients with prospects gets more complex, and reporting takes more time than the team has.
That is when a platform makes sense: to automate the matches between existing clients and prospects, and to track participation at scale. The results from the manual program are what justify that investment.
You do not need a platform to start. You need one place for requests, a way to track how often customers participate, and a way to connect reference activity back to opportunities. Once you can show that the process is being used and that it affects deals, the case for more sophisticated tooling becomes much easier to make.
At Wings4U, we help B2B companies build the foundation their advocacy programs can grow on. Our Advocacy Strategy & Playbooks solution gives teams the strategy, processes, and playbooks they need to make every advocacy motion repeatable, measurable, and ready to scale. Learn more about Advocacy Strategy & Playbooks.
