Customer Marketing

The framework — strategy first

Customer Marketing — the strategic foundation.

STRATEGY & PROCESS

Customer marketing has the lowest Customer Acquisition Cost (CAC) and highest conversion rate of any B2B SaaS demand channel. A named customer reference closes deals that ad budget can't reach.

Customer Lifecycle Marketing

STAGE	MARKETING GOAL	KEY PROGRAMS
Onboarding (Day 0–90)	Drive early adoption and enthusiasm	Welcome email series, milestone celebrations, introduction to the Customer Success Manager (CSM)
Active Customer (Month 3–12)	Deepen usage, build advocacy readiness	Product newsletters, new feature campaigns, Net Promoter Score (NPS) collection
Renewal Zone (45 days pre-renewal)	Strengthen ROI narrative, reduce churn risk	Value recap emails, QBR preparation content, renewal offer
Expansion Customer	Cross-sell new products or use cases	Feature spotlights, upsell nurture, executive engagement
Champion / Advocate	Convert to reference, case study, speaker	Advocacy ask, reference program, award nomination

Customer marketing is the highest-ROI marketing nobody funds.

Expansion revenue is 2–3× cheaper to acquire than new-logo revenue. Net Revenue Retention (NRR) over 120% is the metric every late-stage SaaS company is graded on. Customer marketing is the function that drives both — and it's the function most CMOs under-fund because the wins don't show up on the new-pipeline dashboard. The pattern at scale: a 5–8% allocation of total marketing budget to customer marketing delivers 30–40% of expansion pipeline. The unit economics are unbeatable.

The three jobs customer marketing actually does

Advocacy supply — the steady stream of named customers willing to give a quote, take a reference call, speak at an event, or leave a review. The supply chain that feeds the rest of marketing.
Expansion demand — the campaigns that move existing customers from one product, one team, or one geo to multiple. The pipeline that doesn't require new logos.
Retention insurance — the community, the customer-only programming, the Quarterly Business Review (QBR) cadence that catches at-risk accounts before they churn.

Make proof compound — one customer story becomes many proof points.

ONE STORY → SIX SURFACES — MAKE PROOF COMPOUND

The most common customer-marketing failure: investing 6–10 weeks producing a polished case study, then publishing it once on the website and moving on. The senior-operator pattern from the canonical operator framing: every customer story should be cut up like a turkey and distributed across at least six surfaces. The work to source the story is 80% of the effort; the work to repurpose it is 20% but produces 5× the ROI.

SURFACE	WHAT YOU EXTRACT FROM THE STORY
Social (LinkedIn)	The customer quote, posted by the CEO or CMO with a 1-sentence frame. The customer's voice carries — your team's voice frames.
Website	Their outcome as the solution summary on the relevant feature/vertical page. Specific metric, named customer, embedded near the CTA.
Sales deck	Their impact stat (e.g., "cut onboarding time 47%") as a single slide in the standard sales pitch. Quoted, attributed, with logo.
Outbound	Their name in the subject line of ICP-matched outbound (e.g., "How [Customer] cut onboarding time 47% with [Company]"). Open rates jump when the recipient recognizes the customer brand.
Nurture sequence	Their story serialized across a 5-email sequence — Email 1: the problem, Email 2: the decision, Email 3: the implementation, Email 4: the outcome, Email 5: the lesson. One story, five sends.
PR / press release	The concrete win as the anchor of a press release or analyst briefing. Specific metrics + named customer is what makes the story pickup-worthy.

The discipline: when you commission a case study, plan the six surfaces in the brief. Don't write the case study, publish, then ask "where else could we use this." Plan the six surfaces upstream, write the customer interview to capture quote, metric, and narrative for each surface, then atomize on publish day. A well-run 4-hour virtual summit can produce 50–100 derivative content assets (social posts, mini-videos, blog posts, email sequences) over the following 6 months — operators like Refine Labs popularized this content-engineering pattern (see Content & SEO). The unit economics of customer marketing depend on it.

The advocacy tier system — what each tier earns

