Most of the job is assembling what other people already know. Drift reads across your mail, calendar, tasks and connected tools, and asks before it posts anywhere.
The update you assemble by hand every week. The information already exists. It is in a thread, a stand-up note, a moved ticket and a calendar that shifted twice — and the work of managing is walking all four surfaces and writing down what they add up to, usually on a Friday afternoon, usually twice because the first version was out of date by the time you finished it. Drift reads Gmail, Google Calendar, Google Tasks and Notion directly, and reaches further through its connections catalog — Slack, Asana, Todoist, Linear, GitHub, Jira and more. You choose what to connect, and disconnecting any of them in Settings ends the access and deletes what was cached for it.
One-on-ones you did not stay late to prepare for. The useful question before a one-on-one is not what is on the agenda. It is what was said last time, what you committed to then, and whether it happened — and that is exactly the thing nobody has written down in a place you can find in the four minutes before the call starts. Drift searches twelve months of your own mail and calendar history and answers from what was actually written. Asked what you agreed to in a review three months ago, it goes and finds the thread rather than reconstructing something plausible, which is the failure mode that makes recall untrustworthy.
Your day, minus the meetings you already have. A manager’s calendar is mostly other people’s time, so a plan that ignores it is fiction. Drift subtracts what is already booked before it proposes anything and comes back with about three priorities and one concrete next step, sized to the hours that are genuinely left. It is a short list on purpose. On a day with six meetings, an eleven-item list is not a plan — it is a record of everything you will not get to, delivered in the morning.
It asks before it posts anywhere. Sending a Slack message and posting a comment are on the always-ask list alongside sending mail, and for the same reason: a channel is other people, and a post cannot be recalled by deciding you would rather not have made it. So Drift will draft the update, assemble the summary and write the reply, and every one of those stops on a card showing exactly what would be posted, and where, before it happens. Reading across the same tools never asks, because reading changes nothing.
"What did I commit to in my last one-on-one with Ines?" — Drift searches your own mail and calendar history for it and tells you what was actually agreed, and when.
"Draft the weekly update from what moved this week." — Drift reads across what you have connected and writes it, then shows you the full text before it is posted or sent anywhere.
"What actually needs me today, around the meetings?" — Drift subtracts what is already booked and returns about three priorities with one place to start.