ConsultantStack

Positioning · 2026-11-13

Turning a Finished Project Into a Case Study With Real Numbers

You finished something that worked. Six months later you cannot describe it in a sales conversation, because the details are gone and the only number you remember is the fee. So you say "I did a pricing project for a client" and watch the interest leave the room.

A case study is not writing. It is retrieval: pulling numbers out of a finished project while the arithmetic is still recoverable, and writing them down in a form one client can read. Do the retrieval once, at the end of the project, and it takes thirty minutes. Do it a year later and it is impossible.

What makes a case study credible

Credibility comes from specificity that a stranger could have observed, not from adjectives. Compare:

  • "Helped the client improve their pricing strategy."
  • "Repriced 11 product lines using a 4-band model; the bottom three bands were unprofitable after support costs, and two were discontinued."

The second sentence can be argued with. That is what makes it credible. It commits to a number, a method and an outcome, and a reader can see that something actually happened.

The five numbers to capture before you close the project

Write these down on the last day, not later:

  1. The starting state. A number, not a description. "4 quotes a month, 1 accepted" beats "low conversion".
  2. The change you made. The specific intervention, in one line.
  3. The end state. The same measure, after. Same units, or the comparison is meaningless.
  4. The cost of the work. Hours or fee, whichever you can publish. If neither, say "flat fee" without the number — but say it.
  5. The duration. From kickoff to delivery, in calendar time. This is the number clients use to judge whether they can fit you in.

If you cannot get number three yet, the case study is not ready. Publish the first two as a "what we did" note and finish it when the outcome arrives. An unfinished case study with a real starting state is still more useful than a finished one with invented results.

Get permission the simple way

Ask at handover, not later, and make it easy to say yes:

"I would like to write this up as a short case study — two paragraphs, the numbers we used, no client name unless you want it. I can send you the draft before it goes anywhere."

Three things make this easy to accept: it is short, the client is unnamed by default, and they see it before publication. If they say no, ask whether you can publish the method without the numbers. Usually they will agree to that, and a method case study is still worth writing.

Never publish a client's numbers without permission, and never publish a memorable number you did not measure. A case study that turns out to be wrong costs more than no case study at all.

The shape that reads well

Four sections, in this order, and short enough to read in two minutes:

1. The situation, in one paragraph. Who, what the work was, and the one number that was wrong.

2. What we did, in three bullets. The intervention, the method, the thing that was unusual.

3. What changed, in a table. Before, after, delta. Three rows is plenty.

4. What it cost and how long it took. Honest, including what was harder than expected.

That last section is what separates a case study from a brochure. Clients are deciding whether to hire you, and the two facts they need most — price and duration — are the two most people leave out.

Writing about the parts that went wrong

Include one. Not a confession, a correction: "The first two weeks were spent cleaning data that we assumed was ready; the next project of this shape now starts with a data check." That single line does three things — it explains the duration, it proves you were there, and it tells the buyer what you have fixed.

Case studies without a single difficulty read as marketing, and buyers have learned to discount marketing.

Where the case study goes

Three places, one source:

  • A page on your site, linked from the services page, not buried in a blog archive.
  • A section of a proposal, as proof for the specific claim you are making. Same case study, different sentence quoted.
  • The opening of a sales call, when the client describes a problem that matches one you have already solved.

Write it once in plain text. The site version can have a header and a table; the proposal version is three sentences; the call version is one sentence and a number. All three come from the same thirty minutes of retrieval.

The trap: writing them all at once, later

The temptation is to sit down when you need clients and write five case studies from memory. It does not work — the numbers are gone, so the studies fill up with adjectives, and adjectives do not close work.

The fix is a habit, not a writing session: one page, at project close, with the five numbers and two paragraphs. Ten minutes. Three of those a year is a portfolio.

Related notes