"Should we build it or buy it?" is one of the most expensive questions a growing business gets wrong — in both directions. Buy the wrong platform and you spend years bending your business around software that almost fits. Build the wrong thing and you sink a budget into a tool a €40-a-month subscription would have handled.

There's no universal answer, but there is a reliable way to decide. Here's the framework we actually use with the businesses that come to us — including the times it leads them away from a custom build.

Start from the right default: buy it

If an off-the-shelf tool genuinely fits how you work, buy it. Full stop. It's cheaper up front, live immediately, and someone else maintains it, fixes the bugs, and ships the improvements. For accounting, email, CRM, project management, e-commerce basics — the market is mature and the products are good.

Custom software only earns its keep when "genuinely fits" stops being true. So the real question isn't "custom or standard?" It's: how much are you bending to fit the tool?

The test that actually matters: who bends?

Watch what happens when you try to make a standard package work. There are only two possibilities:

  • The tool supports how you work. You configure it, learn it, and get on with your day. This is a good fit — keep buying.
  • You change how you work to fit the tool. You add manual steps, keep a spreadsheet "on the side," or tell staff "just ignore that field." That's the tool bending your business — and it compounds quietly, forever.

A little bending is normal and fine. When the bending becomes the job — when your process now serves the software instead of the other way around — that's the signal custom is worth a serious look.

When custom actually wins

In our experience it comes down to a handful of honest signals. If several of these are true, a build is probably justified:

  • Your process is genuinely unusual. Not "we like it our way" — actually unusual. If off-the-shelf tools consistently miss the core of how you operate, that gap is exactly what custom fills.
  • The tool you need doesn't exist. You've looked, properly, and there's no product for it — or the closest thing is three tools duct-taped together.
  • The integrations aren't there. The systems that should talk to each other don't, and you're the human API moving data between them by hand.
  • The software is the advantage. If how you handle orders, or route jobs, or serve customers is a real differentiator, owning that software outright is worth more than renting a version everyone else also has.
  • Per-seat pricing is punishing your growth. When licence fees scale faster than the value you get from them, owning the software can change the maths as you grow.

When custom is a mistake

Just as honestly — here's when we'll tell you to walk away from a build:

  • You haven't validated the process yet. Building software to lock in a workflow you're still figuring out just makes the wrong workflow permanent. Prove it manually first.
  • You want it "perfect." Perfect is a budget with no bottom. Custom rewards clear priorities, not endless polish.
  • You're really avoiding change management. Sometimes a standard tool fits fine and the resistance is about people, not software. New software won't fix that — it'll just cost more.
  • The honest budget or timeline isn't there. Custom is an investment. If a subscription solves 90% of the problem today, that's often the right call — buy it now, build later if you outgrow it.
The goal was never "custom software." The goal is the outcome. Custom is just one way to get there — sometimes the best one, often not.

The costs nobody mentions — on both sides

Off-the-shelf looks cheaper, and up front it is. The costs show up later: per-seat fees that compound as you grow, lock-in that makes leaving painful, and paying for a sprawl of features you'll never use while the one thing you actually need stays "on the roadmap."

Custom costs more up front and asks more of you: you need enough clarity to say what "done" looks like, and you own the thing once it's built. Done well, though, there are no per-seat fees, no lock-in, and it fits exactly — because it was made to.

Neither is free. They're just different bills, arriving at different times.

A 30-second gut check

Before you spend a cent either way, answer three questions honestly:

  • If a standard tool fit ~90% of how you work, could you happily change to fit the last 10%? If yes — buy it.
  • Is the part that doesn't fit central to your business, or just a preference? If it's central — custom is on the table.
  • Are you clear enough on the problem to describe what "it works" looks like? If not — do that thinking first, whichever route you pick.

How we'd approach it

We build custom software — websites, web apps, MVPs, portals, dashboards, integrations — at a fixed price on a fixed deadline. But the first conversation is diagnostic, not a pitch. If a standard tool is the smarter call, we'll say so and point you at it. We can only take two clients at a time, so we'd genuinely rather spend that slot on the right fit than talk someone into a build they don't need.

That's the honest version of "build vs. buy": start by trying to buy, build only where buying makes you bend, and be ruthless about which is really true.