The briefing
It sees your whole business.
Every morning, Nerve reads your real rows — revenue, pipeline, spend, operations — and assembles the operating picture: a greeting that says what changed while you were gone, the one thing that needs you most, and the numbers behind it. This is the actual dashboard, not an illustration.
What changed
The overnight feed.
While you were away, deals moved, revenue landed, and campaigns drifted. Nerve turns those raw events into a short readable feed — each line traced to the module it came from, so “a record revenue day” is one click from the orders behind it.
It ranks by consequence, not recency: the Whole Foods contract advancing outranks a routine sync, even if the sync happened later.
Watching
Forward calls, with receipts.
Beyond what already happened, the briefing carries what Nerve expects to happen: each prediction has a likelihood, a basis, and a resolve-by date. When the date arrives, the call gets graded against reality.
The track record is honest by design — until enough predictions have resolved, Nerve shows “building track record” instead of inventing an accuracy percentage.
Honest gaps
When it can't know, it says so.
Ask a question the data can’t support and the briefing doesn’t improvise — it declines, names the reason, and lists exactly which inputs would unlock the answer. This is a real refusal captured from the engine, not marketing copy.
The same honesty runs through the KPI rail: a metric without enough data shows “not enough data yet,” never a fabricated number.
The sources
Where the numbers come from.
Connect Stripe and your books once; Nerve pulls and categorizes every 15 minutes and stamps each metric with its source and freshness — the rail literally says “Stripe · synced 2m ago.”
Anything you haven’t connected can be entered manually and is labeled as such. The briefing never hides where a number came from.