Case Note Testimonials

実際のケースノートから作る、正直なお客様の声を

セッションノート、プロジェクト記録、クライアントのメールを、具体的で承認済みのお客様の声セクションに整えます。状況、変化、結果をクライアント自身の声で表し、公開前に必ず書面の承認を得ます。

こんな方におすすめ

満足したクライアントと強い成果を持ちながら、磨き上げられた推薦文がないチーム

所要時間

1〜2時間

レベル

初級

3ステップでインストール

登録不要。CLIツールも不要です。お使いのAIを選んで、1行コピーして貼るだけです。

Pro — 全511件のスキル

ご自分で入れたい場合は、スキルを購入（$4.99）し、購入完了画面からZIPをダウンロードして、上のディレクトリに展開し、AIのセッションを再起動してください。結果は同じです。すでに購入済みの場合は、AIアシスタントにダウンロードしてもらうこともできます。

パックの内容

SKILL.md（手順書）1点とスターターテンプレート1点が入っています。プレビューはこちらです：

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.
Lay out the section (input: approved testimonials → output: testimonial section)
Arrange 3–6 testimonials with variety: different problems, different outcomes, different kinds of clients. Lead with the one whose problem matches your reader's problem — the first testimonial is the one that decides whether anyone reads the second. Pair each quote with a face or logo if you have permission; a wall of text-only quotes reads like it was written by one person. Keep the section scannable: quote first, attribution second, context line third.

テンプレートのプレビュー

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}