A few sentences in. A briefing out.
One example for each product: the situation as a customer would type it, and the call as the report delivers it. These are illustrative examples, written to the shape of a current Decision Report — the structure, the sections and the kind of answer are real; the scenarios are invented so nothing here is anyone's actual situation.
Below are three briefings. Each one starts with a plain-English recommendation — The Call. Everything after it is the reasoning, so you can check it: where the AI reviewers disagreed, what would change the call, and how confident the system is and why.
Something happened. What do we say?
A food company, a positive lab result at 4:40 on a Thursday, and nothing written. Five sentences describing the situation — no draft statement.
A lab result at 4:40, and nothing written
A batch of our chilled dip tested positive and has to come off shelves. About 9,000 tubs shipped to grocery stores in three provinces between the 8th and the 14th. Our largest retailer knows and is clearing it overnight; the inspection agency has been notified. We have had no illness reports. We have no statement and we need one tonight.
A Crisis Decision Report — with the statement drafted, tested and revised
Publish tonight, and lead with the batch codes. The audience that matters in the first twelve hours is the person standing in their kitchen holding the tub, not the trade press. Open with the batch codes and best-before dates, then the symptom to watch for and how long it can take to appear, then what to do with the product and how the refund works. Say what you know, and name what you do not know yet. Name the inspection agency you notified, and give a direct line with a person's name on it. Cut the sentence beginning “we take food safety seriously” — every segment read it as the company talking about itself while they were working out whether their child will be ill.
- The Call
- Operating Reality
- Who's Reacting
- What's Spreading
- Recommended Response
- What to Avoid
- Evidence & Confidence
- Your Original Input
We're about to say this. Will it land?
An independent fitness studio has to announce its first price increase. The email to test, and the brief behind it.
A fitness studio raising its price, and the email that has to say so
An independent studio with about 600 members, the first increase since it opened. The owner is worried about the long-time members who joined at the founding rate, and about the two competing gyms that opened nearby last year. No discount or freeze is on the table.
A Campaign Decision Report
Refine first. The number lands; the reason doesn't. Long-time members read “costs have risen” as a shrug and “thank you for being part of this community” as the sentence before bad news. Say what the increase pays for in one line — the instructors kept, the hours kept — and give the founding-rate members their own sentence: what they got for three years, and that nothing else changes. Send the two versions to the two groups. Do not add a discount you haven't decided on: the audience that wants one is real, and that is a finding for you, not a line for the email.
- The Call
- Strategic Position
- Audience Reaction
- What Resonates / What Creates Friction
- Reach & Performance Forecast
- Recommended Refinements
- Risk & Watch-outs
- Evidence & Confidence
- Your Original Input
They're already talking. Do we step in?
A town's parking bylaw, the thread under the announcement, and a communications lead who hasn't replied yet.
A town's parking bylaw, and the thread under it
A link to the local paper's story on the new downtown parking bylaw — 140 comments in two days, three residents doing most of the talking, a councillor named twice, and no reply from the town yet. “Do we respond, and does responding make it worse?”
A Pulse Decision Report — and the re-reads that follow
Stay out for now. The thread is plateauing on its own: three of the four arguments gaining ground are about the bylaw's timing, not its substance, and the two voices carrying it have drawn no new participants in a day and a half. A reply from the town re-opens it. If the named councillor is drawn in, step in within the day with a facts-only correction — a reply we tested separately, against staying out.
- The Call
- What We're Reading
- Where This Conversation Lives
- Where It's Heading
- What's Gaining Ground
- Who's Carrying It
- If You Step In
- What Changed Since the Last Reading
- Evidence & Confidence
- Your Original Input
What you're looking at when you open one.
- The CallThe recommendation the evidence supports, in the first paragraph. Share it as-is with the people who decide.
- Findings, with citationsEach one points at the specific simulated reactions it rests on. If you doubt a finding, follow the citation.
- Where the reviewers disagreedThe AI reviewers' split, printed. This is usually the most useful section — it tells you where the real uncertainty is.
- What would change the callThe observable events that would reverse each finding. Watch for them; they're your early-warning system, and the follow-up we ask you later.
- Recommended actionsEach with an owner, a timeframe, and the evidence behind it.
- A confidence readingIt only moves down, with the reasons beside it. Contested situations read low. That's correct.
- Your original inputReproduced exactly as submitted, so anyone reading the report can see what the scrutiny examined.
Live from the catalog — what the app charges today.
Every name, description and price below is read from the same catalog the app bills from, at the moment you load this page. Change a product in the back office and this page changes with it.