When is off-the-shelf business software the wrong choice?

When the workflow you actually run cannot be modelled in it. The usual signals are a spreadsheet running alongside the platform to hold what it will not store, a fee or pricing structure it cannot calculate, a report you rebuild by hand every month, and per-seat costs rising faster than headcount. One of those is tolerable. Three at once usually means you are paying a subscription to work around a subscription.

Is custom software more expensive than a SaaS subscription?

Higher up front, and that is the real trade-off. A subscription is cheap to start and never stops; a custom build costs more on day one and then costs hosting. The crossover depends on seat count and how much manual work the platform forces. It arrives sooner for businesses with many staff on per-seat pricing, and may never arrive for a small team the software already fits.

Do I have to replace my whole system at once?

No, and it is usually a bad idea. The lower-risk pattern is to build the one piece the platform handles worst — the scheduling layer, the quoting logic, the client portal — and integrate it with what you already run. That keeps the migration small and reversible, and you find out whether custom is worth it before committing to a full replacement.

What happens to my data if I stop working with you?

It stays yours, in a database you control, and the code sits in a repository you own. That is the structural difference from a SaaS platform, where leaving means an export file and hoping the next vendor can read it.

Are these industry articles based on real builds?

They are written from the operational patterns that recur across service businesses — how the work is scheduled, quoted, invoiced and reported — and from the published capabilities and limits of the named platforms. They are analysis of an industry problem, not case studies of specific clients, and they should be read that way.

Business software by industry

Where off-the-shelf software stops fitting your business.

Every industry eventually outgrows the platform it started on — the workflow the software cannot model, the fee structure it will not calculate, the report it will not produce. These are industry-by-industry breakdowns of what off-the-shelf platforms do well, where they break, and what a custom build changes. If you want the build itself, that is custom web application development.

Contact

SaaS vs Custom

Service Business

Industry Guide

Field Sales

Industry Operations

Trade Business

Practice Management

More industries

Custom vs off-the-shelf — common questions

: When the workflow you actually run cannot be modelled in it. The usual signals are a spreadsheet running alongside the platform to hold what it will not store, a fee or pricing structure it cannot calculate, a report you rebuild by hand every month, and per-seat costs rising faster than headcount. One of those is tolerable. Three at once usually means you are paying a subscription to work around a subscription.
: Higher up front, and that is the real trade-off. A subscription is cheap to start and never stops; a custom build costs more on day one and then costs hosting. The crossover depends on seat count and how much manual work the platform forces. It arrives sooner for businesses with many staff on per-seat pricing, and may never arrive for a small team the software already fits.
: No, and it is usually a bad idea. The lower-risk pattern is to build the one piece the platform handles worst — the scheduling layer, the quoting logic, the client portal — and integrate it with what you already run. That keeps the migration small and reversible, and you find out whether custom is worth it before committing to a full replacement.
: It stays yours, in a database you control, and the code sits in a repository you own. That is the structural difference from a SaaS platform, where leaving means an export file and hoping the next vendor can read it.
: They are written from the operational patterns that recur across service businesses — how the work is scheduled, quoted, invoiced and reported — and from the published capabilities and limits of the named platforms. They are analysis of an industry problem, not case studies of specific clients, and they should be read that way.