Most businesses should buy standard software where they can.
Accounts software, email, calendars, customer records and booking tools exist because many businesses need broadly the same things from them. A proven product can handle those standard jobs without one company having to build and support its own version.
If a product already does that work well, replacing it with custom software adds responsibility without solving anything specific to the business.
A working rented product can still be worth replacing when the economics of ownership change. We’ve considered that separately in whether your business should rent software or own the system it actually needs.
This article asks a smaller question. Where the existing software is worth keeping, what should happen to the one job that still sits outside it?
A good product can still leave one job outside it
A CRM can manage customer records and sales while the company has its own way of handing work over after an order is won.
Accounts software can handle invoices and payments while the business follows its own preparation and approval steps before an invoice is ready.
Booking software can manage appointments while gathering information or allocating the work follows rules specific to that company.
In each case, the standard software is doing its job. The separate work belongs to the business and needs to be considered on its own.
Separate the job that many businesses handle in much the same way from the job this business handles differently. That gives you a much clearer decision than asking whether the entire product is right or wrong.
If staff are already bridging that gap with spreadsheets, duplicate entry and manual checks, we’ve looked separately at the hidden cost of software that almost fits.
Does that job need software of its own?
Custom software is only one possible answer.
Start with the simplest sensible place for the job. The existing product may be able to handle it with some careful configuration. Another standard product may already fit. A spreadsheet can remain a good answer when it’s clear, safe and easy to manage. A manual step that takes a few minutes and causes no problems can be left alone.
Software of its own becomes worth considering when the job is both contained and important.
A contained job has a recognisable beginning and end. You can identify the information it needs, the people involved and what should happen when the work is complete.
An important job happens repeatedly or has consequences beyond the few minutes it takes. It may affect customers, money or several members of staff. Mistakes may create delays, or the business may depend too heavily on one person knowing what to do.
An approval can be only one step and still hold up every order. A pricing calculation can occupy a single spreadsheet and affect every quote. A short handover can decide whether work starts correctly.
The size of the job isn’t the deciding point. The question is whether it’s clear enough to separate and important enough to justify changing.
If it passes both tests, you can consider giving that job a system of its own while leaving the main product in place.
Make the software decision smaller
You don’t need to begin by asking whether to replace the CRM, accounts package or booking system. Ask your team to show you the specific job they’re still managing somewhere else.
If you can point to that job, bring it to a Day-1 Build call.
We’ll look at how it works, who depends on it and what happens when it goes wrong. Then we can decide whether a focused system makes sense or whether you’re better off leaving it where it is.