Selling an agency without case studies

You can sell agency services without case studies by proving process instead of outcomes: show the mechanism you run, the numbers it is built around, and offer a small, low-risk first purchase that lets the buyer test you cheaply. A case study is testimony; a demonstrated system is evidence, and evidence is harder to fake. Most buyers of agency services have been shown impressive logos before and been disappointed anyway, so the absence of case studies matters less than agencies fear — provided something more verifiable replaces them.

Why don't you have case studies, and does it matter?

The usual reasons are mundane: client NDAs, a recent repositioning into a new sector, results that belong to a previous employer, or work that is genuinely good but confidential. None of these mean the agency cannot deliver. They mean the standard proof format is unavailable, which is a packaging problem, not a capability problem.

It matters less than it feels. Buyers discount case studies heavily because they know how they are made: the best three engagements out of thirty, framed generously, with the failures omitted. What a buyer is actually trying to establish is simpler — does this firm have a repeatable way of producing the result, or did it get lucky once? That question is answered by process, not by anecdotes, which is why the agencies section of Growth Systems by Industry: the UK B2B service firm map treats proof as one component of a pipeline system rather than the foundation of it.

What do buyers actually verify before they buy?

In our experience selling systems work, buyers check four things, roughly in order:

• Specificity. Can you describe their situation more precisely than they can? An agency that says "most 15-person firms in your sector run on referrals and one overloaded account director" has demonstrated more than a testimonial does.
• Mechanism. Can you explain, step by step, how the result is produced — when X happens, then Y follows? Vague method is the real red flag, with or without case studies.
• Numbers. Do you have benchmarks and thresholds you work to? "We expect roughly a 4% positive reply rate and treat below 3% as a signal to fix the campaign" is a claim a charlatan rarely makes, because it is checkable.
• Risk shape. What happens if it does not work? Fixed scope, fixed price and a small first engagement change the buyer's downside more than any PDF of past wins — the same logic that makes hourly automation billing a trap for the buyer in reverse.

What replaces the case study?

Build a proof ladder — a sequence of increasingly committed demonstrations. The mechanism:

1. Document your delivery process as a numbered method with stages, timescales and the metrics checked at each stage. When a prospect asks for proof, then you send the method, not a mood board.
2. Publish your thresholds. When you state in advance what good looks like — reply rates, timelines, review points — then the prospect can hold you to something concrete, and knows you expect to be held to it.
3. Do a small piece of the work publicly. A teardown of the prospect's current setup, a benchmark comparison, a sample list segment — when the buyer sees you operate on their material, then the question "can they do it?" is answered by observation.
4. Sell a paid diagnostic first. A fixed-price audit with a defined deliverable converts "trust us" into "spend a small amount and see". When the diagnostic is credited against the build, then the buyer risks little and you filter for seriousness.
5. Fix the scope and price of the build itself. When the engagement is a defined installation rather than an open-ended retainer, then the absence of case studies stops being a proxy for open-ended risk.

Each rung earns the next. By the time the buyer reaches the build decision, they have watched you work twice.

How does this change your outbound?

It removes the crutch, which improves the writing. Cold emails that lean on "we helped a company like yours achieve 300%" perform poorly anyway, for the reasons covered in cold email etiquette in professional services: claims are cheap and pattern-matched to spam. Emails built on specificity — naming the sub-vertical's actual pipeline pattern, quantifying the cost of the status quo, offering the diagnostic — do not need borrowed logos. The same discipline applies in adjacent sectors with heavier constraints; recruiters, for instance, sell against strict data rules around outreach and still win on mechanism rather than testimony.

What about the "send me some examples" objection?

Answer it honestly and redirect to the ladder: "Most of our work is under NDA, so instead of curated highlights, here is the exact method we would run for you, the thresholds we hold ourselves to, and a £-fixed diagnostic that shows you the findings before you commit to anything." Some buyers will still insist on logos. Those buyers are typically shopping for reassurance rather than a result, and they churn accordingly. The buyers you want are persuaded by the thing case studies were always a weak proxy for: a system they can inspect.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.