The consultant says to replace your software, is he right

Sometimes he is, and that's coming from the people who make a living from the opposite

Boxes full of binders ready for a move, in the middle of an office

Muffin Suite makes its living automating the business software a company already has, so the convenient answer would be to tell you to keep it always, in every case, whatever the consultant says. But that isn't true, and it does nobody any good to say it

There are situations where replacing your business software is the right thing to do, and others where it's an enormous cure for a small complaint, and the difference lies in where the problem really starts

The cases where replacing your business software is the right call

It's worth replacing when the program can no longer handle the volumes you have now. The screens freeze, printouts take minutes, the database has hit its limit and every extra operation makes itself heard. That isn't a problem of manual work around it, that's the engine giving out

It's worth it too when whoever sold it to you has closed down, or has stopped supporting it, because a program with nobody updating it becomes a risk that grows on its own, and no automation can patch that

Then there's the matter of legal obligations. If the business software no longer produces what the rules ask for and the supplier has no intention of bringing it up to date, there's only one road, and it isn't the one Muffin Suite sells

The last case is the nastiest, the data is a mess at the root. Duplicate customer records, fields used for purposes other than the one they exist for, a history that's been inconsistent for years. If the data model is wrong to begin with, automating means running something crooked faster

The cases where replacing it is a cure out of all proportion

Very often, though, the business software does its job. The data fits inside it, the documents come out, the figures add up, and what doesn't work is all the human labor going on around it

People open the supplier's PDF, read the fields, retype them into the screen, check that the amount matches, download the file from the portal, rename it, upload it somewhere else. By the end of the day they've done work the business software never asked to be done that way

If that's the real annoyance, changing program doesn't take it away, it moves it. The same fingers will retype the same fields into a new screen, prettier perhaps, for the same number of hours, because that work was manual not through the program's fault but because nobody had ever automated it

What replacing your business software really costs

The quote for the new software is the part you can see, underneath sit the items that weigh more

There's the migration, moving in the customer records, the history and the documents, and migration is nearly always the point where the problems nobody knew they had come to the surface

There's the running-in, a stretch where the company works at half speed, with the old one still on for safety and the new one still to be learned, and nobody can tell you in advance how long it lasts, it depends on how complicated what you do is

There's the training, which doesn't end with the course, because somebody who could do a job with her eyes shut spends weeks thinking it over, doing it more slowly and checking with a colleague

The question that separates the two roads

There's only one useful question: is the problem inside the business software, or in the work people do around it

If the program can't cope, isn't maintained any more, doesn't meet the obligations, or the data is rotten at the root, the problem is inside. Then you replace it, and whoever advised you to is telling you something sensible

If instead the program does its job and the weight is the hours of retyping, of checking, of files moved by hand, the problem is around it, and there automating your business software without replacing it costs less and doesn't force you to rethink the whole way you work

There's a mixed case too. The software does need replacing, but not tomorrow, and in the meantime the hours get paid for all the same. There it makes sense to automate the piece that hurts most right now, knowing it has a shelf life, and to say so up front instead of finding out later

To get your bearings, line up two numbers of your own, what those hours weigh today and what the road you're weighing up costs, and for the hours you can get an idea from the savings calculator, while for the other figure you need a real quote

If the comparison says replacing your business software is the right road, replace it, because an automation built on top of a program that has to die is money thrown away

What people usually ask us

It depends on where the problem starts, replacing your business software is worth it when the program can't handle the volumes, when whoever sold it no longer supports it, when it doesn't meet the legal obligations, or when the data is inconsistent at the root
Not necessarily, if the business software has hit its technical limit or is no longer maintained, the consultant is telling you something sensible, what needs clearing up is whether the daily annoyance comes from the program or from the hours of manual work going on around it
No, it almost always stays exactly as it was, because that work was manual not through any fault of the old program but because nobody had ever automated it, and the same people retype the same fields into a new screen
Replacing your business software costs you the migration of customer records, history and documents, the running-in period when the company works at half speed with two programs open, and the training, which isn't just the course but all the time somebody spends redoing more slowly what she already knew how to do
It depends how far off it is, if the switch is a long way away and the hours weigh on you every day it can make sense to automate the heaviest step, knowing it has a shelf life, while if the program is being replaced soon an automation built on top of it is money thrown away
Yes, Muffin Suite drives the business software you already use by opening the screens the way an operator would, so it also works on programs with no direct integration at all, but that doesn't make it sensible to keep alive a program that needs replacing for other reasons

Show us what you still do by hand

Describe the process or send a short screen recording and we'll tell you what can be automated

WA