Your own AI, not off-the-shelf
A plain guide to the difference between buying AI and building your own, and how to tell which one your business actually needs.
Everyone's selling AI this year. A chatbot bolted to a website. A new subscription that promises to transform your admin. A tool a competitor mentioned at a show. Most of it is sold the same way, and most owners come away no clearer on what any of it would do for them.
Here's what the noise hides: "AI" isn't one thing you buy. It's three quite different things, and they don't do the same job. Buy the wrong one and you've paid to bend your business around someone else's product. So before you spend a penny, it's worth knowing which one you're actually being sold.
The three things people call "AI"
When someone pitches you AI, they almost always mean one of these three.
The chatbot. You've met these. A box on a website, or one of the general assistants from the headlines. It's good with language: answering a common question, drafting a message, summarising a document. What it isn't is a system. It doesn't know your sites, your jobs, your dates or your rules, and left to itself it will answer confidently even when it's wrong. A useful front door. Not the house.
The subscription. A finished product built for a whole industry and rented to you by the month. If your business runs exactly the way the product assumes, it can be money well spent, and sometimes it's the right answer. The catch is you bend to it, not the other way round. It joins up with your other systems only as far as its makers decided, you're one account among thousands, and the parts that are specific to how you work, usually the parts that are costing you, are the parts it doesn't touch.
Your own build. Software and AI workers built around how your business already runs, reading from the systems you've got, following your rules, doing your dull jobs. Not a product you log into. A thing that fits the way a suit cut for you fits better than one off the rack. What that actually means is the next bit.
| Chatbot | Subscription | Your own build | |
|---|---|---|---|
| Knows your business | No | A little, in its lane | Yes, by design |
| Who bends to whom | — | You bend to it | It bends to you |
| Joins your existing systems | No | Only as far as it allows | Yes, reads what you've got |
| Who else has it | Everyone | Thousands | Only you |
| Best for | A front door, drafting | A standard, solved job | The work specific to you |
What "your own AI" actually means
Forget the word "AI" for a second. Picture a new member of staff who's brilliant at one dull job, never forgets, works through the night, and does what you told them and nothing more. That's closer to the truth than the film version.
A tailored build is a team of those. Each AI worker has one job, a set of rules, and a limit on what it's allowed to do without a person. They take the grind, not the jobs: retyping, chasing, reminding, filing, matching a ticket to an invoice, drafting a reply for a person to check. The work nobody joined your business to do. And they work to your rules, your dates, your duties, your way of doing it, not a generic template.
A person stays in charge. Think of it as three levels of trust:
Runs on its own
The worker does the job and writes down what it did. You read the log.
Runs, a person checks
It does the job and a person checks the log before it counts.
Waits for a person
It waits for a person every time. Nothing reaches a customer, council or regulator without a named sign-off.
That last point is the whole difference between a tailored build and a chatbot let loose. The cleverness is kept on a lead.
What it looks like when it's yours, not theirs
Three builds that already exist. Read them as "what tailored looks like", not as a promise about your numbers. Yours we'd measure against your own data.
Paperwork that assembles itself
HouseComply runs the compliance for 700+ properties. Inspections done on a phone and checked against the rules on site, certificates read automatically, the full audit pack in one click instead of a morning spent pulling it from four places. The build knows the rules of the job it's doing.
Answers only from your own records
An AI guide for one town that answers only from that town's own stories, records and sources, and says where each answer came from. Point the same build at a business and you get an assistant that knows your sites, customers and rules, without making things up from the open internet.
Work that would have taken a team months
For one project, a build mined archives and published sources across ten languages, graded and sourced every fact, and wrote up a thousand years of history in 108 days. The old way was a team of six and the best part of a year. Shape the build around the work, not the work around the build.
Those are real projects with real figures, from our own work and labelled as such. What matters for you isn't our numbers, it's whether a build would pay for itself against yours. That's a thing you can measure, and should.
When off-the-shelf is the right call
I build tailored AI for a living, and I'll still tell you when not to.
- If a standard product does the whole job and your business runs the way it assumes, buy the product. Don't pay to rebuild payroll.
- If the job is rare, low value, or about to change, don't automate it yet.
- If the real problem is a process problem, software won't fix it. Sometimes the answer is a decision, not a build.
- Some things AI shouldn't touch at all. The judgement calls, the awkward customer conversation, anything where being confidently wrong does real harm. Those stay with people, on purpose.
A build earns its place when the work is specific to how you run, it happens again and again, and it's quietly costing you real hours. That's usually exactly the work no off-the-shelf product covers.
What about my data
A fair question, and the honest answer matters more than a reassuring one.
- An agreement is in place before anyone sees your data. A data processing agreement, signed before I look at a thing.
- Nothing leaves your business without a named person signing it off. That's a rule built into the system, not a line in an email.
- Your own AI answers from your own records. It isn't pouring your business into a public tool. It knows what you've given it, and tells you where its answer came from.
Which one do you actually need? A 60-second check
- Is the job standard, or specific to how we run? Standard leans product. Specific leans build.
- Does it happen constantly, or now and then? Constant and dull is where a build pays.
- Do our systems already hold the information, just not joined up? If yes, a build can join them without replacing anything.
- Would being wrong cost us a fine, a customer or a reputation? Then a person stays in the loop whichever route you pick.
If you're not sure, that's normal. It's worth an hour before any money changes hands.
Still deciding?
A call or a couple of hours over a coffee. I'll tell you straight which of the three you actually need, and if the answer is "none yet", I'll say so.