Case Study

Anything the vendor writes reads like the vendor talking, no matter how carefully it's written. Feature lists and product screenshots leave the same question sitting in the reader's head: did a company like mine use this and actually end up better off?

Before there was a document for that, the answer came out of a sales rep's mouth. Ask "is anyone our size running this?" and you'd hear "we have a customer very much like you and they're thrilled." Nobody could take that into a meeting. A story with no company name and no numbers attached puts zero lines on an approval request. The person evaluating the product could like it and still have nothing to hand upward, so the decision slid another three months.

A case study pulls that story out of one person's mouth and fixes it in writing. Who they are, what situation they were in, what they compared the product against, and which numbers moved — all of it attached to a named company. Because the account comes from the side that bought rather than the side that sells, the same claims draw far less suspicion than a product brochure.

One case study runs from the customer's situation to a number, in six pieces.

1. Customer introduction — two or three lines on who they are. Industry, headcount, what they do. Without that the reader has nothing to measure themselves against, and "a technology company" gives them nothing.
2. The problem before — what hurt, described the way that company describes it. Not "collaboration was inefficient" but "meeting notes lived in personal note apps, so finding last month's decision took half an hour."
3. How they chose — what they compared and why this won. This is where a reader running the same comparison right now recognizes their own position.
4. The rollout — when it went in, how, and how many people started using it. Anyone worried about the cost of switching needs this, so the timeline goes in as a number: "two weeks with three teams, then company-wide" is enough.
5. Results — the numbers before and after, side by side. Meeting hours per week down from six to four, or the half hour spent hunting for a document down to three minutes. Without this part, everything else adds up to a testimonial.
6. Customer quotes — one or two lines from an actual user. A name and a job title make it read as a quote; anonymized, it reads like something the marketing team wrote.

The order holds because it matches the order the questions arrive in. Whose story is this, was it my problem, why this product, how long did the switch take, what changed. Lead with the results and the numbers arrive before any reason to believe them, which is exactly when a reader starts discounting them.

A content marketer usually writes it, but never alone. Half the raw material sits with the customer, so the sales or customer success person who talks to that account every week picks the candidate and sets up the conversation.

The work runs in three steps.

1. Recruiting — find a customer with clear results whose profile resembles the market you're targeting. The most similar account beats the largest one.
2. Interview — roughly forty minutes of listening, collecting the before-state and the numbers. Numbers you don't get here cannot be manufactured later.
3. Approval — send the draft back and confirm you may publish the company name, the quotes, and the figures. Skip this and you'll be taking the page down days after it goes live. Plenty of companies won't disclose absolute figures, so percentages get substituted.

The audience is already down to a short list. Someone who just arrived from a search engine doesn't read another company's rollout story end to end. The people who do are evaluators who have narrowed it to two or three options, plus the budget holder they have to convince. A blog post reaches someone who hasn't named their problem yet; a case study settles the last doubt of someone who has.

That changes where it sits. Under the pricing page, attached to a sales email, in the back of a proposal. It sometimes goes behind a lead magnet — a resource offered in exchange for contact details — but there's little sense in stopping a near-ready buyer at a form, so it usually stays open. When the buyer needs more to justify the spend internally, a whitepaper, a long document treating one subject in depth, goes along with it.

"We need three case studies out this quarter. We have nothing in manufacturing."

Buyers in that industry can't find anyone who looks like them, so fill that gap first.

"Could we turn this account into a case study? The numbers came out great."

Proposing a customer with strong results as the next interview.

"Legal is blocking it, so we're dropping the company name and keeping the industry."

The customer refused attribution, and the team is shipping it anyway knowing it persuades less.

At Pagedeck, Ravi owns two per quarter and Sofia usually supplies the candidates. Hearing "do you have anyone like us?" over and over in sales conversations makes it obvious which industries are missing. Booking the interview, collecting before-and-after numbers on the same basis, and getting the draft approved takes about three weeks.

Once one ships, Sofia attaches it to emails for customers in that industry and Ravi hangs it under the pricing page. That's why both of them look at the industry mix before the count. Five case studies from service companies and zero from manufacturing means that in a manufacturing conversation, five is worth less than one.

The most common misreading is that a case study is a pile of compliments. Since it carries quotes from a happy customer, the assumption is natural enough. But readers don't come to verify praise, they come to compare situations. The more concrete the before-state, and the more honestly the rejected alternatives are described, the longer people read. A page stuffed with nice words doesn't get finished, and sales reps quietly stop sending it, which leaves a document nobody uses. The fix is usually to go back to the interview recording and pull out the parts that sounded awkward at the time — the workaround they lived with for a year, the feature they still wish existed.

The second is that the logo has to be famous. Big names catch the eye and look good in a board deck, so the pull is real. But an evaluator is looking for someone their own size in their own situation. A rollout at a 3,000-person company is somebody else's life to a team of 20. Collect only the big names and the segment that actually signs up has nothing to read.