Turn Project Notes Into a Proof-Driven Case Study

The raw material for a credible case study usually lives in project notes, approvals, decisions, and measured results. The challenge is shaping that evidence into a clear story without turning it into fiction.

This guide helps you create a concise case study that shows the starting situation, important decisions, work completed, evidence, and lessons a buyer can trust.

What you need

• Project notes, timeline, deliverables, and approved outcomes
• Customer permission and quote approvals
• Before-and-after evidence or a clear statement that results are qualitative

The workflow

1. Build a fact ledger

List every date, deliverable, decision, result, and quote with its source. Mark anything unverified before drafting.

2. Find the useful tension

The story is not that your business was brilliant. It is the customer's starting constraint, the key choice made, and why that choice mattered.

3. Show the mechanism

Explain enough of the approach that a buyer understands what created value. Avoid vague language such as transformed or optimized without detail.

4. Separate result from attribution

A metric may improve during the project without being caused entirely by your work. Use careful language when attribution is uncertain.

Copy this working prompt

Replace every bracketed field with verified information from your business. If you do not know something, write unknown instead of guessing.

Act as a case-study editor. Use only the approved facts below.

Customer and project:
[PASTE APPROVED DESCRIPTION]

Starting situation:
[PASTE VERIFIED FACTS]

Goals and constraints:
[PASTE VERIFIED FACTS]

Timeline, decisions, and work completed:
[PASTE NOTES]

Results and evidence:
[PASTE VERIFIED NUMBERS, OBSERVATIONS, OR WRITE NO MEASURED RESULT]

Approved customer quotes:
[PASTE APPROVED QUOTES OR WRITE NONE]

Attribution limits:
[DESCRIBE OTHER FACTORS OR UNCERTAINTY]

Write a case study with headline, summary, starting situation, challenge, approach, key decisions, result, attribution note, customer quote if approved, practical lesson, and next step.

Create a fact ledger after the draft that maps every number, quote, and result claim to its source. Mark missing information [CONFIRM]. Do not invent scenes, dialogue, emotions, metrics, quotes, or causation.

Run a second-pass review

The first output should not be the final answer. Use this challenge prompt to find weak evidence, hidden assumptions, or avoidable risk.

Act as a skeptical editor. Identify every sentence that overstates causation, hides uncertainty, uses vague success language, or needs customer approval. Rewrite it accurately without weakening the useful lesson.

What good looks like

• Every claim has a source
• The method is understandable
• Uncertainty is disclosed instead of hidden

Review before you use it

• Did the customer approve their name and quotes?
• Can every result be traced to evidence?
• Does the case study avoid implying guaranteed outcomes?

Privacy and judgment guardrails

• Remove passwords, payment details, private health information, and confidential customer data before pasting anything into an AI tool.
• Treat the output as a working draft. A person remains responsible for the decision, promise, price, and final send.
• Do not let AI invent customer quotes, financial figures, legal terms, capabilities, deadlines, or proof.

Your next action

Send the fact ledger, not just the polished draft, to the person approving the case study.

If your AI tool still lacks the context to do this well, first Create a reusable business brief.