Three questions before you buy another system.

Start with the work, not the software.

Before speaking to vendors, choose one piece of work that is causing delay, taking too much senior time or depending too heavily on one person.

Then ask the people doing that work three questions. Their answers will tell you far more than a feature list.

1. What job are we actually trying to improve?

Be specific.

Fixing sales is not a job. Preparing a quote, checking an order, answering a customer question or approving a price change is.

Describe where the job starts, what needs to happen and what a finished result looks like. Name who does it today and who needs the result.

If your team cannot explain the job in plain language, it is too early to choose software. You risk buying a broad solution for a problem nobody has properly defined.

2. Where does the work wait, and why?

Look at a few recent examples of the job being done. Ask where it slowed down, stopped or came back to the same person.

The reason matters.

The work might be waiting for information, access, approval or judgement. Staff might not know which source is current. A rule may exist only in someone's head. Two systems may hold different parts of the answer.

A new platform will not automatically fix any of those problems. It may simply move the waiting into a different screen.

Find the real point of dependency before deciding what to change.

3. What must improve for a new system to earn its place?

Choose a result that a person can recognise.

Perhaps customers should receive an accurate answer without waiting for the owner. Staff may need to find current information without interrupting the COO. An order might need to move from request to approval without being copied between systems.

Also decide what should remain human. Exceptions, commercial judgement and sensitive decisions often need a named person, even when the routine work around them is improved.

This gives you a practical test for every option: will it improve this job while keeping the right decisions with people?

Sometimes a new system is the right answer.

Your current tools may not support the job reliably. They may be difficult to connect, unable to provide the right access or no longer suitable for the way the business operates.

In that case, buying something new can be the right decision.

The difference is that you are buying it for a clearly understood job. You can assess how it fits the work, what it must connect to and what result it needs to produce. The conversation is no longer about who has the longest feature list.