Most proposals have a case study section. It usually sits near the back, three past clients with logos, a paragraph each and a result in bold. Buyers skim it, if they get that far. Case studies in a proposal work much harder when they're picked for this buyer and placed where they prove a point.
Pick for fit
The biggest logo you've worked with isn't always the best proof. A buyer believes a case study when it looks like their own situation. Same industry, similar size, a similar problem, a similar risk. A mid-size regional client who went through the same messy migration will often do more than a famous brand with a different problem.
Use two or three
A long list of past clients reads like a brochure. Two or three well-chosen stories are easier to remember and easier for your champion to repeat. Keep the full client list for a one-line mention or an appendix.
Put each one next to the claim it proves
Skip the standalone case study section. Place each story beside the part of the plan it supports. If you're promising the rollout won't disrupt operations, put the client whose rollout went smoothly right there. If you're asking them to trust your pricing model, show the client who saved money on it. Proof works best at the moment the reader has the doubt.
Tell it in a few lines
A case study inside a proposal doesn't need the full story. Three parts do the job. What the client was dealing with, what you did, and what happened after. Keep it short enough to read without scrolling.
Use real numbers only
If you have a result the client agreed to share, use it and say where it came from. If you don't have a number, describe what changed in plain terms. Never round up, estimate or borrow a figure from somewhere else. A skeptical reader who catches one soft number will doubt every other one.
Get permission, or describe them without the name
Plenty of clients won't let you use their name or pricing. That's fine. Describe them by industry and size, like "a regional hospital system with six sites," and keep every detail true. We work this way ourselves, and we never share a client's name or pricing without permission.
Let them hear it from the client
A short quote from the client, with permission, is worth more than any sentence you write about yourself. Better still is a reference the buyer can call. In a web proposal, a short client video can sit right next to the claim it backs up.
A case study, before and after
Here's a made-up example. A logistics software company wants to show a prospect that its rollout won't disrupt operations.
The usual version sits on page 22. "Client X, a Fortune 500 manufacturer, partnered with us to transform its supply chain. Results included improved efficiency and cost savings." It's vague, it's far from the claim it supports and it gives the reader nothing to repeat.
The rewrite sits right next to the rollout plan. "A regional food distributor with four warehouses switched to our system last spring. We moved one warehouse at a time over eight weeks, and orders kept shipping the whole way through. Their operations director is happy to take a call." Three sentences, all specific, placed right where the reader is wondering if the rollout will hurt them.
Formats that work in a web proposal
A live web proposal gives proof more room than a PDF does. A short client video can play next to the claim. A before-and-after can show the change visually. A quote can appear right when the reader scrolls to the part it backs up. Our read is that this is one of the clearest places a web proposal earns its keep. Keep the PDF version simple, with the quote and the facts in text. For where proof sits in the overall structure, see the business proposal layout we'd use.
Getting case studies clients will sign off on
The best time to ask for a case study is right after a project goes well, while the result is fresh and the client is happy. Ask what you can share and how. Some clients are glad to be named. Others will approve a description without the name. A few will take a reference call but won't sign off on anything written.
Write the short version yourself, send it for approval and keep a record of what each client agreed to. Over time you build a small library of approved proof, sorted by industry, problem and size. When a new proposal comes up, you pick from the library instead of scrambling for something that fits. It also makes the proposal executive summary easier to write, since the one line on why you is already approved.
Questions we hear about case studies in a proposal
How many case studies should a proposal include?
Two or three is usually enough for a big deal. More than that starts to feel like a brochure, and the strongest one gets lost among the rest.
What if you don't have a case study in the buyer's industry?
Pick the closest match on the problem instead. A buyer cares more about whether you've solved their kind of problem than whether the past client sold the same thing. Say plainly what's similar and what's different.
Where should case studies go in a proposal?
Next to the claims they support. Proof placed in the plan, the timeline or the pricing section does more work than proof collected at the back.
The short version
Pick case studies that look like this buyer. Use two or three. Put each one where it proves a point, keep it short and only use numbers you can stand behind.
If you want help building proof into a proposal for a big deal, see the work or start a proposal.
