Case studies in proposals answer the question your client asks while reading: has this person done this before, and did it work? Use two or three relevant cases. Give each one context, approach and result. Add one specific testimonial, plus a cited outside source if you're short on cases. Place them after the diagnosis, before the price.
Your proposal can have a sharp diagnosis, a detailed scope, a well-framed price and a clear call to action. None of those answer that question directly.
Proof does. Picked and structured well, it lowers resistance and builds conviction before the number shows up. Missing or sloppy, it leaves the proposal asking for trust without giving a reason.
Why do most proposals get case studies wrong?
Mistake 1: listing every client you've ever had. A wall of logos impresses the person who made it. The client mostly skims it. A long client list proves you've worked before. It doesn't prove results.
Mistake 2: describing the work without the outcome. "We redesigned Company X's website from the ground up." That's process. The client isn't buying process. They're buying an outcome, and without one the case study is just a task list.
Mistake 3: using cases that have nothing to do with this project. An e-commerce case study in a proposal for a dental practice, with no bridge explained, creates distance. The client thinks, "That's nothing like my situation."
Mistake 4: no story. A case study that works has three parts: the problem, what you did, and what changed. Without them, it's a paragraph with a few numbers and no reason to believe them.
What kinds of social proof work in a proposal?
Type 1: the results case study. The strongest. A past client with a similar problem, what you did, and the measurable impact. Structure: the client and the challenge, your approach and why, the result with numbers where you have them.
Example format: "An interior design studio was getting plenty of Instagram leads but closing few of them. We rebuilt their proposal around a tailored diagnosis. Within 60 days, their close rate went from 18% to 34% with the same lead volume." The numbers in your case study have to be your client's, measured.
Type 2: the direct testimonial. The most human. The voice of someone who faced the same decision your prospect is facing now.
A testimonial that doesn't help: "Great work, highly recommend."
One that does: "We stopped losing track of versions, and our time to close went from three weeks to under one." Specifics are what make it believable.
How to collect them: don't ask for "a few words." Ask three specific questions. What was the main challenge before? What changed after? What would you tell someone thinking about hiring us?
Type 3: outside data. Useful for skeptical buyers. When you don't have a case in their industry, a published study borrows authority that doesn't depend on your reputation.
The rule: only use a number with a named source and a link in the same sentence. Who ran the research, when, and how many people it covered. A number without a source is a guess dressed up as data, and a skeptical buyer can tell.
Type 4: the visual portfolio. The most relevant for creative work. Two or three closely matched pieces beat twenty unrelated ones. Each piece needs context next to the image: the goal, the approach and the result. Without it, the work looks good but doesn't sell.
How do you pick the right case study for each proposal?
Picking matters as much as quality. A great case study in the wrong proposal still creates distance. Check three things:
Industry fit: ideally, the same industry as the prospect. If you don't have one, the next best is a client with the same kind of problem in any industry.
Size and context fit: a case from a 500-person company in a proposal for a solo founder can backfire. The prospect thinks, "They're nothing like me."
Outcome fit: the result has to be the kind of result this prospect wants. Impressive numbers on the wrong goal don't sell.
How do you write case studies without perfect data?
When you have hard numbers: use them. Percentages, dollar amounts, time frames. The more specific, the more convincing.
When the result is qualitative: describe it with context. "The client told us scope disputes, which used to come up on most projects, mostly stopped." No number, but a real and specific outcome.
When you're just starting out: use demo, pro bono or personal projects, and say so. "This is a demo project built to show how we approach this kind of problem." Being upfront earns trust even with a thin portfolio.
When the client asked to stay anonymous: describe them instead of naming them. "A healthcare marketing firm with a team of eight…" You keep the context and the result without the name.
Where should case studies go in the proposal?
After the diagnosis, before your approach: it shows you've solved a similar problem. The client thinks, "They get my problem, and they've done this before."
After your approach, before the investment: it anchors value before the number appears. The client weighs the price with the result fresh in mind.
In the "about us" section: two or three structured cases and one or two testimonials, right before the next step.
What to avoid: don't open with case studies, before the diagnosis. A proposal that opens with credentials talks about you before it talks about the client, one of the most common proposal mistakes.
In Nepfy, changing the order takes seconds: in the editor, the Sections tab puts Cases before Investment. After you send, the Nepfy Assistant card flags when nobody reached the price and suggests a next step, such as reordering sections, so you adjust the order based on what the client actually read. See the Nepfy Assistant signals.
How do you ask current clients for case studies and testimonials?
The best time is right after final delivery, or once the first results show up. A natural way to ask:
"[Name], I'm really glad the project got these results. I'm putting together a few case studies for future proposals and I'd love to include ours. Could I send you three quick questions? It takes less than 10 minutes."
The three questions: What was the main challenge before we worked together? What changed after the project? What would you tell someone thinking about hiring us for this? Get their OK in writing before you use their name or company.
What should you check before you send it?
- Two or three cases that match the prospect's industry or problem.
- Each case with context, approach and a specific result.
- Results of the kind this prospect is after.
- At least one testimonial with a name, company and specific result.
- Cases placed after the diagnosis, not at the top.
- A clear bridge when the case comes from a different industry.
- A story, not a list of tasks.
- Outside data, with a source and a link, when your portfolio is thin.
Frequently asked questions
How many case studies should a proposal include?
Two or three well-chosen ones. More than that starts competing for attention with the diagnosis and your approach.
What if a client asked not to be named?
Describe them by industry, approximate size and type of result, and say why: "For confidentiality I can't share the name, but I'm happy to walk you through the process."
Can I use someone else's case study?
Not as proof of your work. Case studies have to be yours. Passing off another professional's results as your own is a fast way to lose the client's trust.
What if none of my case studies are in the prospect's industry?
Use the closest one and make the link explicit: "Different industry, but the [type of problem] is the same one you're dealing with, because…"
Why does proof come before the price?
Trust you ask for rarely shows up. Trust you build comes from evidence: someone who stood where your prospect stands, decided to hire you and got the result they're after.
With that kind of evidence in the proposal, the price stops being the obstacle. It becomes the logical end of a decision the client was already leaning toward.
In Nepfy, the Minimal template already has a Cases section, so you just fill it in. And if you write the proposal with AI, testimonials go in exactly as you typed them: the AI never writes a fact.
Start free: 14 days of Pro, no credit card.
