Custom software or subscriptions: ownership and operating cost

Subscriptions can be a practical way to equip a business without commissioning each tool. There is a SaaS product for bookings, one for ordering, one for messaging, one for accounting, one for the website, one for the loyalty programme. Each is reasonable on its own. Together they form the operating layer the business actually runs on; and that layer is, in practice, rented.

What renting buys you

Speed and predictability. An established product may provide maintained software, support and a faster route to use, depending on its contract and fit. For commodity problems this is usually the right answer. We recommend buying off-the-shelf for most accounting, payroll, email and standard CRM use cases; there is no virtue in rebuilding what the market already does well.

What renting costs you

• Recurring fees across several tools, with price-change terms to review.
• Transaction-based charges where the provider uses that pricing model.
• Restrictions on data access, export or use, depending on the provider's terms.
• Integration friction between tools that were never designed to work together.
• Dependence on the provider's product roadmap and support decisions.

When ownership is worth it

Ownership is worth pursuing where the process is genuinely particular to the business, where the data the business holds is itself a competitive asset, or where the rented layer has begun to shape the operation more than the operation shapes the layer. The signal is usually qualitative before it is financial: the team starts saying 'we cannot do that because the system does not allow it' more often than 'that is not how we want to do it'.

A bespoke build does not mean reinventing everything. It usually means owning the two or three points in the operation that genuinely differentiate the business, and continuing to rent the rest.

A sensible default

Buy the commodity. Integrate the rest. Build only where ownership changes how the business competes. Approach the build the same way you would approach buying: with a clear scope, a fixed quote, and a working increment in front of you early. Bespoke does not mean open-ended, and ownership does not mean rebuilding the world.

The long view

Compare the full operating cost over a useful planning period: delivery, subscriptions, hosting, maintenance, support and eventual migration. A custom build still depends on infrastructure and third-party components. Ownership, licences and data portability need to be agreed explicitly; a mix of purchased and custom tools may fit better than either extreme.

Our buy, build or integrate guide develops the decision. A business systems proposal should define ownership and operating responsibilities explicitly.