# Chapter 9: Building the system

## From strategy to operations

The gap between understanding Advocacy-Led Growth conceptually and running it operationally is wide. Most companies that attempt advocacy programs fail because they underestimated the operational infrastructure required, not because the thesis was wrong.

What follows is a summary of what it takes to build and run an ALG program. This draws from the operational model we've developed at Kindling, worked through in our consulting engagements, and refined into what we call the Advocacy Operating System.

## Phase 1: foundation

Before recruiting a single advocate, you need to make five foundational decisions.

First, define your Ideal Advocate Profile. Not every customer is a good advocate. The best candidates use the product regularly, work in roles that your target buyers identify with, have some presence on social platforms (they don't need a huge following, but they should post occasionally), and have a real positive relationship with the product. Your customer success team usually knows who these people are.

Second, design your compensation model. Advocates should be paid transparently for their time. Published rates, per content type, visible to everyone. Typical ranges for B2B SaaS advocacy programs run from $50 to $150 for a LinkedIn text post, $150 to $300 for short video content, and up from there for longer formats. The rates should reflect the value of the advocate's time and expertise rather than the minimum you can get away with.

Third, write your content guidelines. What topics are encouraged? What's off-limits? How much creative freedom do advocates have? What are the FTC disclosure requirements? The guidelines should be clear and concise. A two-page document, not a thirty-page brand manual.

Fourth, build your content brief library. These are the optional prompts advocates can draw from when they want to create content but aren't sure where to start. A good brief library has a mix of evergreen prompts ("how I use the product in my workflow") and moment-driven prompts tied to product launches, conferences, or industry events. Remember: these are a menu, never a task list.

Fifth, set up your infrastructure: a platform for managing the program (this is what Kindling is built for), payout processing (we use Stripe Connect), content tracking, and performance measurement.

## Phase 2: recruitment

Advocate recruitment should be warm, personal, and respectful. The best approach is a personal introduction from someone the customer already trusts, typically their customer success manager or an executive at your company.

The message should convey three things: we value you as a customer, we're launching a program that rewards customers for sharing their experience publicly, and we'd love for you to be one of the first people in it. The tone is invitation.

Expect conversion rates in the range of 40-60% from warm outreach to expressed interest, and 70-85% from expressed interest to enrolled advocate. These rates are far higher than cold outreach because you're asking people to do something they likely would have done for free if they'd thought of it.

Start small. Ten to fifteen advocates in your first cohort is plenty. You'll learn more from running a small program well than from trying to scale before the operational kinks are worked out.

## Phase 3: activation and support

Once advocates are onboarded, the program's job is to make content creation as easy and rewarding as possible. Share available briefs. Be responsive to questions. Review submitted content quickly (24-hour turnaround is the standard we hold ourselves to). Pay promptly and transparently.

Content review is a critical operational function. Every piece of advocate content should be reviewed before publication for factual accuracy, FTC compliance (is the disclosure present?), and brand alignment. The review should be fast, light-touch, and respectful of the advocate's voice. You're checking for problems, not editing for style. If the content sounds like the advocate wrote it, that's a feature.

If content volume is lower than expected, the response should never be to pressure advocates. Instead, ask: are the briefs inspiring enough? Is the compensation fair? Is the process easy enough? Is the review turnaround fast enough? The problem is always on the program side, never on the advocate side.

## Phase 4: optimization

After 60 to 90 days of operation, you'll have enough data to optimize. Which content types generate the most engagement? Which briefs are advocates gravitating toward? Which advocates are most active, and what can you learn from their approach? Where is content showing up in pipeline conversations?

Use this data to refresh the brief library, adjust the rate card if certain content types are generating outsized value, provide coaching to advocates who want it, and recruit your second cohort based on what you learned from the first.

This is also the phase where Thought Leader Ad amplification typically begins, since you now have organic performance data to identify the best candidates for paid promotion.

## Phase 5: transition to internal ownership

If you started your advocacy program with external help, whether from Kindling's consulting team or another resource, there comes a point where the program needs to be owned internally. The goal of any done-for-you engagement is to make itself unnecessary.

Transition works best when it's gradual. The internal program owner shadows the external team for two to three weeks, running the operations with coaching. Then they operate independently for another two to three weeks with the external team available for questions. By the end of that month, they should be comfortable running every recurring process: publishing briefs, reviewing content, processing payouts, communicating with advocates, and producing performance reports.

The handoff should include a complete operations manual documenting every process step by step. Not a strategic overview. Literal click-by-click procedures for every task. This manual is the insurance policy that protects the program if the internal owner changes roles, goes on leave, or gets pulled into other priorities.

## Common operational mistakes

I'll be honest about the basis for this section: Kindling doesn't yet have years of program history behind it. These failure patterns come from three places. Some come from how adjacent categories (influencer programs, gamified advocacy platforms, community programs) visibly fail, which is well documented. Some come from the operational work we've done designing and standing up early programs. And some are predictions from first principles about where the incentives inside a marketing organization will push a program if nobody resists. I'm confident in all of them, and I'll tell you why in each case.

**Slow content review kills momentum.** If an advocate submits content on Monday and doesn't hear back until Thursday, their enthusiasm drops. The 24-hour review SLA is the single most important operational discipline in the program. Every day of review delay reduces the likelihood that the advocate will create a second piece of content.

**Vague briefs produce no content.** A brief that says "write about your experience with our product" gives the advocate nothing to work with. Good briefs give a specific angle, a starting question, and an example of what the output might look like. They reduce the creative burden without constraining the advocate's voice.

**Inconsistent compensation destroys trust.** If payouts are late, unclear, or inconsistent, advocates lose confidence in the program fast. Use a payment processor that handles the mechanics reliably (we use Stripe Connect), and send a line-item breakdown with every payment so advocates know exactly what they earned and why.

**Over-editing advocate content backfires.** The instinct of every marketing team is to polish content until it shines. Resist this. If an advocate's post reads like a marketing team wrote it, you've destroyed the thing that made it valuable. Review for factual accuracy and compliance. Leave the voice alone.

**Treating quiet advocates as a problem.** Some advocates will create content every week. Some will create once a quarter. Some will go silent for months and then produce something exceptional. This is normal. Advocacy is voluntary. The moment you start treating inactivity as a problem to be solved through nudges, reminders, or guilt, you've crossed the line from support into pressure. If overall content volume is low, the issue is usually with the briefs, the compensation, or the onboarding.

**Failing to close the loop with sales.** If your sales team doesn't know the advocacy program exists, the pipeline influence you're generating is invisible. Brief the sales team. Show them where to find advocate content. Train them to share it in deal cycles. And create a simple mechanism for them to report when a prospect mentions advocate content. Without this feedback loop, you can't measure the thing that matters most.