---
title: "Free Case Study Capture Playbook for Small Businesses | TQP"
description: "Capture completed work with an interview guide, evidence sheet, publication approvals and a clear case-study structure. Free playbook for small businesses."
url: "https://www.thequietprotocol.com/resources/free-tools/case-study-capture-playbook"
---

[Back to the free resource hub](https://www.thequietprotocol.com/resources/free-tools)

Playbook [Prompts & Playbooks](https://www.thequietprotocol.com/resources/free-tools/category/prompts-playbooks) Flagship · v1.1 · Updated 2026-10-22 · Trust Systems Practice

# Case Study Capture Playbook for Small Businesses

The job is finished, the customer is pleased, and the useful details are scattered across phones and inboxes. Use this playbook to capture the work, check the evidence and turn approved material into a story your next buyer can understand.

Quick start

What it is

Capture completed work with an interview guide, evidence sheet, publication approvals and a clear case-study structure. Free playbook for small businesses.

Who it is for

Owners, operators, marketers, and client-facing teams responsible for turning real work into usable proof

What it helps you do

Turn a successful engagement into a specific, permission-aware case study that helps the next buyer understand the problem, work, and result.

How to use it

You have wins but almost no usable case-study output Then: The team forgets to capture proof until the details are stale

What to do next

[See the full resource hub](https://www.thequietprotocol.com/resources/free-tools)

Picture the end of a good job. The customer is pleased, the team is packing up and someone says, “We should put this on the website.” A month later, the useful photos are on three phones and nobody remembers what changed.

Capture the story while the people and records are still available. This playbook gives you an interview, an evidence sheet and a draft structure. The aim is a story the next buyer can inspect and understand, with the right approval before anything goes public.

## Choose a Story That Answers a Buying Question

Start with a question you hear before a sale. Can you work around an occupied home? Can you replace a confusing booking process without changing the practice software? What happens when the original plan is not suitable?

Choose completed work that answers one of those questions. A small, well-explained job can be more useful than a large project described only as “a great success.” You need a clear starting problem, a record of what was done and something you can show afterwards.

Write a working brief:

- **Reader:** who needs to make this decision?
- **Question:** what uncertainty should the story resolve?
- **Work:** which completed job or delivery are we documenting?
- **Evidence owner:** who can locate and explain the records?
- **Publication owner:** who checks the facts and obtains the required approvals?

Do not collect private details just to make the story more dramatic. Keep the raw records in the business's approved storage. The public story should contain only what helps the buyer and is cleared for publication.

## Capture the Starting Point

Save the original scope, the customer's stated problem and the conditions that affected the work. Record dates and what was already in place. Separate what the customer told you from what your team directly observed.

For a home-service job, useful material might include an approved condition photo, the selected repair and a note about site access. For a law firm or clinic's administrative improvement, show the booking or reception process using approved demonstration data. A person's legal matter or treatment is not needed to explain a better administrative process.

If no reliable baseline exists, say so in your working notes. You can still explain the work and show the delivered result. You cannot calculate an improvement from a starting number you do not have.

## Interview the People Who Know the Work

Ask the person who delivered the job first. They can help you avoid a polished story that leaves out the decision that mattered. Use these questions as a conversation, not a script that forces a positive answer.

1. What was the customer trying to do before they contacted us?
2. What did we find when we inspected the job or reviewed the process?
3. What options did we consider, and why did we choose this one?
4. What did we actually deliver? What remained outside our scope?
5. Which detail made the work harder or changed the original plan?
6. What can we demonstrate or verify now?
7. What is still unknown, unfinished or dependent on someone else?

Then, where appropriate, ask the customer:

- What was most difficult before the work began?
- What changed in your own experience?
- Which part of the work would help someone choosing a provider understand us?
- Is there anything in our draft that sounds wrong or overstates the result?

Save the customer's exact words separately from your summary. If you edit a quote for length or clarity, send the edited version back for approval. An enthusiastic conversation is not automatically permission to publish a name, photograph or testimonial.

## Build the Evidence Sheet

Each important statement needs a record behind it. Use this sheet before writing the headline.

| Statement to check | Supporting record | What it establishes | Limit or missing context |
| --- | --- | --- | --- |
| [What we plan to say] | [File, date and owner] | [Observed delivery or result] | [What it does not prove] |
| [What we plan to say] | [File, date and owner] | [Observed delivery or result] | [What it does not prove] |
| [What we plan to say] | [File, date and owner] | [Observed delivery or result] | [What it does not prove] |

A completion photo can show the finished work. A test record can show that a configured enquiry reached the agreed destination. A customer quote can describe that person's experience. None of those automatically proves a revenue increase.

If you publish a numerical comparison, keep the underlying definition and dates. Count the same thing before and after, use comparable periods and note other changes such as advertising, staffing or seasonality. Keep the original counts beside any percentage. Where the records show a change but do not isolate its cause, describe the change without claiming that your work caused all of it.

## Clear the Material for Publication

Send a review copy with the exact text and images, the proposed attribution and the places you want to use it. Ask the authorized reviewer to approve that version. Record the approval date and any restrictions. This working record does not replace the business's agreements or professional review.

| Material | Proposed public use | Authorized reviewer | Approval or restriction |
| --- | --- | --- | --- |
| Text and customer attribution | [Page or channel] | [Name or role] | [Approved version and date] |
| Photos or screenshots | [Page or channel] | [Name or role] | [Approved items and exclusions] |
| Quote or testimonial | [Page or channel] | [Name or role] | [Exact approved wording] |

Look beyond names when checking a screenshot or photograph. Addresses, faces, account identifiers, appointment details and distinctive circumstances can reveal more than the caption suggests. Removing a name does not itself establish permission or make a story safe to publish.

For law firms and clinics, have the responsible professional approve the proposed material before publication. When a customer story is unsuitable, a clearly described process walkthrough or demonstration may answer the buyer's question without exposing the underlying matter or patient record.

## Write a Short Story the Buyer Can Follow

Use this structure. Fill the fields with the approved facts; remove any section you cannot support.

### Opening: the situation

[Business or customer description approved for use] needed [specific job]. The difficulty was [constraint]. They wanted [clear, realistic objective].

### Decision: what we chose and why

We reviewed [relevant conditions or options]. We chose [approach] because [reason]. The agreed work covered [scope]. It did not include [important boundary].

### Delivery: what changed

We completed [observable work]. [Approved photograph, demonstration or record] shows [what the evidence actually establishes]. The detail that mattered was [specific decision or execution detail].

### Result: what we can show

The verified result was [supported outcome, with date or measurement window where needed]. [Approved quote, if available.] [Material limitation or unresolved item.] Explain the result in ordinary language before adding a number or a technical term.

### Next step: who this helps

This approach is relevant when [buyer situation]. A different approach may be needed when [constraint]. Link to the service that solves that problem and explain what the next conversation covers.

A strong headline names the work or decision. “A clearer booking route for new consultations” tells the reader more than “Another amazing transformation.” Make the story easy to scan, but keep the details that let someone judge the work.

## Put Images to Work

Choose images that explain the job: the relevant starting condition, an important decision or the delivered work. Keep a consistent viewpoint for a before-and-after pair when possible. Do not imply that unrelated pictures show the same project.

Write a caption that says what the reader is seeing and why it matters. Write useful alternative text for an informative image; keep a purely decorative image's alternative empty. For a screenshot, explain the meaningful result in page text so it is not available only inside the image.

Keep approved originals and a publication copy. Remove private details before upload, check the image at phone size and avoid shrinking a full software screen until none of its labels can be read.

## Publish Once, Then Maintain It

Give the full story one useful home. Link to it from relevant service or proof pages where it helps the buyer's decision. Use a short, accurate excerpt elsewhere rather than copying the full story onto several near-identical pages.

Before publishing, check:

- The opening answers a real buying question.
- The scope, evidence and result agree with one another.
- Names, images and quotes match the approved version.
- Sources and related service links open correctly.
- Mobile reading, image alternatives and the next step work.
- Someone owns corrections and future updates.

After publication, keep the evidence and approval record with the page address. Review the story when the offer, process or permission changes. Ask the sales team whether it answers a recurring question and whether prospects use it to make a better decision. Page views alone do not show that it helped win a suitable customer.

## When You Want the Website Built Around the Work

The Quiet Protocol builds [professional websites](https://www.thequietprotocol.com/professional-website) and [connected Smart Websites](https://www.thequietprotocol.com/solutions/smart-websites) for service businesses. Bring your approved material and the questions buyers ask. We can organize the agreed evidence, service explanation and enquiry route into a website that makes your work easier to assess.

## Sources and Scope

The [FTC's endorsement guidance](https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking) explains US advertising considerations for endorsements, material relationships and result claims. Use the requirements that apply to your business and location; this worksheet does not provide legal clearance.

[Google's people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) supports useful original information and demonstrated experience. This playbook's interview, evidence sheet and publication workflow are TQP's practical method. They do not guarantee rankings, AI citations or sales. Sources checked October 22, 2026.

Common Questions

## Do we need client names for every case study?

No. Use only the attribution and material cleared for publication. Removing a name does not itself establish permission. A process walkthrough or demonstration can be more suitable when a customer story would expose private details.

## Does this replace the proof-capture system?

No. Capture keeps the original records available. This playbook helps you check those records, interview the people involved and prepare an approved story for publication.

Related Resources

[Playbook AI Business OS Playbook A strategic playbook for service businesses that want to understand how AI receptionist workflows, lead response, review growth, proof architecture, and website authority fit together as one AI Business Operating System.](https://www.thequietprotocol.com/resources/free-tools/ai-business-operating-system-playbook) [Template Pack Missed-Call Text-Back Pack A free swipe file of missed-call text-back templates for small businesses, including urgent home services, clinics, and consultation-driven firms.](https://www.thequietprotocol.com/resources/free-tools/missed-call-text-back-swipe-file)

Best for

Owners, operators, marketers, and client-facing teams responsible for turning real work into usable proof

Asset Pack

Open the branded pack, grab the PDF guide, and use the working asset inside your business immediately.

[Open the printable case-study playbook](https://www.thequietprotocol.com/downloads/case-study-capture-playbook)

[pdf PDF guide A branded PDF version for saving, sharing, and forwarding internally.](https://www.thequietprotocol.com/api/downloads/case-study-capture-playbook/pdf) [source Editable source document The editable written version for teams that want to adapt the asset.](https://www.thequietprotocol.com/api/download-sources/case-study-capture-playbook.md) [web Live web guide The browser version with notes, context, and conversion next steps.](https://www.thequietprotocol.com/downloads/case-study-capture-playbook)

Related Links

[Proof capture operating system](https://www.thequietprotocol.com/resources/free-tools/proof-capture-operating-system) [Proof-to-pipeline scorecard](https://www.thequietprotocol.com/resources/free-tools/proof-to-pipeline-scorecard) [Proof](https://www.thequietprotocol.com/proof)

Next Step

## Want the real number behind the leak?

The Revenue Leak Diagnostic turns missed calls, slow follow-up, and weak intake into a revenue estimate you can actually act on. Use the guide, then run the number.

Monthly Intelligence

### The Front Door Report

One real case study. One industry benchmark. One tactical fix. No filler. Service business owners read it because it is the only email that shows them exactly where their revenue is leaking.

No spam. Unsubscribe anytime. By subscribing you agree to our [Privacy Policy](https://www.thequietprotocol.com/privacy).

Use it with confidence

## See the public proof behind this work.

This resource is free and practical. If it helps you uncover a larger front-door problem, you can review the founder, customer proof, case studies, and investment approach before speaking with us. This is especially relevant for Case Study Capture Playbook for Small Businesses. The examples are framed for Owners, operators, marketers, and client-facing teams responsible for turning real work into usable proof.

The Quiet Protocol AI Systems & Automation

Verified Business

Operating publicly as The Quiet Protocol, with a verifiable business profile, named founder, proof library, and clear commercial scope.

[Proof](https://www.thequietprotocol.com/proof) [Investment & Scope](https://www.thequietprotocol.com/investment) [Press and partner kit](https://www.thequietprotocol.com/press-kit) [Founder profile](https://www.thequietprotocol.com/about)

[Customer proof and case studies Evidence you can inspect on-site See customer experience, working demonstrations, measured outcomes, and the evidence standard attached to each claim without leaving the site. Inspect detail](https://www.thequietprotocol.com/proof) [Scoped commercial boundary Written scope before work begins The investment page explains how TQP separates what stays, what changes, what is built, and what is managed before presenting a proposal. Inspect detail](https://www.thequietprotocol.com/investment) [Founder Vikram Roy The founder profile, article bylines, and LinkedIn profile let you see who is responsible for the thinking and the work. Inspect detail](https://www.thequietprotocol.com/about) [Company facts and assets The Quiet Protocol AI Systems & Automation The press and partner kit keeps the company name, contact details, service area, founder profile, brand assets, and proof links in one place. Inspect detail](https://www.thequietprotocol.com/press-kit)