The Short Case Study: Proof Sized for Proposals and Portfolios

Freelancers love long case studies. They’re satisfying to write: the challenge, the approach, the journey, the lessons, the results. Twelve hundred words of craft, with headers and pull quotes.

Then they attach the link to a proposal, and the prospective client, who is reading eleven other proposals between meetings, skims the first paragraph and moves on.

Long case studies have their place. But much of the time, what a prospect needs is smaller: a short case study, sized to be read in thirty seconds, specific enough to be believable and honest enough to survive a follow-up question. This playbook shows how to write them and where to use them.

Why do short case studies work so well?

Because they match how proof is actually consumed. Prospects evaluating freelancers are scanning for three things: Have you done something like this? What exactly did you do? Can I believe it? A compact card answers all three faster than a long narrative.

Short case studies are also more versatile. One card can go into a proposal, a portfolio grid, a pitch email, a profile on a freelance marketplace or a slide. A long case study usually only fits on its own page.

What do famous short reports have in common?

Brevity in reporting has a distinguished history.

“Veni, vidi, vici.” According to ancient sources, Julius Caesar summed up his swift victory at Zela in 47 BC with three words: I came, I saw, I conquered. It’s a report reduced to its essentials.

The telegram. For roughly a century, telegrams were typically charged by the word, which pushed senders toward ruthless economy. People learned to say exactly what mattered and nothing else.

The Gettysburg Address. Abraham Lincoln’s 1863 speech took only a couple of minutes to deliver, following a much longer oration by Edward Everett. It’s the one people remember.

The short case study borrows the same discipline: essentials only, every word earning its place.

What goes into a short case study?

A strong short case study, or portfolio card, has eight elements:

1. Title: what the project was, in plain words.
2. Client label: the client’s name if you have permission, or an anonymized description like “regional outdoor retailer.”
3. Your role: what you were hired to do.
4. Problem: one sentence on what needed solving.
5. What you did: one or two sentences, specific and concrete.
6. Evidence or results line: what you can show or document.
7. Attribution note: one short phrase putting results in context, if you include results.
8. Link: to the work, a full case study or a relevant sample.

That’s it. Around 100 to 150 words.

How do you handle results in such a small space?

Carefully. A short format tempts people to lead with a big number, because a big number is the fastest way to impress. Resist that unless the number is documented.

A good rule: include at most one metric, and only with a source. If the client reported a figure and gave you permission to share it, use it with its timeframe. If not, keep the evidence line qualitative and specific:

• “Delivered 24 product guides on schedule across a six-month engagement.”
• “Rebuilt the onboarding email sequence; the client adopted it as their standard template.”
• “Interviewed four engineers to produce the company’s first technical explainer series.”

Specific qualitative evidence is often more persuasive than a vague number. “Improved engagement” says nothing. “Client adopted it as their standard template” says a lot.

What does an illustrative short case study look like?

Here’s an example for a fictional engagement:

Product guide series for a regional outdoor retailer. Role: freelance writer and editor. The retailer’s buying guides were outdated and inconsistent across categories. I interviewed store staff, built a shared guide template and wrote 12 new guides over four months, each reviewed by a category specialist before publishing. The client now uses the template for all new guides. [View two sample guides →]

That’s 72 words. It answers what, how and why believe it, without a single invented number.

Where should short case studies appear?

Six places where they consistently earn their keep:

• Proposals: two or three cards relevant to the prospect’s problem.
• Portfolio pages: a grid of cards, each linking to a full case study or sample.
• Pitch emails: one card, pasted directly into the message.
• Freelance marketplace profiles: where space is tight and scanning is fast.
• Sales conversations: read aloud in under thirty seconds.
• Your About page: a few cards that show range.

How do you choose which cards to include?

Match the prospect, not your pride. The project you’re proudest of may not be the one most relevant to the person reading. For each proposal, pick the cards that most closely mirror the prospect’s industry, problem or format. Two relevant cards beat five impressive but unrelated ones.

Keep a library of cards, maybe a dozen, tagged by industry, format and problem type. Assembling a proposal then takes minutes.

What about clients who won’t be named?

Anonymize thoughtfully. Use a description that’s specific enough to be meaningful: “a B2B software company with a small marketing team” says more than “a tech client.” Don’t invent a fake logo or a fake name. And make sure details in the card can’t easily identify a client who asked to stay anonymous.

If a client hasn’t given permission at all, the card stays private, or out of your portfolio entirely. When permission is unclear, anonymize or hold the card until the client confirms.

What if you don’t have results at all?

Write the card around process and artifacts instead. Prospects often care more about how you work than about a number they know depends on many factors. A card that shows clear thinking, a defined process and real deliverables is a strong card.

For engagements where results aren’t available, an honest alternative format, focused on the problem, your approach, your decisions and your artifacts, keeps your portfolio truthful and still persuasive.

How do you turn a long case study into a short one?

If you already have full case studies, you have raw material for cards. Work through each one with five cuts:

• Cut the backstory to a single problem sentence.
• Cut the process narrative to one or two concrete actions, the ones a prospect would find most relevant.
• Cut every result but the strongest documented one, or switch to a specific qualitative line.
• Cut adjectives. “Comprehensive,” “innovative” and “seamless” add words and remove credibility.
• Cut the lessons section entirely. Cards are proof, not reflection.

What’s left is usually around a hundred words. Read it aloud. If it takes longer than thirty seconds, cut again.

Going the other direction works too. When you finish a project, write the short card first, while details are fresh. It forces you to identify the essential story, and that clarity makes the full case study, if you write one, much easier.

How do you keep a card library current?

Review it quarterly. Retire cards for work that no longer represents what you offer, update links that have moved and add cards for recent projects. Tag each card by industry, format and problem type, and note its permission status and the date permission was confirmed. A card library is a small asset that compounds: each proposal gets faster and more targeted than the last.

What mistakes make short case studies less credible?

Six to avoid:

1. Round, unsourced numbers. “Increased traffic by 200%” with no timeframe or source raises eyebrows.
2. Taking sole credit for team outcomes.
3. Vague verbs: “helped,” “supported,” “partnered.” Say what you did.
4. Jargon-heavy titles. Use plain words.
5. No link. Give skeptical readers somewhere to verify.
6. Too many cards. Curate.

How does the Case-Study Kit help?

The Content Portfolio Case-Study Kit includes a dedicated Short Case Study template alongside the full template, so you can produce both from the same evidence. It starts with Evidence Collection and a Permission & Anonymization check, so every card is built on things you can show and are cleared to share. An Honest Alternative template covers engagements without publishable results, and the fictional Lumen Harbor example, which contains zero performance statistics, shows how strong the result can be without them.

The 11-page guide explains each template and how to keep cards credible, and Markdown versions make it easy to keep a card library in Notion, Obsidian or a plain document.

Quick answers

How long should a short case study be?

Roughly 75 to 150 words. If it’s longer, it’s becoming a full case study.

Should every short case study link to a long one?

Not necessarily. A link to the work itself or a relevant sample is often more useful.

How many cards should a portfolio have?

Enough to show range, few enough to scan. Six to nine is a comfortable grid for most freelancers.

Make proof easy to read

Prospects don’t owe your portfolio their afternoon. Give them proof sized for the time they actually have: specific, compact and true. A library of short case studies turns every proposal into a quick, confident match between their problem and your record.

Get the Content Portfolio Case-Study Kit and write three short case studies this week from projects you’ve already finished. Your next proposal will be shorter, sharper and easier to say yes to.

You’ll find the Case-Study Kit, short and full templates together, on Content & SEO Workflows.