Agent skill
customer-advocacy
Customer advocacy program design - advocate identification, reference orchestration, case study pipeline, community amplification, and influence-to-revenue attribution.
Filed under Onboarding, retention and expansion.
From varunk130/ai-gtm-skill-library · 31 skills · 5 · pushed 2026-07-31
What it does when it runs
Customer advocacy program design - advocate identification, reference orchestration, case study pipeline, community amplification, and influence-to-revenue attribution. Use when: customer advocacy, customer reference program, case study program, advocate identification, customer marketing, peer review acceleration, G2 / Gartner Peer Insights, customer-led growth, reference architecture.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/varunk130/ai-gtm-skill-library.git /tmp/ai-gtm-skill-library git -C /tmp/ai-gtm-skill-library sparse-checkout set "revops-skills/customer-advocacy" mkdir -p ~/.claude/skills/customer-advocacy cp -R "/tmp/ai-gtm-skill-library/revops-skills/customer-advocacy/." ~/.claude/skills/customer-advocacy/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from varunk130/ai-gtm-skill-library/blob/90e878c73a8fbfd1cab864424ccf674fdc889157/revops-skills/customer-advocacy/SKILL.md, which is licensed MIT (repository). 883 words, 12 headings.
Customer Advocacy (AMPLIFY Framework)
Design a customer advocacy program that converts happy customers into a predictable supply of references, case studies, peer reviews, and community influence - and ties advocacy activity back to pipeline. AMPLIFY replaces ad-hoc "can you do a quote?" asks with a structured advocate pipeline and an attribution model that earns the program ongoing investment.
Core Principle
Advocacy is a supply chain, not a favor. Most advocacy programs starve sales of references because they rely on relationship taps instead of a managed pipeline. AMPLIFY treats advocates like inventory: sourced, qualified, activated, replenished, and attributed.
The AMPLIFY Framework
| Letter | Stage | The Question |
|---|---|---|
| A | Advocate Identification | Who qualifies, and how is the candidate pool sourced continuously? |
| M | Motion Design | Which advocacy motions are in scope (reference, case study, review, speaker, community)? |
| P | Program Mechanics | What's the recruitment, onboarding, and reward design? |
| L | Library & Inventory | How is the advocate inventory tracked, and what's the SLA for sales requests? |
| I | Influence-to-Revenue | How is advocacy activity attributed to pipeline and revenue? |
| F | Feedback Loop | How is fatigue managed and the candidate pool replenished? |
| Y | Yield Optimization | Which motions and segments produce the highest influence per ask? |
Advocate Qualification
Not every happy customer qualifies. A useful candidate has:
| Dimension | Signal |
|---|---|
| Outcome proof | Quantified business result (revenue, cost, time) |
| Stakeholder fit | Named champion willing and authorized to be public |
| Brand fit | Customer logo aligns with target ICP segments |
| Reciprocity readiness | Willing to participate in ≥ 1 motion per quarter |
| Health stability | Health score green; no active risk plays |
Advocacy Motion Catalog
| Motion | Effort to Customer | Sales Influence | Marketing Influence |
|---|---|---|---|
| Sales reference call | 30 min | Very High | Low |
| Written case study | 2-4 hours | High | High |
| Video testimonial | 1-2 hours | Medium | Very High |
| Peer review (G2 / Gartner) | 15 min | Medium | High |
| Conference speaker | High | Medium | Very High |
| Community AMA / panel | 1 hour | Low | High |
| Quote / blurb | 10 min | Low | Medium |
Design the program so high-effort motions are reserved for top-tier advocates and entry motions (review, quote) onboard new candidates.
Reward Design
Rewards should be professional capital first, perks second.
| Reward Type | Example |
|---|---|
| Professional capital | Speaker slots, byline articles, customer-advisory-board seat |
| Access | Roadmap influence, early access to features, exec relationships |
| Recognition | Awards, MVP designations, named cohorts |
| Perks | Swag, gift cards, event invites |
Library & Inventory Discipline
The advocate library must answer four sales questions in under 2 minutes:
- Who can speak to outcome X?
- Who is in industry Y at size Z?
- Who has not been asked in the last N days?
- Who is currently in a risk play and must not be asked?
Influence-to-Revenue Attribution
| Attribution Lens | Definition |
|---|---|
| Reference-influenced deals | Opportunities that received ≥ 1 reference touch, win-rate uplift vs control |
| Asset-attributed pipeline | Pipeline tagged to a case study, video, or review |
| Advocate-sourced pipeline | Net-new logos sourced from advocate referrals |
| Renewal influence | Renewals with advocacy participation, retention uplift vs control |
Output
Save to outputs/customer-advocacy-[motion]-[YYYY-MM-DD].md
| Artifact | Description |
|---|---|
| Qualification Rubric | Criteria + scoring for advocate candidates |
| Motion Catalog | Named motions with effort, reward, and segment fit |
| Recruitment Funnel | Stages from candidate → advocate → active contributor |
| Reward System | Tiered rewards mapped to motion participation |
| Advocate Library Schema | Fields, SLA for sales requests, fatigue rules |
| Attribution Model | Tagging spec + uplift measurement design |
| Pipeline Dashboard | Active advocates by motion / segment, fatigue heatmap, request SLA performance |
Process
- Define qualification with a written rubric - not vibes
- Pick motions matched to current GTM needs; don't try to run all seven at once
- Design the reward system with professional capital as the lead category
- Stand up the library with disciplined fatigue and request SLAs
- Build attribution tagging before launching motions, not after
- Run yield analysis quarterly and rotate motions / segments
Tips
- Cap asks per advocate per quarter - fatigue silently destroys advocate programs
- Tier rewards so entry motions are easy to participate in
- Never ask an at-risk customer to advocate - coordinate with CS
- Sales SLA on references is the program's most visible KPI
- Case study production is a pipeline, not a one-off project
Pairs With
- customer-success - Source of qualified candidates and health gating
- community-catalyst - Hosts and amplifies advocacy motions
- enablement-forge - Produces the case study and reference assets
- demand-engine - Distributes advocacy assets across channels
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- customer-advocacy by taizen-ai · 8
- customer-research by coreyhaines31 · 45,947
- customer-story-writer by zapier · 329
- find-customer-social-proof by zapier · 329
- customer-deck-builder by zapier · 329
- customer-onboarding by louisblythe · 136
- customer-referrals by louisblythe · 136
- ideal-customer-profile-matching by louisblythe · 136
Need help setting it up?
This page tells you what customer-advocacy does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.