Skip to content
Blogs Best-practices

Which system suits my business? Write these three things down first

Which system suits my business? Write these three things down first

Which system suits my business? Business owners usually only ask that question once they have already seen three demos and laid two price lists side by side. Six months later there is a package that looks good, but nobody enjoys working with it.

It often goes like this. Something is pinching in the business. Quotes are left lying, projects overrun or someone retypes the same data every week from one list to another. So you go looking for software. You schedule a few demos, compare subscriptions and pick the package that looks most convincing. That feels like a decision, and that is where the problem lies. You chose between systems while you did not yet know exactly what needed solving.

After six months you notice it. The system can do all sorts of things, just not the one thing you bought it for. Or it can, but your people work around it with their own Excel list. The supplier says anything is possible with a bit of extra configuration. That is probably true as well. The technology can do almost anything. But you still don't know what you actually wanted to achieve, and so you don't know what to have configured either.

The question was framed wrongly from the start. It is not about which system you need. It is about what the system needs to solve for you. The system follows the goal, not the other way round. That sounds logical, but in practice almost every business skips that step because a demo is more fun than a sheet of paper. Yet a good choice starts precisely there, with three things you write down before you call a single supplier.

First the gap, then the package

The first thing you write down: how does the work run now? Draw the process as it really runs, not as it is described in the handbook. From enquiry to invoice, with all the detours included: the phone call someone has to make first, the email that gets forwarded, the list that only lives on one laptop. Ask yourself three questions as you go. What costs us the most time? What causes the most frustration? Where do we want more overview? Then you know where the pain is.

The second: when has it succeeded? "It needs to be better" doesn't count. Make it concrete. Every signed quote is scheduled within a day. We see at a glance which projects are falling behind. Nobody has to retype anything any more. The more concretely you write this down, the easier it will be to choose later and the better you can measure in a few months whether it works.

The difference between those two points, between how it runs now and what it looks like once it has succeeded, is exactly what the system needs to solve. No more and no less. Everything a package can do on top of that is nice for the demo but not what you are paying for. Anyone who has that gap on paper sees straight away which features matter and which only distract.

The people decide whether it works

The third point is the one forgotten most often: who will work with it every day? And who actually wants this change? Does the request come only from you as owner, from a manager or from the people on the shop floor? That makes a big difference. The technology can do almost anything, it usually goes wrong on the human side. If the people who have to work in it every day don't understand why it is needed, they won't work with it either. Then you have an expensive system and the old Excel list.

A useful test: next to each goal from point two, write the name of the person who suffers most from the problem. If only your name appears every time, you have a problem to solve before you buy software. Your colleagues need to recognise the pain themselves, otherwise the new system becomes your project and not theirs.

How to look at a demo differently

With these three things on paper, you approach a demo differently. You don't let the salesperson show you his best screen. You ask: show me how a signed quote gets into the schedule within a day. Show me where I can see which projects are falling behind. If that can't be done without someone retyping something, you know enough. You then judge systems on your work, your goal and your people, not on how slick the interface looks.

Where business owners most often drop out

We keep coming across three pitfalls. One: drawing the process as it should run instead of how it really runs, so you choose a system for a business that doesn't exist. Two: goals that stay too vague, such as "more overview", so afterwards you can't say whether it has worked. Three: involving the shop floor only once the contract has already been signed. Each of those three can be avoided with an afternoon of writing before you schedule the first demo.

Know first what you need and only then choose. The system follows the goal. Our advice: set aside an afternoon this week to write down the three points, together with at least one colleague who will be working with it every day. Take that paper to every demo. If you get stuck or want someone to look over your shoulder while you map your process, Lead Innovation helps you get that gap sharply defined before you sign anything.

Want to know more about monday.com?

The Lead Innovation team at work