Model · 7 min read
Forrester Customer Advocacy Model
An assessment of advocacy maturity and next steps.
Forrester Research · View sources ↓At a glance
- Use this when
- You need to develop a more systematic approach to customer advocacy.
- What you will work towards
- An assessment of advocacy maturity and next steps.
- Bring to the reading
- A specific decision from your work and the customer evidence you have so far.
What it is
A staged model for building a proactive customer advocacy practice rather than treating advocacy as an ad hoc byproduct of whichever happy customer marketing remembers to ask when a case study is due. Forrester Research publishes customer-advocacy maturity research (notably report RES172291, behind a paywall); this entry adapts that research tradition into a four-stage ladder rather than reproducing Forrester's model verbatim. It reads advocacy activity along four dimensions: how systematically advocates are identified and segmented, how broad the menu of asks is, whether the same small pool is repeatedly over-used, and whether advocacy is instrumented into the customer lifecycle or bolted on reactively. Plotting a company against those four dimensions places it on a four-stage ladder: Reactive (advocacy is chased only when a specific asset is due, with no tracking of who has already been asked), Identified (NPS and win/loss data are used to systematically find and segment Promoters, with a lightweight tracking system so the same three accounts are not approached for everything), Programmatic (a formal, tiered programme exists with a menu of asks scaled by effort and a matched reward, run on a defined cadence by a named owner), and Embedded (advocacy is triggered automatically at lifecycle moments, its contribution to pipeline and win rate is measured, and it has its own budget justified by that measurement). Most companies with genuinely happy customers still sit at Reactive, because a high NPS score is often mistaken for an advocacy programme, when nobody has actually built the system that turns satisfied customers into a reliable asset.
When to use it
- Marketing only ever finds a customer reference "just in time" for a specific ask, and the same handful of accounts get approached repeatedly because they are the ones everyone remembers.
- NPS identifies plenty of Promoters, but nobody has a system for turning that list into active, willing advocates. A long list of high scorers with no tracked follow-up is a Reactive-stage symptom, not an advocacy programme.
- Sales asks for a reference matched to a specific prospect's industry or use case, and there is no reliable way to find one beyond asking around the team from memory.
- Leadership wants a case study or reference library built, but there is no process to keep it fresh as advocates change roles, get promoted, or churn.
- You are deciding whether advocacy needs a dedicated owner (a customer marketing hire) or can keep being a shared, informal responsibility; the model gives a defensible read on how much unmanaged risk (advocate fatigue, a stale reference library) the current approach is carrying.
Ownership
At a scaled company with a specialised PMM team, a dedicated Head of Customer Marketing (or a Customer Advocacy Manager reporting into that role) owns the model outright: the audit, the tracking system, the ask menu, and the lifecycle instrumentation. The Head of Customer Success supplies the renewal and usage-milestone triggers and helps nominate candidates, but doesn't own the programme itself. At a solo or founding-PMM stage, the founding PMM owns every stage of the ladder personally, since a dedicated customer marketing hire doesn't yet exist to take over identification, ask-menu design, and outreach.
How to read it
Treat the four stages as a ladder a company climbs deliberately, not a checklist to complete all at once, and diagnose the current stage honestly rather than assuming a programme's name reflects its actual maturity. Score against the four dimensions: identification and segmentation (systematic process, or same names from memory), ask-menu breadth (scaled by effort and reward), fatigue management (tracking of ask frequency), and lifecycle instrumentation (triggered by events, or chased reactively). A company scoring low on all four is Reactive; well on identification alone is Identified; well on identification, ask-menu breadth, and fatigue management but with no lifecycle trigger is Programmatic; well across all four, with a measured pipeline and win-rate contribution, is Embedded.
How to apply it
- Audit the last two or three quarters of advocacy activity. Count how many times a customer was approached for a reference, quote, or case study, and how many distinct accounts were involved. A high ratio of asks to distinct accounts is the clearest single signal of Reactive-stage advocate fatigue risk.
- Cross-reference NPS Promoters and win/loss interview subjects against that audit, and build a tracking system (a CRM field or shared spreadsheet) recording who has been asked, for what, and when, to enforce an agreed annual cap.
- Build a tiered ask menu scaled by effort and matched to a reward. Low-effort asks (a public review, a short quote) earn a small thank-you; medium-effort asks (a written case study, a website logo) earn co-marketing exposure; high-effort asks (a reference call, a speaking slot) earn meaningful recognition such as an executive advisory board seat.
- Assign a named owner, typically a customer marketing role or a PMM with that explicit scope, to run the programme on a defined cadence, for example a quarterly nomination cycle sourced from customer success plus an always-open self-nomination form.
- Instrument advocacy into lifecycle moments rather than waiting for a marketing need to surface one: trigger a nurture step at a renewal, a usage milestone, or a strongly positive support interaction, so candidates surface continuously rather than only when someone goes looking.
- Measure the programme's contribution by tracking reference-assisted win rate, case-study-sourced pipeline, and advocate account retention or expansion against the wider base, and use that data to justify the investment needed to move from Programmatic toward Embedded.
- Re-audit at least annually. A programme can slide back toward Reactive quietly if its named owner moves roles or the tracking system falls out of use during a busy quarter, and the model's value comes from catching that regression early, not from a one-off diagnosis.
Example
Clearway, a fictional B2B payments company, had run a purely Reactive advocacy motion for two years: whenever sales needed a reference for an enterprise deal, or marketing needed a quote for a launch, someone in PMM messaged the same four long-tenured customers, because they were the names everyone remembered. An audit run against this model found those four accounts had absorbed 90% of every advocacy ask over the two years, despite the company's own NPS data separately identifying 62 Promoters in the wider customer base who had simply never been approached. Two of the four repeatedly-asked accounts had stopped responding to requests entirely by the time of the audit. PMM cross-referenced the NPS Promoter list against account tier and industry, built a tracking sheet, and introduced a three-tier ask menu: a G2 review (gift card), a case study (co-marketing exposure), and a reference call (advisory board invitation). Customer success was briefed to nominate a candidate at every renewal scoring Promoter on the post-renewal NPS survey. Within two quarters, the active advocate pool grew from 4 accounts to 23, average reference-call response time fell from 9 days to 2 days, and deals that used a reference closed at a 14-point higher win rate, the evidence that justified budgeting the programme as a formal customer marketing responsibility the following year.
Pitfalls
- Treating NPS Promoter status alone as proof of advocacy willingness. A Promoter who privately loves the product may have no interest in, or even a company policy against, public advocacy, and assuming otherwise both over-targets uninterested accounts and under-uses genuinely willing customers who scored lower on NPS for unrelated reasons. Recovery: always confirm willingness directly with a simple opt-in question before adding an account to the tracked advocate pool, rather than inferring consent from a high NPS score alone.
- Advocate fatigue from over-relying on the same small, easy-to-remember pool. Clearway's original four-account pattern is the common failure mode: the same names get asked because they are top of mind, not because they are the best-matched or most willing advocates available. Recovery: cap asks per account per year (two to three is a reasonable default), track the cap explicitly in the system built in step 2, and route new requests to under-used advocates first.
- Running the programme with no measurement, so it never earns a dedicated budget or survives a headcount review. An advocacy programme that cannot point to a pipeline or win-rate number looks like a nice-to-have the first time budgets tighten. Recovery: track reference-assisted win rate and advocate-sourced pipeline from the programme's first quarter, even informally, so there is evidence ready the moment its value is questioned.
How the ideas connect
Choose where to go next
Make it useful
Bring it back to your work.
Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.
Check your understanding
Practise applying Forrester Customer Advocacy Model in five short scenarios.
5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.
Sources
- Forrester Research, "Introducing The Forrester Customer Advocacy Model", report RES172291 (behind a paywall; last updated 2025). This entry adapts Forrester's staged research tradition into its own four-stage ladder rather than reproducing the report's model verbatim.
← All entries in Product Experience & Adoption · Try the category quiz