Write a Client Case Study from Project Notes Without Invented Results

Turns your raw project notes into a problem-approach-result case study that uses only your real numbers and never fabricates client quotes.

You getHeadline, at a glance and the Problem

Prompt

Prompt
You are a B2B copywriter who writes case studies for freelancers and independent consultants.

I will paste my project notes right after this prompt. Turn them into a client case study. If the notes do not cover these points, first ask me up to 3 short numbered questions in one message, then wait: whether to name or anonymize the client, what the main result was, and whether I have a real client quote.

Rules:
1. Use only numbers, dates and outcomes found in my notes or answers. If a result was not measured, describe it plainly with no figure.
2. Never write a client quote. If I paste one, use it word for word. If I have one but did not paste it, add the line "Client quote goes here: use their exact words." If I have none, drop the quote section.
3. The problem section covers the client's situation and what it cost them, not my skills.
4. Every approach step starts with a verb and describes what I actually did.
5. Keep it 300-450 words with no hype adjectives.

Output format:
- Headline (result-led, under 12 words)
- At a glance: Client, Industry, Timeline, Services
- The Problem (one paragraph)
- The Approach (3-5 numbered steps)
- The Result (bullets, each tied to a figure from my notes or marked qualitative)
- Client quote (only per rule 2)
- One-line call to action

Finish with a short list of claims I should double-check before publishing.

Example output

At a glanceLarkfield Home checkout: before and after redesignResults in the six weeks after launch
ItemBeforeAfter
Checkout completion41%53%
Delivery support tickets per monthAbout 120About 70
Checkout screens42
Account creationForcedOptional

Example for: a freelance UX consultant who redesigned checkout for a small online furniture store; client has a quote but it was not pasted.

Checkout Completion Rose from 41% to 53% in Six Weeks

At a glance

  • Client: Larkfield Home (online furniture retailer, 9 staff)
  • Industry: E-commerce, home goods
  • Timeline: March to mid-April, 6 weeks
  • Services: Checkout audit, usability testing, redesign specs

The Problem

Larkfield Home was losing more than half of shoppers who started checkout. Only 41% of carts that reached the shipping step became orders. The support inbox was taking about 120 tickets a month asking about delivery dates and fees, which customers could not see until the final screen. The two-person support team was spending most of its week answering the same question, and the owner suspected surprise shipping costs were driving people away but had no data to confirm it.

The Approach

  1. Reviewed three months of analytics to find where shoppers left checkout.
  2. Ran five remote usability sessions with recent Larkfield customers.
  3. Moved the delivery cost and date estimate onto the product and cart pages.
  4. Cut checkout from four screens to two and removed the forced account creation.
  5. Wrote handoff specs for Larkfield's developer and checked the build before launch.

The Result

  • Checkout completion rose from 41% to 53% in the six weeks after launch.
  • Delivery-related support tickets fell from about 120 to 70 per month.
  • Account creation is now optional, and the owner reported fewer complaints about passwords (qualitative, not measured).

Client Quote

Client quote goes here: use their exact words.


Losing shoppers at checkout? Book a 20-minute call to see where your funnel leaks.


Check before publishing

  • Confirm the 53% figure covers the same traffic sources as the 41% baseline.
  • Ask Larkfield for written permission to use their name and numbers.
  • Verify the ticket count of 70 is a monthly average, not a single month.
  • Confirm the six-week window did not overlap a sale or holiday spike.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Restricting figures to your notes stops the model from inventing impressive but false percentages.
  • The quote rule prevents fabricated testimonials and leaves a clear marker when you have a real one to add.
  • The closing check list flags weak claims and permission issues before the case study goes public.

Use after a project wraps and you want a portfolio piece. Have your notes, before-and-after numbers and any real client quote ready to paste into ChatGPT, Claude or Gemini.

Common edits

  • Ask for a 120-word version for a LinkedIn post or proposal appendix.
  • Tell it to anonymize the client as an industry descriptor if you lack permission to name them.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business