Comparison
Build, buy, or hire: choosing an AI system in 2026
Most of the time, you should buy a subscription. If the job is standard — scheduling, note-taking, drafting email, a CRM — someone has already built it better than a custom system would be, and for a fraction of what building costs. Hire an agency when you need extra hands for a defined push and you already know what you want done. Have a system built that you own when the work is specific to how your business runs, when the information it works on is your own, and when you expect to still be doing it in three years.
That last case is the only one we take on, and it is the smallest of the three. The rest of this page is the reasoning, including the parts that argue against us.
The three ways, and what you are actually buying
1. Buy a subscription
You rent finished software. It works on the day you sign up, someone else maintains it, and if it is wrong for you, you leave.
- Right when the job is common enough that a product exists for it, and doing it slightly differently from everyone else gains you nothing.
- The real cost is not the monthly fee. It is that you adapt your business to the software, and the working history it builds up — what was decided, why, by whom — lives in the vendor’s system, not yours.
- Where it breaks down: you end up with several, none of which know about each other, and you are the integration.
2. Hire an agency
You rent people. They bring expertise you do not have and capacity you cannot spare.
- Right when the work has an end — a launch, a migration, a campaign — or when you need someone who has done it before to tell you what you actually want.
- The real cost is that capability arrives and leaves with the people. When the engagement ends, what you keep is whatever was written down.
- Where it breaks down: ongoing work. Paying people indefinitely to do a job that could have been built once is how retainers quietly outgrow what a build would have cost.
3. Have a system built that you own
Software made for how your business actually works, running under your name, that you keep.
- Right when the process is specific to you, the information is yours and sensitive, and the job recurs often enough that encoding it pays back.
- The real cost is time before anything runs, more commitment up front than a subscription, and a process stable enough to be worth encoding.
- Where it breaks down: if what you need is standard, you have paid for something you could have rented. If your business changes shape entirely, the system has to change with it.
Side by side
| Subscription | Agency | Built & owned | |
|---|---|---|---|
| Time to first result | Same day | Weeks | Weeks |
| Fits how you work | You adapt to it | Depends who you get | Built to it |
| Who holds what it produces | The vendor | Shared, in practice | You |
| When you stop paying | Access ends | Work stops | It keeps running |
| Does it compound | Resets with each new tool | Leaves with the people | Yes — each build starts ahead |
| Effort from you | Low | Low to medium | Real, at the start |
| Best when | The job is standard | The work has an end | The process is yours and lasting |
When not to build
Do not have something built if any of these are true. You have not tried the off-the-shelf option yet. The process you want encoded is still changing every month. Nobody internally has time to answer questions during the build. Or you want it mainly because it sounds like the modern thing to do.
The first two are the common ones. A build encodes how you work, so it pays back when how you work is settled and repeated — and is wasted when it is not. If you are in that position, buy something, give it six months, and see what it still cannot do.
What “you own it” means here
The word gets used loosely, so it is worth being exact. Owning the system means all four of these, not some of them:
- The application — the thing built for you, running under your name, on infrastructure you control.
- Your data — exportable, yours on the first day and the last.
- Everything it produces — the pipeline, the records, the decision history. This is the part that is most often quietly kept by someone else.
- The engine underneath is licensed — that is the foundation a build stands on, and it is why this takes weeks instead of quarters. It stays ours; everything built on top is yours.
What this looks like in practice
We built and shipped a candidate-sourcing system for a national home-care franchisor, replacing work they had been buying from an outside firm. It has found and researched 147 real people, each with a written brief and a score that cites its own evidence. It runs unattended overnight. They own the system, the candidates, and every decision recorded in it.
Questions people actually ask
Isn't it cheaper to just buy a subscription?
Almost always, and for most jobs you should. A subscription only becomes the expensive option when you are paying several of them to work around the fact that none of them knows your business, or when the thing you need is specific enough that no product is built for it. Until you hit one of those, buying wins.
What does “you own it” actually mean?
Four things: the system itself, running under your name on infrastructure you control; your data, exportable, on the first day and the last; everything the system produces — the pipeline, the records, the decision history; and the right to keep all of it if you stop working with us. You license the engine it is built on. Everything built on top is yours.
So we pay once and you are gone?
No, and you should be sceptical of anyone who says otherwise. You own the system — you pay us to run it and keep making it better. Ownership means it cannot be taken away from you and does not reset when a contract ends. It does not mean support is free.
What happens if you disappear?
You still have the system, the data, and everything it has produced. That is the whole point of building it this way. Compare that to a subscription, where the day you stop paying is the day you lose access to your own working history.
Can't we just use ChatGPT?
For asking questions, yes — genuinely, and it is free to try. This is a different thing: a system that runs on your business's own information, on a schedule, whether anyone opens it or not, and hands a person something to approve.
We already have software for this. Does that make it harder?
Usually it makes it easier. Existing systems are where the information already lives, and a build reads from them rather than replacing them. The part that tends to be missing is not storage — it is something that knows what the information means and who is allowed to see it.
Do we need our data organised before we start?
No. If it were already organised you would need much less of what we do. Working out what the business actually knows, and where it disagrees with itself, is part of the build rather than a prerequisite for it.
How long before something is running?
Weeks, not quarters — that is what the engine underneath is for. The first thing we build is deliberately small and real: one job, done end to end, that someone can look at and judge.
If the third column is the one describing your situation, tell us what the job is — or read what we build and how it works.
Written August 2026. If something here stops being true, we will change it rather than leave it up.