Back to Blogs
Customer advocacy drives more than testimonials. It can strengthen retention, expansion, product learning, reputation, and sustained revenue when customers receive meaningful opportunities to participate. Tejal Parekh, Rebecca Stone, and Suzanne Reed explain why advocacy needs executive support, cross-functional ownership, thoughtful segmentation, and patient measurement rather than a collection of isolated requests for references and reviews.
A satisfied customer is not automatically an advocate. Advocacy develops when an organization consistently delivers value, recognizes the customer’s interests, and creates relevant opportunities for that customer to participate.
A CMO Huddles Studio conversation about customer advocacy brought together Tejal Parekh, Rebecca Stone, and Suzanne Reed.
Their discussion positioned advocacy as a business capability spanning marketing, sales, customer success, product, and executive leadership. Customer stories remain important, but they represent one expression of a much larger relationship.
A testimonial, reference call, review, or conference appearance may be an output of advocacy. None of those activities defines the relationship itself.
Advocacy becomes transactional when a company contacts customers only when it needs public proof. A more durable program creates value for participants through visibility, access, learning, professional recognition, peer relationships, or influence over future decisions.
The right opportunity varies by customer. One executive may enjoy speaking at an event, while another prefers a private advisory council. Some companies can approve a public case study. Others face communications policies that prevent them from publicly endorsing vendors.
A flexible program makes room for different levels of participation. It avoids treating public promotion as the only meaningful contribution a customer can make.
Customer marketing may coordinate the program, but no single department owns the entire customer relationship. Sales understands the commercial history. Customer success sees adoption and satisfaction. Product receives feedback about unmet needs. Marketing can organize stories and experiences. Executives may create access that a program manager cannot.
Shared ownership works when responsibilities are explicit. The organization needs a process to identify advocates, record preferences, manage requests, recognize contributions, and follow up after participation. Tejal broke the work into two related responsibilities.
“There’s the identifying of advocates, and then there’s how do you turn these advocates into evangelists for your company. How do you amplify their voices? How do you give them a platform?”
Customer success or account management may identify promising advocates, while marketing can build the programs and platforms that amplify their experiences. The goals remain shared because advocacy depends on customer relationships that extend across the organization.
Without coordination, the same enthusiastic customer may receive overlapping requests from several teams while quieter customers remain overlooked. A central view of the relationship can help the company recognize both overuse and untapped potential.
Executive support also matters. When customer advocacy is treated as a side project owned only by marketing, other teams have little reason to contribute information or protect the customer experience.
Suzanne addressed how organizations interpret the information they receive about customers. “You’ve got to be careful where you get customer and product feedback from. Is it true customer sentiment, or is it more team members’ sentiment?”
Suzanne’s distinction affects advocacy recruitment and product learning. A seller may believe a customer is highly satisfied because the commercial relationship feels positive. The users responsible for daily adoption may have a more complicated experience.
Direct feedback, customer-health data, renewal behavior, participation history, and qualitative conversations can create a fuller view. The purpose is not to reduce advocacy to a score. It is to avoid building the program around internal optimism.
The same discipline protects the customer from being approached at the wrong time. An executive may have agreed to a case study while the working team is struggling with implementation. Shared data and communication can prevent a public request from exposing a private disconnect.
Customer advocates can contribute far beyond a polished case study. Their participation may include:
Each activity supports a different purpose. A peer reference may reduce late-stage uncertainty. An advisory board can reveal unmet needs. A customer speaker can create credible event content. A community participant may help other users succeed.
The program becomes more strategic when each request connects with a defined customer benefit and business objective. The customer understands why the opportunity matters, and the company understands what it hopes to learn or enable.
Rebecca considered how expectations change when recognizable enterprise customers join an advocacy program.
“Everybody understands that large organizations with strong brand affinity are good to be attached to. You don’t have to explain the value of customer advocacy if you get that success, but it takes time.”
Rebecca’s point highlights the tension between relationship-building and immediate attribution. Some outputs can be measured directly, including reference-assisted revenue, participation, content usage, retention, and expansion. Other benefits accumulate through reputation, customer trust, and market visibility.
A balanced model can track program activity, customer experience, commercial influence, and long-term relationship health. No single metric captures the complete value.
Specific examples often make the strongest executive case. A customer reference may have helped an opportunity advance. Advisory feedback may have changed a product decision. A customer speaker may have attracted the right audience to an event. Those examples give the quantitative measures business context.
Advocacy is often treated as an acquisition asset because customer voices can influence prospective buyers. The relationship can also deepen the advocate’s connection with the company. Suzanne connected advocacy with the broader economics of customer relationships.
“Smart growth starts with retention of your clients.”
Retention protects the existing revenue base and reduces how much new acquisition must replace customer losses. Advocacy signals such as engagement, NPS, social participation, and customer lifetime value can therefore contribute to a wider view of growth.
Participation gives customers additional access to executives, peers, product teams, and the organization’s broader community. That access can improve learning, increase visibility, and make the relationship more valuable.
The effect is not automatic. A speaking request followed by silence may leave the customer feeling used. A reference program with no recognition or feedback loop can turn goodwill into fatigue.
Follow-through matters. The company can share the outcome of the customer’s contribution, recognize the value created, and offer a relevant next opportunity without assuming continued participation.
Highly engaged customers can become the default choice for every request. Their enthusiasm makes them easy to approach, but repeated asks can turn recognition into unpaid work.
A central participation record can help teams distribute opportunities more thoughtfully. It can track what the customer enjoys, what they have already done, and whether the company delivered the value it promised.
Advocacy also benefits from reciprocity. A thank-you message is appropriate, but deeper relationships may involve executive access, speaking visibility, peer connection, early product insight, or professional recognition.
This does not mean every contribution requires a formal reward. It means the organization considers the customer’s goals alongside its own.
Customer advocacy does not need to erase every complication from the story. Buyers often find credible detail more persuasive than universal praise. Rebecca considered what other buyers find useful in an advocate’s account.
“You want them to talk about their journey to using our products, and what they’ve learned in that journey, whether it be good or bad.”
Credibility comes from the complete experience, including implementation challenges and lessons learned. A customer who explains how the organization worked through a difficult stage may provide more useful proof than a testimonial consisting only of praise.
A customer can describe the original problem, the implementation process, the decisions required, and the results achieved. Acknowledging complexity makes the account more useful because prospective buyers can see what success involved.
Private advisory conversations can be even more candid. Customers may identify friction, product gaps, or competitive concerns that would never appear in a public testimonial.
That feedback can be uncomfortable, but it is one of the program’s most valuable outputs. Advocacy gives the company proof, relationships, and a learning mechanism.
No. Testimonials are one output. Advocacy can also include references, advisory work, events, research, reviews, community participation, and product feedback.
Marketing may coordinate it, but sales, customer success, product, and executives all contribute to the relationship.
It can reduce buyer uncertainty, strengthen retention and expansion, and make customer value more credible during sales conversations.
Useful measures include participation, customer experience, reference-assisted revenue, content usage, retention, expansion, and documented influence on decisions.
Listen to the full customer advocacy conversation.
CMO Huddles helps B2B marketing leaders win by bringing together peers, fresh perspectives, and opportunities to build stronger personal brands. Want to join the huddle? Learn more about CMO Huddles and join CMO Huddles Starter.