What we started withThe same facts, as an email
Fictional project email
Cedar Studio × Signal Desk — next steps after kickoff
Hi Mira and Jules,
Here is our September 7, 2026 snapshot. Our agreed first useful result is to review one weekly campaign summary, identify one change and record one next action in the existing project thread. We have not achieved that yet.
The pilot covers one campaign, supplied synthetic data, a draft and a guided review. Live account connections, historical imports and company-wide rollout are excluded. Mira, please confirm the campaign and the meanings of its supplied fields in the project thread. Those inputs are pending.
I will prepare the draft after those inputs are confirmed, using only the supplied source. Drafting has not started. Jules will then check totals against that source, identify a change and record the next action in the thread. The review has not happened; none of the milestones is complete.
At kickoff we proposed review within five working days after input confirmation. No date or booking is confirmed, and this is not a service commitment. While waiting I can demonstrate the format using a synthetic sample, but no demonstration is recorded as complete, and a demonstration would not count as customer first value.
Please send questions and confirmations in the same thread; no response time is promised. I will update this snapshot after review. It is not live tracking and contains no credentials, private customer information or working system links.
Theo, plan owner
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>Cedar Studio · First useful report</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f6f8f5;color:#20352f;font:17px/1.65 system-ui,sans-serif}main{max-width:960px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.12 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.25 Georgia,serif}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.5 system-ui,sans-serif;letter-spacing:.1em;text-transform:uppercase}.intro{font-size:20px}.action{background:#174b40;color:#fff;padding:26px;margin:28px 0}.action p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,235px),1fr));gap:20px;margin:24px 0}.card{background:#fff;border:1px solid #bfcec4;padding:24px}section{margin:36px 0}ul,ol{padding-left:23px}li{margin-bottom:14px}.note{color:#455e53;font-size:14px}.pending{border-left:5px solid #92651d;padding-left:20px}footer{border-top:1px solid #bfcec4;padding-top:24px;margin-top:40px;font-size:14px}@media print{body{background:white}.card,.action{break-inside:avoid}}
</style></head><body><main>
<header><p class="label">Cedar Studio + Signal Desk / Fictional example</p><h1>Your first useful report. One clear next step.</h1><p class="intro">Review one weekly campaign summary, identify one change, and document one next action in the existing project thread.</p><p class="note">Agreed at kickoff · First value is not yet achieved.<br>Reviewed snapshot: September 7, 2026 · Plan owner: Theo</p></header>
<aside class="action"><p class="label">Customer action / Inputs pending</p><h2>Mira, confirm the campaign and field meanings.</h2><p>Use the existing project thread. Those inputs unlock Theo’s report draft. Draft work has not started.</p></aside>
<section><h2>A responsibility on each side</h2><div class="grid"><article class="card"><p class="label">Customer / Mira</p><h3>Confirm the inputs</h3><p>Choose the campaign and confirm the meanings of its supplied fields in the project thread.</p><p class="note">Status: required inputs pending.</p></article><article class="card"><p class="label">Vendor / Theo</p><h3>Prepare the report draft</h3><p>Start after required inputs are confirmed. Use only the supplied source, with no live account access.</p><p class="note">Status: not started.</p></article><article class="card"><p class="label">Customer / Jules</p><h3>Review and record the action</h3><p>Check totals against the supplied source, identify one change, and record one next action in the existing project thread.</p><p class="note">Status: review not yet performed.</p></article></div></section>
<section><h2>The path to the first result</h2><ol><li><strong>Inputs confirmed.</strong> Mira supplies the campaign and field meanings before draft work begins.</li><li><strong>Draft prepared.</strong> Theo turns the confirmed inputs into a report for Jules to review.</li><li><strong>Customer review recorded.</strong> Jules checks the totals and records the observation and next action in the project thread.</li></ol><p class="note">No milestone is marked complete in this snapshot.</p></section>
<section class="pending"><p class="label">Timing / Proposed, not booked</p><h2>The clock depends on confirmed inputs.</h2><p>Review is proposed within five working days after required inputs are confirmed. No calendar date or booking is confirmed. This interval is not a service commitment.</p></section>
<section><h2>What this first phase includes</h2><div class="grid"><article class="card"><h3>In the pilot</h3><ul><li>One campaign.</li><li>Supplied synthetic data.</li><li>A report draft.</li><li>A guided customer review.</li></ul></article><article class="card"><h3>Outside this phase</h3><ul><li>Live account connections.</li><li>Historical imports.</li><li>Company-wide rollout.</li></ul></article></div></section>
<section><h2>A demonstration can help. It is not the result.</h2><p>While inputs are pending, Theo can show the format with a synthetic sample. That demonstration does not count as customer first value. No demonstration is recorded as complete.</p><p>The evidence we need is Jules’s review of the report totals, an identified change, and a next action recorded in the project thread. That review has not happened yet.</p></section>
<section class="card"><h2>Questions and changes belong in the project thread.</h2><p>Ask Theo there if an input or instruction is unclear. No response-time promise is supplied. Record task changes and customer confirmation there; Theo updates this page after review.</p><p class="note">This is a reviewed snapshot, not live progress tracking. It does not collect inputs or provision access.</p></section>
<footer>Fictional worked example by share/artifacts. Organizations, names and dates are invented for demonstration. Source: the fictional kickoff notes accompanying this example. No private customer data, credentials or working system links are included.</footer>
</main></body></html>