What exactly do you build?
A set of small, connected parts on the accounts your firm already has: its email, calendar, files and spreadsheets. One part answers enquiries, one runs the diary, one drafts the letters and quotes, one raises and chases invoices, one builds the reports. Beside them sits an agent: anything your people can do on the screens, it can do when they ask in one sentence, and it shows exactly what it is about to change before it changes anything. Each part follows written rules about what it may do alone and what waits for a person. Nothing is migrated and nobody learns a new tool.
Do we have to change the tools we use?
No. What I build is a layer on top of the systems your firm already uses. If you work in Google Workspace, I build with Google's tools; if you run on Microsoft 365 and Azure, I build with those. AI joins them up, carries information from one to the next and does the repeated steps. Along the way I tell you plainly what is worth changing and how to make better use of what you already have.
Is this for my firm?
If you are two to twenty people and one or two of you are the admin for everybody, yes. Practices, agencies, trades, consultancies, clinics, accountants and lawyers all have the same pile: enquiries, bookings, forms, letters, invoices, reports. The trade changes the words, not the work.
What happens on the day?
I spend the day with the person who does the admin, online with the screen shared, or at your office if you are nearby. I look at how your firm works and the tools it already uses, and choose what fits. Nothing is built or switched on that day. Within the week you get a written report with the next steps in order, the price of each, and a step-by-step recipe for the first automation. The report is yours whether or not we go on.
How long does the build take, and what does it cost?
Each automation has a fixed price, written in the report next to what it saves you: most firms spend £3,000 to £7,500 on the whole build. I build one at a time, each runs on live work as soon as it is built, and you can stop after any of them. Support after that is by the hour, only when you need it.
What does it cost to run afterwards?
Very little on top of what you pay now. The system lives in your firm's own accounts, so there is no server to rent and no subscription to me. AI is paid by use and billed straight to your firm; I choose the model for each job, set a limit and watch the use with you.
Who in my team has to be involved?
The person who does the admin today, for the day of work and about twenty minutes a day during the build, to say what is right and what to change. Nobody from IT, because there is no IT to set up: the system runs on the accounts you already have.
Where does our data live, and who can see it?
In your firm's own accounts, where it is today. I work under a written UK GDPR agreement; the system sees only the folders and inboxes you switch on. The text it drafts passes through the AI provider you choose, under commercial terms that do not allow it to be used for training.
What if the system gets something wrong?
Anything that reaches a client waits for a person's yes until your team trusts it, so the worst a mistake costs you is a no. When something does not work, it says so plainly rather than guessing.
Where do the numbers come from?
Fifty-eight per cent of the working day on work about work: Asana, Anatomy of Work, 2023, 9,615 people. About 112 emails a week per person: OnePoll for Slack, 2023, 8,000 people. The hours and the minutes in the story come from our own firm's practice. In the sample report the total is that practice's own, and the split across the kinds of work is my estimate.