Resourcesicon
How to Align Your Customer Reference Program with Sales
Graphic showing cartoon silhouette of man holding two money bags on a funnel with a curved lin leading to green money bag.

How to Align Your Customer Reference Program with Sales

How well do you know your company’s sales process? How does a customer reference program manager know if customer advocate resources are being used by Sales to the fullest? This is a really important part of setting appropriate expectations (yours and leadership’s), as well as establishing continuous improvement goals aimed at winning more opportunities.

When we help a client estimate the activity volumes they should expect, we ask a lot of nuts and bolts questions regarding the Sales function. Pieced together, the answers provide necessary context, and paint a complete picture.

For some program managers this might be the first time they dive into the weeds of your company’s sales process, but it’s important to do so. Here’s an example of how it works. The blue entries are the particulars needed from Sales or Sales Ops leaders.

A) # quota-carrying salespeople500B) Average annual quota per salesperson$1,500,000C) Average opportunity size$180,000Average # opportunities per year8.33Average # opportunities per quarter2.08Average # opportunities per month.69

A) If your team is fairly homogenous the number of salespeople is a single number. However, there may be material differences (commercial vs. public sector, or enterprise vs. SMB) that warrant calculating these numbers separately for multiple segments.

B) Average annual quota is new or incremental revenue where references are most commonly employed (versus add-on licenses, for instance).

C) Opportunity size, coupled with volumes identified in the previous two questions, helps estimate the amount of revenue references contribute to the metric, revenue influenced, one of the most quantifiable measurements in our domain.

D) % of opportunities that require references to close70%E) Average # of reference accounts needed per opportunity2

D) How many opportunities require a reference seems like a simple question, but consider these sales process scenarios  where references aren’t needed:

  • The solution/product is an industry standard (e.g., Kleenex = facial tissue).
  • The buyer didn’t feel the need for references. Maybe the salesperson was THAT good.
  • The buyer was previous client and had firsthand experience.
  • The decision had little risk (e.g., freemium option).

E) The number of references per deal varies. We hear everything from 1 to 5, or more. In industries like insurance, it’s not unusual for a B2B buyer to request a few current clients, a mixture of long and short-term clients, and even some former clients. This is in addition to the requirement of a particular organization size, geo, products, etc.

Below are the anticipated reference request needs each salesperson would have, if evenly distributed over the year. Multiple by the number of salespeople (A), and you have a good guesstimate of reference demand. The next step is to find out where the typical peaks and valleys are throughout the year, and weight accordingly.

Each SalespersonAverage # account requests per year12Average # account requests per quarter3Average # account requests per month1

Are Customer References Being Maximized Thought the Sales Process?

Most customer marketers assume that salespeople are using customer advocates effectively. Don’t. If they are hunting for references through Slack or email blasts, it’s an unpleasant task and therefore avoid to whatever degree possible. Sometimes a buyer concern/objection arises and a salesperson doesn’t think, “We’ve got just the customer video or customer contact to jump on a reference call to remove the obstacle!” Optimizing customer reference use throughout the sales process take on-going work. This is where education comes in at new hire onboarding, and at virtual “lunch and learn” sessions offered throughout the year. What a great opportunity to share effective reference use success stories!

What Program Goals Make Sense?

Ultimately, no goals are attainable unless customer references are being used as often as possible. They can’t help move a deal to close if they’re not inserted into the sales cycle at the right time. In our opinion the fundamental objective should be to increase the % of deals leveraging references to whatever level makes sense using the numbers in our exercise as a reality check. If you expect 70% of deals to leverage references and only 40% do, then additional discovery work is warranted. What’s in the way of achieving the ideal rate of 70%?

When achievement of this fundamental goal is reached, then revenue influenced, win-rates (with and without references), and sales cycle acceleration come with it. For more on program metrics, check out this post.

So you’ve set your goals based on anticipated activity and suddenly you’re missing your numbers. What happened? The Sales world is dynamic, ever changing. Your forecasts should be revisited quarterly in order to adjust expectations for seasonality, and other events that affect buying behavior.

Your Sales Process Savvy is Rewarded

You’ll find that understanding the inner workings of the Sales process at your company provides insights that drive the bulk of what you do as a program manager. Whatever Sales is tasked with in terms of company growth all other supporting functions (PR, Social, Digital, etc.) will have customer advocate needs all facing in the same direction. And that makes your priorities crystal clear.

It Started With a Legitimate Aspiration

It's only natural that many advocacy leaders have landed on the same objective: make the program easier to use by meeting users where they're already working.

Today, that increasingly means Microsoft Copilot, ChatGPT, Claude, Gemini or whatever generative AI assistant employees happen to have open.

Imagine a salesperson simply asking AI, "Find me three German healthcare customers using product Y, willing to speak with a prospect," instead of navigating to another interface, or waiting for someone from advocacy, or elsewhere, to respond. It's easy to see the appeal. Removing friction has always been one of the fastest ways to increase adoption.

It is exactly the right instinct.

The difficult parts, arguably the reason program managers exist, occur before and after AI says, "Here are your three best matches."