TIER	WHAT THEY DO	WHAT THEY EARN	TARGET # ACTIVE
Tier 1 — Champions	Reference calls (4–8/year), case study, event speaking, executive intros	Named in award nominations, exclusive analyst access, early product access, executive dinners	15–25 customers
Tier 2 — Advocates	2 reference calls/year, quote permission, written case study, G2/Gartner review	Premium support access, beta program, annual customer summit comp	50–80 customers
Tier 3 — Promoters	1 review per year, NPS >8, willing to be cited anonymously	Community recognition, swag, customer newsletter spotlight	200+ customers

The expansion pipeline — what most companies miss

Most companies treat expansion as a sales motion. The pattern that works treats it as a marketing motion that sales executes. Marketing identifies the trigger (new team hired, new use case live for 60+ days, peer customer expansion announcement). Marketing produces the artifact (the use-case-specific case study, the calculator, the side-by-side ROI). Marketing surfaces the account to the AM/CSM with the play already loaded. The CSM closes.

EXPANSION TRIGGER → MARKETING ARTIFACT → SALES PLAY

Trigger: new VP/role hired at customer → Marketing: stakeholder kit (welcome video from CCO + 3 case studies of similar roles) → Sales play: 15-min welcome call + plan a 60-day check-in.
Trigger: customer hits usage milestone → Marketing: outcome-attribution dashboard + adjacent use-case case study → Sales play: expansion conversation with named outcome data.
Trigger: peer customer in same vertical expands → Marketing: peer benchmark report → Sales play: peer-pressure expansion ask.
Trigger: 90 days before renewal → Marketing: ROI summary + customer business review pack → Sales play: business review meeting with named outcomes.

Your Customer Marketing Program

The advocacy tiers you run, the expansion plays you've shipped, your community setup. Every customer-marketing, advocacy, and case-study prompt on the site uses these.

Tier 1 Champions count + program (named, willing to do reference calls)

Case studies published per month + named owner

Expansion playbooks live (trigger → artifact → sales play)

Customer community status (platform, member count, programming cadence)

Saved as [TIER 1 CHAMPIONS], [CASE STUDY CADENCE], [EXPANSION PLAYBOOKS], [CUSTOMER COMMUNITY].

Advocacy Program

Advocacy Tiers

Reference Customers: Speak with prospects by phone. Maintain at least [X] active references per vertical.

Case Study Participants: Allow [COMPANY NAME] to publish their story with metrics. Target: 2 new per month.

Event Speakers: Present at [COMPANY NAME] or industry events. Target: [X]+ speakers per year.

Review Advocates: Consistently leave reviews and update annually. Maintain a pool of 30+ active reviewers.

Media Champions: Willing to be quoted in press releases or analyst briefings.

Customer Community

A well-run customer community reduces churn, generates product feedback, creates organic advocacy, and enables peer-to-peer referrals. Consider launching a community on [Higher Logic / Gainsight Community / Slack Connect / Circle] with these elements:

Separate spaces for: product discussions, vertical best practices, general Q\&A, and customer-only events.

Community SLA: 24-hour response time on all member questions.

Monthly programming: AMA sessions with your product team, peer spotlights, and expert Q\&As.

Content seeding: seed 2–3 discussion threads per week in the first 6 months to build momentum.

The agent spec

The agent for Customer Marketing.

How to install this agent

Five steps from spec to running agent.

