Resourcesicon
Secure Real Executive Support for Your Advocacy Program
Close up picture of professionals of diverse ethnicities clapping illustrating executive support for advocacy programs.

Secure Real Executive Support for Your Advocacy Program

Executive support. We all know it’s important. When I hear a client or prospect say, “I’ve got executive support,” I ask, “What’s that look like?” You may know where I’m going with this. There are different flavors of “support,” and they are not equal.

To be fair, I don’t think all program managers articulate what they need in terms of executive support. When you hear an executive say, “This is important to me. Let me know how I can help.” that’s a good start, but not in and of itself the definition of executive support. You cannot expect an executive to know what you need from them to make your program successful. This is on you.

You’ll need different things at different times. Let’s separate what’s required in terms of leadership involvement (1) leading up to and including program launch, and then (2) post-launch.

Pre-Launch/Launch

  • Change Management –You’re introducing non-trivial change to your organization; change is hard. Customer advocates have existed mainly in the heads of salespeople, customer success managers, product managers, executives, and others in the know. Some of your co-workers like it that way. It’s their secret “power.” Some are lazy, and the idea of formalizing and committing their advocate knowledge is a bother. Adhering to a process for requesting the use of advocates, tracking that use, and updating information about advocates is all very different than the way they’ve “always done it,” maybe for their whole career.
  • Communicating Strategic Importance –When an executive or executive team vigorously communicates a strategic change, that usually gets the workforce’s attention. Such a change results from carefully considered factors directly tied to company growth. The logic for investing in an advocate program and the anticipated benefits must come from leadership and align with each management level.
  • Participation Not Optional – There will always be the rebels, those that march to their own drumbeat. Allowing those people to play by different rules will undermine the program’s strategic goals. There is leakage. Like an engine that isn’t properly tuned, the program just won’t perform at its best. Leadership must express intolerance for system dysfunction and not getting on board.

Post-Launch

  • Process Enforcement – After the launch of a program, there will be growing pains. But it’s essential to bring those working outside the new system inside quickly. Consequences for disregarding company imperative are required. These aren’t easy to secure, but they will accelerate participation, just as rewards will. You will earn stakeholder attention by tying various program support activities to job performance measurement.
  • Recognition/Reward – Change happens with more joy when it’s rewarding. Routinely recognizing program successes and contributing stakeholders is vital for building company-wide momentum. Some company executives are philosophically opposed to the idea of incentivizing employees to “do their jobs.” It’s understandable, but also old school and short-sighted. Do you want to win by breaking with precedent or lose on principle?
  • Strategic Planning Inclusion – A successful program is joined-at-the-hip with company growth plans and goals. It does not operate in its own orbit because it exists to support every part of the organization that can execute its mission better with customer advocates (Sales, demand gen, PR, events, digital, social, etc.).
  • Program Advisory Board – Because a customer marketing program that’s running well is easy for VPs and CxOs to forget, it’s imperative that an executive is a member of your program advisory board.

Specifically, what does executive support look like?

In short, it is explicit, not passive involvement. It is visible actions to back up words (which do matter). It is sustained rather than fleeting interest.

Communications

Channels

The medium may be written (email, Slack/Teams), video (internal communications videos), or spoken (team or all-hands meetings); whatever has proven to be the most effective channel(s).

Cadence

Communication is not a one-and-done task. You know the adage: “Tell ’em what you’re going to tell ’em; then tell ’em; then tell ’em what you told ’em.” That all applies here. Work with leaders on a recurring communications plan; build a communications calendar. The cadence could be weekly to start, then bi-weekly, and ultimately monthly. But it should never stop.

Content

It’s easier to edit than to create. Some executives completely get the value of customer advocates. Some understand it intellectually, but it isn’t yet emotionally internalized. The latter group could benefit from your guidance. Write some or all of the suggested pieces for them.

Pre-Launch

Build excitement, set expectations.

  • The importance of the program (e.g., competitive differentiation)
  • Anticipated benefits (e.g., improved win rates)
  • Behavioral changes expected (e.g., stop shadow market referencing)
  • How behaviors will be enforced/reinforced (e.g., performance review component, spiff program)
  • Updates on program progress (e.g., 100 new F1000 advocates onboarded!)

Post-Launch

  • Updates on program progress (e.g., 50 new Insurance advocates using Product A onboarded)
  • Stakeholder success stories (e.g., Joanna Birk closed $3.8M this month using 6 reference accounts)
  • Program impact stats (e.g., Opportunities leveraging advocates have a win rate 30% higher than those that don’t)

Strategic Planning Inclusion

“Getting a seat at the table” is the ultimate goal for many customer marketing managers. That means being invited to key planning meetings that include directors, VPs and CxOs. These meetings give program managers critical visibility into upcoming advocate needs for email campaigns, webinars, earnings calls, digital marketing, etc. You can then suggest ways in which the program can help; ways which no one would have thought of without you being in the conversation.

Executives have the influence needed to get you that seat. Once they understand the advocate expertise you have and the “assets” the program has to offer, they’ll be able to identify advocate opportunities: “That’s a great idea! Did you talk to customer marketing to get their thoughts? They have some strong advocates in that segment you should leverage.” Customer marketing is still a relatively young function and often not considered the strategic discipline that it should be. Changing this perception may take persistence and change management effort on your part. But, the benefits to the organization are worth it!

Program Advisory Board

Their participation ensures they understand what’s working and what’s not, which they can help solve. They can bring big picture perspective into the conversations. Likewise, the more they know about the program the more they can infuse executive conversations with insights into how customer advocates are being used across the enterprise, which will likely spark creative customer advocate applications.

I’ve laid out how we believe executive support should work. If the version of it at your company doesn’t include the elements described above, you don’t have it—yet. If you’re not sure how to get it, read our post: How to Capture and Keep CxO Engagement. In short, you must think like an executive and talk in terms of their areas of interest, their priorities, and connect the dots to your program. Do not assume they will connect those dots on their own.

Don’t be shy about asking for genuine support from your executives. The ask alone sets an expectation: Customer reference management is a team sport, and executives are on that team.

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.