What goes wrong

I've been deliberately optimistic throughout this book because I believe in the thesis. But intellectual honesty requires me to address the ways advocacy programs fail, because they do fail, and understanding the failure modes is as important as understanding the success patterns. As with the operational mistakes in Chapter 9, these come from documented failures in adjacent categories, from our early operational work, and from first-principles reasoning about organizational incentives. Judge each one on whether the mechanism rings true.

Failure mode 1: the program becomes an influencer campaign

This is the most common way advocacy programs die, and it usually happens gradually. The marketing team, under pressure to show results, starts treating advocates more like contractors. Briefs get more prescriptive. Deadlines get introduced. Someone creates a content calendar with advocates' names slotted into specific weeks. An executive asks "why hasn't [advocate] posted this month?" and suddenly the program has performance expectations attached to individual people.

The advocates feel the shift. They went from being valued customers who were invited to share their experience to content producers with implicit quotas. The best advocates, the ones with the most credibility and the biggest audiences, are usually the first to disengage. They have real jobs and plenty of other demands on their time. They joined because it was interesting and voluntary. The moment it feels like an obligation, the math changes.

The content quality degrades too. Posts that were once real reflections on the product start reading like marketing copy. The engagement drops. The buyers who were connecting with the authentic voice start scrolling past. The program is still producing content. It's no longer producing trust.

The fix is structural. If your program is drifting toward assignment, the problem lives in the incentives and expectations within your own organization, never in the advocates. Revisit the organic principle. Remove deadlines. Stop tracking individual output. Refocus the team on creating conditions for content instead of demanding content.

Failure mode 2: wrong advocates, right program

Not every happy customer is a good advocate. Programs recruit customers who love the product but hate creating content. They agreed to participate because the CSM asked nicely and they didn't want to say no. They go through onboarding, look at the briefs, and never produce anything. This is a failure of recruitment targeting, and the program design can't fix it.

The ideal advocate has three characteristics: they like the product, they are already somewhat active on social platforms (they post about their work occasionally, even if infrequently), and they have an audience that overlaps with your ICP. Missing any one of the three makes advocacy a heavy lift.

A customer who loves the product but never posts on LinkedIn will struggle to start. A customer who posts regularly but is ambivalent about the product will produce content that lacks conviction. A customer who loves the product and posts regularly but works in a completely different industry from your ICP will generate engagement that doesn't translate to pipeline.

The fix is better qualification during recruitment. Ask CS for their happiest customers who are also active on LinkedIn, and do the social listening research before making the introduction. A smaller cohort of well-matched advocates will outperform a larger cohort of poorly matched ones every time.

Failure mode 3: compensation that feels transactional

Compensation is a tricky balance. Pay too little and advocates feel undervalued. Pay too much and the relationship starts feeling like a content production deal rather than a recognition program. The worst outcome is when advocates start to feel like they're being paid for their opinion rather than for their time.

The framing matters enormously. The compensation should feel like a thank-you for the time and effort of creating content rather than a fee for a positive review. The distinction is subtle and real. When an advocate feels they're being compensated for their time, they create honest, nuanced content. When they feel they're being paid for enthusiasm, the content becomes performative.

Published, transparent rates help with this. When everyone can see that a LinkedIn post pays $100 regardless of whether it's glowing praise or balanced feedback, the transactional pressure drops. The advocate knows they'll get paid for creating quality content, period. They don't need to manufacture enthusiasm to earn their rate.

Failure mode 4: no one closes the loop

Picture an advocacy program that produces great content, generates meaningful impressions, and clearly influences pipeline, but no one inside the company can prove it. The sales team doesn't know the program exists. There's no mechanism to track whether prospects encountered advocate content. The monthly report shows content metrics but can't connect them to revenue.

This is a slow death. The program works, but because its impact is invisible to the people who control budget, it eventually gets defunded in favor of channels with cleaner attribution. The paid ad campaign that can show a direct line from click to demo request wins the budget fight, even though the advocacy program may be generating more actual pipeline influence through unmeasured channels.

The fix is to build measurement into the program from day one. Add "customer recommendation or LinkedIn post" as a source option on your demo request form. Train sales to ask prospects what they've heard about you. Create a simple process for sales to flag deals where advocate content played a role. Accept that attribution in B2B will never be perfectly clean, and build a preponderance-of-evidence case rather than waiting for perfect data.

Failure mode 5: the program depends on one person

If your advocacy program is run by a single person who holds all the advocate relationships, manages the briefs, processes the payouts, and produces the reports, you have a key-person risk that will eventually materialize. People change roles. They go on leave. They leave the company. And when they do, the program collapses because everything was in their head.

This is why documented operations matter. Every process should be written down in step-by-step detail. Every advocate relationship should be tracked in a system rather than someone's inbox. Every payout should be processed through a platform with a clear audit trail. The test of operational maturity is: could someone new take over this program in two weeks and run it competently? If the answer is no, you have documentation work to do.

Failure mode 6: expecting results too fast

Advocacy-Led Growth compounds, which is its great strength and its great challenge. The compounding means it gets much better over time. It also means the first 60 to 90 days look underwhelming compared to the immediate gratification of turning on a LinkedIn ad campaign.

A company that launches an advocacy program, sees modest results in Month 2, and pulls the plug in Month 3 has made a mistake they'll never know about. The program would have been generating meaningful returns by Month 6 and strong returns by Month 12. But because the early returns are modest, and because there's always pressure to shift budget to channels with faster feedback loops, the program gets killed before the compounding has a chance to work.

The fix is to set expectations accurately at the start. Advocacy is a 6-to-12-month investment, not a 30-day experiment. The early months are about building infrastructure, recruiting advocates, and establishing content patterns. The returns come later, and they come with a compounding curve that paid channels cannot match. Communicate this to every stakeholder before the program launches, and hold the line when the inevitable "is this working yet?" question comes in Month 2.