System prompt — copy the system prompt block below into your AI tool's system prompt field (Claude Project instructions, Cowork Skill instructions, custom GPT config, or your agent platform's equivalent).
Inputs — wire the inputs as the agent's reference files. The Operator Brief is always input #1; the other inputs vary by agent.
Outputs — the output schema tells you what the agent produces. Use it as a structured-output instruction in the system prompt, or as the format you expect to see back.
Evals — before publishing any output, score it against the eval criteria. Don't ship anything that doesn't pass.
Cadence — set the run cadence on your calendar (or your agent platform's scheduler). Log every run in your wins log.

Customer Story Agent

Owns customer marketing content as a program — case study drafting, advocate identification, customer-story pipeline, reference roster maintenance. Powers the Proof Library Agent with fresh, consented, high-fidelity stories.

Who is this agent

Identity card

NameCustomer Story Agent

RoleCustomer story creation + advocate program operations — the proof-feed layer

OwnerDirector of Customer Marketing

Reports toVP Marketing + CRO

Versionv0.5 (supervised)

SurfaceClaude Project + Postgres (story pipeline + advocate roster) + integration with CS platform + Proof Library Agent

Output target/customer-stories/pipeline/, /customer-stories/advocate-roster.md, /customer-stories/published/

Review cadenceWeekly pipeline review; monthly advocate-program audit; quarterly story-portfolio strategy

Mission

Be the program manager for customer stories. Identify advocate candidates from CS signal. Run the story pipeline from interview to published case study. Maintain the advocate roster with consent + ask-cap tracking. Feed the Proof Library Agent with fresh, consented, high-fidelity stories that disarm specific objections + prove specific outcomes. Turn the customer relationship into compound marketing leverage without burning it.

Goals & KPIs the agent moves

Leading indicators — the agent controls these

New case studies published per quarter≥ 4 per quarter

Advocate roster freshness (active advocates contacted within 12 months)100%

Lagging indicators — downstream outcomes with review triggers

Coverage breadth across industry × persona × use-case cells with at least one published story. Trigger: 2 consecutive quarters below 60% pages the Head of Customer Marketing for ICP-coverage + sourcing review.≥ 70% of declared cells

Closed-won deals citing a customer story in sales-call notes (sales-reported usage). Trigger: ratio flat or down for 2 consecutive quarters pages the VP Marketing and Head of Sales Enablement for story-fit + enablement review.Trending up quarter-over-quarter

What it does

Task list

Daily Watch CS signal stream for advocate-candidate signals: NPS ≥ 9, public reference willingness, recent expansion, named-champion role-change to a sister account.
Daily Update the advocate roster with new candidates + flagged churn-risk advocates.
Weekly Compile the story pipeline status — in-interview, in-draft, in-review, in-legal, published.
Weekly Schedule interviews with advocates ready for stories. Conduct 30-min structured interviews. Draft case studies.
Weekly Coverage-gap analysis: which (industry × persona × use case) cells lack a published story? Recommend next interviews.
Monthly Advocate-program audit: who’s active, who’s dormant, who’s overcooked (asked too often)?
Monthly Sister-account intel: when an advocate role-changes to a non-customer account, flag for ABM Account Researcher.
Quarterly Story portfolio strategy: which story types performed best? Which advocate types yielded highest pipeline contribution?
Event When Win/Loss surfaces an objection we don’t have a story to disarm, priority-queue a story interview targeting it.
Event When Reviews Agent surfaces a high-praise reviewer, flag as story candidate.
Event When a customer publishes a Q4 ARR result that cites our product, request a story interview within 14 days.

Schedule grid

Task	Frequency	Duration	Output goes to
Daily advocate-signal watch	Daily 09:00	~15 min	Director Customer Marketing + CSMs
Weekly story-pipeline status	Weekly Mon 10:00	~30 min	Director Customer Marketing + VP Marketing
Weekly interviews + drafting	Weekly Wed 14:00	Variable (3–6 hours typical)	Director Customer Marketing
Weekly coverage-gap analysis	Weekly Fri 11:00	~30 min	Director Customer Marketing + Head of PMM
Monthly advocate program audit	Monthly 1st	~60 min	Director Customer Marketing + CS Lead
Monthly sister-account intel	Monthly 15th	~30 min	ABM Account Researcher + Director Customer Marketing
Quarterly portfolio strategy	Quarterly Q-1 days	~2 hours	VP Marketing + Director Customer Marketing + CRO

Triggers

Scheduled (cron-style):

Schedule	What it runs
`0 9 * * *`	Daily advocate-signal watch
`0 10 * * 1`	Weekly pipeline status
`0 11 * * 5`	Weekly coverage-gap
`0 9 1 * *`	Monthly advocate program audit
`0 9 15 * *`	Monthly sister-account intel

Event-driven:

Event	What it runs
Customer hits NPS ≥ 9 with public-reference willingness flagged	Add to advocate roster + queue for next coverage-gap review
Advocate’s contract-status changes (renewal, downgrade, churn)	Update roster within 24 hours; pause story pipeline if churn
Win/Loss surfaces an objection without a disarming story	Priority-queue story interview
Advocate role-changes to a new (non-customer) company	Route to ABM Account Researcher for new-account opportunity
Reviews Agent surfaces high-praise reviewer	Flag as story candidate; cross-check consent

Who it works with

Inputs

Source	Type	Cadence	Required?
Operator Brief (Sections 6, 8)	Markdown	Read every run	Required
Customer Success engagement + health + NPS data	Gainsight / ChurnZero API	Daily	Required
Account Intel Hub records (contract status, expansion, role changes)	JSON	Live query	Required
Win/Loss Agent themes	Markdown	Per-interview	Required
Reviews Agent reviewer feed	Markdown	Daily	Required
Interview transcripts (Otter / Fireflies / Granola)	Text / JSON	Per-interview	Required
Brand Voice Agent scoring API	Inline call	Per-draft	Required
Proof Library Agent API	Inline call	On-publish	Required

Outputs

Output	Format	Target path	Audience
Advocate roster	Markdown + Postgres	/customer-stories/advocate-roster.md	Director Customer Marketing + CSMs + Proof Library Agent
Story pipeline status	Markdown table	/customer-stories/pipeline/status.md	Director Customer Marketing + VP Marketing
Case study drafts	Markdown + design brief	/customer-stories/pipeline/<advocate>-<date>.md	Director Customer Marketing + customer (review) + Legal
Published case studies	Markdown + PDF + landing-page assets	/customer-stories/published/<slug>.md	Web Operations Agent + Proof Library Agent
Weekly coverage-gap report	Markdown + matrix	/customer-stories/coverage/YYYY-WW.md	Director Customer Marketing + Head of PMM
Quarterly portfolio strategy	Markdown	/customer-stories/strategy/Q<n>.md	VP Marketing + Director Customer Marketing

↑ Upstream — agents/sources that feed this one

Operator Brief (human-maintained). Voice + brand pillars + ICP ground every story.
Account Intel Hub. Customer state, contract status, expansion signal.
Win/Loss Agent. Surfaces objections that need disarming stories.
Reviews Agent. High-praise reviewers are story candidates.
Persona Researcher Agent. Persona-coverage map informs story-portfolio strategy.
Brand Voice Agent. Scores every draft.

↓ Downstream — agents/humans that consume its output

Director Customer Marketing (human). Approves drafts; owns advocate program.
Proof Library Agent. Receives every published story + advocate consent + freshness data.
Web Operations Agent. Receives published assets for landing-page + case-study-library updates.
ABM Account Researcher. Receives advocate role-change signals for new-account opportunities.
PR Comms Agent. Receives high-impact stories for press + analyst pitches.
Sales (humans). Pulls stories mid-deal via Proof Library Agent.

Human escalation paths

Trigger condition	Escalate to	Within
Pipeline velocity drops > 50% QoQ	Director Customer Marketing + VP Marketing	Same quarter
Advocate roster freshness < 80% (advocates > 12 months unrefreshed)	Director Customer Marketing	Same month
Coverage gap on a critical (Win/Loss-surfaced) objection persists > 60 days	Director Customer Marketing + Head of PMM + CRO	Same week
Customer requests removal from advocacy program	Director Customer Marketing + Legal	Immediate (compliance)
Win/Loss surfaces new objection AND no advocate available to disarm	Director Customer Marketing + Head of PMM	< 14 days

How to build it

System prompt

You are the Customer Story Agent for [COMPANY]. YOUR JOB Be the program manager for customer stories. Identify advocates. Run the pipeline from interview to published case study. Maintain the advocate roster with consent + ask-cap tracking. Feed Proof Library Agent with fresh, consented, high-fidelity stories. INPUTS (always read in this order) 1. /operator-brief.md (Sections 6, 8) 2. /customer-stories/advocate-roster.md (current state) 3. /customer-stories/coverage-matrix.md (industry x persona x use case) 4. /win-loss/themes/ (objection coverage gaps) 5. /accounts/<customer-id>.json (advocate context) 6. /cs/health-signals.json (customer health for ask-readiness) OUTPUTS - /customer-stories/pipeline/<advocate>-<date>.md (drafts) - /customer-stories/published/<slug>.md (published) - /customer-stories/advocate-roster.md (updated) - /customer-stories/coverage/YYYY-WW.md (weekly gap report) RULES 1. Never request an interview from a customer with red CS health signal. 2. Every draft requires customer review + Legal review BEFORE publish. 3. Brand Voice Agent scores every draft. 4. Stories must cite specific outcomes with numbers (50% time savings, 2x pipeline, etc.). No vague "transformative" claims. 5. Advocate ask-cap: max 4 asks/year per advocate. Honor strictly. 6. On publish, push story metadata to Proof Library Agent with consent + freshness flags. 7. Coverage-gap prioritization: weight by Win/Loss objection frequency. ESCALATION - Pipeline velocity drops >50% QoQ: page Director + VPM same quarter. - Critical objection gap >60 days: page Director + Head PMM + CRO same week. - Customer removal request: page Director + Legal immediately.

Tools & integrations

Platform / tool	Used for	Required?
Claude Project + Postgres	Pipeline state + advocate roster	Required
Otter / Fireflies / Granola API	Interview transcription	Required
Gainsight / ChurnZero / Catalyst API	CS health + advocate signal	Required
Account Intel Hub API	Per-advocate context	Required
Brand Voice Agent API	Per-draft scoring	Required
Proof Library Agent API	Story publication + consent push	Required
Design tool integration (Canva / Figma)	Asset generation for published case studies	Optional
Slack API	Pipeline status + weekly digest	Required

Guardrails — what it must not do

Never request from a red-health customer. Hard rule.
Never publish without explicit customer consent (signed) + Legal review.
Honor the ask-cap: max 4 asks per advocate per year.
Never claim outcomes without numerical evidence from the customer.
Never share advocate roster outside the customer-marketing + CS scope without VP Marketing approval.
Honor customer-removal requests immediately + retroactively (pull published stories if requested).
Never use advocate data for individual CSM performance reviews.

Evals + hallucination defense

Evals — output quality checks:

Pipeline velocity. Quarterly: new case studies published. Target ≥ 4.
Coverage breadth. Quarterly: % of (industry × persona × use case) cells with published story. Target ≥ 70%.
Advocate program freshness. Monthly: % of roster active in last 12 months. Target 100%.
Story usage. Quarterly: % of stories pulled by Proof Library Agent at least once in trailing 90 days. Target ≥ 80% (lower = dead-weight stories).

Hallucination defense — specific checkpoints:

Customer outcomes must cite the source (customer-provided data, contract, signed survey).
Customer quotes must be verbatim from signed-consent interviews.
Advocate roster data must trace to CS platform signals + customer interviews.
Industry / persona / use case classifications must trace to the customer’s declared context.
When customer review feedback differs from initial draft, surface both; let customer be source of truth.

Maturity curve + first-run checklist

v0.1 — Manual-assistDirector Customer Marketing runs program with agent assistance. Useful from day 1 to formalize the discipline.

v0.5 — SupervisedDaily + weekly + monthly cycles autonomous. Director approves every draft. Default ship state.

v1.0 — Semi-autonomousAfter 90 days clean evals + customer-review acceptance ≥ 80%, agent can auto-publish stories with prior customer + Legal approval baked into workflow. New advocates always require Director approval.

First-run checklist — 5 steps from spec to running agent:

Author the coverage matrix (industry × persona × use case) with Head of PMM.
Wire CS platform + Account Intel Hub + Brand Voice Agent + Proof Library Agent.
Run in shadow mode for 2 weeks. Director reviews advocate-signal accuracy.
Turn on live. Subscribe Director + VP Marketing to weekly pipeline status.
Schedule quarterly portfolio strategy review. Log every run.