AI for business
Don’t hire an AI employee. Redesign the work.
The ads want you to imagine a headcount line that costs $27. The useful version is less romantic and more valuable: pull every role in your business apart into tasks, hand the drafting, monitoring and reconciling to a crew of agents, and keep the judgement where it belongs. Here’s what that actually looks like from the owner’s chair.
Think in tasks, not job titles
No role in a small business is one thing. “Marketing” is research, drafting, scheduling, posting, and reading the numbers. “Admin” is chasing, formatting, filing and flagging. When you break a role into its tasks, a clean line appears: the tasks with a defined input and a checkable output are crew work. The tasks that need judgement, a relationship, or someone to be accountable are yours, or your people’s.
That line is the whole design. I didn’t give my crew a department, I gave each agent a brief: what it does, what it can touch, how it reports back. The role that’s left over for the human is smaller in hours and bigger in consequence.
What the owner’s week becomes
Mine looks like this: drafts arrive instead of blank pages. The nightly numbers are reconciled before I’m awake, and anything that doesn’t tie out is flagged, not buried. The scheduled jobs run on schedule. And everything that matters passes a review layer before it ships, because I’d rather catch it there than in front of a customer.
What I still do: decide, direct, and read what the crew produces. That’s not the fine print, it’s the job. You become an editor and an operator instead of a typist, and the hours you get back start in single digits per week, not the forty the ads promise.
The twelve seats
One crew, every function a small business actually has
Twelve specialists, not one chatbot pretending to be twelve: strategy, creative, governance, build, support, monitoring, finance, autonomy, fulfilment, sales, compliance and audit. Each is a file with one job, and you reskin them to your business. If yours is one of the business types we’ve mapped, setup tunes the crew to it before you start.
Scout
Research & Intelligence
Watches the market so Archer plans from facts, not vibes.
Archer
Strategist & Architect
Turns a vague goal into a plan the crew can build. The one I argue with most.
Forge
Builder
Takes the blueprint and ships it. Writes, wires, deploys.
Red
Creative
Voice, campaigns, the words that sell. Has opinions. Usually right.
Ember
Autonomy / Overnight Runner
Runs the scheduled jobs while I sleep. Knows its limits, because I drew them.
Bench
The Council
Not a single specialist, but a panel. Reviews every piece of work and can veto it.
Ruby
Interface Layer
How I talk to the whole crew, including over WhatsApp. The front door.
Finn
CFO
Consolidated finance across four brands. The one you already met.
Porter
Fulfilment
Owns every order between paid and delivered, so the customer never has to chase.
Hunter
Sales & Partnerships
Researches outbound leads and drafts the outreach. Sends nothing until I've read it.
Vera
Compliance
Checks the public promises: terms, privacy, refunds, prices. Not a lawyer, and says so.
Judy
Audit
Rules on whether the crew's claims are true, with evidence. Read-only, and reports to me.
The operating model: drafts by default, judgement by you
Drafts, not surprises
The crew’s default output is a draft waiting for your eyes. Work only goes out unattended when you’ve scoped that exact job and decided it’s safe to ship.
Reviewed before it matters
A governance layer reads the work against the brief before it ships, and can veto it. The typo in the customer’s name gets caught in the machine, not in their inbox.
Escalated, not guessed
When something needs a decision, it comes to a human with the context attached. The crew executes and drafts. You decide. That boundary is a feature, not a limitation.
The full mechanism, all three layers of it, is on the how it works page, in the open. If a vendor won’t show you theirs, that tells you something.
If you have staff: elevate the person, out loud
The worst way to bring a crew into a business with employees is quietly. Your people will work out what’s happening long before you announce it, and what they’ll assume is worse than the truth. The honest version: the crew takes the grind out of a role, and the role gets redesigned around what’s left, which is the judgement, the relationships, and the reviewing. Say that plainly. Show the working. Let them see which tasks move and what their hours become instead.
Done in the open, this is a genuine elevation: fewer hours spent being a typist, more spent being the person who directs and checks. Done in the dark, it’s a morale fire you lit yourself. I wrote the employee’s side of this, honestly, at AI for employees. Send it to your team before they find it themselves.
The honest limits
What no crew will do for your business
- ✕Run the business itself. Nothing on the market makes judgement calls you never scoped, and anyone claiming otherwise is selling a costume.
- ✕Fix a business that doesn’t work. A crew accelerates a machine. If there’s no machine, it accelerates nothing, expensively.
- ✕Remove you from the loop. You’ll direct it and read its output every week. That’s the product working, not the product failing.
- ✕Spare you the technical bar. This generation of real tools runs in Claude Code, a developer tool. The fit check on the how-it-works page will tell you straight if that’s not you.
The mechanism first. Your money after.
Read how the three layers work, run the fit check, and only then look at pricing. In that order, on purpose.