Right now there is one. Between almost every company and the AI it is paying for, there sits a person — writing the prompts, wiring the connectors, keeping the workflow alive. Bonz-Ai Limited built the technology that removes them.
Before search boxes taught everyone to type keywords, there was a website whose whole premise was that you should just ask a question the way you would ask a person. It was a lovely idea attached to technology that could not deliver it, so the world learned to speak machine instead — keywords, then filters, then syntax, then prompts.
Twenty-five years on the technology finally exists, and the industry has quietly gone back to making people speak machine: prompt engineering, context windows, model selection, tool schemas, API keys. A whole vocabulary invented so a person can explain to a computer what they want.
If you asked Jeeves today, he would ask Zai. The question was always the right interface. What was missing was something on the other side capable of answering it — not with a list of links, but by going and doing the thing.
Buy an AI tool for your business today and you have not finished. You have bought a capability that cannot reach any of your systems, knows nothing about your company, and forgets you between sessions. To make it useful, somebody has to connect it up.
So a second purchase follows the first: an automation consultant, an agency retainer, an in-house engineer, a platform specialist — someone whose job is to sit in the gap between a company and its own AI. Then they stay there, because connectors break, models change, workflows drift, and nobody else in the building can read it.
That is not temporary. Every tool that requires configuration guarantees a market for people who configure it, and the incentive runs directly against ever making it simple.
Not AI for everybody who can afford a retainer. Not AI for everybody who can read documentation. Not AI for everybody willing to learn what a context window is. Everybody — the person running a two-van business off a phone, the practice manager with four hundred emails, the household that would like some help and has forty pounds a month spare rather than four hundred.
Nobody should be paying £500 a month for workflows they could get by asking. If the only people who get the benefit are the ones who could already afford to hire someone, the technology has just moved the gate.
Ask Zai has no setup screen, because there is nothing for you to set up. You do not pick a model — the system routes each part of the job to whichever one suits it, and the cheap mechanical parts never touch an expensive model at all. You do not write prompts, manage keys, or learn a syntax.
You say what you want in the words you would have used with a person, and the system works out the rest: which sources to look in, which tools to call, in what order, what to do when one fails, and when it has enough to answer you. Persistent memory across three tiers means you explain your business once, not at the start of every conversation.
Every integration platform on the market has a list of what it connects to, and your business is the one running the thing that is not on the list — at which point you are back to a developer, a timeline and a quote.
Zai treats a missing connector as a task rather than a limitation. If a service has an interface — an API, a feed, a login, a file drop, a page she can read — she can work out how to talk to it, write the piece that does so, test it against the real thing, and keep it once it works. The next person who needs it gets it immediately.
A tool library that grows by being used is a fundamentally different thing from one that grows when a vendor decides to add something. The first bends around your business; the second asks your business to bend around it.
Behind Zai are four sisters, each with a fixed name, role and voice. One researches, one reviews code, one handles architecture and design, one does fast execution. You never assign work to them and never manage them — you talk to Zai, and she decides who is needed, hands over the right context, gathers the results and returns one answer.
Every job the middleman used to do is done by one of them, continuously, at no marginal cost. When a connector breaks, a sister fixes it. When a model is deprecated, the routing moves and the persona you talk to does not change. When a workflow drifts, it is noticed by something watching all the time rather than by a consultant on a monthly call.
The retainer was only ever paying for attention, and attention is the one thing software can supply infinitely.
None of this matters if running it costs more than hiring somebody. It does not, and the reason is architectural. Most steps in a real job are mechanical — classify this, extract that, reformat this list, decide which folder to look in. Sending those to a frontier model in a rented data centre is the biggest source of waste in the industry.
Break the work into pieces small enough for a model running on your own machine, send only the genuinely hard part out, and the same errand goes from $20.53 to $0.01. It is also the private answer and the fast answer in the same move: work that never leaves your device cannot be intercepted, retained or trained on, and does not wait on a network.
For a business. A private assistant that knows your business — your inbox, documents, customer records and calendar — and does the work in them, running on your infrastructure so your data does not become somebody else's training set.
For a product. The orchestration layer, persona system, memory and voice pipeline embedded in the product you already sell. Your brand on the front, our engine underneath.
For a team. The jobs that currently need a person to babysit them — chasing invoices, triaging support, pulling a weekly report together, keeping two systems in step. Described once in plain language, then run on a schedule.
For a household. Ask Zai itself: Zai and her four sisters, persistent memory, real-time voice and a safety layer built for families, at roughly a pound a month.
Tell us what you are currently paying someone to do. Not a specification, not a budget — just the job that needs a person in the middle of it. Email founder@bonzai.ltd.