Case studies occupy an uncomfortable position in most SaaS companies' content stacks. They're supposed to prove the positioning with real customer evidence. They're also the content most likely to contradict the positioning, because they feature customers describing the product in their own words — and customers rarely use the exact language the positioning brief specifies. The result is case studies that are authentic but off-positioning, or case studies that stay on-positioning by scripting customer quotes that don't sound like real customers.
Both extremes are failures. The goal is case studies that preserve customer authenticity while reinforcing the positioning's core claims. The four moves below are how this is done without either faking quotes or letting the case study drift.
Our old case studies used customer language verbatim. They were authentic and contradicted our homepage on category noun, ICP framing, and differentiator language — all three. We rebuilt the program around a specific discipline, and the case studies still sound like customers while reinforcing the positioning.
The specific drift pattern
Case studies drift from the positioning brief in four predictable ways.
Drift 1 · Customers use a different category noun. The homepage says "positioning audit"; the customer quoted in the case study says "positioning review" or "messaging assessment." The case study preserves the customer's authentic word choice, which contradicts the canonical category noun.
Drift 2 · Customers describe a narrower problem. The positioning brief's Layer 3 describes a broad strategic problem ("your category vocabulary drifting across surfaces over time"). The customer in the case study describes a narrow tactical problem ("we needed to update our pricing page"). The narrow framing, while true, doesn't reinforce the broad claim.
Drift 3 · Customers credit the wrong differentiator. The brief's Layer 5 claim is about audit speed. The case study customer credits "the ongoing consulting relationship" or "the specific recommendation format." Both may be true; neither matches the brief's anchor claim.
Drift 4 · Customer context doesn't match the ICP. The brief's ICP is mid-market SaaS; the featured customer is a large enterprise or an early-stage startup. The case study exists because the customer is willing to be featured, not because they're the central persona the positioning targets.
Any one of the four drifts reduces the case study's positioning value. All four together produce a case study that technically names the company and the product but doesn't reinforce any of the positioning the marketing team needs reinforced.
The four moves to preserve both authenticity and positioning
Move 1 · Select customers for positioning fit, not just willingness
The first discipline is selection. Case studies should feature customers who match the ICP, used the product for the specific problem the Layer 3 positioning names, and achieved the specific outcome the Layer 5 claim promises. Not every willing customer is a candidate.
This narrows the pool substantially. Most SaaS companies have 20 customers willing to be case-studied but only 5–6 who also match the positioning tightly. The discipline is to pick from the 5–6, not from the 20.
The side effect: you'll have fewer case studies. That's correct. Five well-aligned case studies reinforce the positioning more than 15 off-positioning ones.
Move 2 · Shape the interview to elicit positioning-aligned language
The interview itself can be structured to surface positioning-aligned content without scripting the customer's answers. The specific technique: open-ended questions that anchor to the brief's layers, allowing the customer to express in their own words but within the frames the positioning uses.
The interview questions that preserve both
Move 3 · Edit for clarity, not rewrite for positioning
The case study's written form is edited, not verbatim transcribed. Editing for clarity — removing filler, tightening sentences, fixing tense — is acceptable and necessary. Rewriting for positioning — changing the customer's words to match the brief — is not acceptable because it damages authenticity.
The middle ground: select the quotes that are most naturally aligned with the positioning, edit for clarity, but don't fabricate. A customer who doesn't naturally use the canonical category noun isn't made to. But a customer interview that produces 20 minutes of transcript will usually have at least one natural quote that aligns with each positioning layer — the editor's job is to find those and center them.
We follow a specific rule: we can cut anything and we can compress anything, but we can't add anything the customer didn't say. The rule forces us to either get the positioning-aligned content from the interview naturally, or not to include that positioning layer in the case study at all.
Move 4 · Use the narrative frame to bridge customer language and positioning language
The case study's prose (the parts written by marketing, not quoted from the customer) uses the positioning's canonical language. The customer quotes are authentic. The combination produces a case study that reads authentic at the quote level and consistent at the narrative level.
Example: customer says "we needed to update our pricing page." The case study's narrative frames this as "the team was experiencing the Layer 3 problem of positioning drift, specifically on their pricing page." The narrative bridges customer's specific experience to the positioning's general frame. The customer's quote and the narrative frame work together rather than contradicting.
What the audit looks like
A quarterly case-study audit checks existing published case studies against the current positioning brief. The protocol:
For each published case study:
- Does the customer's profile match the ICP? (score 0–2)
- Does the case study's stated problem align with Layer 3? (score 0–2)
- Does the case study's stated outcome align with Layer 5? (score 0–2)
- Does the narrative prose use the canonical category noun? (binary)
- Does the customer, in quote, use language compatible with the positioning? (score 0–2)
Studies scoring above 8 of 10 points are healthy. Studies scoring below 5 should be either rewritten or retired. Studies in the 5–8 range need targeted updates.
Most companies have case studies from 2–3 years ago that made sense at the time and no longer match the current positioning. Retiring these cleanly (rather than letting them continue to circulate) is usually a positioning-consistency win.
The portfolio view
Beyond individual case studies, the portfolio of case studies tells a collective story. A healthy portfolio has:
- 3–5 case studies featuring customers across the ICP's full range (not just the top-revenue customers).
- Coverage of the Layer 3 problem from 2–3 angles (different buyer personas experiencing the same underlying pain).
- At least one case study with a specific, numeric outcome that supports the Layer 5 claim.
- At least one case study explicitly mentioning the competitive alternative from Layer 4.
Most portfolios fail on the last two. Numeric outcomes are hard to get; competitive-alternative mentions are uncomfortable to solicit. The companies that invest in both produce portfolios that do more positioning work than case studies typically do.
The ongoing relationship
Case-study-aligned customers are worth maintaining. A customer who participated in a case study a year ago can be updated with fresh data ("here's what happened in the 12 months since"), used as a reference call, or refreshed into a new case study angle. The customer relationship is an asset that pays back multiple times if maintained.
The specific discipline: the PMM or content lead keeps quarterly contact with case-study customers. Not sales outreach; relationship maintenance. "Wanted to share how we've been using your story, ask how things are going on your side, thank you again for the original participation." Low-effort, high-value, and the customers appreciate the continued engagement.
Case studies are the most underleveraged positioning asset in most B2B SaaS content stacks. The ones that exist are usually off-positioning; the ones that could be created aren't. Investment in a disciplined case-study program — selection, interview, editing, portfolio curation — produces positioning evidence that no other content type can match. Competitors can claim what you claim; they can't cite your customers saying it.
Message Consistency
Stop your story from drifting across channels, reps, and pages.
Message Consistency audits your own content — site copy, sales decks, help docs — against your positioning pillars and flags where the story has drifted. Catch the inconsistencies before a prospect does.
- ✓Audits site, rep content, and docs against your pillars
- ✓Flags drift before it compounds into lost deals
- ✓Specific fix recommendations, not vague scores
One sharp B2B marketing read, most Thursdays.
Practical frameworks, competitive teardowns, and field observations across positioning, messaging, launches, and go-to-market. Written for working CMOs and PMMs. No listicles. No vendor roundups. Unsubscribe whenever.
Keep reading
7 Signs Your Messaging Is Drifting (And How to Catch It Early)
Messaging drifts the way codebases drift — each local change looks fine; the aggregate contradicts itself. Here are the seven patterns that appear first.
The 30-Day Message Consistency Audit
A four-week, seven-surface audit that finds message drift before the board notices — what to pull, what to score, and the single spreadsheet that makes the patterns visible.
Message Consistency Across 7 Channels (Website, Email, Sales, Social, PR, Support, Docs)
Seven channels, seven owners, seven slightly different stories — and the four-layer reconciliation protocol that keeps the canonical message from fragmenting across them.