Skip to content

AI Strategy & Business Transformation

Should you keep, integrate or replace your business software?

An application can do everything it was bought to do and still cost the business hours every week. Staff may have to export data for reports, re-enter orders or work around a process that has changed. The first question is where that effort comes from. A different application can leave the same problems in place if nobody has looked at how the work moves through the business.

Keep it when the problem can be fixed in the workflow

Look for steps your team can change with the tools it has. If everyone keeps their own copy of a customer list, agree which system holds the current details and who updates them. If an approval ends up in someone’s inbox, give the team one place to see what’s waiting and who can act. Test the change with the people who do the work.

You also need to know whether the current application can remain in use on acceptable terms. Check its support status, whether you can get to the data you need and what happens when someone is away.

Integrate it when the work piles up between applications

Your CRM may handle customers well and your billing tool may handle invoices well. If staff spend their time moving details between the two, test whether the systems can exchange the fields you need. Run a typical case, then deliberately try a duplicate, an incomplete record and a correction. Agree which system can edit each field and who deals with failed transfers.

Include the cost of the connection, subscriptions and ongoing exception handling when you compare options. An integration is worth keeping if the team can see when it has failed and knows how to recover.

Replace it when a core requirement is hard to meet

Replacement deserves a serious look if a system cannot support an essential workflow, has lost the support you depend on or blocks access to important data. Start with a list of cases the new system must handle, then ask to see those cases run with representative data. A polished demo can leave your hardest case untouched.

Allow for data cleaning, migration, training, time spent running two systems in parallel and the work required to switch back if the change goes badly. Check what you can export and how your team would move again later.

Make the decision on evidence

Choose one workflow that matters and compare the three options using the same cases. Write down which requirements each option meets, the time the team would spend on it and what still needs to be tested. Ask each supplier to state what is included in the quote and which work would fall to you. The decision is much easier when the options answer the same question.

If you still need to identify the workflow, start with what to automate first.

See how I approach software integration Discuss a workflow