Inbox & client updates

An inbox that is sorted before you open it.

See what needs you, route the rest to the right person and keep clients informed. I connect your inbox and project records so your team spends less time sorting, chasing and writing the same updates.

Illustration of a business owner reviewing an email draft beside colour-coded message trays.

At a glance

The task
Sorting incoming messages, chasing replies, keeping clients informed
Who it helps
Founders and small teams handling client conversations
What changes
Clear owners, overdue replies flagged, update drafts ready
Who sends
You or your team review and send every client reply

The problem

When every message waits for you

Some founders spend hours every day in their inbox and their messages, and never reach the end. Urgent and routine arrive looking the same. The team does not write to clients, so every reply comes back to the founder.

Meanwhile the silences go unnoticed. A client who has not answered for a week is holding up a project, and nothing says so. Clients who do not know where their project stands write to ask, which adds to the pile.

So the replies move to the evening, and the evening becomes part of the working day.

You should decide what needs you. Not discover it by reading everything.

The change

Less sorting. Clearer ownership.

Today

  • Every message waits for you to read it first
  • Urgent and routine look the same
  • A client stops replying and nobody notices for a week
  • Clients write to ask where their project stands
  • You catch up on replies at night

With an agreed process

  • Messages are grouped by what needs you, what the team can handle and what can wait
  • Recognised messages are linked to the right client, project and owner
  • Overdue replies are flagged against the deadlines you set
  • Update drafts use the recorded status of the work
  • You or the responsible person check and send each reply

An example

One question. A clear path to a reply.

For an architecture studio, a consultancy or an agency, the same question can interrupt several people. Here is how a connected process could handle it.

A client writes“Where are we with the next stage of my project?”

  1. Find the context

    The message is matched to the client and project. The current stage and responsible person come from your records. An uncertain match goes to review.

  2. Prepare the update

    A draft brings together the latest recorded milestone, what happens next and anything needed from the client. Missing information is flagged for your team.

  3. A person sends it

    The owner checks the facts, adjusts the wording and sends the reply. If you need an answer back, an agreed deadline creates a follow-up task.

Want clients to check progress themselves? Your own app or client portal can give them a view of their project, alongside the email process.

A straight answer

AI reads the language. Your team keeps the judgement.

AI can suggest what a message is about, how urgent it looks and who should handle it, then prepare a first draft. It can also misunderstand a request, which is why the review process matters.

Ordinary automation handles the agreed rules: which client belongs to which project, who owns the next step and how many days count as late. Those rules depend on current records and working connections.

The reply to a client stays with a person. I design the routing, drafts and checks around the way your team works.

An unclear message

Send it to a review queue with the original message available. Your team can correct the category or owner before acting on it.

A missing project update

Flag the missing detail. A draft should use recorded information, rather than invent a date or promise to fill the gap.

A failed connection

Agree who gets the alert, how unfinished work is tracked and when to retry. The original inbox remains available for your team to handle the message.

Read more: AI and automation are not the same thing

How we get there

Three paid phases.
You decide after each one.

The fix starts with agreeing who owns what, before any tool is switched on. We define the access, routing rules and review steps together.

Time Leak Audit

I map how the work happens today, estimate the hours that could be recovered and rank the opportunities against your goals. Under two hours of your time.

From £950 · fixed fee

Process Design

A working session with your team, then detailed mapping: the steps, the data, the business rules and the exceptions that decide how the build behaves. We agree which providers process which information.

Separately scoped · fixed fee

Implementation and handover

I build it around the tools you use, test normal and exception cases, document it and show your team how to run it. Any new tools or ongoing charges are agreed before the build.

Fixed project price · quoted after Process Design

Before any of it, a free fifteen-minute conversation. Bring the process as it actually happens, not as it should.

Before we talk

Questions about your inbox.

Something else on your mind?
Email me directly.

Will AI reply to my clients?

No. AI can help sort messages and prepare a first draft. You, or the person responsible, read it and send it. Nothing reaches a client without a human decision.

Does the system read all my email?

We agree which inboxes, messages and fields it needs, then use the access your tools allow. Connected automation and AI providers may process that content. Before the build, I explain which providers receive what, what they retain and how access can be withdrawn.

What happens if AI sorts a message incorrectly?

Messages that are unclear go to a review queue. Your team can correct a category or owner. We test the routing against real examples, and agree how missing data, failed connections and overdue tasks are flagged. AI sorting is a suggestion, not a guarantee.

Can the system prepare updates without a client asking?

Yes. An agreed project milestone or update schedule can trigger a draft for the responsible person to check and send. It uses the project information you maintain. Missing or conflicting information should be flagged for review rather than filled in by AI.

What about WhatsApp?

What is possible depends on your WhatsApp account and how your team uses it. I check the available connections before proposing a build. If the conversation cannot be connected reliably, we agree how the relevant information will reach your project records.

We use Gmail. Or Outlook. Does it matter?

Gmail and Microsoft 365 Outlook have APIs for working with messages and drafts. The connection we can use depends on your account, permissions and administrator settings. I check those first, then map who handles each kind of message.

After the conversation

Turn meeting notes into a useful next step.

A transcript or approved notes can help prepare a concise summary and follow-up draft. The team checks the decisions and dates.

  1. Start with the notesUse the meeting transcript or approved record.
  2. Prepare the summaryBring decisions and proposed actions together.
  3. Check the detailsConfirm owners, deadlines and commitments.
  4. Follow upSend the checked message and maintain the next action.

Keep reading

Your business

How many hours did your inbox
take this week?

Fifteen minutes, no charge. We will look at which messages actually need you.

15 minutes · No charge
Prefer to write? [email protected]