Customer marketing: the PMM's expansion revenue playbook

Most companies talk to a customer twice. Once to sell, once to renew.

A store's return policy tells you what it thinks of you after the money moved. Thirty days, no receipt needed, we'll take it back opened. Or fourteen days, original packaging, fifteen percent restocking fee, final sale on anything marked down.

Same product on the shelf. Two completely different opinions of the person carrying it out to the parking lot.

Our post-sale programs are a return policy. They tell customers what we actually think of them now that the deal is closed.

Most of ours read like the fourteen-day version.

We know why. Acquisition is loud, pipeline is visible, and demand gen wants copy by Tuesday. Nobody has ever been paged about a quiet customer base.

So the week goes to landing pages and outbound sequences, and the people already paying us hear from us when we want something.

Call that the renewal-only relationship. The only contact is the ask.

Nobody's program

Customer marketing gets claimed by three teams and run by none.

Customer success owns the relationships. Demand gen produces the content. Product marketing touches the positioning.

Shared ownership means the work happens whenever somebody has a spare week, which is never.

It belongs with PMM, and not because of an org chart argument.

A case study sales will actually use is a positioning project. Reference matching is a segmentation problem. Getting usable language out of a community thread is research, and deciding which outcome a buyer will believe is messaging.

All of it is work we already do. We just do it for strangers.

The three willing customers

Every company has three customers who say yes to everything.

They take the reference calls, the webinars, the quote requests, the analyst intros. They're wonderful, and we're using them up.

A rep needs a reference this week. Same industry, same size, same use case. What she gets is the same operations VP she used last quarter, who by now sounds rehearsed.

The repair is unglamorous. Sort references by segment before recruiting anyone, then map the active ones against live pipeline and find the holes.

Recruit into those holes early, around the ninety-day mark, when we can already see whether the customer got what they bought.

Make the ask small and bounded. Thirty minutes, once a quarter at most, with someone in your industry. Vague asks get declined by people who would have said yes to a specific one.

Give something back. Early access, or a seat in the session where the roadmap gets argued about.

A reference we only call when we need one is the renewal-only relationship with extra steps.

Reviews that all sound alike

Scroll the reviews on anything you've bought online lately.

Five stars. Great product, exceeded expectations, shipping was fast, would buy again. Forty of them, and you could swap them between listings and nobody would notice.

So we skip past all forty and hunt for the three-star one. The one that says the drawer sticks and here's the workaround.

That's the review we believe, because it's the only one that risked anything.

Our case studies are the five stars. Company X reduced processing time with Product Y.

Streamlined operations. Improved visibility. Delighted users.

Buyers read those the way we read the fortieth five-star review, which is to say they don't.

The repair happens in the interview, long before anyone opens a doc.

Open with the problem in the customer's own words, from before we tidied them up. The VP had to cut first-response time in half before renewal season, and the triage process was making it worse.

Say what changed and how long it took. Close on an outcome the economic buyer can defend upward to their own boss, not one the power user enjoyed.

Then include the part that was hard. The migration that took two tries. The team that ignored the new workflow for a month.

Nobody has ever been talked out of a purchase by a case study that admitted something.

Once the interviews are good, stop making assets one at a time. Build a library tagged by industry, size, use case, and outcome, so a rep inside a live deal can filter down to the two things that will hold up in that room.

Record every interview. Transcribe it. The finished asset is the smaller half of what we just got.

The features nobody turned on

Customers using a sliver of what they pay for don't expand. Customers whose Monday runs through our product do.

Release notes and help articles belong somewhere else. PMM's job here is connecting a capability to an outcome the customer already wanted.

Find the gap first. With CS and product analytics, look at which workflows show up constantly in accounts that expand and rarely in accounts that don't. That delta is the opportunity.

Then write to the outcome. Not "how to configure routing rules." Here's the workflow that cuts a support team's first-response time in half, here's how to set it up, and here's what good looks like at ninety days.

Build two of those for the segments that matter and hand them over the day onboarding ends.

Community sits in the same category, with one warning. It compounds slower than anything else here and it dies without a full-time driver, so don't start one until somebody can give it three days a week.

When it works, it's because members organized around a professional identity instead of around being users of our software. The modern support leader beats the Product Name user group every time.

The part worth more

But the references and the case studies are the smaller prize.

Positioning drifts. It starts accurate, built from real research, and then the market moves, competitors reposition, and the words buyers use for their own problem change underneath us.

Nothing announces this. One morning the messaging is describing a product we shipped three years ago.

The customers who already bought are the only people who can tell us. They evaluated us, chose us, lived with the choice, and have no reason left to flatter us.

So treat the case study interview as messaging research that happens to produce an asset.

When a customer says "we went from guessing at savings to proving them to the CFO," that sentence beats anything a workshop will generate. Put it on the page unchanged.

The questions customers ask each other show where the positioning leaves a hole. The objections that surface in an advisory session are next quarter's enablement.

Twice a year, pull the transcripts, the community threads, the NPS write-ins, and the advisory notes. Tag the language. Hold it against what we currently say, and fix what drifted.

That's the entire loop, and it costs less than one campaign.

The number to watch

Most of this is measurable. The metrics just don't live on the demand gen dashboard, so nobody looks.

Watch active references by segment against live pipeline. Watch which case studies reps actually send. Watch how much customer language survived into the last messaging update.

One measure matters more than the others. Time from a rep asking for a reference to the introduction landing.

When that stretches to weeks, deals stall and reps quietly stop asking. That's how a reference program dies without anyone filing a report.

Every program here is a line in our return policy.

Write the thirty-day version.

What to do next

If sales keeps asking for references you don't have, and the case studies you do have could belong to any vendor in the category, the problem usually sits upstream of the assets.

A Bare Strategy positioning audit starts by reading what your customers actually say about you and holding it against what you say about yourself. The gap is the work.

If that's where you are, start here. The first conversation is free.