Reporting assistant
Prepare recurring figures, source summaries and draft packs for review.
The desk
Come back. The drafts are there.
A crew on your mail and files. Friday already moving. It feels like extra people. It isn’t. You still hit send.
01The week moves
Drafts, packs, first passes — waiting when you get back from the room.
02Named jobs
Each seat has a job: inbox, pack, files. Not a vague superpower.
03You send
Nothing goes out until a person says so. That is the whole point.
How it works
A crew. Not thirty unsupervised bots.
We stand up a small set of seats around the week you already have: inbox, pack, files, who to call next. Each one has a job, a boundary, and you at the send button.
It is not a bigger team. It looks like one. You still hit send.
- Choose the first roles.Identify the reporting, admin, knowledge or follow-up work worth supporting first.
- Set the boundary.Define sources, permissions, outputs, approval points and what must stay human-led.
- Build the staffroom.Configure the first assistants around approved tools, prompts, workflows and handover notes.
- Manage adoption.Review usage, improve outputs, retire weak patterns and expand only where value is proven.
What you get
The Friday picture, stood up on your tenancy.
Seats with job cards, your files, your tone, the send button still yours — plus the notes so the next person can run it on Tuesday.
Common starting roles
Inbox assistant
Classify, prepare and route incoming messages without making final decisions.
Knowledge assistant
Find approved policy, procedure and project material faster.
Staff assistant
Help with first drafts, meeting notes, summaries and routine preparation.
Start here
If you want the desk, say what’s taking the week.
We’ll point you at the first seats. You still hit send.