← All guides

From customer notes to a defensible result

A result readers can believe.

A customer case study connects an approved customer story to the work performed, measured results and limits of the evidence.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method
  1. 01
    Show the comparison.

    90 minutes became 60 across four preparations in each period.

  2. 02
    Keep other changes visible.

    The team also narrowed report scope; the outline’s effect is not isolated.

  3. 03
    Leave the quote out.

    No testimonial was supplied. A polished story does not create customer approval.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Your evidence. Your agent. A believable customer story.

Bring approved context and checked measurements. Let the result stand without inventing a testimonial or causal claim.

Start with three things

  1. Customer-approved context and sharing permissions.
  2. The changes made, including concurrent changes.
  3. Comparable measurements, limitations and exact approved quotes.
Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the case studyFrom a bigger claim to a supportable story

How do I create an evidence-led customer case study?

Give your agent the approved customer context, what changed, measured results and the limits of those measurements. Ask for a story that connects the problem, work and evidence without turning correlation into a promise. Confirm customer permissions and every quotation before sharing the reviewed page.

What to give your agent

  • Customer-approved background and the scope permitted for external sharing.
  • The actual work performed and its dates, including other changes that may affect results.
  • Measured before/after values with definitions, time periods, sample sizes and limitations.
  • Exact approved quotations and attribution permissions, or an explicit decision to use no testimonial.
  1. Start with permission, not polish

    Check what the customer permits you to name, quote and describe. Permission to analyze a support conversation is not permission to publish it. Keep the final approval record in your existing process and ask about missing permissions before drafting identifying material.

  2. Define the problem at the right scale

    Describe the specific team and task rather than implying a company-wide transformation. Preserve the starting conditions and explain what was actually changed. Do not quietly omit concurrent changes that could contribute to the outcome.

  3. Make the result auditable

    Put periods, units and measurement limitations beside the headline. Compare like with like and check arithmetic independently. A before/after observation is not proof your service caused every improvement or a guarantee another customer will see the same result.

  4. Let the evidence carry the story

    Use a readable HTML page with problem, intervention, checked result and limitations. Include a quote only if its exact wording and attribution are approved. Share the draft with the authorized reviewer; do not generate a testimonial to fill an empty design slot.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →
Using only authorized materials, draft a customer case study with the approved customer context, problem, work performed, checked results and measurement limitations. Ask for missing permissions, dates, units and evidence. Preserve concurrent changes and distinguish observed results from causal claims or guaranteed outcomes. Use only exact approved quotations with approved attribution; do not invent endorsements, customer identities, metrics or approval. If no quote is supplied, omit the testimonial. Use readable static HTML with no scripts or forms and my saved style if available. Show the draft and permission gaps for review. Do not publish or change access without separate explicit approval.
Check before you shareAccuracy, clarity, and permission
  • Are customer name, scope and quotes approved for this audience?
  • Are periods, samples, units and calculations comparable?
  • Are concurrent changes and attribution limits visible?
  • Does the page avoid fabricated testimonials or guaranteed outcomes?

When HTML fits

An evidence-led story buyers can read or forward, with supporting detail near each result.

When another format fits better

A page does not obtain customer consent or replace the underlying measurements. Keep approval records and sensitive source data in their authorized systems.

What we started withThe same facts, as a wiki page

Fictional team wiki

Elm Studio — reporting preparation story draft

About this draft

Prepared September 7, 2026, by Casey. This is an illustrative fictional story, not a real customer endorsement. No real customer quotation, logo or identity is used.

Changes and observations

Authors previously started weekly reports from different outlines. The team introduced a shared outline and narrowed report scope at the same time. Four preparations before and four after used the same preparation-time definition. Average time was 90 minutes before and 60 after: a 30-minute decrease. Individual observations and variation are not available.

Limits of the comparison

The small, uncontrolled comparison does not isolate the outline’s effect because scope changed too. It cannot promise equivalent results elsewhere. Only preparation time was measured: not revenue, retention, comprehension or decision quality. No future-savings forecast is available.

Attribution and permission

No testimonial, customer approval or paid relationship is supplied. A real publication would require permission for the final text and attribution.

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Elm Studio · Reporting story</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#faf6fa;color:#302439;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#53355f;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Fictional case study / September 7, 2026</p><h1>A shared outline. A smaller report. Less preparation observed.</h1><p class="intro">Elm Studio compared four weekly preparations before and four after two reporting changes. This is an invented example, not a customer endorsement.</p></header><aside class="lead"><h2>30 minutes lower average preparation.</h2><p>90 minutes before; 60 minutes after. Four preparations in each period. Individual variation is not supplied.</p></aside><section><h2>What changed</h2><p>The fictional team had been starting from different outlines. It introduced a shared outline and narrowed the scope of its weekly report at the same time.</p></section><section><h2>What the observation supports</h2><p>The recorded average preparation time was lower: 90 − 60 = 30 minutes. Both periods use the same definition of preparation time.</p></section><section class="warning"><h2>What it does not establish</h2><p>Because scope changed too, the comparison does not isolate the outline’s effect. This small sample is not a controlled experiment. No revenue, retention, reader comprehension or decision-quality data was collected.</p><p>No future savings or equivalent result for another team is promised.</p></section><section><h2>No invented testimonial</h2><p>No quote is supplied. This demonstration includes no real customer logo, identity, paid relationship or approval. A real story needs permission for the final text and any attribution.</p><p class="note">Prepared by Casey from the fictional notes accompanying this example.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>
The original worked scenarioThe source scenario, step by step

A smaller, defensible before-and-after

All organizations and measurements in this example are invented; it is not a real endorsement.

The original notes

Fictional Elm Studio compared four weekly report preparations before and four after adopting a shared outline. Average preparation was 90 minutes before and 60 minutes after: 30 minutes lower. The team also narrowed the report scope. Only preparation time was measured; no revenue or reader-outcome data. No customer quote is supplied.

Context

Elm Studio compared four weekly report preparations before and four after the change.

Change

A shared outline and narrower report scope were introduced together.

Observation

Average preparation: 90 minutes before, 60 minutes after—30 minutes lower.

Limits

No revenue or reader-outcome data; no customer quote is supplied.

Readers can see the result without mistaking it for an isolated causal effect or testimonial.

Questions, adaptations & sourcesGo deeper when you need to

Can I publish an anonymous story?

Only after checking that the remaining details are permitted and do not identify the customer indirectly. Removing a name alone does not settle permission.

What if we have no numerical result?

Describe the verified work and any approved qualitative observation. Do not invent a percentage or imply an unmeasured benefit was demonstrated.

Can an agent improve a customer quote?

Do not present rewritten words as an exact quote. Use approved wording, or prepare a clearly labeled paraphrase for the customer's separate review.

Further reading