AN AI OPERATING PARTNER™

The Mercurious Fleet

A managed AI operating partner for professional-services firms that want the work handled — not another system to manage.

The follow-ups, the drafting, the chasing, the reporting: handled, quietly, every day. Your people spend their hours on the work clients actually pay for.

WHAT IT IS

A small team of agents for the work that never reaches an invoice.

Every firm carries work nobody bills for. Follow-ups. Drafting. Reporting. Chasing. Summarising. It has to happen or the firm stops functioning, and no client has ever been charged a minute of it.

The Fleet is a handful of AI agents deployed inside your firm to carry that load. Configured around the way your firm actually works, watched every day, improved every month. Not a licence you're left to figure out on your own.

Your people make the calls they've always made. I look after the fleet, and whether it's still earning its keep.

That second sentence is what "operating partner" means in practice. I deploy the fleet, I mind it, I report on what it did, and when an agent stops earning its keep I say so and retire it. The judgement stays where it has always been: with the people whose names are on the door.

CLIENT ZERO

The fleet that runs this practice.

My own practice runs on one. Five agents, working together, today. Not a demo and not a pilot.

  • The Argus — the chief of staff, and the one I actually talk to. He works out what needs doing, hands the jobs to the others, and tells me each morning what needs me and what doesn't.
  • The Archivist — keeper of what the firm knows. Finds the file, the thread, or the clause, and shows where it came from, so the things that matter stop living only in somebody's head.
  • The Structuralist — writes down how the work is actually done, step by step, so a process can survive the person who invented it.
  • The Alienist — reads the notes and the correspondence and separates what was said from what was only implied: what repeated, what changed, what nobody mentioned at all.
  • The Profiler — learns how the firm sounds from its own sent work, so anything drafted sounds like your firm and not like a chatbot.

That's the basic fleet, and it's the smallest thing I'll deploy. An AI assistant can genuinely help the person using it — plenty of people get real value from one. But an assistant works for one person, and the work I keep talking about belongs to the firm. Handling it takes a team: different jobs, working together, running whether or not anyone remembered to ask. These five have done months of real work on my own business before they go anywhere near yours. Nothing reaches your firm that hasn't already survived mine.

They have names. I'm aware that's a bit much for software. It stuck anyway, mostly because people find it easier to say "the Archivist has that" than to recite a workflow name nobody remembers.

See the Fleet Log

THE WORK

What your first fleet could take on.

The morning brief.

What happened yesterday, what's due today, and the two or three things that actually need a decision from a person. Read it with the first coffee, and ignore the rest with a clear conscience.

The meeting briefing.

Whoever walks into the client meeting carries the last three call notes, the promises still open, and the questions that keep coming back. Assembled before anyone had to ask.

Drafts in the firm's voice.

Follow-ups, letters, and replies drafted the way your firm actually writes, sitting in a queue waiting for a person to approve them. Nothing sends itself.

The report that's ready before it's due.

Weekly and monthly reports assembled from the notes people already made, structured and sourced, with the writing-up taken off somebody's Friday afternoon.

The firm's memory, kept.

What the firm knows, filed with its source and findable by everyone, so the answer stops depending on which person happens to be in that day.

The exact list is different in every firm, and it comes out of your Census, not out of a brochure.

HOW IT RUNS

You graduate into a fleet.

Nobody starts here. You start with an Orientation Session, where the honest answer might well be that AI isn't worth your time yet. If it is worth your time, the Census spends a day inside your firm counting the work that never reaches an invoice, weighing it, and mapping it to the roster. The fee for the Census comes off the deployment in full if you go ahead within ninety days.

Some firms finish that day and hear "not yet". That's a real result, and it's cheaper than the alternative. The firms that do go ahead arrive at the Fleet already knowing what it's for.

Ten client firms. That's the whole list.

I keep ten places and no more. Ten is what one person can look after properly, and I'd rather say no than say yes badly.

Your accounts. Your keys. My job to mind them.

Every account and API key belongs to your firm, set up in your name and managed by me. The work happens in accounts you own, and I don't keep a separate copy of your business data. In a professional-services firm that matters more than anywhere else, and it's the first question a sensible client asks.

One new agent a quarter.

At the Quarterly Count I show you what the agents actually did, and you pick the next one from the ideas you parked along the way. The limit isn't how fast I can build. It's how much change a firm can absorb before the whole thing gets ignored.

Leaving is meant to be dignified.

If you stop, you keep everything: the agents, the accounts, the configuration, the lot. You keep the machine; you'd be cancelling the mechanic. Nothing gets switched off to make a point.

Nothing arrives untested.

Mercurious is client zero. Every agent runs on my own work first and only joins the client roster once it has earned it. I'm building this in public through the summer and into the autumn, failures included, so you can watch the whole thing before you decide anything.

WHAT IT COSTS

You'll notice there's no price on this page. The shape of it: an implementation at the start, then a monthly fee with the monitoring, the training, and the support already inside it. The monthly climbs with the number of people the fleet is minding, since more people means more requests, more approvals, and more attention. It isn't a licence per head. The Census settles the actual numbers honestly, before anybody commits to anything.

The implementation.

Real work, and charged for. The operating model and the core agents already exist and run my own practice, so there's no development project to fund and no year of waiting to find out whether it was worth it. The implementation is the configuration: the roster set up around your firm, your material, and the way you actually do things, with the specialist work your Census surfaced added on top.

The monthly.

A month of minding, in practice: the fleet watched daily; anything that breaks investigated and fixed; drafts and exceptions queued for a person's approval rather than sent; prompts, processes, and connections updated as your firm changes; your people supported while they get used to it; and a one-page summary in your inbox at the end of the month. Each quarter we sit down for the Count, look at what the agents actually did, and decide what joins next.

Ten client firms. A place opens when one leaves.

Ten is what one person can look after properly, and I won't stretch it. If the list is full when you ask, the wait is useful: the Orientation and the Census happen while you queue, so the day a place opens you're already counted, already mapped, and deployment starts within a fortnight.

Book Your AI Orientation — €450
Talk to Me About a Fleet