Customer advocacy: programs, metrics and how to build one
Customer advocacy is the practice of identifying customers who have succeeded with your product and giving them a structured way to say so. It covers references, case studies, reviews, referrals and community participation. In the lifecycle model used here it is the final stage, and the one that most directly feeds back into acquiring the next customer.
What this guide covers
What customer advocacy is, and how it differs from brand advocacy and advocacy marketing
The five types of advocacy and what each one asks of the customer
What drives advocacy, and why sentiment alone is not enough
When to ask, and when not to
How to build a programme, from objective to maturity
How to measure advocacy and connect it to revenue
What software supports it, and where AI helps
Share
What is customer advocacy?
Customer advocacy definition
Customer advocacy is the practice of turning customers who have achieved an outcome with your product into visible, repeatable advocacy through references, reviews, referrals, stories and community participation.
One terminology note. Usage varies. Customer advocacy can also refer to a company representing the interests of its customers internally. This guide uses the business-to-business customer marketing meaning: customers actively endorsing the company to buyers and to other customers.
Advocacy can happen organically. A programme gives customers who are already willing a structured way to do it, and makes the willing ones findable.
Customer advocacy vs brand advocacy vs advocacy marketing
These three terms overlap and describe different scopes of work.
What it covers | Unit | Usual owner | |
Customer advocacy | Named customers providing references, case studies and referrals | The account | Customer success, customer marketing |
Brand advocacy | Anyone who promotes the brand, including customers, employees and partners | The market | Marketing, communications |
Advocacy marketing | Programmes that generate and distribute advocate-created content | The campaign | Marketing |
The distinction matters because the mechanics differ. Brand advocacy is usually measured in reach and sentiment across an audience. Customer advocacy is measured in named accounts: who is willing to take a reference call, and whether they did.
In business-to-business, customer advocacy can influence a buying decision directly, because buyers often want to hear from a company like theirs more than from an aggregate of mentions.
What is a customer advocate?
A customer advocate is someone at a customer account who is willing to speak about their experience, publicly or to a specific prospect.
Two things make someone an advocate rather than a happy user:
They achieved something. The outcome is specific enough to describe to a stranger.
They are willing to participate. The ask fits what they and their employer will allow.
Named participation usually carries more context in business-to-business, because the buyer wants to know who said it. Legal, privacy or company policy can limit public identification without removing the value: an anonymised story, a private peer call or a company-level review still answer the buyer's question.
Customer advocacy vs customer success
Customer success is accountable for whether the customer reaches their outcome. Advocacy is what becomes possible once they have.
Advocacy is downstream of value realisation, even though advocacy activity can continue alongside customer success, renewal and expansion. What it cannot do is run ahead of the result. A programme that asks for references from accounts that have not succeeded will produce reluctant advocates and strain the relationships it draws on.
Why customer advocacy matters
Advocacy matters commercially in three ways.
Peer references can reduce buyer uncertainty. A reference from a comparable company answers the objection no amount of marketing material will, and can shorten some evaluations.
Referrals can create a lower-friction acquisition channel, though the economics vary by business and by segment.
Willingness to advocate is a relationship signal. It is evidence of value and stakeholder commitment, not a renewal guarantee.
The 5 types of customer advocacy
Advocacy is not one ask. Each type requires a different level of time, reputation and internal approval.
Type | What it is | Cost to the customer | When to ask |
Reviews | A rating and short comment on a public site | Minutes | After a clear win, early in the relationship |
References | A call with a prospect | An hour, repeatedly | Once the outcome is established |
Case studies | A documented story with named people and numbers | Internal approvals, legal review | After a result worth publishing |
Referrals | An introduction to someone in their network | Their own reputation | Only with a strong relationship |
Community | Answering questions, speaking, user groups | Ongoing time | When the person benefits personally |
Customer advocacy examples
A review. A customer success manager notices an account hit a milestone, sends a link, and the customer leaves a rating on a software review site that week.
A reference call. A prospect in financial services wants to speak to a current customer with similar compliance requirements. An existing customer takes a 30-minute call and answers questions the sales team cannot.
A case study. An account reduced its reporting cycle from five days to one. Six weeks of drafting, legal review and approvals later, there is a published story with numbers and a named sponsor.
A referral. A champion moves to a new company and brings the product with them, or introduces a peer who has the same problem.
Community participation. A power user answers questions in a user forum, speaks at a customer event, or joins an advisory board.
Previous participation signals willingness, without implying a fixed sequence. An executive who will never write a review may be an excellent reference, and a prolific reviewer may never agree to a case study.
What drives customer advocacy
Advocacy is an output of everything that happened earlier in the lifecycle, which is why programmes that start by asking tend to struggle.
Advocacy starts with adoption
A customer with little evidence of adoption has a weak product story to advocate. They can be pleasant, responsive and still unable to describe a result, because there is no result yet.
The strongest candidates are accounts where the product is in the workflow it was bought for, and where someone internally can point to what changed.
See customer adoption for how that gets measured, and customer lifecycle management for where advocacy sits relative to the other stages.
Customer advocacy signals
Four useful signals:
High sentiment with a specific comment. A promoter score is a number. The free-text answer behind it is the actual lead.
Unprompted positive contact. A customer who writes to say something worked is telling you they are willing to say it.
Depth of adoption. Accounts using the product fully have more to describe.
Stakeholder stability. The champion who ran the implementation is still there and still engaged.
Why sentiment alone is not advocacy readiness
A high survey score on its own does not make an account ready to advocate. Pair sentiment with evidence of value and with willingness to participate.
The check is whether the account can name what changed. If the answer is about the relationship and not about an outcome, that is a strong relationship without a story attached.
Connecting sentiment to outcomes is what separates a usable advocate list from a list of people who scored nine. Greenspace Health maintains a promoter view in Planhat that sales and marketing can work from directly, built on net promoter responses that are followed up automatically instead of collected and filed.
When to ask for customer advocacy
Lifecycle triggers and signals
The best moments are the ones where the customer has just experienced the value, not the ones where you need the asset.
After a measurable win. A milestone hit, a target reached, a problem resolved visibly.
After a successful onboarding. Energy is high and the result is fresh.
After a renewal. They have just made a commercial decision in your favour.
After a high promoter score with substance. The free-text comment tells you what they would say.
After an expansion. Choosing to deepen the relationship is a useful signal that there is a result worth discussing.
When not to ask
Equally important and more often ignored.
During an open escalation. Even a resolved one too recently.
Before first value. The account has nothing to say yet.
Immediately after a champion change. The new person has no history with you.
During a budget or procurement review. The ask reads as pressure.
When they advocated recently. Covered under fatigue below.
How to build a customer advocacy programme
Step 1: Define the objective and the owner
Before anyone is asked anything, the programme needs to know what it is for.
A reference programme, a referral programme, a review programme and a community programme need different advocate pools, different workflows and different metrics. One reason advocacy programmes can look busy while producing little is that they build one and report on another.
Ownership sits between customer success, customer marketing and sales, which means it often sits nowhere. Three arrangements are common:
Customer marketing owns it. Works when there is a dedicated function. Depends on customer success for the relationships.
Customer success owns it. Works at smaller scale. Competes with everything else on the customer success manager's plate.
Shared, with a named programme lead. Creates clear accountability, and it requires someone whose job this actually is.
Whichever model, the thing to settle is who approves an ask to a specific account. Without that, sales, marketing and customer success all reach the same customer in the same month.
Step 2: Identify advocates from data, not nominations
Most programmes start by asking customer success managers to nominate advocates. That produces a list biased toward whoever has the best relationships, not whoever has the best results.
A data-led list starts from outcome and sentiment, then adds willingness. The nomination becomes a filter at the end instead of the source at the start.
Step 3: Design the value exchange and avoid advocacy fatigue
Advocacy asks the customer for time and sometimes reputation. Something has to come back.
In business-to-business, what customers value often has nothing to do with payment:
Recognition. Visibility for them personally, not only for the company.
Access. Early product views, roadmap input, a direct line to the product team.
Peer networking. Introductions to people with the same problems.
Influence. Evidence that their feedback changed something.
Advocacy fatigue is what happens when the same ten accounts carry the whole programme. They say yes until they stop, and then the programme has no bench. Three things prevent it:
Track every ask, across teams. Including the ones that were declined.
Set a cadence per account. A reference call quarterly is different from one monthly.
Keep widening the pool. A programme that is not adding advocates is depleting the ones it has.
Step 4: Measure the programme
Covered in the next section. The point to make here is that advocacy is usually measured by output volume, which describes how busy the programme was and not what it produced.
Step 5: Assess programme maturity
A useful four-stage maturity model:
Ad hoc. Sales asks customer success for a reference when they need one.
Tracked. There is a list, and someone maintains it.
Programmatic. Advocates are identified from signals, asks are routed, fatigue is managed.
Measured. The programme reports influenced pipeline and revenue, not activity.
Customer advocacy metrics
Advocacy measurement fails in a specific way: programmes count what they produced and not what it did.
Metric | What it tells you | Who reads it |
Net promoter score | Sentiment signal, used to identify candidates | Leadership, programme owner |
Active advocate accounts | Accounts with at least one currently willing advocate | Programme owner |
Advocate participation rate | Share of asks accepted | Programme owner |
References delivered | Output volume | Sales, programme owner |
Case studies published | Output volume | Marketing |
Reviews collected | Output volume | Marketing |
Referral pipeline | Opportunities sourced by advocates | Sales, finance |
Reference-influenced revenue | Closed revenue where a reference was used | Finance, leadership |
Sentiment signals
Net promoter score and customer satisfaction are sentiment signals that help identify candidates. They are inputs to advocacy, not measures of it.
Review volume is different: it is an advocacy output, because leaving a review is itself an act of advocacy.
All sentiment measures share a limitation. They reflect the people who responded, which in most accounts is a small subset of the people who matter.
Participation metrics
Participation rate = (Accepted advocacy asks / Total advocacy asks) × 100
Active advocate accounts and participation rate describe the health of the programme itself.
A falling participation rate with a stable advocate count can be an early signal of fatigue.
Output metrics
References delivered, case studies published, reviews collected. These are what most programmes report, and on their own they describe effort more than effect.
Revenue metrics
Referral pipeline and reference-influenced revenue are what make the programme defensible in a budget conversation.
A workable approach is simpler than perfect attribution: tag opportunities where a reference was used, and compare win rate and cycle length against those where one was not. Treat the comparison as directional unless you are comparing similar deal cohorts, since reference use is not randomly assigned and tends to cluster in larger or later-stage deals.
How to measure advocacy return
If the attribution is solid enough to defend, state it as a return:
Advocacy return = (Attributable gross profit − Programme cost) / Programme cost × 100
If it is not, report the two numbers separately instead of combining them into a ratio that implies causation:
Influenced revenue to cost = Influenced revenue / Programme cost
Programme cost includes the headcount, the tooling and any incentives. Influenced revenue needs a stated rule about what counts, applied consistently.
The number matters less than having one. A programme that cannot answer what it produced is harder to defend in a budget conversation.
Getting there usually means moving the data out of survey tools and spreadsheets. DrFirst consolidated that work in Planhat: as Seth Terbeek describes it, net promoter scores used to run through a separate survey system and then into Excel, where now the filters sit against the customer record itself.
How customer advocacy connects to retention and growth
Advocacy is usually framed as a marketing output. In a subscription business it is also a commercial signal.
Advocacy as a relationship signal
Willingness to advocate can be evidence of value delivered, trust and stakeholder commitment. It can therefore inform how you read renewal risk.
It is not a substitute for adoption data, health scoring or commercial evidence. Advocates churn, champions leave, and budgets get cut for reasons that have nothing to do with how well the product worked.
See customer renewals.
Advocacy and expansion
Advocacy and expansion draw on the same evidence. A customer who can describe a result to a stranger can describe it to their own budget holder.
The practical overlap is that both motions are triggered by the same signals, and both are damaged by asking too early.
See customer expansion.
Reference-driven pipeline
The commercial case for advocacy is that the assets compound. A reference used in one deal can be used in the next, and a published case study can answer the same objection across multiple deals until the product, the market or the logo's relevance moves on.
What limits it is availability. A sales team that cannot find a reference for a specific segment, region or use case has a coverage problem, which is an argument for building the bench before it is needed.
Common customer advocacy challenges
Customer advocacy software
What advocacy software does
Four functions, and most teams have the first two covered badly in a spreadsheet.
Maintains the advocate list with what each account is willing to do.
Tracks asks and outcomes, including declines, so fatigue is visible.
Routes requests from sales to the right advocate.
Connects advocacy to the customer record, so the list reflects current health and not last year's enthusiasm.
Dedicated advocacy platforms vs customer success platforms
Two categories, solving adjacent problems.
Dedicated advocacy platforms typically specialise in advocate engagement and activation: portals, reference and referral workflows, gamification, rewards, sentiment analysis and content collection. The unit is the advocate.
Customer success platforms typically contribute the account context used to decide when and whom to ask: health, outcomes, usage, sentiment, stakeholders and contract.
Some products cover parts of both. The evaluation question is whether you need programme mechanics, account context, or both.
Why advocacy spreadsheets fail
When advocacy runs in spreadsheets, three things tend to happen.
The list goes stale, because nobody updates it when an account's health drops. It is invisible to sales, so asks happen outside it. And history is easy to fragment or lose, which makes fatigue undetectable until an advocate declines.
The cost is not the spreadsheet itself. It is the references that were never asked for because nobody knew they were available.
What to look for in advocacy software
For evaluation criteria and vendor questions, see the buyer's guide to customer success software.
Planhat is an agentic customer platform that combines CRM, customer success and professional services automation in one system. Sentiment, outcomes, stakeholder activity and the contract sit against the same customer record, so teams can build an advocate view around which accounts are currently succeeding, not which ones were succeeding when a spreadsheet was last updated. Trend Micro uses that foundation for customer communication, and found the sender matters: as Tracy Shouldice describes it, invitations sent by the customer success manager reach a 38% open rate, against 1% to 2% for the same invitation sent as a marketing email.
AI for customer advocacy
How AI identifies advocates
With the right customer and conversation data, AI can contribute in three ways:
Coverage. AI can evaluate every account against defined advocacy-readiness criteria, instead of only the ones a customer success manager remembered.
Signals in unstructured text. A positive comment on a call, in a support thread or in a survey free-text field is an advocacy lead that structured fields can miss.
Matching. Finding the advocate who fits a specific prospect by segment, region, use case and product, a task that becomes increasingly time-consuming as the advocate pool grows.
What still needs a person
The relationship. An ask that arrives without context from someone the customer does not know performs differently from one that comes through their customer success manager.
A model can rank the base by advocacy readiness and draft the ask. What it cannot reliably do is know that the champion is mid-reorganisation, or that this particular customer dislikes public visibility regardless of how happy they are.
See AI in customer success for how automation, copilots and agents differ, and where approval sits.
Customer advocacy FAQs
What is customer advocacy?
The practice of turning customers who have achieved an outcome with your product into visible advocacy through references, case studies, reviews, referrals and community participation. The term is also used for a company representing its customers' interests internally; this guide uses the customer marketing meaning.
What is a customer advocate?
Someone at a customer account who is willing to speak about their experience, publicly or to a specific prospect. Two things are required: a result worth describing, and willingness to participate within whatever their employer allows.
What is the difference between customer advocacy and brand advocacy?
Customer advocacy works with named accounts and produces references, case studies and referrals. Brand advocacy is broader, covering anyone who promotes the brand including employees and partners, and is usually measured in reach and sentiment, not in named accounts.
What are examples of customer advocacy?
A review on a software comparison site, a reference call with a prospect, a published case study with named people and numbers, a referral to someone in the customer's network, and participation in a user community or advisory board.
How do you build a customer advocacy programme?
Start by defining what the programme is for, since a reference programme and a referral programme need different pools and metrics. Then name an owner and an approver, identify advocates from outcome and sentiment data instead of from nominations, design what the customer gets in return, track every ask across teams to prevent fatigue, and measure what the programme produced.
Who should own customer advocacy?
Customer marketing where that function exists, customer success at smaller scale, or a shared model with a named programme lead. What matters more than the model is that one person approves asks to a specific account, otherwise several teams reach the same customer in the same month.
How do you measure customer advocacy?
Across four layers: sentiment signals that identify candidates, participation metrics that show programme health, output metrics that count what was produced, and revenue metrics that show what it did. Most programmes stop at output, which describes effort.
Do advocacy programmes drive revenue?
They can, and proving it requires a stated attribution rule applied consistently. Tag opportunities where a reference was used and compare win rate and cycle length against those where one was not, treating the comparison as directional since reference use is not randomly assigned.
Should advocacy programmes offer incentives?
In consumer programmes, incentives are common. In business-to-business, treat them carefully. Payment for a reference can affect how a prospect weighs it, and it may conflict with the customer's own policies. Any incentive should comply with the customer's employer policies, the review platform's rules and applicable disclosure requirements. Recognition, early access and peer networking can be lower-friction alternatives to cash or gifts.
What is advocacy fatigue and how do I prevent it?
Advocacy fatigue is what happens when a small group of accounts carries the whole programme until they stop saying yes. Prevent it by tracking every ask across teams including declines, setting a cadence per account, and continuously adding to the pool.
What software do I need for customer advocacy?
Dedicated advocacy platforms specialise in engagement and activation: portals, workflows, rewards and content collection. Customer success platforms contribute the account context that decides when and whom to ask. Some products cover parts of both, so the question is whether you need programme mechanics, account context, or both.
How is customer advocacy different from customer success?
Customer success is accountable for whether the customer reaches their outcome. Advocacy is what becomes possible once they have. Asking for references from accounts that have not succeeded produces reluctant advocates and strains the relationship.
Turn successful customers into visible proof
The accounts that would say yes are usually in the data already, spread across a survey tool, a support desk and a product analytics platform.
Planhat's agentic customer platform keeps that context together, so teams can identify and maintain an advocate pool around who is succeeding now.