Build a Proof Library
Ivona Namjesnik
Clients
Ask most agencies where their proof lives and you'll get pointed to a shared Google Drive. Open it, and it's a graveyard of folders by client name. A few kickoff decks, some project schedules, the odd stray asset. It only gets touched when someone's scrambling to build slides for a pitch.
We know the pattern because we've lived it. You do genuinely great work for a client, you move on to the next thing, and six months later you sit down to write the case study and can't remember the specifics. So you cobble something together, half-invent the details, and ship a thinner version of the truth. That's a missed opportunity, repeated every quarter.
Here's the reframe. Most agencies treat proof as sales collateral, the stuff BD drops in a deck. That's part of it. But proof is bigger than that. Proof is the artifact of your expertise. It's how you make the work you've already done visible and verifiable, and the act of creating it is valuable on its own. It institutionalizes what your agency knows.
Think of it against positioning. Positioning is the claim about what your agency can do. Proof is the demonstration of it. Without proof, positioning is a facade with nothing behind it. That's why it's an investment, not a chore.
Proof has three components: case studies, artifacts, and active references.
Case studies
A strong case study is built on three pieces.
The problem, clearly stated. Not "they needed a new website." What situation was the client in? What were the stakes? What was breaking? Articulating this is itself a display of expertise. It shows you understand what the client's problem actually was.
The methodology. How you approached the work. The diagnostic, the decisions, the trade-offs, the sequence. Not your scope of work copy-pasted, but enough that a prospect can follow it and think, "Okay, this is how they work." This is what separates a case study from a portfolio piece. A portfolio shows what shipped. A case study shows how the team thought.
The outcomes, with evidence. Be specific. "Increased conversion from 1.8% to 3.2% in 90 days," not "improved conversions." And tie the number back to the original problem, because a metric with no context closes no loop. Not every engagement comes with clean numbers. If you have them, lead with them. If you don't, strong qualitative outcomes still carry the story.
Then the things that make it robust: visuals that break up the wall of text, client quotes in the client's own voice, team context so a prospect can picture working with you, and the timeline, especially in pressure-cooker situations. "They needed to re-platform in 100 days, and we did it."
What's easy to miss is how far one case study travels. Sales is the obvious use. But marketing turns case studies into blog posts, social content, conference talks. One of our agencies, Barrel, did a project with a brand involving a Mattel partnership for the Barbie movie, and that case study became a panel at Expo West, with the agency's CEO moderating an on-stage conversation with the client and the partner from Mattel. One engagement, one case study, a stage at a major expo. Case studies also give partners the context to refer you, help prospects find you through search, and orient new hires to what the agency has actually done.
That's why we call it a library, not a folder. And a library only works if you can find things. Most agencies organize by client name and stop. Go further. Organize by wedge, the specific problem that got you in the door: conversion optimization, e-commerce re-platform, lifecycle marketing, brand refresh. Organize by trigger, the situation that made the client act: a Series B raise, a CMO switch, a forced migration. Organize by client type: enterprise, mid-market, SMB, by vertical.
Done that way, sales, marketing, and partnerships can each pull exactly what they need. If it's hard to use or missing context, nobody uses it, and the library dies.
Artifacts
An artifact is a sanitized piece of the actual work that shows how your agency thinks and operates. Where a case study tells the story of an engagement, the artifact is the tangible thing itself, something a prospect can poke around in. Less a claim, more "here's what we actually produce."
A good artifact is representative. It shows how you really work, not a glossed-up abstraction. And ideally it's useful on its own. When a prospect looks at your intake questionnaire or diagnostic checklist and thinks "this is actually helpful for how we should think about this," before they've even hired you, that's the artifact doing its job.
Examples: roadmap templates, diagnostic frameworks, delivery checklists, audit samples, cleaned-up strategy docs, teardowns. It doesn't have to be static. One of our agencies pulls up a live, sanitized dashboard in the sales process so the prospect sees the real thing.
Two principles. Be as specific as possible and share the real thing, because buyers can tell the difference between an actual artifact and a too-sanitized version. And don't be precious. If you're worried a competitor will copy your checklist, you have bigger problems. A checklist isn't what you're selling, and copying it won't outsell you.
Active references
A strong reference is a current or former client who'll pick up the phone and speak credibly about a specific part of working with you. Late in a deal, references often make or break it.
What makes one strong:
Recent. You've talked in the last quarter, and they know what's happening in your world.
Briefed. They know they'll be contacted, by whom, and roughly what they'll be asked. Never blindside a reference.
Scoped to the claim. Match the reference to what the prospect cares about. An enterprise client for an enterprise project, similar work for similar work.
Genuinely enthusiastic. Not someone merely willing to vouch, but someone who loves doing it. With references, if it isn't a hell yes, it's effectively a no. A lukewarm call can hurt you. We've had references go sideways when we were the ones who supplied the name. It happens, and it's avoidable.
The real problem is doing it
None of this is controversial. The hard part is that proof gets created after the engagement, when the energy's moved on and the details have faded. So the whole game is building the habit of capturing it while it's fresh.
A few forcing functions make it nearly automatic.
Capture at the close. For a project, start drafting in the final two weeks and use the close to grab a quote and ask for the reference. For retainers, you don't get one close, so write case studies around specific initiatives inside the relationship. One logo can produce several case studies: a re-platform, a loyalty feature, an international expansion.
Use the debrief. If you run a team debrief after an engagement, and you should, that's the moment to draft the case study against the notes.
Use the QBR. A quarterly business review forces an internal recap of the work done together. That recap is basically a case study draft.
Ask in the moment of joy. When a client says "you knocked it out of the park," that's when you ask if they'll be a reference. Not six months later when the context is gone.
Templatize it. A one-page form anyone can fill out, junior or senior, to take the first stab. With AI you can feed a debrief transcript into a skill with your template built in and get a usable first draft. The tools only get better. You just have to take the first step.
Give it an owner. This is the one that matters. If nobody owns proof, it doesn't get done. The owner doesn't have to be the CEO. At Barrel it started with the design team and moved to a marketing coordinator spending a few hours a week. The point is that someone owned it, so it always got done.
Proof is how your expertise shows up in the market. The work you've already done is sitting there as latent evidence. The only question is whether you've made the investment to turn it into an asset. Write it while it's fresh. Ask while they're happy. Make it a habit, not a scramble.
This is foundation work, and it backs every claim your positioning makes. Pressure-test yours at foundation.agencyhabits.com.
