An unsolicited summary has about ten seconds to justify itself. Most of them spend those seconds restating the calendar.
Key takeaways. A briefing is unsolicited, so every line has to earn its place against being deleted unread. Include only what changed, what is close, and what is waiting on you. Every surfaced item needs the plain reason it is there, or the briefing is asking for trust it has not earned. Say when nothing needs attention. A briefing that always finds five things is not reading anything.
The bar an unsolicited summary has to clear. A briefing is different from every other surface in a product because you did not ask for it. That inverts the usual generosity: a page you navigated to gets the benefit of the doubt, and a message that arrives on its own has about ten seconds before it becomes something you skim past every morning without reading. Almost all of them fail the same way. They restate the calendar you already know, add a sentence of encouragement, and list every unread email. All three are cheap to generate and none of them is information, because information is the part you did not already have.
Three things that earn a place. What changed since you last looked. A meeting moved, a deadline shifted, someone replied to the thread you were waiting on. Change is the only thing that is definitionally new, which makes it the safest content in a briefing. What is close. The next commitment, with a relative anchor rather than a timestamp — "in 40 minutes" needs no arithmetic, and 10:40 does. Anything outside today should name its weekday for the same reason. What is waiting on you specifically. Not unread mail. Mail where you are the person who has to do something, which is a much shorter list and the only part of an inbox summary that is worth reading. Everything else is padding. The full task list belongs in the app; a motivational line belongs nowhere; a count of unread messages is a number that has never once changed anyone’s behaviour.
The reason is not optional. The single most important line in a briefing is not the item, it is why the item is there. "Marked important" is not a reason. "You said you would send the numbers by Friday and this thread is the one asking for them" is a reason, and it is checkable. This matters because a briefing is a claim about your priorities made by software, on limited evidence, without asking. The reason is what makes that claim auditable — it lets you disagree with the ranking rather than having to disagree with the whole surface. A briefing that surfaces without explaining is asking for trust it has not earned, and once it is wrong twice without saying why, it stops being read. The same applies to freshness. Anything assembled from cached data should carry a last-refreshed time, because a confident summary of yesterday is worse than no summary at all.
Saying that nothing needs you. A briefing that finds five urgent things every single morning is not reading your accounts, it is filling a template. Real weeks are not uniform, and the days when nothing needs attention are real days. Being able to say so is what makes the other days credible. It also means the length has to be allowed to vary, which rules out designs where a fixed number of slots have to be filled. A quiet briefing is a feature. If the software cannot ever tell you there is nothing to do, it is not measuring anything.
How Drift builds one. Drift assembles a briefing in the background on the Flow and Horizon plans, reading across the accounts you have connected and putting together what changed, what is next, and what is waiting on you. Surfaced email always shows the plain reason it is present, and cached content carries its last-refreshed time. It is assembled, not acted on. A briefing that mentions a thread has not replied to it — drafting happens when you ask, and sending stops for your approval on a card showing the recipients and the full text. The briefing is a read of your day, and reads are the part of this that are free. Where it lands is the ordinary quiet version: the app when you open it, and email if you would rather have it there. The tone is the same as everything else, which is to say it does not congratulate you.
Three things: what changed since you last looked, what is close in time, and what is waiting specifically on you. Anything else — the full task list, unread counts, encouragement — is padding that trains people to skim past the parts that matter.
Proactive daily briefings run in the background on the Flow and Horizon plans. The Free plan can assemble the same view whenever you ask for it; what the paid plans add is having it ready before you open the app.
For a scheduled briefing, yes — assembling it requires reading across the accounts you connected, on the schedule you set. Reading is the part of Drift that runs without interrupting you; nothing in a briefing is sent, replied to or deleted on your behalf.