AI Employee
Back office
The executive assistant layer as an AI Employee
The assistant’s job is context rather than typing. This is how an agent holds the schedule, the prep and the follow-through for one executive while every commitment made in their name stays with them.
The assistant's job is being done, badly, by the executive
Today
The calendar schedules itself around whoever asked last
- Your calendar schedules itself around whoever asked last, and the meeting that mattered ends up in the slot that was left.
- You walk into that meeting with the context scattered across a thread, the last notes, a deck someone sent, and your memory.
- The follow-up lives in your head until it does not.
- The assistant's job is being done, badly, by the executive, in the gaps between the work the executive was hired for.
With agents
Calendar, prep and follow-through held in one place, in your name only on your say
- Your calendar follows your rules rather than the order requests arrived in.
- You walk in with the context assembled.
- Follow-through stops depending on memory.
How an agent runs it
The assistant's job is context rather than typing. Holding the calendar, the prep and the follow-through in one place is what makes the role useful, and one governed role can hold it while you keep every commitment made in your name.
01
Monitors
Watches the calendar and inbound requests against the rules you set for your time, so scheduling starts from your priorities rather than from the last email. Scheduling as a workflow has its own page; here it is one duty of the role.
02
Drafts
Prepares holds, scheduling replies and reschedules for your review, with the conflict it resolved shown.
03
Assembles
Builds the pre-meeting brief from the records your team already has: who is in the room, what was last agreed, and what is still open.
04
Human gate
Routes every confirmation to an outside party, every reply sent in your name, and every commitment or document that leaves the company to you for a decision, because those actions speak for you.
05
Records
Captures agreed actions and owners after a meeting from the notes you authorize it to read, into the task system you already use.
06
Assembles
Builds the status view on your cadence from those records, so the follow-through is visible without a status meeting.
07
Flags
Names the commitments that are overdue and the requests that have waited past the window you set, with the owner shown.
Results
What changes when context is assembled before you walk in
Your calendar follows your rules
The rules are written down and applied to every request, so the slot that matters is protected before it is asked for.
The brief is built, not remembered
The brief is built from records the team already keeps, on a trigger tied to the meeting rather than to someone remembering.
A commitment is a record
Actions are recorded with owners and the status view is built from them, so a commitment is a record rather than a recollection.
Where this fits
AI Employee
Tier 2 through the AI Employee door: a full role of known-process work handed to one governed agent. The proof step is a single workflow, and one back-office workflow, document intake, is already written and names an administrative role as its next step; this role is one shape that step can take. Its boundary is schedule, prep and follow-through for one executive, under one gate on anything in their name. It does not make decisions, set priorities, or decide who gets your time, and it does not handle document filing or company-wide request triage. From here the pattern can extend toward an agent-run back office, as a direction rather than a promise. How It Works describes how the gates are built.
Tier 2 / Scale
How It Works
Questions, answered
It drafts. Anything sent in your name or confirmed with an outside party is gated by default and opens only on your decision. Your calendar and your records stay in your systems, and you can take any thread back at any point and run it by hand.
AI Opportunity Audit
See which rule would have caught it
Bring next week's calendar and the last meeting you walked into unprepared, and see which rule would have caught it.
Related use cases
Back to Use Cases
Workflow
Back office
Document intake, extraction, and filing
Filing looks like the cheap part of the work until you need something back. Deciding what a document is, and what it changes, is the
Learn More
Workflow
Back office
Meeting scheduling and calendar coordination
Every scheduling thread re-derives the same rules about your time by hand. This is how an agent holds those rules in one place, proposes against
Learn More
Workflow
What makes a workflow ready for an agent (the readiness checklist)
Most processes fail an agent handoff for the same few reasons. Here is the checklist to run before you pick a first workflow.
Learn More