Your business repeats itself. That part does not need you.
The same enquiries answered again. The same details typed into three systems. The same answer hunted down in a file. We build AI that does that work — joined up to the tools you already use, and proven in our own business before it goes anywhere near yours.
One is running on this page. Open the chat and try to talk it into a discount — it cannot give you one, and it will tell you why.
The same week, twice
Nothing here is a new way of working. It is your week with the waiting taken out of it.
Your week now
With one of these running
10.47 pm
A customer messages. Nobody sees it until morning — by then they have asked somebody else.
Answered in seconds, details taken down, and waiting for you in the morning as a real enquiry.
Tuesday, 11 am
The same customer details typed into the third system by hand, because that is how it has always gone.
Entered once. It puts them everywhere else, and says so when it cannot.
Thursday afternoon
Gone. Bills, statements, chasing, filing — the work that never changes and never ends.
Handled in the background. What is left on your desk is the handful that needed a decision.
Any time somebody asks
The answer is in a file, and one person in the office knows which one.
Anyone asks, gets the answer, and gets the document it came from.
A few of them. Yours is probably the same shape.
Once you can see the shape, you start finding it everywhere in your own week.
Every one of them has the same three parts
What starts it
An email, a form, a payment, a document, a date on the calendar
What the AI does
It reads it, checks it against your records and your rules, and does the steps
What you get
The work is done — and anything odd is put in front of a person
Money and paperwork
The work that has a deadline and no judgement in it
A supplier invoice arrives
Read, checked against what you ordered, filed — only the mismatches reach you
A payment lands in the bank
Matched to the invoice, marked paid, reminder stopped
An invoice goes past due
Chased politely, on a schedule you set, until it is paid or you step in
Customers and enquiries
The work that is costing you money while it waits
A new customer signs up
Created once, in every system you use — nothing typed twice
An enquiry goes quiet
Followed up in your words, remembering the whole thread
Someone asks what it would cost
A draft quote off your price list, ready for you to check and send
Trading operations
The work around the trades — never the trading decision itself
A strategy stops sending orders
You hear about the silence when it starts, not when you next check the screen
The broker rejects an order
The reason read, put in plain words, and sent to you with what needs changing
Your records and the broker statement disagree
Reconciled line by line, with only the mismatches brought to you
The market closes
The day's fills pulled from the broker, journalled, and summarised before you sit down
Knowledge and tools
The work that is slow because the answer is buried
Your team needs an answer from your own files
The answer, plus the document it came from, so they can check it
The Monday report
Pulled together from wherever the numbers live, in your inbox before you open the laptop
A contract or tender to go through
The odd clauses flagged, so you read those instead of forty pages
A job no software fits
Your own tool, on your own data, built with AI coding agents doing the typing
Running a strategy rather than a back office? The execution side — signals to broker, with the risk controls — is a product of its own: Automation Bridge.
And the one you are thinking of
If it happens the same way every time, it has the same three parts — tell us what starts it and what you want at the end.
Proof
You are on a page that has one running
We do not publish results from customers we have not measured. We would rather you tried the real thing.
Test it yourself, before you speak to anyone
The chat button on this website is our own front desk. It answers from our documentation, admits when something is outside what it knows, takes down the details we would need to follow up, and can take a customer all the way through a purchase.
Ask it something awkward. Try to talk it into a cheaper price — it cannot give you one, because the price is looked up by our system and only a verified payment can complete an order. That is the whole approach: the AI handles the conversation, our code holds the line. It is the difference between a demo and something you can leave running.
Running in our business today
Built by AI coding agents
This website and the trading product behind it, written with Claude and Codex.
Agents running in the background
Answering, following up, and watching for the things that need a person.
n8n between our systems
The plumbing that moves our own information around without anyone re-typing it.
Crews of AI workers
Several of them with a defined handover, for jobs one answer cannot finish.
Search over our own documents
So nothing here — including the chat on this page — is answered from memory.
Watched, with numbers
We see what it got wrong before a customer has to tell us.
Answering your customers
The fastest payback and the easiest to judge: every enquiry gets a reply, and you can see what happened to each one.
A customer messages you
- Your website
Your AI front desk reads it
It knows your prices, your services and your answers, because you gave them to it
It answers
The customer gets a proper reply in seconds. Their details are saved for you. If they go quiet, it follows up.
Or it fetches you
Anything unusual, sensitive, or about money goes to a real person — with the whole conversation, so you are not starting cold.
Replies in seconds, day or night. The 11pm WhatsApp, the Sunday form, the email that lands mid-meeting.
Only uses your answers. Your prices, your services, what you do and do not take on.
Asks your usual questions first. What they need, roughly what budget, by when — so it reaches you as a real enquiry.
Chases the ones that go quiet. On your schedule, remembering what was already discussed.
Knows when to fetch a person. Money, commitments, or an unhappy customer — handed over with the whole thread.
Shows you what it did. Answered, waiting, passed to you, gone quiet. Counted, not guessed at.
It cannot make things up
Whatever the job is, the first question every owner asks is what stops it saying something wrong. This is the answer, and it holds for every one of them.
- Your price list
- Your FAQs
- Your policies
- Your service list
Whatever we build you
Reads only what you gave it
If the answer is in there
It replies, and records which of your documents the answer came from — so you can check it.
If it is not
It says it does not know and passes the question to you. It does not guess, and it cannot invent a price.
A person always has the last word
We do not build something that can promise a customer anything, quote outside your rules, or take a payment decision on its own. It does the preparation; your team decides.
Your data stays yours
Your enquiries and your customers' details belong to you. What gets stored, where it sits, and how long it is kept is written down before anything is switched on. Your business information is never used to train anybody's AI.
WhatsApp has rules, and we work inside them
Replying within 24 hours of a customer's message is free and open. Messaging them first after that uses wording WhatsApp has to approve, and WhatsApp charges for it. That shapes what automatic follow-up can do, so we explain it up front rather than halfway through.
It will sometimes get things wrong
Anything built on AI will occasionally misread a question. That is exactly why the handover rules and the reporting exist. The aim is something that fails in a way you can see and correct — not something that claims it never fails.
Your first one, live in 14 days
One job — a kind of enquiry, a process, one piece of the paperwork — running on your real work with your real answers, and a screen at the end showing you whether it worked.
Days 1–3
We load what it needs to know
Your price list, your common questions, your policies, the files the job depends on — whatever you already have, even if it is a WhatsApp note and a PDF. That becomes what it knows.
Days 4–9
We set up one job, end to end
One kind of enquiry, or one process, done properly from start to finish. Deliberately narrow: doing everything at once is how these projects fail slowly.
Days 10–12
We agree when it fetches you
Which situations go to a person, who gets them, and what the customer is told while they wait. Agreed before it goes live, not after the first upset customer.
Days 13–14
You get the numbers
A simple screen showing what came in, what it handled, and what needed you — so at the end you can judge it on facts rather than a feeling.
Day 15 onwards
A demo is easy. Keeping it right is the job.
Anyone can show you something clever for ten minutes. Still correct in six months, joined up to your systems, sensible when it is unsure — that is the different piece of work, and it is the one we already do.
Joined up to your tools. Your customer list, your calendar, your inbox. One that answers but writes nothing down is a toy.
Watched, and corrected. What it gets wrong, what it keeps passing to you, what it cannot answer yet — we fix those as your business changes.
Kept honest about stopping. The hard part was never the answering. It is stepping back when it is unsure, when money is involved, or when someone is unhappy.
Not sure where it would help?
Then start with the audit, not a project. We follow where enquiries, paperwork and information actually go in your business, and tell you plainly what is worth automating first.
- One conversation about your week, not a sales deck.
- You leave knowing which job to start with, and roughly what it costs.
- Including the ones we would tell you not to automate at all.