Skip to content

The daily brief

The daily brief is one composed summary of your company’s day: a headline, the things that need your decision, and a line per head. It is generated once a day per company, kept on its own page, and it is the surface a founder is meant to open first.

It reports and links. Nothing on it executes anything — every item takes you to the place where a person decides.

The full brief lives at /brief, and a compact version sits near the top of your overview screen as the Your CEO Brief card, showing today’s headline and up to three items that need you.

The brief page is not in the left sidebar. You reach it from the overview card’s “open” link, or by going to the address directly.

When no brief has been composed yet, both surfaces say so in plain words — “No brief yet — it’s composed each morning” — rather than showing an empty shell that looks broken. The overview screen itself is covered in the overview cockpit.

Every brief carries four things: a state of the business headline, a Needs you list with a count, a By Head section with one line per head, and a footer with how many key results synced and what you spent today.

Three further sections appear only when they have something to say, and are left out entirely otherwise — no zeros, no filler:

  • To move your goals — key results with no live source, unbound guards, guard breaches, and approvals waiting on you.
  • Competitor moves — competitors scanned this week, grouped by offering.
  • Web behavior — website metrics that are bound to a key result, with a day-over-day change and a warning marker when a frustration signal is at least twice its seven-day baseline.

The headline and the per-head summaries are written by a model from the real counts. The model rewords prose only — it never touches the numbers, the needs-you list or the spend figure, and if it fails you get the plain generated version instead of nothing.

When is it composed, and can you get one early?

Section titled “When is it composed, and can you get one early?”

The background worker ticks every 15 minutes and composes your brief once your company’s local send time has passed for that day. The default send time is 08:00, and the clock used is Europe/Berlin — a per-company time zone is not configurable yet.

You get one brief per company per day. Running it again the same day refreshes the existing brief with newer numbers rather than creating a second one.

To get one immediately, press Generate brief now at the top right of the brief page. That control is owner or admin only; if your role is lower, the page tells you it failed rather than pretending it worked.

In-app always, and email if you switch it on. The controls are in Settings, on the card titled Daily Brief delivery: In-app is checked and locked, Email is the one channel you can enable, and a Send time (local) field sets when the brief is composed and sent. Saving needs admin rights.

The email goes to the account owner’s address on your company’s Business-Gym account. That makes it a notification to yourselves rather than a message to a customer, which is why it does not sit behind an approval — the external-send rule described in autonomy and the hard floor is untouched by it.

Teams, WhatsApp and SMS are listed on the same card as “coming soon” and are greyed out. They are shown rather than hidden so you can see what exists — but they cannot be selected.

What happens to the Teams version of the brief?

Section titled “What happens to the Teams version of the brief?”

It is staged as an approval, never sent automatically. The Teams path is built so that instead of posting, it creates a draft approval in your queue carrying the brief text, and reports the channel as staged rather than delivered. A send happens only after a person approves that draft.

Today it stops earlier than that. Teams cannot be selected in Settings, and the server-side gate for the Teams path is off in production — so nothing about the brief reaches Teams yet. Treat this section as how the mechanism is designed, not as something you can turn on from the product.

If a staged draft ever does appear for you, it is worked like any other item in the approval queue.

How is the brief different from the CEO digest?

Section titled “How is the brief different from the CEO digest?”

The brief is a composed snapshot of one day; the CEO digest is a live page that re-reads your current state each time you open it. You will find it in the sidebar under Measure → CEO digest, at /ceo-digest.

The digest is also the surface where you can act in place: it shows up to five of your open approvals as decision cards with approve and reject buttons, posting to the same endpoint the approvals page uses. The brief page has no such buttons — its items are links.

Digest sections whose source is not wired show a status chip saying so instead of a number. That is the same honesty rule the brief follows when it omits an empty section.

It will never act on your behalf, and never report something that did not happen. Autonomy across the platform is supervised and propose-only, and the brief is a reporting surface on top of that — not an exception to it.

Two consequences worth knowing:

  • Every button on the brief page is navigation. “Approve”, “Review”, “Send” and “Decide” take you to the approval or the head where the decision is made.
  • If a delivery channel fails, the failure is logged and retried on the next tick, and the channel is not recorded as delivered. You never see a “sent” for a message that never went out.

Next: read how decisions are actually made in working the queue, or how a head produces the work the brief summarizes in working with a head.