Bespoke AI software vs off-the-shelf: build or buy?

Every operational problem now has a dozen SaaS products claiming to solve it, and every business has processes those products don't quite fit. Here's the decision framework M22 uses, including the cases where M22's answer is "don't hire us, buy the tool".

Question 1: Is your process a commodity or an edge?

Accounting, payroll, scheduling, generic CRM: commodity processes, superbly served off the shelf. Buy. But if a process is part of how you win (how you quote, how you source deals, how you deliver), then forcing it into someone else's software means working their way. Bespoke exists for the processes that make you different.

Question 2: How many tools does the work cross?

Off-the-shelf products are strong inside their own walls and weak across them. If your painful process spans four systems (enquiry in the inbox, job in the CRM, costs in the accounts, delivery in a spreadsheet), no single product fixes it, and you end up either re-keying (the thing you were trying to kill) or buying integration middleware that becomes its own project. Cross-system work is where bespoke usually wins.

Question 3: What does the cost curve look like at scale?

SaaS pricing is per-seat, per-month, forever, and rises as you grow. Bespoke is expensive up front, then costs maintenance. The crossover is often two to four years. Below it, buy; beyond it, if the process is stable and central, building starts to look like the cheap option. Factor in ownership too: bespoke means you own the asset rather than rent access to it, provided the contract assigns the copyright to you in writing; under UK law the developer owns it by default.

What are the common mistakes when building or buying AI software?

• Building a commodity. A bespoke CRM for a standard sales process is money on fire.
• Buying fifteen tools to avoid one build. The subscriptions quietly total more than the build would have, and the re-keying between them never dies.
• Building without a number. Bespoke only pays when it's pointed at a priced problem.
• Buying and abandoning. Software nobody adopted is the most common failed automation of all.

The honest sequence: audit first, so you know what the problem costs; check the off-the-shelf options seriously; build only where specificity, integration or scale justify it. That's the order we follow even though M22 sells builds, because a build pointed at the wrong problem fails, publicly, and we'd rather not.

How does M22 help with this?

This decision is exactly what the AI Audit answers before anything gets built. M22 Consultancy prices the off-the-shelf option against a bespoke workflow automation, platform or Company Brain, and is honest when the right answer is to buy the tool instead. Where a build is the better option, M22 builds it for a fixed fee agreed before work starts, and the client owns the code, data and documentation at the end, not M22. The AI Audit starts at £1,500, a fixed fee agreed before day one, with no obligation to build afterwards. Book a thirty-minute call to price your own build-or-buy decision.