← All examples

SAME INFORMATION. A DIFFERENT WAY TO SHARE IT.

A customer review that does not confuse adoption with value

A fictional account review keeps a measured adoption change separate from unmeasured time savings and the next proposed plan.

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 send this as an email.

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

Email · Fictional example

Harbor Ops — quarterly review and proposed next step

Hi Elena,

For our October 5, 2026 review, our earlier objective was to reduce report preparation time. We still lack a preparation-time baseline, target reduction and monetary value.

Weekly active analysts increased from 4 of 10 in the April–June review to 7 of 10 in July–September. Active means creating at least one report in the final complete week of each period, with the same ten eligible analysts. These are final-week snapshots, not quarterly averages or evidence of work volume or time saved.

Two customer comments describe easier navigation, but we have no quotation text or evidence that all ten analysts share that view. I delivered the glossary and you confirmed acceptance in the account record; that also does not prove reduced preparation time. Template maintenance ownership remains unconfirmed between us.

Could you approve or revise a two-week timing exercise using a consistent report task? This is a proposed duration, not a booked start. Participants, method, data handling, owner and success threshold need agreement first. No renewal, expansion, commercial terms or customer resources are committed, and no revenue, savings or ROI data is available.

Let us record next steps in the existing customer workflow. This is a reviewed snapshot, not an account-platform update; source record URLs are not supplied.

Ravi, account lead

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>Harbor Ops · Quarterly customer review</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f5f8fc;color:#182e46;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:#23486b;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 review / October 5, 2026</p><h1>Adoption is up. Time savings are still an open question.</h1><p class="intro">Harbor Ops · July–September review · Customer lead Elena / Account lead Ravi</p></header>
<section class="lead"><p class="label">Customer objective</p><h2>Reduce report preparation time.</h2><p>No baseline or target reduction was collected. We cannot yet say whether this objective improved.</p></section>
<section><h2>What the adoption evidence shows</h2><div class="grid"><article class="card"><p class="label">April–June review</p><span class="metric">4 of 10</span><h3>Weekly active analysts</h3></article><article class="card"><p class="label">July–September review</p><span class="metric">7 of 10</span><h3>Weekly active analysts</h3></article></div><p>Same ten eligible analysts. “Active” means at least one report created in the final complete week of each review period.</p><p class="note">These are final-week snapshots, not quarterly averages. They do not measure output volume or time saved.</p></section>
<section><h2>Progress and gaps beside each other</h2><div class="grid"><article class="card"><h3>Glossary delivered and accepted</h3><p>Ravi delivered it; Elena confirmed acceptance in the existing account record. This does not establish faster report preparation.</p></article><article class="card"><h3>Template ownership unconfirmed</h3><p>No maintenance owner has been agreed. Do not assign the work by implication.</p></article></div><p>Two customer comments describe easier navigation. No quotation text was supplied, and this is not feedback from the entire analyst group.</p></section>
<section class="warning"><h2>Decision requested—not a new commitment</h2><p>Elena: approve or revise a proposed two-week timing exercise using a consistent report task.</p><ol><li>Agree the participants, method, and data handling.</li><li>Confirm an owner and success threshold.</li><li>Agree a start date only after those conditions are settled.</li></ol><p>Two weeks is a proposed duration. No start date is booked.</p></section>
<section><h2>What this review does not claim</h2><p>No savings, ROI, renewal, expansion, or customer resource commitment is established. Record agreed next steps in the existing customer workflow; this page does not collect approval or update account records.</p><p class="note">Source: the accompanying fictional quarterly notes. Reference URLs were not supplied.</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 customer review that does not confuse adoption with value | share/artifacts