Resourcesicon
Customer Reference Management Requires Cross-Functional Work
Ground up shot of several people putting their hands together showing that customer reference management is a team sport.

Customer Reference Management Requires Cross-Functional Work

Customer reference management is a team sport, yet how many customer reference programs out there are remote islands in their respective corporate sea? Too many! Customer reference programs are one of the most cross-functional programs in an enterprise. Yet, they’re often set up for failure when leadership isn’t involved in establishing the right conditions for success. In defense of corporate leadership, most executives have many competing, high-priority demands. Traditionally, a customer advocate program and the customer reference portion of it are delegated downstream. Leadership doesn’t see how reference programs directly contribute to their personal goal achievement, so the don’t give it much mind share. However, you can change the perception of your program from nice-to-have to essential.

In the absence of an “enlightened” executive team that fully appreciates a customer reference program’s strategic value, a program manager must consider organizational education necessary groundwork to everything else they want to accomplish. Gaining C-suite backing and understanding establishes the foundation of the cross-functional team needed for a vibrant, impactful reference program.

Once you have that executive endorsement you have the “juice” needed for two specific purposes:

  1. Corralling the stakeholder groups who play a role in the customer reference ecosystem.
  2. Securing the support from IT, sales enablement, training, corporate communications, and other groups that directly or indirectly impact the program.

Stakeholder Cooperation

Effective customer reference management requires synergy with stakeholders in PR, digital, demand gen, and events, to name a few. They have reference contacts you don’t have and vice versa. These teams own specific objectives that contribute to your company’s key growth goals. The database of customer reference contacts you build must support their needs. You’re success is tied directly to getting these stakeholder groups to play by your customer reference protocols and practices to maximize reference value while being committed to preventing overuse. If their leadership team tacitly or explicitly approves of a “wild west” reference management approach, you will fail. When each stakeholder group manager clearly understands they are part of a reference management team with common goals, then the whole thing works.

What does this collaboration look like? It isn’t the same for every company. We’ve seen both formal and informal approaches to customer reference management work. Organization size and degree of a teamwork culture are deciding factors in each case. More formal processes involve recurring reference planning meetings where stakeholder representatives present a list of upcoming reference needs and activities under consideration. Attendees strategize together to optimally coordinate activities for their respective benefit and that of the customer. For example, PR may attend a phone interview for a case study to obtain quotes for a future release. Digital marketing may leverage portions of a virtual event for website content. And so on. The possibilities are endless.

There are even a few ways to build cooperation into the system with rewards and performance measurement. Rewards and performance metrics will apply primarily to Sales and Customer Success. Think of salespeople being rewarded for not using the customer reference shadow market and for helping to identify reference candidates. Renewals are common Customer Success goals, but what if client referenceability or how many reference candidates they cultivate becomes a metric? Talk about alignment! Using these “levers” removes contradictory motives that create unproductive friction in the customer reference management ecosystem.

Program Supporting Cast

For a customer reference program to work, there must be a strong supporting cast. Depending on how you’re maintaining reference contact and content information, you likely need IT involvement, including the CRM system and content management system administrators. You’ll need sales enablement or sales operations to help with training at the point of onboarding, as well as continuing education about the program and its technology/tools. A customer reference program needs to be woven into current Sales practices as well.

Don’t forget your colleagues in other marketing teams. Your program may leverage tools like Marketo, Eloqua, or Pardot for customer reference-related campaigns, which means periodic coordination with the campaign management team. If you’re in charge of customer content production, there is the creative team (in-house or outsourced). Want a page for the program on your website? You’ll need digital marketing’s help. Since promoting and sharing the customer reference program’s capabilities and successes via Slack, company newsletters, or executive videos is essential, you can add corporate communications to your supporting cast list.

I hope you can now begin to see how many parts of the organization contribute to a program’s success and why you need leadership support. Your biggest champion may come in the form of a Chief Revenue Officer. By describing your program in these holistic, team-oriented terms and explaining why it’s worth their backing, you position yourself and your vision in a very different light. That will set you apart from many other program leaders and garner respect and engagement.

It’s easy to quickly become mired in the day-to-day of running a program, which is the opposite of evangelizing the team sport nature of a customer reference program. And it will work counter to establishing and cultivating something that drives company revenue and growth. That’s ultimately what our job as customer reference professionals is all about.

Go deep! Check out this free ebook

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.