Case Note Testimonials
Honest testimonials built from your real case notes
Shapes session notes, project records, and client emails into specific, approved testimonial sections: situation, change, and outcome in the client's own voice, with written approval before anything goes live.
Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Buy the skill ($4.99), download the ZIP from your checkout confirmation, unzip it into the directory shown above, restart your AI session — same result. Already bought it? Your AI assistant can download it for you.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Case Note Testimonials
When to use
- You have great client outcomes buried in case notes, session records, or project docs, but no testimonial page
- A client said wonderful things in a call or email but never sent a clean quotable line
- Your testimonials page is full of vague praise ("Great service!") that convinces nobody
- You need a testimonial section for a landing page, proposal, or pitch deck by Friday
- You want testimonials that name a real problem, a real outcome, and a real person — the three things that make them believable
Workflow
- Gather the raw material (input: case notes, emails, call records → output: source pack)
Collect everything the client actually said or did: session notes, thank-you emails, project wrap-ups, support tickets they closed happy. Keep the client's exact words wherever they exist — a paraphrase of a paraphrase is where testimonials turn fake. One testimonial = one client's source pack, with dates attached. - Extract the story (input: source pack → output: story skeleton)
Find the three beats every believable testimonial needs: the situation before ("We were losing two days a week to manual reports"), what changed ("They rebuilt the workflow in a week"), and the outcome with a number if one exists ("Now it takes an hour"). If a beat is missing, mark it missing — don't invent it. A two-beat testimonial with a gap is more honest than a three-beat one with a fabricated middle. - Draft in the client's voice (input: story skeleton → output: testimonial draft)
Write it the way that client talks: short sentences if they're terse, warm and detailed if they're effusive. Keep every quoted phrase verbatim from the source pack; clearly separate quoted words from connective tissue you added. Aim for 40–80 words — long enough to be specific, short enough to be read. Attribute fully: name, role, organization (as they agreed to be shown). - Get approval (input: draft → output: approved testimonial)
Send the draft to the client with the exact words that will appear, where they'll appear, and how they'll be attributed. No testimonial goes live without a yes — a "sounds fine" in a call is not a yes; get it in writing. If they edit, take their edit verbatim. If they decline attribution, offer first-name-only or anonymous-with-context, or drop it. Never publish a testimonial someone hasn't approved in its final form.
Template preview
Case Note Testimonials — Template
One client = one source pack, one approval. No testimonial goes live without a written yes.
Client: {name} | Role: {role} | Organization: {organization}
Source material (keep exact words):
Story skeleton (mark missing beats missing — never invent)
- Situation before: {e.g. We were losing two days a week to manual reports}
- What changed: {e.g. They rebuilt the workflow in a week}
- Outcome (with a number only if the notes support it): {e.g. Now it takes an hour}
Draft testimonial (40–80 words, client's voice)
> {draft — quoted phrases verbatim, connective tissue clearly separated}
