A droid that opens the day for a founder: it reads the calendar, inbox and Slack before you’re up, hands you a short briefing with the three things that matter, protects your focus time, handles the scheduling back-and-forth, and surfaces the few threads that actually need you — with a draft already written.
Does
Briefs the day, guards time, triages comms
Where
~40-person startup, founder/CEO
Reaches people on
Slack, email
Works inside
Google Calendar, Gmail, Slack
Runs
Every morning + through the day
01The situation
The day starts shouting before you've decided what matters.
The founder started every day buried. The calendar, the inbox and a dozen Slack channels all shouted at once, with no sense of what actually mattered — so the first hour went to triage instead of the things only they could do. Double-bookings slipped through, and the scheduling back-and-forth quietly ate the gaps between meetings.
The fix would have been a chief of staff — someone to read the day, guard the calendar, and surface only what needed a decision. At forty people, that wasn’t a hire they could justify yet. So the important threads kept getting answered last, and focus time kept losing to whoever booked it first.
02How it works
How the droid took it on.
Rather than wade through the calendar, inbox and Slack every morning, the founder handed the opening of the day over. The droid reads it all before they’re up, distills it to three priorities, guards the focus time, handles the scheduling, and surfaces only what truly needs a person.
TASK#256Daily briefing & day-of supportstanding
trigger
Every weekday at 7:00am
also
Scheduling requests through the day + a 6:00pm wrap
scope
Calendar, inbox, and Slack
runs as
A contained droid action per run or request
memory
Your priorities, people, and how you like things handled
Set up once, in plain language: “every morning, tell me the three things that matter, protect my focus time, handle the scheduling, and only bring me what actually needs me.” The droid turned that into a standing job, the chief of staff a 40-person startup couldn't justify hiring yet.
FIG. 1The durable task, exactly as it exists in the runtime.
Every morning trips the same loop:
01Morning run fires7:00am, every weekday
02Droid wakesBefore you're up
03Reads calendar + inbox + SlackPlus what it knows about you
04Synthesizes prioritiesThe day in three things
05Guards time + schedulesFocus held, conflicts resolved
06Needs you?Routine → handle it · Important → surface with a draft · VIP → flag now
07Sends the briefingOne short message
…then the next run picks it up, two hours later.
FIG. 2The loop each run walks.
03Ongoing handling
How it ran, through one day.
Here’s a working day as it actually unfolded, from the 7am briefing onward, down to how it reached for each app. Only one thing all day was left for the founder to send.
7:00amdaily briefing
Read the calendar, inbox and Slack from overnight; sent three priorities and held a 90-minute focus block.
8:15amreschedule
On request, moved the 2pm to 4:30 with the attendees and held a board-prep block in the gap.
11:20amconflict
Caught a double-book tomorrow, kept the customer call and moved the 1:1, all before it bit.
1:30pmSlack catch-up
On request, pulled the two threads that needed a decision and drafted a reply for each.
3:40pmVIP · investor introescalated
A board member's investor intro, surfaced with a drafted reply and left it unsent for the founder.
6:00pmday wrap
Closed the day: what's done, what's open, and a pre-read of tomorrow with the deck flagged due tonight.
The morning run, scheduling requests, and the odd VIP land on the left. Watch the droid pick up each one and work it end to end across the calendar, inbox and Slack, bringing in the founder only for the message that warrants it.
The result
What changed, by the numbers.
Mornings backthe day pre-triaged before you're up
~1 in 20messages that needed you, with the rest handled for you
Conflicts caught firstoverlaps resolved before the day starts
Focus helddeep-work time protected, not booked over
An illustrative workflow built from real product mechanics. The connected apps, the schedules and the run handling are how a droid actually works; the companies, the people and the figures are composites rather than a customer's numbers.
Try this workflow
Run this workflow yourself.
Copy the brief below and paste it into Unify. It’ll walk you through the prerequisites, connect what it needs, and stand the workflow up with you.
Workflow brief
I'm the founder of a ~40-person startup, and I start every day buried. My calendar, inbox and a dozen Slack channels all shout at once with no sense of what matters, so my first hour goes to triage instead of the things only I can do. Double-bookings slip through, and the scheduling back-and-forth eats the gaps between meetings. What I really need is a chief of staff, but at this size I can't justify the hire yet.
Be my chief of staff. Apps/channels: Google Calendar (my schedule and conflicts), Gmail (my inbox and replies), Slack (channels and DMs to me).
Run every weekday at 7:00am, respond to scheduling requests through the day, and post a wrap at 6:00pm. Each morning:
1. Read my calendar, inbox and Slack from overnight.
2. Give me a short briefing: the three things that actually matter today.
3. Protect a focus block before the day fills up.
4. Handle the routine inbox and scheduling yourself: confirmations, reschedules, conflicts.
Through the day, resolve calendar conflicts proactively, handle scheduling requests when I ask, and catch me up on Slack on demand. Use judgment on what reaches me: handle the routine, surface the important with a draft reply ready, and flag anything VIP, like an investor intro, immediately, but never send it on my behalf. Remember my priorities, the people I deal with, and how I like things handled, so each day starts smarter than the last.
