By the work · Calendar and inbox
Scheduling and triage are procedures. Nobody wrote them down.
The rules for what reaches you, what gets scheduled and what gets followed up are real, consistent, and documented nowhere. Orchard records them being applied, one triage and one scheduling round trip at a time, until they are legible enough to hand over under supervision.
The shape of the problem
Where the hours actually go
Triage eats the morning
Every message is a small decision, and the decisions pile up faster than anyone can make them.
Scheduling is ten emails per meeting
Finding a slot is a negotiation performed by hand, against rules that never change and never get written down.
Follow-ups survive on memory
The intro you promised, the invoice you are owed, the reply you are waiting on: remembered, occasionally.
What the record holds
Everything above is already happening. None of it is written down.
- Which messages are opened and worked, which are opened and left, and which are never opened at all
- The scheduling patterns repeated every week without anyone having written them down
- How many times one scheduling thread and the calendar screen are re-opened for a single meeting
- What is copied out of a thread, and precisely where it is pasted
- The threads that get returned to, and the ones never opened again
What the record holds after a few weeks of watching one seat run.
The work
Calendar, inbox, and follow-up
Learned from how the seat is actually run, in its own rules rather than generic ones.
- Sorting the inbox into what needs a person and what does not
- Holding the calendar’s rules without being reminded of them
- Preparing meeting briefs from your own materials
- Following up until a thread closes
How it learns the work
Watched, learned, proposed, then armed by you
It starts by watching
Install quietly and keep working. Every five seconds Orchard records which application has focus and what was done inside it: the screen, the control, the value in the field, what was copied and where it landed. Never a screenshot, a printable keystroke, or a password.
Repeated work becomes evidence
One desk generates thousands of observations a day. Across weeks they resolve into the shape of the job: the steps, what varies each time, what never does, which exceptions are real rather than noise, and what the whole thing costs in hours. You do not have to know what to automate first.
It asks before it acts
When the evidence is strong enough, Orchard proposes the piece of the work it is ready to take on, with the receipts underneath it. Nothing runs until someone on your team arms it.
Supervised first. Autonomy earned.
Armed work runs supervised: outward writes wait for approval, every run keeps a step-by-step record, and your team decides when a proven Playbook has earned more room.
Where this work happens today
It records in the systems you already use
- Outlook
- Google Workspace
- Slack
- Teams
- Your expense tool
Orchard records at the interface, on the same screens your team already uses. No API, no integration project, and no system that has to expose its data before Orchard can see the work happening in it.
Control before autonomy
Your hand stays on the controls
- Not employee surveillance: Orchard keeps task structure, decisions, and outcomes — never screenshots, printable keystrokes, or passwords.
- Nothing acts unreviewed. Work begins supervised, and approvals sit in front of anything that leaves your systems.
- Autonomy is chosen, not assumed — and your team can pause everything at any time.
- Your business owns the result: the Playbook, its procedures, and the record of every run.