← All examples

SAME INFORMATION. A DIFFERENT WAY TO SHARE IT.

A case study with a bounded result

A fictional reporting change separates measured preparation time from unproven benefits.

Fictional worked example · Not a published customer artifact.

Your agent can use your own context or help you try the fictional sample. Review a draft first; nothing is published without your approval.

01 / The familiar format

You could share this as a wiki page.

A fictional wiki entry with the same underlying facts. Read it here, then compare how the HTML version presents the information.

Team wiki · Fictional example

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.

02 / The HTML version

Same information. See what needs your attention.

This is the complete static HTML example, not a screenshot. Scroll inside the preview to read it all. It has no live data, scripts, forms, or external resources.

Inspect the complete HTML source

This is the authored source for the example. The preview above passes through our HTML sanitizer before rendering in an isolated frame.

<!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>

Make the next one about your work.

  1. Take the task to your agent. We provide a request with the goal, example, and checks. Copy it into the conversation where your context lives.
  2. Supply only what is missing. Use material your agent is authorized to access. Don’t substitute the example’s invented facts for your own.
  3. Review a draft before sharing. Check facts, readability, and sensitive information. Publishing and choosing who can open it are separate, explicit decisions.
Make this with my agent

No publishing connection is needed for an initial local draft. Your agent needs to be able to create an HTML file; preview and connection support vary by client.

A case study with a bounded result | share/artifacts