The Executive Summary
Agency founders at $30-$60K/month are losing deals at 15-20% close rates on results they already produced,3 structured case studies push that to 35-50%.
Who this is for: Agency founders at $30-$60K/month with at least 3 completed client engagements and zero systematically documented case studies
The proof gap problem: Close rate of 15-20% without structured proof versus 35-50% with it; suppressed revenue running at $4,500/month ($205/day) on existing client results
What you’ll learn: The Case Study Engine — Stage 1 Outcome Capture (48-hour window), Stage 2 Five-Section Structure, Stage 3 Distribution Protocol (3 placement locations), Stage 4 Proof Update Cadence (12-month refresh)
What changes if you apply it: Sales conversations shift from founder-dependent verbal descriptions to documented proof assets that pre-sell before the discovery call starts
Time to implement: 2–3 weeks; spend 5–6 hours in Week 1 building the capture template and reviewing 3 past engagements, 3–4 hours in Week 2 placing the first case study in all 3 locations, and 2 hours in Week 3 drafting the second and third case studies and setting the quarterly refresh trigger.
Written by Nour Boustani for service agency founders at $30-$60K/month who want inbound leads from proof they already earned without adding outreach volume.
› Library Navigation: Quick Navigation · Service Agencies
How to Write Agency Case Studies That Help Close Leads
The Case Study Engine is a four-stage system for agency founders at $30–$60K/month. It captures client results within 48 hours of project completion, translates raw metrics into buyer-language impact, and places the proof in three sales locations.
The problem is not a lack of results. Founders may have completed strong client work but left the evidence undocumented, forcing prospects to rely on verbal descriptions when evaluating a high-value retainer.
The shift is to turn each completed engagement into a case study a prospect can assess before deciding. Capture the outcome while the numbers are fresh, explain what it meant for the client, and put that evidence where buyers encounter it.
Where are you with this right now?
“We’ve delivered strong results but haven’t turned any of them into case studies yet.” You’re inside the constraint. The framework below starts with what you already have - completed client work with measurable outcomes. The Outcome Capture Template in Stage 1 runs retroactively on your last 3 completed engagements. Start there.
“We have some case studies but they’re not generating leads.” The case studies exist but aren’t placed correctly or aren’t written in buyer language. Stage 3 (Distribution Protocol) and the Outcome-Translation Calculator in the toolkit address both gaps directly. The structure is likely right - the language and placement are wrong.
“Our clients won’t give us permission to publish their results.” This is a consent gap, not a results gap. Stage 1 of the framework includes the permission capture process that gets authorization at the natural moment - immediately post-project when satisfaction is highest. Waiting to ask later is the reason permission gets declined.
Try This Now
Pull up your most recent completed client engagement. Write down three things:
Before metric: Where the client started.
After metric: Where the client ended.
Timeline: How long it took.
Then write one sentence: “We took [client type] from [before] to [after] in [timeline].”
If you can’t write it in two minutes, you don’t have a case study problem. You have an outcome capture problem. Stage 1 solves that.
Turn Client Results Into Proof Prospects Can Use
Agencies in the Survival band produce results, but those results often stay in the founder’s memory instead of becoming case studies a prospect can evaluate.
An agency at $45K/month with 6 active clients is producing measurable outcomes. Ad campaigns hit ROAS targets. SEO clients gain rankings. RevOps clients shorten sales cycles. The founder sees the results when clients renew, but a new prospect has no written proof.
When a prospect asks for examples, the founder describes a result from memory and follows up with a loosely formatted Google Doc that needs explanation. In this example, the close rate is 15–20%. With three structured case studies in the right locations, the same founder closes 35–50% of equivalent leads. The work hasn’t changed; the proof is now usable without the founder explaining it live.
How the Proof Gap Appears Across Agencies
Performance marketing agency at $38K/month: Delivered double-digit ROAS improvements for three clients, but documented none of them. Prospects receive a verbal account instead of a case study.
3-person SEO agency at $52K/month: Moved six clients from page 3 to page 1. The founder sends every prospect the same 12-month-old screenshot, even though it shows a different industry and timeline and does not connect the ranking gain to revenue.
RevOps consultant-to-agency at $57K/month: Shortened the average sales cycle for two B2B clients by 30%, but has no case study. Each discovery call starts without written proof of that result.
The result exists. The proof a prospect can assess does not.
The Proof Gap at the Survival Band
Results produced each month:
6 active clients.
Multiple measurable outcomes.
Real before-and-after data.
Proof available to prospects:
0 structured case studies.
Verbal descriptions.
Old screenshots.
Close-rate comparison in this example:
Without structured proof: 15–20%.
With structured proof: 35–50%.
Gap: 15–30 percentage points.
Why Testimonials Do Not Replace Case Studies
The common advice is to ask clients for testimonials: send a follow-up email, include a few questions, and request a paragraph about working with you.
A testimonial records client opinion. A case study gives a buyer evidence. A prospect considering a $2,500+/month retainer needs more than “it was great to work with them.” They need to see how an agency took a company like theirs from X to Y in Z months.
Testimonials answer “were you happy?” Case studies answer “did it work, how much, and how fast?” The Case Study Engine shifts the work from collecting praise to documenting outcomes.
Calculate the Cost of Undocumented Results
Consider a $45K/month agency with 6 active clients and zero case studies. In this model:
Each placed case study generates 2–3 inbound inquiries per month.
Three case studies generating 2 inquiries each produce 6 inquiries per month.
At a 30% close rate, that is 1.8 new clients per month, or 21.6 per year.
At a $2,500/month average retainer, the modeled opportunity is $4,500 in new monthly recurring revenue from one month’s inquiries.
Each case study takes 4 hours to produce.
The formula is:
Monthly inquiries from placed case studies × close rate × average retainer
= new monthly recurring revenue from that month's inquiries
0 inquiries × 30% × $2,500 = $0
6 inquiries × 30% × $2,500 = $4,500The original $54,000/year figure is 12 months of $4,500. It does not account for additional clients acquired in later months or for churn. Likewise, $205/day is an approximate business-day equivalent of $4,500/month, not a calendar-day figure.
Sell the Transformation: How to Prove Your Results So Clients Say Yes describes the proof asset this model depends on: a before-and-after outcome statement with a specific timeline and a result translated into dollars. It contrasts that with generic testimonials, which it says convert at roughly half the rate of structured outcome-based proof.
How Proof Changes Acquisition Economics
The model estimates customer acquisition cost (CAC) from founder time. Without proof, it puts CAC at approximately $1,250–$2,000 per client at a 15% close rate on cold leads. With proof assets and a 35–45% close rate, it estimates $415–$1,000 per client, a stated 50–60% reduction.
Those ranges are model assumptions. At $75/hour, 8–12 hours of founder time costs $600–$900, so that time estimate alone does not produce the stated $1,250–$2,000 CAC range. Track all outreach and call time before using the range for your agency.
At a $2,500/month retainer and 14-month average retention, modeled lifetime revenue (LTV) is $35,000:
Without proof, at $1,500 CAC: $35,000 ÷ $1,500 ≈ 23:1 LTV/CAC.
With proof, at $600 CAC: $35,000 ÷ $600 ≈ 58:1 LTV/CAC.
Producing three case studies at 4 hours each requires 12 hours. At $75/hour, that is $900 in founder time. If a new client produces $2,500 in first-month revenue, that revenue exceeds the modeled production cost. Whether the investment pays back in less than 30 days depends on when an inquiry arrives, closes, and pays.
The client results already exist. Documenting them makes those results available to the next prospect.
If the Damage Is Already Done
Within 30 days:
Every completed engagement from the last 6 months can be retroactively captured using the Outcome Capture Template
Cost: 4 hours per case study to document from memory and client records
Recovery: 2-3 inbound inquiries/month within 30 days of placement on the first case study produced
30-90 days:
If client permission was never requested, the post-project window has passed for recent engagements
Recovery path: reach out to the 3 clients with the strongest results, frame it as a partnership spotlight, offer to share the case study with their network as additional value
Cost: 1-2 conversations per case study to gain permission retroactively; success rate lower than in-window capture but workable
Timeline: full case study library of 3 assets within 60-90 days
90+ days:
Chronic absence of proof assets for 6+ months with active clients indicates the capture process was never installed
Recovery requires: retroactive capture on all eligible past engagements, immediate installation of the 48-hour capture trigger for all current work, and a 30-day placement sprint for the first 3 assets produced
Cost of delayed recovery: $4,500/month × months of suppressed revenue already accumulated
One thing from this section:
The proof gap is not a quality gap - it’s a documentation gap. Agencies with weaker results and stronger case studies will consistently outclose agencies with stronger results and no case studies.
The cost of the gap is quantified. The next section installs the four-stage system that closes it - starting with capturing proof before it fades from memory.
How to Write Agency Case Studies That Turn Client Results Into Sales Proof
Proof converts when it speaks the buyer’s language, not the agency’s. The Case Study Engine translates the work delivered into an outcome a prospect can assess.
The sequence matters: capture the outcome, structure the case study, distribute it, then refresh it.
Stage 1: Capture Client Outcomes Within 48 Hours
Run the outcome capture debrief within 48 hours of project completion. The result is fresh, the numbers are easier to access, and the client can review them while the work is still recent. Do not wait for an end-of-month review or rely on the founder to reconstruct the details later.
Use the Outcome Capture Template as a post-project debrief form. Complete these six fields:
Field 1, baseline metric: Record the starting number. “Traffic was 4,200 monthly visits,” not “traffic was low.”
Field 2, target: Record the result the client wanted. “Target was 8,000 monthly visits.”
Field 3, achieved metric: Record the measured result. “Achieved 9,400 monthly visits.”
Field 4, timeline: Record the duration from start to measurement. “Over 5 months.”
Field 5, primary method: Name the main action in one sentence. “Rebuilt the site architecture and redirected 400+ broken links.”
Field 6, secondary factors: Note other contributions briefly. “Client published two pieces of long-form content we provided.”
The completed template gives you the raw material for a case study in 20 minutes. Send the client one verification question: “Can you confirm the numbers are accurate before I put this together?” Once they confirm, ask separately: “Would you be willing to let us use this as a case study?”
Confirmation verifies the numbers. It does not replace permission to publish.
Quick Signal
Check your last 3 completed projects. Can you find each project’s before-and-after metrics without asking the client or reconstructing them from memory, emails, or records? If not, outcome capture was missing from the workflow. Apply the 48-hour rule to future projects.
Capture Gate
All 6 fields are complete, with specific numbers rather than estimates for the baseline and achieved metrics.
The client has reviewed and confirmed the numbers.
The client has granted permission to use the result as a case study.
Pass: All three criteria are met. Proceed to Stage 2.
Fail: Stop. If the data is unverified, fix the data gap. If permission is declined or still pending, do not publish the case study.
Stage 2: Structure the Case Study Around Buyer Questions
Raw outcome data is the input, not the finished case study. Use the five-section format to show a prospect in a similar situation what was wrong, what changed, and what happened next.
Section 1: Client Situation
Describe who the client is, what they do, and their starting business context in one paragraph. Give the prospect enough detail to recognize a comparable business.
“A 6-person B2B SaaS company at $180K MRR, selling to operations teams at mid-market companies.”
Section 2: Specific Problem
State what was broken, how long it had been broken, and what it was costing. Use numbers where available.
“Organic traffic had plateaued at 4,200 monthly visits for 8 months despite a 12-piece monthly content output. The client was spending $4,000/month on content production without generating incremental traffic.”
Section 3: Approach Taken
Name the one or two actions that drove the result, not every deliverable.
“A site architecture audit found 400+ broken internal links. The agency rebuilt the information architecture and redirected the broken links over 6 weeks.”
Section 4: Measurable Results
Report the after metric and timeline. Add a dollar translation only when the underlying calculation supports it.
“Traffic reached 9,400 monthly visits within 5 months, a roughly 124% increase from 4,200.”
The additional 5,200 monthly visits multiplied by a 2.4% conversion rate equals approximately 125 conversions per month. Multiplying that figure by a $3,200 annual contract value gives approximately $399,360 in annual contract value if those conversions are paying customers. It does not establish the draft’s $14,000/month pipeline estimate. To use a dollar figure, define what the conversion rate measures and apply the appropriate lead-to-customer rate.
Section 5: Next Step Applied
State what the client did next, or what the agency is working on now, in one sentence.
“Currently in month 3 of a conversion rate optimization engagement to capture the traffic increase.”
When accurate, this final section shows that the initial result led to continued work, rather than implying that every engagement expands.
Each section answers a buyer question in order:
Section 1, Client Situation: Is this client like us?
Section 2, Specific Problem: Did they face the same constraint?
Section 3, Approach Taken: What did the agency change?
Section 4, Measurable Results: What happened, and how was it measured?
Section 5, Next Step Applied: What happened after the initial result?
A prospect reads a case study to judge what a similar result could mean for their business. Section 4 should make that calculation possible without treating an estimate as realized revenue.
Case Study Quality Gate
Section 4 includes a dollar-translated result, not just a percentage or volume metric. Label modeled figures as estimates.
The case study is under 500 words.
A prospect in a similar situation can use Section 4 to assess whether the result justified the investment.
Pass: All three criteria are met. Proceed to Stage 3 distribution.
Fail: Identify the missing evidence before distributing the case study.
Dollar translation missing: Use the relevant inputs and state the assumptions. For example, additional volume × 2% × $3,000 ACV estimates annual contract value only if the 2% represents customers acquired from that additional volume.
Over 500 words: Cut explanation that does not establish the client’s situation, action, result, or next step.
Investment case unclear: Rewrite Section 4 with a supported dollar figure and a matching time period. Label it as estimated if it is modeled, and include the investment figure if the reader needs it to judge whether the result justified the cost.
Do not distribute a case study that fails the gate. It may attract an inquiry without giving the prospect enough evidence to make a buying decision.
Stage 3: Place Case Studies Where Buyers Decide
A case study cannot support a sale if prospects never encounter it. The Distribution Protocol puts each approved case study in three locations: the website, the outreach sequence, and the discovery-call follow-up.
Placement 1: Website Discovery
Give the case study a dedicated page with a headline that names the client type, result, and timeline. Use a relevant primary keyword phrase in the page URL.
Generic: “Case Study: Acme Corp.”
Specific: “How We Increased Organic Traffic 124% for a B2B SaaS Company in 5 Months.”
This gives a prospect researching your work a specific result to evaluate before contacting you.
Placement 2: Outreach Activation
Turn the case study into a two-sentence hook for cold email or LinkedIn outreach:
We recently helped a [client type] go from [baseline] to
[result] in [timeline]. If you're dealing with [specific
problem], I'd be happy to walk you through what we did.Link to the case study so interested prospects can assess the result. Name the problem the work addressed, rather than sending the same claim to everyone.
Placement 3: Discovery-Call Follow-Up
When a prospect describes a problem the case study directly addresses, reference it in the conversation:
That's similar to the situation we solved for [client type].
I'll send you the case study after this call.Send the link within 30 minutes of the call. The prospect receives relevant proof while evaluating whether to move forward.
Performance Marketing Agency Example
A performance marketing agency at $47K/month placed its first structured case study in all three locations. In Month 1, it recorded:
4 inbound inquiries from the website page.
3 positive responses to the outreach hook in a 30-message sequence.
2 discovery-call references that led to proposals within 72 hours.
Across the 9 case-study-influenced conversations, the reported close rate was 44%, compared with the agency’s prior 18% close rate on equivalent qualified leads.
Stage 4: Refresh Case Studies Every 90 Days
The Proof Update Cadence is a quarterly check for stale results and outdated descriptions. A case study based on results measured 18 months ago needs a clear measurement date; do not present those numbers as current.
Every 90 days:
Review the result date in each active case study.
Flag any case study with results data older than 12 months.
Ask the client: “We’re refreshing our case study documentation. Do the results numbers need updating, or has anything moved significantly?”
If the engagement is active, verify current metrics and update Section 5: Next Step Applied where appropriate. For example: “Now in month 18, traffic has reached 14,200 monthly visits.”
If the engagement has ended, confirm the last-measured result and show when it was measured.
The review keeps the proof accurate and creates a natural reason to reconnect with the client. If the work is ongoing, say so in Section 5: Next Step Applied. Continued engagement can signal retention, but do not imply that a refreshed case study guarantees a higher close rate.
Translate Results Into Buyer Language
The Case Study Engine teaches a principle that applies beyond case studies: prospects evaluate outcomes in terms of their business, not your deliverables.
“We increased organic traffic 124%” describes an agency metric. A buyer also needs to know whether that traffic produced qualified leads, pipeline, or revenue.
Use the same translation in outreach emails, discovery calls, proposals, and LinkedIn posts, but claim a dollar impact only when the client’s data supports it. Do not repeat the $14,000/month pipeline estimate without a calculation that produces that figure.
Why Structured Proof Helps Buyers Decide
A prospect considering a $2,500+/month retainer has not seen your team deliver. A verbal account asks them to accept your description of the work. A case study gives them a client type, verified before-and-after metrics, a timeline, and a result they can assess.
Testimonials record client satisfaction; structured case studies document what changed. The article’s 2:1 conversion comparison is a claim about those two forms of proof, not a guaranteed result for every agency.
The gross-margin model illustrates the potential effect of a higher close rate:
At an 18% close rate on 10 qualified leads, an agency expects 1.8 new clients.
At a 38% close rate on the same 10 leads, it expects 3.8 new clients.
The difference is 2 clients. At a $2,500/month retainer and an assumed 50% delivery margin, each contributes $1,250/month in gross margin.
Two additional clients contribute $2,500/month in gross margin while both retainers remain active.
The 50% delivery margin is the model’s Parakeeto benchmark. Treat the projected gain as conditional on lead quality, close rate, and client retention, not as indefinite income from publishing case studies.
Draft a Case Study With AI
Writing a structured case study from memory, formatting it, and translating the outcome can take 3–5 hours per asset. The article’s AI-assisted estimate is 45–60 minutes using Claude at claude.ai. Use the Outcome Capture Template first; AI can organize and calculate from supplied inputs, but it cannot verify missing client data or grant publication permission.
Copy-paste prompt:
Write a B2B agency case study using only the verified information below.
- Client type: [type]
- Business context: [brief description]
- Specific problem: [problem and cost, if known]
- Baseline metric: [number and measurement period]
- Target: [number and measurement period]
- Achieved metric: [number and measurement period]
- Timeline: [duration]
- Primary method: [one sentence]
- Secondary factors: [brief description]
- Next step with the client: [confirmed next step]
- Client-approved details: [what may be published]
Use these five sections: Client Situation, Specific Problem,
Approach Taken, Measurable Results, and Next Step Applied.
Keep the full case study under 500 words. Write in direct,
buyer-focused language without hype.
In Measurable Results, show the before-and-after calculation.
If the supplied data supports a dollar translation, show the
formula, units, time period, and assumptions.
Use [client conversion rate, if verified] and [client ACV, if verified]
only where they measure the relevant steps in the calculation.
If either is missing, do not present a default 2% conversion
rate or $3,000 ACV as a client fact. Label any scenario using
those assumptions as illustrative, not achieved revenue.
Do not invent metrics, dates, quotes, client actions, pipeline,
revenue, or permission. Flag missing inputs after the draft.A prompt can force the dollar-translation question into the drafting process; it cannot guarantee a valid dollar answer. Review the calculation and client approval before publishing.
At the stated time ranges, six case studies would take 18–30 hours manually or 4.5–6 hours at 45–60 minutes each with AI. That is approximately 12–25.5 hours saved, depending on the time taken per asset, rather than a fixed 15–25 hours.
The distinction is not only whether the agency has results. It is whether a prospect can evaluate those results in a form relevant to their decision.
I built the first version of the Outcome Capture Template after losing a $3,200/month proposal to an agency I believed had weaker results. They had a case study; we had a verbal description. The prospect chose the agency that handed them written evidence.
Premium Toolkit available for members
The Case Study Engine System includes:
Outcome Capture Template — capture verified results and client permission while outcomes are fresh and easy to document.
Outcome-Translation Calculator — turn raw performance metrics into buyer-facing dollar impact that strengthens case-study credibility.
Case-Study Reuse Scorecard — identify overlooked distribution channels that turn completed proof into more sales conversations.
Plug-and-play AI diagnosis sessions — drop into Claude, Gemini or ChatGPT, answer a few questions, save hours of guessing, get your exact next move
Audio key points — concentrated frameworks you can absorb in minutes, implement while you move
Unlock 750+ ready-to-use constraint toolkits — built to solve every business problem operators actually face.
Recover $4,500/month in suppressed inbound revenue by turning three completed engagements into sales-ready proof assets.
Cancel anytime. Every download you’ve accessed stays with you.
This toolkit is built for agency founders at the Survival band who have completed at least 3 client engagements with measurable outcomes but have not yet systematically documented or distributed them as proof assets.
If you haven’t yet defined your repeatable service delivery, start with Every Client Is a New Custom Job - The Agency Seed Protocol first - the Case Study Engine requires a standardized outcome to capture.
Build the proof library once. Let it close leads permanently.
One thing from this section:
The Case Study Engine doesn’t create proof - it captures and translates proof that already exists into the language that closes deals.
The framework is defined. The next section maps the installation sequence - how to build the first case study in one session, place it in all three locations, and set up the capture trigger before the next project completes.
How to Build a Repeatable Agency Case Study Process
Follow the Case Study Engine in order: build the capture process, verify past results, structure the case studies, distribute them, then set the refresh cadence.
Step 1: Build the Outcome Capture Template and Set the Trigger
Create a reusable form with six outcome fields and a separate permission-status field. Set a calendar event or project-management trigger when a project moves to “complete,” so the form goes out within 48 hours.
Outcome Capture Template
- Baseline Metric: [starting number and measurement period]
- Target: [target number and measurement period]
- Achieved Metric: [measured number and measurement period]
- Timeline: [start date to measurement date]
- Primary Method: [main action that drove the result]
- Secondary Factors: [other relevant contributions]
- Client Permission Status: [requested / granted / declined]Send the client a separate permission request: “Would you be comfortable with us documenting this result as a case study for our agency?” Record the response; requesting permission is not the same as receiving it.
Tool: Any document tool, paired with a calendar event or project-management tag.
Time: 45 minutes to build. If setup takes more than 60 minutes, simplify it. Keep the outcome capture to six fields; track permission separately.
Output: A reusable form and a trigger that a contractor or team member can operate without the founder.
If clients do not complete the form, ask first for the baseline, achieved metric, and timeline. Collect the remaining fields on a short follow-up call. Do not draft or publish from partial, unverified data.
Step 2: Run Retroactive Capture on the Last 3 Engagements
Apply the Outcome Capture Template to your last 3 completed engagements with measurable outcomes. Start with project notes, client emails, and reporting documents. Use memory to locate evidence, not as a substitute for verified numbers.
When a metric is missing, ask the client: “I’m putting together some agency documentation and want to make sure I’m representing your results accurately. Can you confirm [specific metric]?”
Tool: The Outcome Capture Template from Step 1: Build the Outcome Capture Template and Set the Trigger.
Time: 2–3 hours across 3 engagements. If one takes more than 60 minutes and the data remains inaccessible, move to the next; return only if you can verify the result and obtain permission.
Output: 3 capture templates, each with its permission status recorded.
Ready-to-draft check: All six outcome fields are complete and verified; at least 2 clients have granted permission if the goal is to draft 2 publishable case studies.
If none of the 3 clients grants permission, offer to send the finished draft for approval before publication: “We’d like to share how we worked together in a way that might help your network. We’d send the final version to you for approval before publishing anything.” Do not treat that offer, or a lack of reply, as consent.
Step 3: Draft the First Case Study Using the 5-Section Format
Choose the strongest verified outcome from Step 2: Run Retroactive Capture on the Last 3 Engagements. Use the completed Outcome Capture Template as source material for the five sections: Client Situation, Specific Problem, Approach Taken, Measurable Results, and Next Step Applied.
Translate the result into buyer terms where the data allows:
Additional volume × relevant conversion rate × ACV
= estimated contract value from the additional volumeThe conversion rate must describe the step being calculated. If the client’s conversion rate or ACV is unknown, the article’s 2% conversion rate and $3,000 ACV can be shown only as an illustrative scenario, not as a verified client result. Label the calculation and its time period. Do not call it realized revenue or pipeline unless the underlying data supports that description.
Tool: Use Claude for a first draft with the prompt in Draft a Case Study With AI; then check every metric, calculation, and permission detail.
Time: 45–60 minutes with AI assistance or 3–4 hours manually.
Output: A five-section case study under 500 words, with a supported dollar translation in Section 4: Measurable Results where possible.
Quality check: A comparable prospect should be able to read it in under 3 minutes and judge whether the agency solved their problem and whether the documented result justified the investment.
If the draft exceeds 500 words, remove detail that does not establish the situation, method, result, or next step. If you cannot support a dollar figure, do not invent one to pass the quality gate; obtain the missing data before making a financial claim.
Step 4: Place the Case Study in All Three Distribution Locations
Deploy the approved case study within the same week it is written.
Website placement: Publish a dedicated, indexable page with a specific headline, such as “How We Increased Organic Traffic 124% for a B2B SaaS Company.” Do not rely only on a generic case studies index.
Outreach hook: Add a two-sentence version to the existing prospecting sequence.
Discovery-call reference: Introduce the case study when a prospect describes a matching problem, then send it within 30 minutes of the call.
Use these scripts:
Outreach hook
We helped a [client type] go from [baseline] to [result]
in [timeline]. If you're dealing with [specific problem],
[CTA].Discovery-call reference
That's similar to the constraint we solved for [client type]
[verified time reference]. I'll send you the case study
after this call.Tools: Website CMS, existing outreach tool, and a calendar reminder for call follow-ups.
Time: 2–3 hours for the first case study; 30–45 minutes for each subsequent placement.
Output: One approved case study active in all three locations, with a way to count inquiries arriving through or referencing the dedicated page.
Check for at least 1 inquiry referencing the case study or arriving via its page by the end of Week 2. If none arrives by Week 4, review the page’s traffic, search visibility, and headline before changing it. If the page has no traffic after 30 days, check indexation first; then test a headline that names the specific client problem or result in the language prospects search for.
Step 5: Install the Quarterly Refresh Trigger
Set a quarterly calendar event titled “Case Study Refresh Review.” Attach this checklist:
List every active case study and its result measurement date.
Flag results data older than 12 months.
Ask those clients whether updated metrics are available.
If verified numbers are available, update the result and the timeline in Section 5: Next Step Applied. If the engagement has ended, show when the final result was measured.
Republish the revised case study and update the outreach sequence wherever the old numbers appear.
Tool: Calendar tool, plus the original case study production workflow.
Time: 90 minutes per quarter for a library of 3–5 case studies.
Output: An active library reviewed every quarter, with results older than 12 months either refreshed or clearly dated.
Check: Every active case study was reviewed in the current or previous quarter.
If a client does not respond, do not update their metrics from an assumption. Keep the last verified result with its measurement date, and follow up through the normal client relationship process. A missed refresh reply alone does not establish churn risk.
Install the Case Study Engine
Week 1: Build the Outcome Capture Template, set the 48-hour trigger, and run retroactive capture on the last 3 engagements.
Week 2: Draft the first case study in the five-section format and activate all 3 placements.
Week 3 onward: Capture outcomes after every new completion and track case-study-influenced inquiries.
Day 90: Run the first refresh review and update or date each case study as needed.
Apply the Case Study Engine to Your Agency
Solo-Founder Performance Marketing Agency
Context: $38K/month and 4 active clients.
Constraint: The founder finishes a campaign and moves to the next client without starting the outcome debrief.
Action: Set a project-completion tag in the task management tool to trigger the six-field Outcome Capture Template. Build the first case study from a verified, approved result from the best-performing past campaign.
Modeled outcome: 2–3 inbound inquiries within 6 weeks of placement and $2,500–$5,000/month in new pipeline. Treat these as targets to test, not guaranteed results.
3-Person SEO Agency
Context: $52K/month and 6 active clients.
Constraint: The team records rankings and traffic but does not translate them into financial impact.
Action: Run the Outcome-Translation Calculator on each completed engagement before drafting. Use verified conversion and contract-value inputs where available; label any assumption-based figure as an estimate. Add the resulting case study hook to the LinkedIn prospecting sequence.
Modeled outcome: A 30–40% improvement in outreach response rate within 30 days. Measure responses against the agency’s pre-deployment rate.
RevOps-Focused Agency
Context: $57K/month and 5 active clients.
Constraint: The client may not want pipeline or sales-cycle figures published.
Action: Ask: “We’d like to reference the methodology, not the specific company metrics. We’ll share the draft with you for approval.” Publish only the details the client approves. If metrics cannot be shared, do not imply a quantified result.
Modeled outcome: A methodology-focused case study placed within 45 days, with a target of 1–2 inbound inquiries from competitors of existing clients. Track whether those inquiries occur rather than assuming anonymized proof will perform like a named, quantified case study.
Check That the Engine Is Installed
Confirm that these five artifacts exist:
The Outcome Capture Template is built, with a 48-hour trigger in the project workflow.
Retroactive capture is complete for at least 2 engagements, with verified data and permission granted.
The first five-section case study is drafted, with a supported dollar translation in Section 4: Measurable Results.
The case study has a live website page, an outreach hook, and a prepared discovery-call reference.
The quarterly refresh trigger is set in the calendar.
If an artifact is missing, that part of the Case Study Engine is not yet operational. A drafted case study cannot generate inquiries through placements that are not live.
The operating rule is simple: capture proof within 48 hours, translate it into buyer language, and put it where prospects evaluate the agency. Test Your Case Study Engine With Your Numbers checks the calculator, the 90-day trajectories, and the milestones that distinguish lead generation from asset production.
How to Test Whether Your Agency Case Studies Generate Leads
A placed case study and a converting case study are not the same thing. Track the inquiries and sales conversations it influences, not just whether the page is live.
Calculate Your Proof Gap
Run the Proof Gap Cost Calculator before installing the Case Study Engine. The example models potential new monthly recurring revenue from one month of inquiries, not revenue already earned.
Example: $45K/month agency, 6 clients, 0 active case studies
- Current inbound inquiries from proof assets: 0/month
- Assumed close rate on proof-backed leads: 35–50%
- Average retainer: $2,500/month
- Current new monthly recurring revenue from proof assets: $0
- Modeled inquiries from 3 placed case studies: 3 × 2 = 6/month
- Modeled new clients: 6 × 30% = 1.8/month
- Modeled new monthly recurring revenue: 1.8 × $2,500 = $4,500
- Approximate business-day equivalent: $205/dayThe example uses 30% for the revenue calculation, even though it lists 35–50% as a proof-backed close-rate assumption. Use a consistent rate when calculating your own scenario.
Your Proof Gap Cost Calculator
- Case studies in active distribution: [number]
- Proof-attributed inbound inquiries last month: [number]
- Close rate on proof-influenced conversations: [percentage]
- Average monthly retainer: $[amount]
- Assumed inquiries per placed case study per month: [number]
- Scenario close rate: [percentage]
- Modeled new monthly recurring revenue at 3 placed case studies:
3 × [assumed inquiries per case study] × [scenario close rate]
× $[average monthly retainer] = $[amount]
- Current new monthly recurring revenue from proof assets:
[proof-attributed inquiries] × [actual close rate]
× $[average monthly retainer] = $[amount]
- Modeled gap: $[scenario revenue] − $[current revenue] = $[amount]The Sell the Transformation: How to Prove Your Results So Clients Say Yes comparison puts proof-backed close rates at 2–3 times those of equivalent leads without proof. Treat that as a benchmark to test against your own qualified leads, not a forecast.
Test the Case Study Engine Before You Build
Use this as a modeled scenario, not a forecast. The starting agency earns $47K/month from 5 clients, has 0 case studies in active distribution, has completed retroactive capture on 3 engagements, and has drafted its first case study.
Week 2: The website page is live and the hook is in the LinkedIn sequence. Of 3 messages sent with the hook, 1 prospect replies, “That’s interesting. What was the methodology?” The agency sends the case study link and continues the conversation.
Week 6: The page has generated 2 inbound inquiries, both from companies in the client’s vertical; 1 books a discovery call. A 30-message outreach sequence produces 4 positive responses, compared with 1 in the previous 30-message sequence.
Week 12: Two more case studies are live. Proof assets generate 5–6 inquiries per month. The modeled close rate on case-study-influenced conversations is 38%, compared with a pre-engine rate of 17% on equivalent cold leads. The scenario projects $3,750–$5,000/month in new retainers from proof-influenced closed deals.
The Week 12 revenue range is an assumption, not a direct calculation from 5–6 inquiries at a 38% close rate. At a $2,500 retainer, those inputs imply approximately $4,750–$5,700 in new monthly recurring revenue from one month’s inquiries. Check the inquiry count, qualification, close rate, and retainer before using either range as a target.
Run Your Own Scenario
Paste this into Claude to calculate the model with your numbers:
I run a [type] agency earning $[X]/month. My average
monthly retainer is $[amount]. I plan to publish a case
study about [result type] for [client type].
Model 1, 2, and 3 case studies using 2 inquiries per asset
per month and a 35% close rate. For each scenario, show:
- Monthly inquiries.
- Expected new clients per month.
- New monthly recurring revenue from one month's inquiries.
- Annualized value of that single month's new recurring revenue.
Then show a separate 12-month acquisition scenario with
the assumptions needed for retention and capacity. State
that inquiries and close rates are assumptions, not
guarantees. Use a compact list, not a table.Compare the 90-Day Paths
Without the Case Study Engine
New business remains dependent on referrals and founder outreach. In this scenario, close rates stay at 15–20% on qualified leads.
The agency adds 1–2 clients per quarter, barely replacing churn, while revenue stays flat.
Results continue to accumulate, but older engagements become harder to document accurately.
With the Case Study Engine
Day 30: The first case study is active on the website, in outreach, and in discovery-call follow-ups. The scenario targets website inquiries within 2–3 weeks and a 20–30% improvement in outreach response rate.
Day 60: The second and third case studies are live. The scenario targets 4–6 proof-attributed inquiries per month, with prospects able to review relevant evidence before the call.
Day 90: The capture trigger runs on new completions, and the scenario targets $3,500–$4,500/month in new retainer revenue from proof-influenced conversations.
These are two modeled paths, not outcomes the framework guarantees. Track the date each asset went live, inquiries and responses by placement, qualified calls, closed clients, and new retainer revenue to see which path your agency is actually following.
Check Progress at Day 14, Week 4, and Week 8
Day 14
Send the Outcome Capture Template after at least 1 project completion, if a project has completed.
Draft the first case study with all 5 sections and a supported dollar-translated result.
Publish the dedicated website page and confirm it is indexed.
Week 4
Activate all three placements: website, outreach hook, and discovery-call reference.
Track at least 1 inquiry attributable to the website page or outreach hook.
Run the capture trigger on every new project completion.
Week 8
Build the library to 2–3 case studies.
Compare proof-attributed inbound inquiries with the 4–6 per month target.
Compare the close rate on proof-influenced conversations with the pre-engine rate using comparable leads.
Confirm the quarterly refresh trigger is set and review at least 1 case study.
If the website placement has produced no inquiry by Week 4, check these in order:
Is the page indexed?
Does the headline use language a prospect would search for when facing that problem?
Is the supported dollar-translated result visible near the top of the page?
Fix gaps in those three checks before changing the broader distribution plan.
If It Does Not Work - Rollback and Retest
If website placement produces no traffic after 30 days:
Check indexation via Google Search Console
Rewrite headline with more specific search intent (“case study” + result type + industry + outcome)
Retest: re-submit to search console, measure at 2-week mark
Timeline: 4 weeks to confirm whether rewrite worked
If outreach hook produces no response improvement:
The problem is in the hook sentence - the result described doesn’t match what the prospect is currently searching for
Retest: identify the most common objection in recent discovery calls and write the hook around the result that directly addresses it
Timeline: 30 messages with the revised hook before evaluating
If discovery call case study references don’t convert to proposals:
The case study is being described but not sent - prospects are hearing about proof, not evaluating it
Fix: send the case study during the call, not after. “Let me pull it up for you now.” Screen share or paste the link in chat.
Retest: measure close rate difference on calls where case study was viewed during the call vs. sent after
Read the Signals Your Case Studies Produce
Signal 1: Prospects Ask for Proof Before Booking
A request for proof may signal that a prospect is evaluating whether your agency can solve their problem. Track how many prospects ask for a case study before booking, whether you can send a relevant one, and what happens next. The request alone does not establish that the prospect is qualified.
Signal 2: A Case Study Generates No Inquiries in 30 Days
Do not assume the headline is the problem before checking whether prospects can find the page. Review indexation, page traffic, placement, search intent, and whether the result is clear. Compare the wording of the top 3–5 competitor case study headlines in your vertical for useful search language; do not copy their claims.
Signal 3: A Client Declines Permission
Record the decision and respect it. A refusal can reflect confidentiality requirements or publishing preferences, not necessarily dissatisfaction or churn risk. If other relationship signals warrant a check-in, address them directly rather than treating the refusal as a diagnosis.
Proof Asset Diagnostic
No website inquiries: Check indexation, then headline search intent, then whether the supported dollar result is visible near the top of the page.
No outreach response lift: Check whether the result addresses the prospect’s active problem. Rewrite the hook around the most common relevant objection and compare response rates.
No close-rate lift: Check whether prospects receive the case study while evaluating the decision. Reference it during the call when relevant and send it promptly afterward.
If a case study generates no inquiries in its first 30 days, investigate placement and discoverability before rewriting the case study itself. A five-section format does not, by itself, prove that the result or structure is effective.
The next section, Keep Your Case Study Engine Working After Launch, addresses metric decay, single points of failure, and the longer-term effects of a growing proof library.
Keep the Case Study Engine Working
A case study library needs maintenance. Without a refresh cadence, the results remain published while their measurement dates get older. Prospects may then question whether the agency can produce a comparable result now.
The Single Point of Failure: Metric Age Creep
An agency builds three case studies in its first 90 days and places them in the sales process. Delivery gets busy, the quarterly review slips, and 18 months later the same results are still being presented without context. A prospect sees old traffic data and asks whether it reflects the agency’s current work.
Use the Proof Update Cadence to prevent that gap:
Every 90 days, review each active case study and its result measurement date.
Flag any results data older than 12 months.
If the client is still active, request and verify current metrics before updating the case study.
If the engagement has ended, date the last verified result. Say it was maintained independently only if the client has confirmed that.
Build toward a library of 5 case studies before relying on it as the primary source of sales proof. Three assets can give prospects relevant examples; five provide more coverage when 1–2 need updating. Neither library size guarantees a close-rate improvement.
The quarterly check is the safeguard: identify aging metrics and update or clearly date them before a prospect has to ask when the result was achieved.
Failure Mode Analysis
Failure Mode 1: Capture trigger fires but permission is never requested
What goes wrong: The 6-field template is sent, the client completes it, the data is collected, but the permission question is omitted. The founder then can’t publish the case study without going back to the client - a conversation that’s harder to have 3 months later and easier to avoid entirely.
Early Signal: The capture template folder contains completed forms with no permission status field populated.
Recovery Path: Add the permission question as Field 7 of the capture template - not as a follow-up, as part of the same send. “One more question with the above - would you be comfortable with us documenting this result as a case study? We’ll share the draft with you before publishing.”
Correction Timeline: 1 hour to update the template. Permission rate on next 3 sends should confirm the fix.
Failure Mode 2: Case study placed on website but not in outreach or discovery calls
What goes wrong: The website page is live but the agency isn’t actively deploying the asset in the outreach sequence or referencing it on discovery calls. The website generates modest organic traffic but the case study isn’t participating in active sales conversations.
Early Signal: Monthly inbound from the website page is 0-1, and the founder can’t recall referencing the case study on a call in the last 2 weeks.
Recovery Path: Write the 2-sentence outreach hook and add it to the next 30-message outreach sequence this week. Write the 1-sentence call reference and use it on the next 3 discovery calls where the problem matches.
Correction Timeline: 30 minutes to write and deploy both. Results visible within 2-3 weeks of deployment.
Failure Mode 3: Dollar translation is missing or vague
What goes wrong: The case study documents the agency metric (traffic, ranking, conversion rate improvement) but doesn’t translate it to a buyer-language dollar impact figure. The prospect reads the result and can’t calculate whether it would justify the retainer.
Early Signal: Prospects who read the case study before a discovery call are asking “but what did that actually mean for their business?” - they’re doing the translation work themselves because the case study didn’t do it for them.
Recovery Path: Add the Outcome-Translation Calculator formula to every existing case study: additional volume × conversion rate × ACV = monthly pipeline impact. Even an estimated figure (labeled as estimated) closes at a higher rate than no translation.
Correction Timeline: 15-20 minutes per case study to add the translation. Close rate on proof-influenced conversations should improve within 2-3 weeks of updating the library.
Second-Order Consequence Mapping
Month 1 without the Case Study Engine:
The proof gap is invisible. The founder is producing strong results, clients are renewing, and new business is coming through referrals and founder outreach.
The absence of documented proof doesn’t feel like a constraint because the agency is growing. The opportunity cost of $205/day isn’t measured because there’s no baseline to compare against.
Month 3 without the Case Study Engine:
A competitor agency in the same vertical publishes a case study documenting results in the founder’s target vertical. Two prospects that were in the founder’s pipeline choose the competitor.
Both say variations of: “They had examples of doing this for companies like ours.” The founder describes their equivalent results verbally. Neither prospect chose the verbal description over the written proof.
Month 6 without the Case Study Engine:
The referral-dependent pipeline hits a dry period. No proof assets exist to generate inbound independently of founder outreach. The founder increases outreach volume to compensate.
Close rate on cold outreach remains 15-18% - below the 35-45% that proof-backed conversations produce. Revenue stays flat or declines.
The agency has been producing proof-worthy results for 6 months. None of it is accessible to prospects.
Test Whether the Engine Can Scale
The Case Study Engine should keep capturing proof as the agency changes, rather than depending on the founder remembering to ask for it.
Under higher client volume: Each completed engagement triggers the Outcome Capture Template. Check that the trigger still fires and that someone follows up on incomplete forms.
Under team growth: A team member or contractor can send the six-field template at project completion. Keep the founder’s review focused on dollar translation, accuracy, and permission before publication.
Under market competition: Maintain a relevant library of 5–10 placed, refreshed case studies. It gives prospects more comparable examples, though library size alone does not create a guaranteed competitive advantage.
Implementation Speed Target
Aim to install the Case Study Engine in 2–3 weeks:
Week 1, 5–6 hours: Build the capture template, set the 48-hour trigger, complete retroactive capture on 3 engagements, and draft the first case study.
Week 2, 3–4 hours: Publish the first website page, add the outreach hook, and prepare the discovery-call reference.
Week 3, 2 hours: Draft the second and third case studies from verified, approved captures and set the quarterly refresh trigger.
What to Do When the Process Stalls
Blocker 1: “My clients won’t give permission.”
Ask within 48 hours of a completed project, verify the numbers, and make a separate, explicit request to use the result. Offer to send the final draft for approval. If the client declines, do not publish identifiable details or assume anonymization removes the need for permission. A methodology-only example is an option only if it respects the client’s agreement and cannot identify them. The article’s 60–70% conversion comparison for anonymized versus named proof is not a reason to override a refusal.
Blocker 2: “I don’t know how to calculate the dollar translation.”
Use the relevant conversion rate and annual contract value if the client can verify them. If those inputs are unavailable, the 2% conversion rate and $3,000 ACV can illustrate a scenario:
Illustrative estimate
- Additional monthly volume: [number]
- Assumed conversion rate: 2%
- Assumed annual contract value: $3,000
- Additional monthly volume × 2% × $3,000
= $[amount] in modeled annual contract value
from one month's additional volumeDo not label that output “monthly pipeline impact” or achieved revenue without data that supports those terms.
Blocker 3: “I didn’t record the before metric.”
Check the original reports and project records, then ask the client: “What was your [metric] when we started, and do you have a report that confirms it?” If the baseline cannot be verified, do not substitute an industry benchmark for the client’s actual starting point. You can present a sourced benchmark as market context, but not as the before figure in a before-and-after claim.
Build the Case Study Engine With AI
Use Claude at claude.ai to draft the capture form, calculator, case study structure, outreach hook, and deployment checklist in one session. The 30–40-minute target covers a draft for review, not verified metrics, client permission, or publication.
I run a [type] agency at approximately $[X]/month.
My primary service is [describe service]. I have [number]
completed client engagements to assess for case studies.
Using only the information I supply, create:
1. A six-field Outcome Capture Template: Baseline Metric,
Target, Achieved Metric, Timeline, Primary Method, and
Secondary Factors. Add Field 7 for permission status
(requested / granted / declined) and a separate,
one-sentence request for permission to publish.
2. An Outcome-Translation Calculator for [specific metric
type, such as organic traffic, paid ROAS, or pipeline
velocity]. Define each input, formula, unit, and time
period. Use verified client conversion and ACV figures
if supplied. If they are unavailable, show 2% conversion
and $3,000 ACV only as illustrative assumptions. Do not
call the result achieved revenue or monthly pipeline
unless the inputs support that label.
3. A five-section case study structure with buyer-language
instructions for Client Situation, Specific Problem,
Approach Taken, Measurable Results, and Next Step Applied.
4. A two-sentence outreach hook template tied to the
client's verified result and the prospect's problem.
5. The seven-channel deployment checklist from the Case
Study Reuse Scorecard. I will paste the scorecard here:
[paste the seven channels]. If it is not provided, do
not invent its channels; flag it as missing.
Use this verified input to draft the first case study:
[paste your best result, including baseline, achieved
metric, timeline, method, and client-approved details].
Format each deliverable as a separate labeled section.
Keep the case study under 500 words. Show calculations,
assumptions, and missing information explicitly. Do not
invent results, permission, client quotes, or next steps.AI can organize the material and propose a calculation suited to the service type. The founder still needs to check whether that calculation reflects the client’s actual conversion path, verify the figures, and obtain permission before placing the case study.
A maintained quarterly refresh cadence keeps the library usable. If results age without an update or measurement date, a proof asset can raise questions instead of resolving them.
Running This System in Your Current Condition
Contraction: Revenue Declining or Unstable
When revenue falls, use the smallest version of the Case Study Engine to support outreach already underway: one recent, verified, approved case study and a relevant hook in the existing sequence. Defer the website placement if building traffic is not the immediate priority.
The model compares 30 outreach messages per week at a 15–18% close rate without proof with 30 messages at a 30–40% close rate with proof. Those are scenario assumptions, not a promise that adding a link will double results. Compare outcomes on equivalent qualified conversations rather than applying a close rate directly to every message sent.
Priority: Document a recent result that matches the service and capacity the agency can offer now.
Risk: An impressive result from an earlier peak may raise questions if the agency cannot explain its current ability to deliver comparable work.
Diagnostic: If prospects engage with the case study but do not book, inspect the follow-up, offer, pricing, and fit. Engagement shows interest, but does not establish that the case study is converting.
Stability: Revenue Consistent, Not Growing
Use stable capacity to complete all 5 implementation steps, capture outcomes from the last 12 months of engagements, build a library of 3–5 case studies, and install the quarterly refresh cadence.
Check whether the constraint is lead volume or conversion. At 10 qualified inquiries per month, an 18% close rate implies 1.8 expected new clients; a 38% rate implies 3.8. That is a difference of 2 expected clients from the same inquiry volume, if lead quality and other conditions remain comparable. Case studies may also generate inquiries, so track acquisition and conversion separately.
Priority: Finish retroactive capture while the team has room to verify metrics and secure permission.
Drift signal: If close rate falls while qualified lead volume stays steady, check case study age and relevance alongside other possible causes. Run the refresh checklist rather than assuming stale proof is the only explanation.
Expansion: Revenue Growing and Services Broadening
When the agency adds a service, existing proof may not answer the new buyer’s question. A performance marketing result does not, by itself, demonstrate RevOps capability.
What breaks first: The Distribution Protocol has no service-matched website page or outreach hook for the new offer.
Guardrail: Run the Outcome Capture Template on the first 2 completed engagements for each new service. Treat the first as a pilot; use the second and third to build publishable proof when results are verified and permission is granted. Do not claim that two data points validate the service as a whole.
Capacity trigger: If the quarterly refresh takes more than 3 hours as the library grows beyond 8–10 assets, assign a content or operations owner to coordinate capture, drafting, distribution, and refresh. Keep metric verification and publication approval explicit.
The Case Study Engine in the Agency Operating System
The Repeatable Sale: Turn One Yes Into Ten Without More Pitching defines repeatable success that case studies can document. Use this when client outcomes vary too widely.
How to Build Credibility Without Case Studies builds credibility before you have completed results to document. Use this when you lack three completed engagements.
Sell the Transformation: How to Prove Your Results So Clients Say Yes translates delivery results into buyer-facing business impact. Use this when case studies lack commercial relevance.
The Client Exit Protocol - Turning Offboarding into Referrals builds case-study permission into a structured client offboarding process. Use this when permission requests happen too late.
Diagnostic Question
Can a prospect in your primary target vertical assess your agency’s results from the case studies you currently publish and distribute, without speaking to you or your clients?
If not, the Case Study Engine is not yet doing its job.
Your Proof Library Fix Starts Now
What you’ll be able to say at Week 8:
“We have 3 placed case studies generating 4-6 inbound inquiries per month without additional outreach volume.”
“Our close rate on proof-influenced conversations is above 35% - more than double our pre-case-study rate.”
“Every project completion automatically triggers a capture process - the library grows with the work.”
Three time-boxed actions:
In the next 30 minutes:
Open your most recent completed client engagement.
Record the before metric, after metric, and timeline.
Write: “[Client type] went from [before] to [after] in [timeline].”
This week:
Spend 45 minutes building the six-field Outcome Capture Template.
Complete it retroactively for the client with the strongest result.
Verify the numbers and ask separately for permission to publish.
Week 1 deliverable: One template and one client conversation.
Before next month:
Draft the first case study in the five-section format.
Once the client approves it, publish a dedicated page with a searchable headline.
Add the outreach hook to your next prospecting sequence and prepare the discovery-call reference.
The first case study is ready to distribute when the results are verified, the client has granted permission, and prospects can find and assess it.
Case Study Engine Progress Milestones
Milestone 1: Outcome Capture Template exists; 48-hour trigger installed in project workflow; at least 1 retroactive capture complete with permission granted
Milestone 2: First complete 5-section case study drafted with dollar-translated result in Section 4; reviewed and approved by client before publication
Milestone 3: Case study placed in all three distribution locations; website page indexed; outreach hook in active sequence; discovery call reference prepared
Milestone 4: Case study library at 3 assets; monthly inbound from proof assets measurable; at least 1 inbound inquiry attributable to a specific case study
Milestone 5: Quarterly refresh cadence installed; no case study in the library with results data older than 12 months; close rate on proof-influenced conversations tracked monthly
If you take one thing from each section:
The proof gap is not a quality gap - it’s a documentation gap. Agencies with weaker results and stronger case studies will consistently outclose agencies with stronger results and no case studies.
The Case Study Engine doesn’t create proof - it captures and translates proof that already exists into the language that closes deals.
The Case Study Engine is operational when proof is captured within 48 hours, translated into buyer language, and placed in all three locations where buying decisions get made.
A case study that isn’t generating inquiries in the first 30 days has a placement or headline problem - the result and structure are correct in the large majority of cases where the 5-section format was followed.
The Case Study Engine that compounds is the one with a maintained refresh cadence - proof assets that age out without updating become liabilities, not assets, in the time-sensitive B2B sales environment.
But if you remember only one thing:
The proof the agency has already earned is sitting in completed project folders, client emails, and the founder’s memory - undocumented, untranslated, and generating zero inbound. Installing the four-stage capture system turns what’s already been delivered into the sales infrastructure that delivers the next client.
Case Study Engine Checklist
Reference this checklist before placing any proof asset in active distribution.
☐ Verify all 6 Outcome Capture Template fields, including the actual before-and-after metrics.
☐ Confirm the client’s permission in writing for the details you will publish.
☐ Include a supported dollar-translated result in Section 4. Label estimates clearly.
☐ Prepare all three placements: a website page with a searchable headline, an outreach hook, and a discovery-call reference.
☐ Set the quarterly refresh trigger and flag results data older than 12 months.
Use this check for every case study. Missing verification or permission stops publication; missing translation or placement limits what a prospect can evaluate.
FAQ: The Case Study Engine
Q: How long does it take to build the first case study from scratch?
A: With AI assistance, a complete five-section case study takes 45 to 60 minutes once the Outcome Capture Template is filled in. Manually, it runs 3 to 5 hours. The bottleneck is almost never the writing — it is the dollar translation step, which is where most founders stall.
Q: What if I do not have before metrics because I did not track them at the start of the engagement?
A: Ask the client directly. Most clients remember their starting point better than agencies assume.
Q: My clients are in sensitive industries and will not let me use their names. Can anonymized case studies still work?
A: Yes, though at a reduced conversion rate. Named case studies with verified metrics outperform anonymized ones, but anonymized proof still converts significantly better than no proof. Use “a B2B SaaS client in the operations space” rather than a named company.
Q: When is the right moment to ask for case study permission?
A: Within 48 hours of project completion — the same window as the Outcome Capture Template. Client satisfaction peaks immediately after a strong result is delivered, then declines as time passes and new priorities take over. Asking at the 48-hour mark produces significantly higher consent rates than asking at the monthly review or end-of-quarter check-in.
Q: We already have case studies but they are not generating leads. What is wrong?
A: Two likely causes, in order of frequency. First, placement — most agency case studies live on a generic “Case Studies” page that gets minimal traffic and no active use in outreach or discovery calls. The Distribution Protocol in Stage 3 puts each asset in three specific locations where it participates in live sales conversations.
Q: How many case studies do I need before the library produces reliable inbound?
A: Three placed assets is the functional minimum. Each case study generates roughly 2 to 3 inbound inquiries per month when placed correctly, so three assets running together produce 6 to 9 inquiries.
Q: What happens to the case study when a client relationship ends?
A: The case study stays active. Timestamp the final measured result in Section 4 and update Section 5 to reflect that the engagement concluded.
Q: What is the quarterly refresh process and how long does it take?
A: Every 90 days, review each active case study for metric age. Any asset with results data older than 12 months gets flagged. Contact the client, confirm whether the numbers have moved, and update Section 4 and Section 5 with current figures.
Q: Our discovery calls are going well but prospects are not converting to proposals. Could the case study be the problem?
A: The case study is probably not the problem — but how it is being deployed on the call might be. If the case study is described verbally and sent as a follow-up after the call, the prospect evaluates it after the decision window closes. Send it during the call instead.
Q: What is the difference between a testimonial and a case study, and why does it matter for close rates?
A: A testimonial answers “were you happy working with them?” A case study answers “did it work, how much, and how fast?” At a $2,500 or more per month retainer decision, buyers are asking the second question. Testimonials ask prospects to extend trust. Case studies give prospects something to evaluate.
Q: Can I use case studies for a service type I have only delivered once?
A: One completed engagement produces one data point, which is a thin base for a published case study. The framework recommends running the Outcome Capture Template on the first two completions for any service type before distributing proof for that category.
⚑ Found a Mistake or Broken Flow?
Spotted a math error, unclear framework, or broken link? Use this form to flag it — helps me keep the articles accurate and useful. Report a problem →
› More to Explore: Quick Navigation · Service Agencies
➜ Help Another Founder, Earn a Free Month
If the Case Study Engine just showed you how much revenue your completed work is failing to capture, share it with one founder stuck producing strong results that never become proof assets.
When you refer 2 people using your personal link, you’ll automatically get 1 free month of premium as a thank-you.
Get your personal referral link and see your progress here: Referrals
Get The Case Study Engine Toolkit
You’ve read the system. Now implement it.
Premium gives you:
Ready-to-use PDF toolkit—every template, diagnostic, and formula pre-filled, zero setup, immediate use
Plug-and-play AI diagnosis sessions—drop into Claude, Gemini or ChatGPT, answer a few questions, save hours of guessing, get your exact next move
Audio key points—concentrated frameworks you can absorb in minutes, implement while you move
Unrestricted access to the complete library—every system, every update
What this prevents: Leaving $4,500/month in suppressed inbound revenue from proof assets at $30-$60K/month.
What this costs: $12/month.
Download everything today. Implement this week. Cancel anytime, keep the downloads.
Already upgraded? Scroll down to download the PDF, audio, and your AI session.
