Customer Marketing: The PMM's Expansion Revenue Playbook

B2B SaaS has a math problem.

The average cost to acquire a new customer is five to seven times higher than the cost of retaining and growing an existing one. In enterprise SaaS, the ratio is often higher. Yet most PMMs spend the overwhelming majority of their time writing acquisition messaging — landing pages, outbound sequences, event content — and almost none of it on the customers already paying them.

This isn't irrational. Acquisition is loud. Pipeline is visible. The demand generation team is asking for copy by Tuesday. Customer marketing is quieter, slower, and harder to measure in a quarterly sprint.

But the companies that win consistently are the ones that treat customer marketing as a core PMM discipline, not an afterthought. Their positioning gets more accurate over time because they're in constant conversation with their best customers. Their sales cycles shorten because their case studies are specific and their reference pipeline is healthy. Their product adoption improves because the enablement they build is grounded in how customers actually use the product.

This is the playbook.

---

Why Customer Marketing Is a PMM Function

Before the framework, the framing problem.

Customer marketing is often owned or claimed by three teams simultaneously: customer success (because they own the relationships), demand generation (because it generates content), and product marketing (because it touches positioning). When three teams share ownership of something, accountability diffuses and the work doesn't get done systematically.

The case for PMM ownership is simple: the programs that work require skills only PMM typically has.

Building a case study that sales teams actually use isn't a writing project — it's a positioning project. You need to understand what the customer achieved, why it matters to the buyer segment you're trying to reach, and how to frame the story against the specific objection the asset is meant to overcome.

Identifying the right reference customers for a specific deal isn't a relationship task — it's a segmentation task. You need to know which customers map to the prospect's segment, size, use case, and evaluation criteria.

Mining community discussions and advisory board sessions for positioning signal isn't a content task — it's a research task. You need to know what you're looking for and how to translate raw customer language into messaging that lands.

This is PMM work. Own it.

---

The Four Programs That Drive Customer Marketing

A customer marketing system has four interconnected programs. Each produces different outputs, but together they create a compounding effect: customers feel like partners, your positioning stays calibrated to market reality, and your sales team has the assets and references they need to close competitive deals.

Program 1: Reference and Advocacy Development

The reference pipeline is where most companies have the sharpest gap between what they need and what they have.

Sales reps need references on demand — a customer in the same industry, at the same company size, with the same use case, available to speak within three to five business days. Most companies have three customers willing to do anything, and they get called for every deal.

When those three references burn out or start giving lukewarm referrals because they've done it 40 times, deals start stalling.

How to build a healthy reference pipeline:

Start early. The best time to identify a potential reference is at the 90-day mark post-onboarding — not at year two when you need one. By 90 days, you know if the customer is achieving the outcome they bought for. If they are, that's the moment to invite them into a more collaborative relationship.

Segment before you recruit. A reference from a 500-person SaaS company means nothing to a prospect at a 20,000-person enterprise bank. Build your reference pipeline by ICP segment: industry, company size, use case, buyer persona. Map your current active references against your current pipeline. Find the gaps. Recruit into the gaps.

Make it frictionless and reciprocal. Customers don't say no to reference calls because they don't like you — they say no because the ask is vague, the time commitment is unclear, and there's nothing in it for them. Be specific: "This would be a 30-minute call, once per quarter maximum, with a prospect in your same industry." And give something back: early product access, advisory input sessions, co-marketing opportunities, executive access.

Maintain the relationship. Don't call references only when you need them. CS and PMM should be touching reference customers quarterly with something valuable — a product insight, an industry benchmark, a preview of upcoming capabilities. When the relationship is warm, the ask is easy.

Track like a pipeline. Every reference should have a status (active, dormant, burned out), a segment tag, and an owner. When sales needs a reference, the match should happen in 24 hours. If it takes a week, deals stall and sales teams stop asking.

---

Program 2: Case Studies and Proof Library

The case study is the most underperforming asset in B2B SaaS. It's the one piece of content that almost every company produces and almost no company does well.

The core failure: case studies are written about products, not about customers.

A customer doesn't care that your implementation took eight weeks. They care whether the outcome they're buying — the thing they're going to tell their VP they achieved — is plausible. And a PMM who writes "Company X reduced processing time with Product Y" is leaving the most important work undone.

