Resourcesicon
Becoming a Strategic Customer Advocacy Program Leader

Becoming a Strategic Customer Advocacy Program Leader

The term strategic is tossed around all the time. We all want to be strategic. Tactical sounds so pedestrian, right? Some in customer marketing might view the customer reference management component as tactical. Respectfully, I vehemently disagree.

How does one become strategic and behave strategically in the context of customer reference management? It begins with how you view your program, which lets co-workers and executives know how they should view your program.

On the surface, what are the primary objectives of customer reference management?

Bigger Than Sales

These objectives are not just about supporting Sales. Far from it. The advocate database is a corporate asset that—built, used and maintained properly—improves any activity with the infusion of customer advocate experiences and insights  (customer videos and quotes in campaigns, live presentations at conferences, sales calls, earnings calls, investor calls, etc.).

The reality is that most customer marketing managers must be both strategic and tactical simply because there are many teams of one out there. If that’s your situation, then think of the following as “hats” you wear, and not different people.

  • The strategic person asks what should we be doing and why, which markets and segments will be critical in the future, how will we differentiate ourselves, what trends will impact how we do business, what is happening in the world and how does that apply to our business/my team?
  • The tactical person asks what resources, plans, decisions, processes and activities need to be in place and/or executed to support the strategy?

Connecting the Dots

To act strategically you have to both understand your company’s growth goals and translate your program’s goals and tactical execution to align with those strategic goals.

The Haves and Have Nots

How do you translate all of this to customer reference programs? Following is a list of key program aspects, and two program versions: one without strategic alignment (and therefore perceived value), the other with strategic alignment.

Program Aspect – Not Strategically Aligned vs. Strategically Aligned

Program Aspect
Not Strategically Aligned
Strategically Aligned
Scope
  • Your program supports only a fraction of enterprise advocate use cases (e.g., only marketing, only sales, only produces customer content, only procures customer reviews, etc.).
  • You fully support all enterprise advocate needs, in recognition that many departments benefit from advocate stories as part of initiatives that support growth goals.
Program Goals
  • Your program lacks business outcome goals (e.g., revenue influenced), or goals are not connected to company growth goals (e.g., add X reference accounts, even if unrelated to demand and company goals).
  • Advocate recruiting, request fulfillment and ultimately revenue influenced is clearly in support of company growth goals.
  • KPI data, shared regularly with leadership, reflects your program’s impact on company growth goals.
Relationship with Leadership
  • Key leadership (VP Sales, CMO, CRO, VP CS) know little to nothing about your program.
  • You don’t think leadership cares about, or has time for your program, so you hesitate to engage them.
  • Your program is on leadership’s radar because they see its relevance to what they care about.
  • There is regular engagement with leadership to share successes, and secure assistance with program obstacles.
Relationships with Sales
  • You/Your program is not known to most sellers.
  • Sellers don’t view the program as helpful in meeting quota.
  • You don’t have a deep understanding of Sales operations (avg. deal size, avg. sales cycle, % of deals requiring references, etc.).
  • You don’t have a regular “slot” on Sales meetings for program topics.
  • The program is on leadership’s radar.
  • Key leadership understands the program’s purpose, and alignment with leadership’s growth goals.
  • There is regular engagement with leadership to share successes and secure assistance with program obstacles.
Relationships with Marketing
  • You don’t meet regularly with PR, Events, Social, Demand Gen, etc., to understand initiatives, and propose reference solutions.
  • Reference needs in 3-6 months aren’t known, which would inform recruiting plans/goals.
  • Marketing departments are still using “back pocket” references rather than working through your system to track, protect and reward advocates.
  • You allocate time to join stakeholder department meetings to learn of future plans and provide advocate consulting.
  • Marketing departments wouldn’t make a move regarding the use of advocates without consulting you.
  • You have specific Marketing advocate needs included in your proactive recruiting plans/goals.
Relationships with Customer Success
  • Customer Success views you as extra work.
  • CSMs view customer reference activities as a distraction.
  • When asked for advocate nominations, CSM provides little to no candidates.
  • CS is not measured on customer referenceability.
  • You work closely with Customer Success managers to align goals.
  • You have helped CS managers establish performance metrics related to referenceability.
  • CSMs know and trust you to use their time efficiently, and maintain, if not improve, customer relationships.
Training & Education
  • Employees are not trained on how advocates are to be incorporated into their activities, in support of company growth goals.
  • Advocate best practices are not taught at onboarding, or otherwise.
  • Sales and Marketing receive regular training and reference best practices in team meetings.
  • As new advocates and customer content is added to support growth goals, Sales and Marketing are notified and coached on optimal use.
Leadership Planning
  • You are not included in planning that should incorporate advocates such as product launches, new industry-aligned GTM plans, regional event initiative, etc.
  • You have a seat at any relevant planning meeting because your program is viewed as an integral part of Sales and Marketing initiatives.

The Wrap

At a recent customer marketing conference, attendees were surveyed and asked about their career ambitions. Well over half had C-Suite positions in mind. To get there it’s important to start thinking like an executive in your customer marketing role, and developing that executive muscle now. It’s a form of training: think of it like you’re marathon training only for your career rather than a race. Once your strategic potential is recognized, doors will open and you’ll be on your way. But stay purely in the tactical space and you’ll simply be a best-kept secret.

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.