An agent that prepares a busy person's day. It reads the calendar and inbox it is given access to, produces a morning briefing, keeps a list of what is owed and to whom, and proposes replies, meeting changes and reminders that happen only when you approve them.

An executive's inbox and calendar are a second job. The important email sits under forty unimportant ones. A meeting is accepted with no time to prepare. A promise made in a corridor is forgotten. A human assistant solves this with judgement built over years. Software usually solves it by acting on your behalf with too much confidence, and the first wrong reply to the wrong person ends the experiment.

This page describes a workflow we propose to build as a custom project. It does not exist as software yet. It would reuse the propose-then-approve pattern that runs across our demonstrations, where nothing is written to a system until a named person accepts it. Reading a mailbox and calendar, briefings and proposed actions are not built.

02Step by step

From the First Signal to the Record

An example of one case, in 6 steps. The same steps play in the picture at the top of this page.

Morning

At seven the briefing arrives with six meetings, three decisions and two overdue promises.

Preparation

Before the board call it links the papers and the two open questions from last time.

Triage

Forty new emails are sorted. Four need a decision today.

Draft

A reply to a supplier is drafted, leaving the price decision blank for you.

Proposal

A clash on Thursday is shown with two ways to resolve it. You pick one.

Evening

The day's new commitments are listed, with what is due tomorrow.

03The problem

What Goes Wrong Without It

The important email, buried

It was read on a phone and forgotten.

Back-to-back days

No gap to prepare, travel or think.

Promises that vanish

"I'll send that over" is said five times a day and done twice.

Meetings nobody needed

An hour that an email would have covered.

Automation that overreaches

A tool accepts an invitation or sends a reply you would not have.

Confidential by default

The inbox holds matters no tool should spread around.

→Request a quote

What We Need to Scope This

The process as it runs today, in a few lines.
The systems it touches, for example mailbox, calendar, documents, tasks.
Rough monthly volume, and who approves what.

Request a quote Book a 30-minute callA quote starts from a written scope, so that the figure means something.

04Executive assistant agent

Six jobs it carries through

01Morning briefing

Prepares the day in one page.

Today's meetings with their purpose
What each needs from you
Emails that need a decision
What is owed to you and by you

02Inbox triage

Sorts mail by what it requires.

Needs a decision, a reply or nothing
Senders and topics you prioritise
Threads that are waiting on you
Nothing deleted or archived without your rule

03Draft replies

Drafts replies for you to send.

In your tone
From what the thread and your documents say
Short, with the decision left to you
Saved as drafts

04Calendar proposals

Suggests changes to the calendar.

Conflicts and their options
Time to prepare before key meetings
Meetings that could be shorter or declined
Proposed, never applied

05Commitment tracking

Keeps the list of promises.

What you said you would do
What others owe you
Reminders before each is due
Closed when the email or task shows it done

06Confidentiality rules

Respects what it must not touch.

Folders and senders you exclude
Topics you mark private
No content shared outside your account
A log of what it read

05Operating boundaries

It Prepares and Proposes, and Never Acts as You

Everything this agent does to the outside world is a proposal: a draft, a suggested change, a reminder. You approve each one, and you can see what it read. It does not send email in your name, accept meetings or share your information with anyone.

An executive's mailbox contains other people's confidential matters. The agent reads only what you include, inside your organisation's account, and keeps a log of what it accessed.

Drafts and proposals only
Nothing sent in your name
No calendar change without approval
Excluded folders never read
A log of what was read
Access limited to your own account

06Scope

The Systems Around It

The systems named here are the kind this agent works with. Which ones it connects to in your case is settled in the scope.

Mailbox

Microsoft 365
Google Workspace

Calendar

Your own and those you may see

Documents

Papers and notes linked to meetings

Tasks

Your to-do or project tool

Contacts

Who matters, as you define it

Policy

What is excluded and what is private

07Questions

Straight Answers

Not as designed. It drafts and proposes, and you approve. For most people the saving is in the preparation, not in the final click. If you later want specific routine actions done without asking, each is switched on separately.

Meeting preparation builds a brief for each customer meeting for anyone on the team. This agent serves one person across their whole day: inbox, calendar and commitments. It can include the meeting brief as one part of the morning briefing.

The inbox agent works a shared mailbox for a team and creates tickets. This one works an individual's mailbox and calendar together and answers to that one person.

Not as software yet. This page describes a proposed workflow. It would reuse the propose-then-approve pattern that runs across our demonstrations, where nothing is written to a system until a named person accepts it. Reading a mailbox and calendar, briefings and proposed actions are not built. A project starts by mapping your process, then proving the first steps on test data before anything touches a live system.

Start a project

Describe an Ordinary Tuesday

Tell us what your day looks like and where it goes wrong. The first version is usually just the morning briefing, and it proves itself or not within a week.

Start an AI agent project Book a free 30-minute consultation

Response within 24 hoursFree consultation and scopingNDA available on request