A BETTER WAY TO SHARE THE WORK
Tell a customer story the evidence can support
A believable result is more useful than a bigger claim you cannot substantiate.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
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.
01 / SEE THE DIFFERENCE
A smaller, defensible before-and-after
All organizations and measurements in this example are invented; it is not a real endorsement.
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.
Open a complete fictional HTML example, with its source notes →
Create my customer case study02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
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.
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.
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.
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.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
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.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- 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.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
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.