The value advocacy professionals bring is the ability to operationalize and scale customer advocacy for maximum impact. Quality advocate information doesn't just appear, it's the result of a system.

What's Next?

Now that the user has three advocates, what should happen?

  • Should they email the customer directly?
  • Should they contact the Customer Success Manager first?
  • The account executive for one of the accounts was about to make a request. Was that considered?
  • Has anyone noticed that this customer has already participated in three activities in the last 60 days?
  • Are they currently navigating a difficult support issue?
  • Did they recently decline another invitation?
  • Would someone else actually be a better choice?

Notice what happened. The search was completed.

The next steps are just as manual as ever if AI search is the be all, end all.

Reality Check
AI can tell you who could participate. It can't tell you who should participate unless someone (or something) has been keeping score.

Haven't We Seen This Movie Before?

This is where the story starts to feel strangely familiar.

Many companies still operate their program using spreadsheets, scattered CRM fields, shared drives, email folders, and the remarkable memories of a handful of program managers.

Eventually, organizations realize they aren't managing an advocacy program at all. They're managing lists that happen to contain advocates.

But the shortcomings are real:

  • A spreadsheet might tell you that Sarah from ABC Company has spoken at a conference. It couldn't tell you that she'd spoken three times already this quarter.
  • Custom CRM fields could tell you a customer was referenceable. They alone couldn't coordinate approvals, notify relationship owners, recognize participation, measure outcomes, or attribute revenue.

Purpose-built advocacy platforms emerged because advocacy is much more than a search problem.

Ironically, AI has convinced some organizations to revisit the same shortcut they worked so hard to escape.

When Search Replaces Process

Let's imagine two different worlds.

In the first, AI recommends an advocate for a sales call.

  1. A request is automatically created.
  2. The Customer Success Manager approves participation.
  3. The customer receives preparation materials.
  4. The call takes place.
  5. The activity is recorded.
  6. Recognition is issued.
  7. The opportunity is linked to the advocacy activity.
  8. If the deal closes, revenue attribution updates automatically.
  9. Executive dashboards reflect the contribution.

Months later, AI knows this customer recently participated and may deserve a break before being asked again.

Now imagine the second world.

  1. AI recommends the same advocate.
  2. The salesperson sends an email.
  3. The customer agrees.
  4. The meeting happens.
  5. Everyone moves on.

Three months later someone asks how many customer reference contributed to the revenue this quarter.

Silence. Nobody really knows.

The advocacy happened...hopefully. The program didn't. Collectively, the organization slowly stopped feeding the very system it depended on to understand its advocacy program.

Reality Check
If AI helps facilitate twenty closed-won opportunities this quarter, but none are recorded, your executive dashboard still says zero.

Invisible Work Stays Invisible

One of the easiest mistakes to make in an AI-first world is assuming that successful interactions somehow become organizational knowledge on their own.

They don't.

If a customer agrees to speak with a prospect and nobody records it, the organization loses far more than a single activity.

  • It loses context, attribution, and recognition.
  • It loses another piece of history that could have helped improve the next decision.

The most valuable advocacy data isn't simply who your customers are.

It's everything they've done.

  • Every request, acceptance/decline, event presentation, analyst interview, product beta, reference call, press interview, reward, closed-won opportunity revenue influenced by their participation.

That's the story AI actually wants to read.

AI Needs Memory, Not Just Data

It's often said that AI needs good data.

That's true.

But operational history is far more valuable than static customer information.

  • Advocate profiles answer questions about who someone is.
  • Operational history answers questions about what consistently works.
  • That's where AI begins uncovering insights that no spreadsheet could ever reveal.
  • Perhaps healthcare advocates participate twice as often as financial services advocates.
  • Perhaps customers who join advisory boards are twice as likely to become conference speakers.
  • Maybe advocates who receive recognition within a week participate significantly more often than those who don't.

Those aren't search results.Those are patterns.

  • Patterns emerge from history.
  • History emerges from process.
  • Process emerges from systems.

Remove any one of those pieces and AI becomes little more than an exceptionally fast search engine.

Reality Check
Every workflow skipped today is a pattern AI won't discover tomorrow.

Don't Stop at "Who?"

The AI revolution has created tremendous excitement, and rightly so. Finding the right advocate is becoming dramatically easier than it was only a few years ago.

That's worth celebrating.

Just don't confuse a better search experience with a better advocacy program. Search is only one chapter in the story.

The organizations that see the greatest return from AI won't necessarily be the ones with the most sophisticated models.

They'll be the ones with the richest operational history.

  • Every request becomes institutional memory.
  • Every activity measured.
  • Every contribution attributable.
  • Every outcome becomes another lesson AI can learn from.

Those organizations won't use AI merely to answer the question, "Who should we ask?"

They'll use AI to answer far more valuable questions.

  • "Where are we running short of advocates?"
  • "When is the most effective time to use advocates?"
  • "What types of advocacy generate the greatest business impact?"
  • "What patterns have we been missing?"

That's when AI stops behaving like a better Google search.

That's when it starts behaving like a strategic partner.

Finding the right advocate has always been the opening scene.

If your AI can find advocates but your program can't learn from using them, you've built a remarkable search engine instead of a remarkable advocacy program.