The case study formula that gets used:

Open with the business problem in the customer's language. Not "Company X was using an outdated solution." But: "The CFO needed to cut procurement cycle time by 30% before the fiscal year closed, and the current process was adding 14 days per sourcing event."

Show what changed — specifically. Not "they implemented a more modern solution." But: what capability did they use, how long did it take to see the first result, and what did the before/after look like in the buyer's metric?

End with an outcome stat in the language of the economic buyer. Not "users loved the interface." But: "$2.3 million in annualized savings in the first year." Or "67% reduction in sourcing cycle time." Or "procurement headcount stayed flat while managed spend increased 40%." Economic buyers need to see numbers they can defend upward.

Include one quote from the economic buyer. Not the power user who loves the product — the person who wrote the check or approved the budget. That's the voice that converts.

Building the case study system:

Don't build individual case studies. Build a proof library — a searchable, tagged archive of outcomes organized by: industry, company size, use case, outcome type, and buying persona. When a rep is in a competitive deal, they should be able to filter to "Financial Services > 5,000 employees > Strategic Sourcing > procurement cycle time" and get the two or three assets that will land in that conversation.

Conduct formal case study interviews. Don't write case studies from customer emails or support tickets. The best case studies come from a structured 45-minute interview (CS identifies the customer, PMM conducts the interview, covers: the before state, the decision criteria, the implementation experience, and the specific outcomes achieved). Record and transcribe. The raw language from these interviews is your best positioning research.

Refresh on a cadence. A case study that's two years old is a liability in a competitive deal. Prospects ask: "Is this still how the product works?" Build a quarterly review cycle where your top ten most-used case studies are checked for accuracy.

---

Program 3: Adoption Enablement

Expansion revenue requires product adoption. Customers who use 20% of what they're paying for don't expand. Customers who are deeply embedded into the product's core workflows do.

PMM's role in adoption is often misunderstood. It's not about writing feature release notes or help center articles. It's about building the materials that help customers connect product capabilities to the outcomes they care about.

The adoption enablement framework:

Identify the adoption gaps. Work with CS and product analytics to understand where customers drop off in the product experience. Which features are underutilized? Which workflows are common in high-expansion accounts but rare in low-expansion accounts? That gap is the adoption opportunity.

Build outcome-focused enablement, not feature tutorials. The worst adoption content explains how to click buttons. The best adoption content explains: "Here's the workflow that takes the average procurement team from 14-day sourcing cycles down to 5. Here's exactly how to set it up, and here's what good looks like at 90 days." Frame capability in the language of the outcome, not the feature.

Create segment-specific playbooks. A financial services procurement team has different workflows, different compliance requirements, and different success metrics than a tech startup. One-size-fits-all adoption content serves no one well. Build two or three core ICP playbooks and make them the first thing new customers receive after onboarding.

Close the loop with CS. Adoption enablement should be reviewed quarterly by CS. What's working? What are customers ignoring? What questions are they asking that the content doesn't answer? Treat adoption content like a product with a roadmap and iterate based on customer feedback.

---

Program 4: Community-Led Advocacy

Community is the customer marketing program with the highest ceiling and the most patience required. It compounds over time in a way that none of the other programs do.

The goal of a customer community is not to create a support forum. It's to build a place where your best customers connect with each other, share outcomes, develop professional relationships, and become evangelists for a way of working — not just a product.

What makes B2B community work:

Identity and outcome, not product. The communities that grow are built around professional identity and shared ambition, not around being a user of your software. "The Modern Procurement Leader" community is more compelling than "The [Product Name] Users Group." Give members an identity worth having.

PMM drives the content and conversations. Community left to fend for itself dies. PMM should be generating two or three discussion prompts per week — provocative takes, open questions, data points from recent research that invite response. The goal is to make community the most valuable professional learning resource in your buyers' ecosystem, not just a product update channel.

Mine it for positioning signal. Every discussion thread is a window into what your customers care about, what they're struggling with, and how they describe the value of your product to each other. This is research. PMM should be reading community content the same way they read win/loss transcripts — with a notebook open, tagging themes, pulling quotes for the language bank.

