Insights

Custom web app or off-the-shelf software: how to choose

Building custom is not always the right answer, and neither is bending your business to fit a template. Here is how to tell which one you actually need.

Start with off-the-shelf — genuinely

If an existing product does most of what you need, use it. A good off-the-shelf tool has had years of work, thousands of users finding its bugs, and a support team you are not paying for directly. For a shop, a booking page, a newsletter or a basic CRM, custom software is usually the wrong first move.

Any developer worth hiring will tell you this, even though it means less work for them. If someone reaches for custom before asking whether you need it, be careful.

The signs you have outgrown it

Off-the-shelf starts to cost you when your business no longer fits the shape the software assumes. The usual signals:

  • Someone spends hours a week doing by hand what the software cannot do — exporting, re-keying, copying between tools.
  • You are paying for five separate subscriptions that do not talk to each other, and the gaps between them are where mistakes happen.
  • Your process is genuinely different from your competitors’, and that difference is part of why customers choose you — but the software flattens it.
  • You are paying per user or per record, and success is making the bill grow faster than the value.

When the workarounds cost more — in time, errors and lost opportunities — than building the thing properly would, it is time to look at custom.

What custom actually buys you

Custom software fits your process instead of the other way round. It does exactly what you need and nothing you do not, it connects the tools you already use, and — importantly — you own it. No per-user pricing that punishes growth, no feature you depend on being removed in someone else’s next update, no data locked inside a platform you cannot leave.

That ownership is the real prize. The software becomes an asset your business controls, not a rent you pay forever.

The honest costs on both sides

Neither option is free of downsides, and a fair comparison names both.

  • Off-the-shelf — fast and cheap to start, but you inherit its limits, its pricing and its roadmap, and the monthly fees never stop.
  • Custom — fits perfectly and you own it, but it costs more up front and someone has to maintain it. Software that is built and then abandoned rots.

The right question is not “which is cheaper?” but “which is cheaper over the next three years, once the subscriptions, the wasted hours and the maintenance are all counted?”

The middle path most people miss

It is rarely all or nothing. Often the best answer is to keep the off-the-shelf tools that work and build a thin custom layer that joins them together — a small system that moves data between your shop, your accounts and your email so the manual copying disappears, without rebuilding any of them.

You can also start off-the-shelf and move the parts that hurt to custom later, one at a time, as the business justifies it. You do not have to choose the whole strategy on day one.

Common questions

Is custom software always more expensive?

Up front, usually yes. Over a few years, often no — once you count monthly subscriptions, per-user pricing and the hours staff spend on workarounds. The comparison that matters is total cost over time, not the first invoice.

Can I start with off-the-shelf and move to custom later?

Yes, and it is often the smart route. Prove the business with existing tools, then replace the parts that cost you most — one at a time — with custom software that fits. You keep what works and only build what earns its place.

What about no-code and low-code tools?

They sit between the two: faster and cheaper than full custom, more flexible than fixed software. They are a good fit for simple internal tools, and a poor fit once you need real scale, unusual logic or full control of your data. They are worth considering, with eyes open about where they stop.

Next step

Need this done properly?

Describe the problem in plain language and I’ll tell you what it actually needs — including if that is less work than you expected.

WhatsApp