Custom or off-the-shelf management software: how to choose

Choosing between custom and off-the-shelf management software comes down to how similar your processes are to everyone else’s. If you work the way most businesses in your sector do, an existing product is almost always the right choice. If the way you work is precisely what sets you apart, or you spend your days working around the software’s limits, custom development is worth considering. And there is often a third route: connecting the tools you already use.

The short answer: it depends on your processes

Spreadsheets, a subscription product (SaaS), an ERP and custom software are not rungs on a ladder you have to climb in order. They are different options, each suited to different situations. This table is a first orientation:

Note the last two rows: having many integrations to manage does not automatically mean you need custom software.

When to choose off-the-shelf software

A standard product is the sensible choice when:

• Your processes are typical for your sector: invoicing, customer records, orders, payment schedules with no special rules.
• You need to start immediately, without an analysis and development phase.
• Your initial budget is limited and you prefer a recurring cost.
• You don’t want to handle maintenance: updates, security and backups are the vendor’s job.
• The product already covers almost everything you need, and the rest is marginal.

In these cases, building custom means paying to reinvent something that already exists. If that is the picture that emerges from the initial analysis, I will tell you.

When standard software becomes a constraint

The warning signs are usually practical, not theoretical:

• Parallel spreadsheets to track what the software doesn’t handle.
• Data re-keyed by hand from one program to another, with errors and lost time.
• Features used “creatively”: notes fields turned into statuses, categories used for purposes they were never meant for.
• Extra modules and extra seats that push up the subscription without solving the underlying problem.
• Feature requests that sit in the vendor’s queue, because your need matters only to you.
• Data that is hard to export, making it difficult even to evaluate an alternative.

One or two of these are manageable. When they become the normal way of working, the standard software is costing you more than it seems.

When custom development makes sense

Custom development makes sense when the software needs to follow the way you work, not the other way round:

• You have your own processes that are part of your advantage: pricing rules, approval flows, case handling that no product reflects.
• You need to bring together several channels or parties (offices, agencies, partners, customers) with different views and permissions.
• You want one system instead of several tools and spreadsheets that only talk to each other because someone copies data across.
• You want control over your data and over how the software evolves.

A concrete example is the management system for a travel agency I built: bookings, suppliers, supplier payment deadlines and automatically generated documents in a single system. These are activities an agency runs by its own rules.

Custom does not mean everything at once. You can start with one module, the one that solves the heaviest problem, and add the rest in phases.

Comparing costs fairly

The most common mistake is comparing an off-the-shelf product’s monthly fee with the development quote for custom software. They are different quantities.

A fair comparison, over the same number of years, puts on one side fee × users × years, plus add-on modules, setup, data migration, training and the manual work the software leaves out. On the other side: development, infrastructure, maintenance, migration and training.

Custom software does not always cost more: it depends on how many users you have, how long you will use the system and how much manual work it removes. But it does not always cost less either. I go through what drives the cost of custom development, and what keeps costing afterwards, in how much custom management software costs.

Customising a SaaS product is not the same as owning custom software

Many subscription products let you add fields, configure workflows, install plugins or pay the vendor for bespoke work. That is useful, but it is not the same as custom software:

• You work within the product’s limits: you can configure what the vendor has anticipated, and no further.
• Vendor updates can change how your customisations behave.
• Customisations stay tied to that product: if you switch one day, they don’t come with you.
• The subscription continues, and often rises with add-on modules.

Customising a standard product is often the right choice. Just be clear about what you are buying: an adapted product, not software of your own.

A third option: integrate your existing tools

Before replacing everything, ask whether the real problem is that your tools don’t talk to each other. If your invoicing software works, your CRM works and your website works, you may need a connection between them rather than a new system.

Software integrations can synchronise customer records, orders and bookings across systems, removing the manual step. Or a small custom tool can cover only the missing piece, building on the software you already have. I explain how APIs and integrations work, and what makes them reliable, in how to connect management software, CRM, website and other tools.

Seven questions before deciding

1. Processes: which of your activities genuinely differ from others in your sector, and which are common?
2. Coverage: how much of what you need does an existing product already cover? Is what’s left out marginal or central?
3. Integrations: which systems must the software talk to, and do they have documented APIs?
4. Users: how many people will use it, with which roles, and will that number grow?
5. Budget and total cost: what will you spend in total over the same span of years, not just in the first month?
6. Timing: do you need it running now, or can you allow for analysis, a prototype and modular development?
7. Maintenance: who will handle updates, backups and enhancements, and with what budget?

If the answers point mostly to “common processes, high coverage, few users, right now”, choose a standard product. If they point to “own processes, low coverage, many exceptions”, custom software deserves a serious look.

Frequently asked questions

What does “customised management software” mean?

The term is used for two different things: a standard product configured or extended for your business, or software built specifically for it. The difference matters for cost, limits and control, as explained above.

When does an ERP make sense?

When you need to bring together many business areas, such as accounting, stock, production and HR, and your processes are close to what the ERP expects. If part of your work is very specific, a custom module connected through an integration can sit alongside the ERP.

Can I start with just a few features?

Yes. My method starts with a free analysis and a prototype of the main screens, then development in phases, even starting from a single module.

Check what already exists first

Before developing anything, let’s check whether the software you need already exists. If it does, I will tell you. If it doesn’t, or if it needs something of your own alongside it, we can talk it through starting from your processes: see how I build custom management software or tell me about your case.