Activate advocates for external amplification. Community members who are vocal, articulate, and achieving good outcomes should be invited into your external advocacy programs: speaking at events, contributing to thought leadership, participating in analyst briefings as customer references. This is the flywheel: community builds the relationship, external advocacy amplifies the signal.

---

The Positioning Feedback Loop

Here's the function of customer marketing that most PMMs miss entirely, and it's arguably the most valuable of all.

Your positioning drifts from market reality over time. It starts accurate — built from customer research, win/loss data, and competitive analysis. But markets shift, customer language evolves, and competitors move. If you don't have active feedback mechanisms connected to your customers, your positioning slowly becomes a description of the product you built three years ago.

Customer marketing is your positioning recalibration system.

The language customers use in case study interviews is your most accurate source of messaging copy. When a customer says "we went from guessing at savings to proving them to the CFO," that phrase belongs in your messaging before any variation you could invent internally.

The questions customers ask in community discussions tell you where your positioning is leaving gaps. If customers are consistently asking how your product compares to a specific capability, that's a positioning gap to close.

The outcomes customers cite in NPS qualitative responses are your best proof points. Sort NPS qualitative responses by theme, tag the measurable outcomes, and compare them against what your current case studies and sales assets are using. The gap between what customers say and what your materials claim is your messaging credibility gap.

The objections that surface in customer advisory board sessions are your sales enablement roadmap. When multiple customers cite the same "I had to convince [persona] that this was worth the investment," that's a conversation PMM needs to be having with sales and translating into materials.

Connect these feedback channels to your messaging review cadence. Twice a year, run a positioning audit: pull recent case study interview transcripts, community discussion themes, NPS qualitative responses, and advisory board notes. Tag the language. Compare it to your current messaging house. Update what's drifted. This is how positioning stays current.

---

Measuring Customer Marketing Impact

Customer marketing is easier to measure than most PMMs assume. The challenge is that the metrics don't show up in the same dashboards as demand generation metrics, which is why they often go unmeasured.

Reference health metrics:

• Active references by ICP segment (are you covered for your most common deal types?)
• Reference acceptance rate (when sales asks, what percentage say yes?)
• Time-to-reference-match (how long does it take to find the right reference for a deal?)
• Reference burnout rate (how many times is your average reference used per quarter?)

Proof library metrics:

• Asset utilization rate by segment (which case studies are sales actually using?)
• Case study influence on win rate (do deals where a case study was used close at a higher rate?)
• Case study staleness (what percentage of your library is more than 18 months old?)

Adoption and expansion metrics:

• Feature adoption rate by customer segment
• Correlation between adoption score and expansion rate (this is your proof that adoption enablement is working)
• Adoption of specific workflows vs. expansion rate in the following six months

Community metrics:

• Active participation rate (not total members — active contributors)
• Content sourced from community for positioning updates (how many messaging changes per quarter were informed by community language?)
• Advocate pipeline (how many community members are in active advocacy programs?)

The metric that surprises teams most when they start measuring it: deals where a case study was used in the cycle close at significantly higher rates than deals without one. When you can show that number to your CMO, customer marketing stops being a nice-to-have and becomes a pipeline priority.

---

Where to Start

Customer marketing feels overwhelming as a totality. Four programs, multiple metrics, new cross-functional relationships to build. The PMMs who make progress fast start narrow.

Pick the highest-value gap first. For most companies, it's the reference pipeline — sales is asking for references they don't have, deals are stalling, and the same three customers are getting called constantly. Start there. Map your ICP segments against your current active references. Find the two biggest gaps. Launch a 90-day program to close them.

Once reference health is no longer the crisis, move to case studies. Audit what you have, identify your top three underperforming asset categories (where do prospects ask for proof that you can't provide?), and build toward those.

Adoption enablement and community come after the foundation is solid. Both require internal alignment and ongoing investment. Don't start community until you have someone who can commit to driving it three days per week minimum.

The through-line across all four programs: treat customer marketing as a system, not a project. Projects have end dates. Customer marketing compounded over two or three years is what produces the reference pipeline, proof library, and positioning calibration that makes your company almost impossible to compete against.

---