Inside the brief, under the day band, the assistant offers exactly one observation. Not a digest, not a list: one thing.
Why one
A home screen that opens with six insights is a home screen nobody reads. The constraint is the feature: if only one thing can be said, the thing said has to be worth saying.
The observation is computed against your actual numbers rather than written in advance, and it arrives as it is generated rather than appearing all at once, so the screen is useful before it has finished.
It comes with somewhere to go
Every insight carries a button, and the button knows where the subject lives.
An insight about pipeline opens deals. One about invoices opens finance. Tickets open support, campaigns open marketing, sprints open engineering.
That mapping is deliberately small, and anything without a specific destination falls back to the dashboards rather than guessing. The rule behind it is that an insight you cannot act on from where you are read it is an observation, and observations do not change anything.
What it draws on
The insight is computed against the measures your organisation already tracks, so it is grounded in the same numbers as your dashboards rather than in a separate opinion about your business.
The practical consequence: if a number looks wrong in the insight, it is wrong in the dashboard too, and the fix is upstream in the data rather than in the assistant.
It also reads live data when it needs to, using the same tools the assistant uses everywhere else in the platform.
In a new account it greets instead
For the first day or so of a brand-new workspace, the assistant says hello rather than producing an insight.
This is a real design decision and worth explaining, because it looks like the feature is missing.
A new organisation has almost no data. An insight engine pointed at four records produces statements that are technically true and completely useless: revenue up three hundred per cent, four deals against one. Publishing those on somebody's first morning teaches them that the number is noise, and that lesson is very hard to unteach.
So during the welcome window it greets, and once there is enough history to say something real, it starts saying it.
What it costs
The insight is generated, so it spends credits, and it is generated when you open Home rather than on a schedule.
That is worth knowing for a team of forty people who all open Home every morning. It is a small cost per person and it is not nothing, and it is one of the few places in the platform where simply arriving spends anything.
Where it appears in the brief
It sits between the day band and the rings, which is the middle of the card and the natural resting place for the eye.
That position is doing work. Above it is what is definitely true about today: your hours, your meetings, your tasks. Below it is how the week is going. The insight sits between the two because it is the only element on the page making a claim rather than reporting a fact.
How to read it
Treat it as a pointer, not a verdict. It has noticed something in the numbers. Whether it matters is your judgement, and it does not know what you already know.
Follow the button when it is relevant. The whole design assumes the insight is a doorway. Reading it and staying on Home extracts about a third of the value.
Ignore it freely. Some mornings the most interesting thing in your data genuinely is not interesting. There is no penalty for scrolling past, and no record of whether you read it.
When it is wrong
Two kinds of wrong, and they need different responses.
Wrong number. The insight is reading the same measures as your dashboards, so a wrong figure here means a wrong figure there. Take it up with whoever owns that measure.
Right number, wrong emphasis. It has surfaced something real and unimportant, usually because the thing that actually mattered this week is not measured. That is a genuinely useful signal about what your organisation tracks, and it is worth acting on rather than dismissing.
Why it is generated fresh
It is not written once and cached for the day. Opening Home computes it against the numbers as they stand.
That means the insight at nine in the morning and the one at four in the afternoon can legitimately differ, and the afternoon one is the more current of the two. It also means there is no stale-cache failure mode where the observation is about yesterday.
It is not the Cockpit's reasoning
Both surfaces have the assistant saying something, and they are doing different jobs.
The Cockpit's reasoning explains a specific item already in your queue: why it was ranked as it was and what it suggests doing. It is attached to a thing that arrived.
The Home insight is unprompted. Nothing routed it to you. It comes from looking at your numbers and noticing something.
The practical difference is that the Cockpit is about what other people and systems have sent you, and this is about what nobody has told you yet. Both are useful and neither replaces the other.
When it keeps saying the same thing
An insight that repeats across several mornings is usually correct and is telling you something you have decided not to act on.
Two reasonable responses. Act on it, or accept that the underlying measure is not one you manage, in which case the more useful fix is upstream in which measures your organisation prioritises.
What is not worth doing is treating it as broken. Repetition means the number has not moved.
What it is not
It is not a report. One observation is not coverage, and treating it as such would mean missing everything it did not mention.
It is not personalised to your role beyond your access. It reads what you can see.
It is not a conversation. For anything more than the single observation, the search box and the Conversations tab are where the assistant will actually answer questions, follow up, and remember what you asked.
Did this answer your question?
No, ask a person