One prompt that reads tonight's meetings, the mail that arrived since yesterday, and your open loops, then delivers a single briefing ranked by what will hurt you if you ignore it — so the first thing you read is the day that matters.
You are not behind because you did nothing. You are behind because reconstructing what yesterday actually cost you takes twenty minutes you did not budget for.
Nobody starts the day confused about their job. They start it confused about yesterday — what came in overnight, what was promised, which thread was left mid-thought. That reconstruction is four inboxes and two task lists deep, and it happens before the first useful hour rather than during it.
A 45-minute slot titled 'Acme sync' tells you the meeting exists and nothing else. Whether you need to prepare, whether the last thread with them went unanswered, whether you already have the numbers they will ask for — none of that is on the invite. So the prep happens in the fifteen minutes before, or in the meeting.
An unranked list of forty items reads identically whether the day contains a deadline or a slow Tuesday, and the result is that you work whatever is newest instead of whatever matters. The ranking is the value of the brief — not the collection, which you could do yourself with a filter.
Copy it once, paste it into Zaira, and it assembles the brief before you wake: last night's mail, today's calendar with each meeting pre-read, the tasks nobody has moved, and the three things most likely to derail the day.
Three stages, one goal. The brief lands on a schedule before your day starts, so the first decision you make is a real one instead of a guess about where you left off.
Scheduled for the hour before you wake, it does the collecting while you are not looking. The result is a day you start by deciding rather than by scrolling, and the twenty minutes of archaeology becomes two minutes of reading.
The line that changes behaviour is the asymmetry check — whether they are waiting on you, you are on them, or you had the last word. People arrive at meetings knowing which conversations are stuck, and prep happens the night before instead of in the room.
Because the brief carries forward what you said you'd do and how many days ago you said it, the things that slip — the file you meant to send, the answer you promised — become visible while there is still time, rather than surfacing as an apology weeks later.
The practical questions people ask before handing an agent their whole morning.
For the brief as written, yes — mail and meetings are the two halves, and a brief missing either one is the same archaeology in a different shape. Run it with only Gmail and you still get overnight mail and open loops ranked, which is most of the value. Add the calendar connection when you want the pre-reads and the waiting-on-you asymmetry check, which is the part that changes how you run meetings.
Late enough that it lands after the last of the day's mail, early enough to read before you start — for most people that is somewhere between 6am and 8am in their own timezone. Worth getting right the first time, because a brief generated before the overnight mail arrives is confidently wrong, and you will learn to distrust it.
It ranks, which is the reason the page exists. Step 4 asks for the three things that would be worst to miss, cross-referencing your declared priorities, the calendar's attendee asymmetry, and the staleness of your open loops. It is a reasoned ranking from context you gave it, not a judgement about what matters to your business — which is exactly why the 'what's on fire' section of the context is the one to keep accurate.
It reads what your connected mailbox contains, so treat the exclusion list as real rather than decorative — name the people and prefixes that should never surface in a briefing and it will leave them out. Gmail's own MCP server can be scoped to specific labels if you would rather it never saw a category at all, and if your mail is simply too mixed to triage safely, run the brief on a dedicated label and file into it nightly.
A digest tells you what arrived. This tells you what to do, which is why it reads the threads behind the notifications, checks who is waiting on you, carries yesterday's promises forward, and hard-caps itself at 400 words. Digest tools are also built for newsletters, where volume is the point — the whole premise here is that volume is the problem and the brief should get shorter as your inbox gets busier.
No — Zaira charges per plan rather than per task, so a heavier morning is not a separate bill. If you want to keep the brief genuinely short as your inbox grows, tighten the context section: fewer people on the priority list, fewer items on fire, and a lower word cap in Step 4 all cost nothing and improve the ranking more than any amount of extra data.