Home / Chapters / Chapter 12

ALG alongside PLG and SLG

A layer that makes your existing motions work better

I want to be clear about something: Advocacy-Led Growth is not a religion, and it isn't asking you to abandon what's already working.

If you have a strong product-led motion, keep it. If you have a sales team that closes deals, keep them. If your content marketing generates inbound, keep doing it. ALG is the layer that makes all of them work better.

ALG + product-led growth

The standard PLG funnel looks something like: prospect discovers product, signs up for free trial, uses the product, hits a moment of value, converts to paid, expands over time.

The weak link in this chain is the "discovers product" step. In a crowded market, free trials are everywhere. What makes a prospect choose to try your product over the fifteen others in the category? Often, it's because they heard about it from someone they trust.

An advocacy program feeds the top of the PLG funnel with the highest-quality awareness possible. When a prospect signs up for a free trial because they saw a practitioner they respect posting about the product, that trial user arrives with a higher level of trust, a clearer understanding of the product's value, and a greater likelihood of converting. The PLG machine doesn't change. The quality of what enters it improves.

ALG + sales-led growth

For companies with sales teams, advocacy creates what I think of as air cover. When a prospect has already seen customers talking positively about your product on LinkedIn, the first sales call is warmer. The buyer has context. They've seen social proof that wasn't orchestrated by the sales team, so the conversation starts from a different place.

Advocacy also gives you a tool for deal acceleration. When a deal stalls, a sales rep who can share a recent advocate post ("one of our customers just posted about this exact use case, thought you'd find it relevant") has a more credible touchpoint than yet another follow-up email or case study.

And for competitive deals, where the prospect is evaluating multiple vendors, a visible library of customer content creates a trust asymmetry. If your customers are openly talking about you and your competitor's aren't, the buyer notices that gap. I lost a seven-figure deal to exactly that gap in 2014. It's the story this book opens with.

ALG + content marketing

Content marketing teams spend enormous effort producing blog posts, whitepapers, videos, and thought leadership. All of that content carries a brand stamp. The reader knows it was produced by the company selling the product.

Advocate content fills a gap that branded content cannot fill: the outside perspective. A marketing team can write a blog post about their product's value. They cannot write a first-person account of what it's like to use the product every day. Only a customer can do that.

The two content streams complement each other. Branded content educates and creates awareness. Advocate content validates and creates trust. Neither one alone is as powerful as both together.

The integration playbook

In practical terms, integrating advocacy into your existing growth motions means connecting the advocacy program's output to the systems your other teams are already using.

For PLG integration: your growth team or product team should have access to the advocacy content library organized by use case and feature. When a trial user is exploring a specific feature, the onboarding flow can surface a link to an advocate post about that exact feature. A real user explaining how they actually use it, rather than a branded tutorial. The conversion lift from social proof at the moment of evaluation is real.

For sales integration: your AEs should have a tagged, searchable library of advocate content organized by persona, industry, and buying stage. When an AE is working a deal with a VP of Marketing Operations at a mid-market SaaS company, they should be able to find an advocate post from a VP of Marketing Operations at a mid-market SaaS company talking about the product. That's a peer speaking in their own voice, and the deal team can share it as a natural touchpoint: "thought you might find this relevant, one of our customers posted about this exact use case."

For marketing integration: your content calendar should include a rhythm of repurposing advocate content (with permission) into other formats. An advocate's LinkedIn post can become a quote in a blog post, a snippet in a newsletter, a slide in a webinar, or a testimonial on a landing page. Each repurpose extends the life and reach of content you didn't have to create from scratch.

For customer success integration: your CS team should know which of their accounts include active advocates. Advocates are your most engaged, most loyal customers. They're also the ones most likely to expand their usage, provide product feedback, and resist churn. A customer who is actively advocating for your product is not a churn risk, which makes the advocacy program a retention signal as much as a marketing tool.

The organizational home for ALG

One of the most common practical questions I get is: where does the advocacy program sit organizationally?

There is no single right answer, but there are wrong answers. The advocacy program should not sit exclusively in customer success (it becomes an internal-facing reference program). It should not sit exclusively in content marketing (it becomes a content production initiative). It should not sit in demand generation (it becomes a campaign).

The best home for an advocacy program is wherever the company's go-to-market strategy lives. If you have a VP of Marketing who owns pipeline, it sits there. If you have a VP of Growth who owns the full funnel, it sits there. If you're a founder-led company where the CEO drives go-to-market, it reports to you.

The key requirement is that the person who owns the advocacy program has the authority to work across marketing, sales, and customer success. Advocacy touches all three functions. If it's siloed in one of them, it will underperform its potential, because it will lack the cross-functional connections that make it work.

Read the whole book offline

Enter your email and we'll send the complete book as a PDF — one email, no newsletter.

One email, no newsletter.