Case studies and proof in a proposal

Every proposal a client receives says some version of "experienced, reliable, detail-oriented". None of it is checkable, so none of it counts. What does count is a short account of a client like them, a problem like theirs and what changed after you worked on it. That is a case study, and in a proposal it should be shorter than you think.

This playbook is about the proof section of a freelance proposal: what to write, where the numbers come from, and what to do when you do not have any yet.

What a proposal case study looks like

It is not a portfolio page. It is 80 to 150 words with four parts: who the client was, what they needed, what you did, and what happened.

[CLIENT, or an anonymised description: industry, city, size]
[THE PROBLEM, one or two sentences in plain words. What was not working, and why did it matter?]
[WHAT YOU DID, two or three sentences. The specific choices you made, not a list of tasks.]
[THE RESULT, one sentence with a number, a date or a visible change. Only with the client's permission.]
[OPTIONAL: one line from the client, with their name and role.]
[OPTIONAL: link to the full case study.]

Filled in, it might read like this:

Kadam Organics, a Nashik-based D2C brand selling millet snacks online.

Most of their traffic came from Instagram on phones, but the product pages were built for desktop and nearly all visitors left before adding anything to the cart.

I redesigned the product and cart pages for mobile first, moved reviews and delivery dates above the fold, and cut checkout from four screens to two.

In the eight weeks after launch, the share of mobile visitors who completed an order roughly doubled, according to their Shopify reports.

"Neha understood our customers better than our own team did." Rahul Kadam, founder

The client and quote are invented for this example. Yours must be real.

Pick the one that matches

One or two case studies are enough. Five tells the client you could not decide which was relevant. Choose by whichever of these is closest to the client in front of you:

• The same problem (slow checkout, a launch deadline, inconsistent branding), even in a different industry.
• The same industry, so they recognise the situation without explanation.
• The same size and stage. A seed-stage founder wants to see you have worked with another small team, not only a large corporate.

Write each case study once, then keep a few versions with different emphasis, so you are choosing rather than rewriting each time.

Getting real numbers, with permission

The best time to collect a result is a month or two after the work goes live. By then there is something to measure, and the client still remembers you. Ask for the number and for permission to use it in the same message.

Subject: A quick favour about the checkout redesign

Hi Rahul,

It's been about two months since the new product pages went live. I hope they're working well for you.

Two small requests, and either is fine to say no to:

1. Could you share how mobile orders have changed since launch? Even a rough before-and-after from Shopify is useful.
2. Would you be happy for me to describe the project in proposals to other clients, with Kadam Organics named, and with a line or two from you about what it was like to work together?

If you'd prefer I keep the brand anonymous, I'll describe it as "a D2C snack brand" instead.

Thanks,
Neha

Build this into the end of every project. The offboarding checklist includes it as a step, so you do not have to remember.

Keep everything you collect in one place, a simple "proof file" in Notion or a spreadsheet: the client, the problem, what you did, the number, the date, whether you may name them, and any quote. Six months from now you will not remember the details, and the proof file will.

When there are no numbers

Many projects do not produce a clean metric, and some clients will not share theirs. You can still be specific.

Speed and scale are facts: "Designed 40 product images for a Diwali catalogue in six working days." So is scope: "Wrote the full help centre, 62 articles, for a fintech app before its Play Store launch." A before-and-after image, with the client's agreement, often says more than a percentage.

Never estimate a result, borrow one from another project, or round up. Indian business circles are small, and clients do sometimes call the people you list.

Confidential work and NDAs

Read the NDA before you mention a project anywhere. Some allow you to describe the kind of work without naming the client; others forbid any reference. The NDA review checklist shows what to look for. If a description is allowed, anonymise properly: "a Pune edtech company with two lakh learners" rather than a detail that identifies them in one search. If you are unsure, ask the client. Most agree to an anonymised version.

If you are just starting

You have more proof than you think, as long as you label it honestly.

Work from a past job counts, described as your role on a team, without the employer's confidential numbers or client names. A recommendation from a former manager on LinkedIn is a usable testimonial. Pro bono work for a local NGO or a friend's shop is real work with a real client, and can produce a real result. A personal project or redesign concept is fine too, as long as it is labelled as self-initiated and not passed off as client work.

Put the full versions on the club showcase and link to them from your proposals. Members and clients browse it, and it gives your short case studies somewhere to point.

Where proof goes in the proposal

Put the case study right after your approach and before the prices. The client has just read how you plan to do the work; the case study shows it worked before, and then they see what it costs. That order makes the price easier to accept, which is the same idea behind anchoring your price.

A single short testimonial can also sit just beside the pricing table. Choose one that answers the worry this client is most likely to have: deadlines for a founder with a launch date, communication for a client who has been let down before.

Proof is also what lets you charge more over time. Each strong case study is a reason to raise your rate, and the pricing pillar covers when to do it.

If you only do one thing this week, send the request email above to your two most recent happy clients.