Strategy · 2026-09-22 · 9 min

Your Case Studies Are Your Outbound: How Dev Agencies Turn Past Work Into Replies

Most dev agency case studies sit on a portfolio page doing nothing. Here is how to turn the work you have already delivered into the research, proof and first messages that open new conversations.

Every dev agency we work with already owns the raw material for a strong outbound programme. It is sitting in the portfolio, gathering dust, formatted for a website visitor who never arrives.

A case study is not a trophy. It is the evidence your first message leans on, the reason a CTO replies, and the only thing that separates you from the hundred other agencies claiming senior engineers and fast delivery. This is how we turn it into pipeline.

Why Case Studies Decide Reply Rates

A technical buyer reading a cold message is running one test: has this agency seen my situation before? Your positioning can promise it. Only a case study can prove it.

When the first message can say "we took a Series A logistics platform from a ten engineer architecture to a forty engineer one, here is what broke first", the conversation starts at a completely different level than "we build scalable web applications". The first is a peer. The second is a brochure.

Mine Each Project for Four Assets

Take your three best delivered projects and extract four things from each:

1. The before state. What was broken, slow or missing when the client arrived. This becomes the problem sentence in your first messages.
2. The decision. What you chose and what you deliberately did not do. This is what senior buyers actually want to read.
3. The outcome, with a number. Revenue, time to market, cost avoided, team size, uptime. If the client will not share numbers, use shape: "three months from kickoff to first release".
4. The situation it matches. Which kind of company, at which stage, has this exact problem right now. This becomes your targeting filter.

That last one is the step everyone skips, and it is the one that matters most for outbound.

Work Backwards From Proof to List

Most agencies build a list first and then look for something relevant to say. Do it in reverse.

Start from the outcome you can prove, then find the companies currently living in the before state. If your best case study is rescuing a legacy migration, your list is companies whose job postings mention the old stack and the new one together. If it is scaling a platform after a funding round, your list is recently funded companies hiring engineers faster than they can onboard them.

This is signal-led list building, and it is why our lists are two hundred accounts rather than two thousand. The proof defines the audience, not the other way round.

The First Message Structure

Once the list is built from the proof, the first message writes itself in three sentences:

1. Their problem, named specifically. "Your postings suggest you are mid migration from X to Y."
2. How you have solved it before. "We ran the same migration for a logistics platform last year without taking the product offline."
3. A clear ask. "Worth an intro call to compare notes?"

No attachments, no deck, no capability list. The case study exists so the message can be short.

Keep Follow-Ups Relevant, Not Generic

The first message is written from scratch for each prospect. The follow-ups can and should be prepared, but they still have to reference the same situation. A follow-up that says "just bumping this" wastes the research. A follow-up that shares one more detail from the matched project, or a written teardown of the problem they are facing, keeps the thread alive.

We send the first messages by hand and run the follow-ups on a sensible cadence through our tooling, because the follow-up's job is timing, not discovery. What we never do is send a generic message with no context and call it personalisation.

Anonymise Without Weakening

Under NDA you cannot name the client. That is not a blocker. "A Series B fintech processing eight figures annually" carries nearly all the weight of a logo, and buyers understand why names are withheld. What kills credibility is vagueness: "a leading company" proves nothing. Specific shape, honest constraint, real outcome. That is enough.

What to Expect

Case-study-led outbound does not compress the sales cycle, because agency engagements are still considered purchases. What it changes is reply quality: conversations start with context instead of suspicion. Expect first replies in weeks two to three, first calls in weeks four to six, and signed work over the following months.

If you would rather have this run for you, that is the whole service. See how it works, the pricing and our own case studies. Related reading: How Dev Agencies Can Use LinkedIn Outbound to Win New Clients and How to Build a LinkedIn Outbound Strategy for a Dev Agency.

Outbound glossary · How it works · Pricing