You May Not Need New Software: Start With What You Already Have

When something stops working, new software can seem like the answer

A team is struggling to keep track of customer enquiries.

Follow-ups are missed. Information is spread across spreadsheets and emails. Managers cannot easily see what is waiting or who is responsible for the next step.

Someone suggests getting a new CRM.

It sounds reasonable. A better system might make the work easier to manage.

But before choosing one, there is a more important question to answer:

Why is the current process not working?

Perhaps the existing CRM is poorly configured. Perhaps the team has never agreed how enquiries should be handled. Perhaps nobody is responsible for keeping records up to date.

A new system will not automatically solve these problems.

In some cases, it may simply give the business another place to store information.

Find out what is actually going wrong

Before looking at new software, choose one process that is causing difficulty.

It could be handling new enquiries, preparing quotes, managing service requests or producing a weekly report.

Follow a recent example from beginning to end.

Ask a few basic questions:

• What starts the process?
• Who handles each step?
• Where is the information recorded?
• Where does the work wait?
• What do people do when the normal process does not work?
• What makes the task harder than it needs to be?

You are trying to identify the cause of the problem, not simply list the symptoms.

For example, a manager may say that the team needs a better way to track follow-ups. But after looking at the process, you may find that the CRM already supports tasks and reminders.

The real issue may be that enquiries do not have a clearly assigned owner, so nobody knows who should create the next task.

That is a different problem, and it requires a different solution.

Check whether your existing tools can do the job

Many businesses already use systems with features they have not fully adopted or configured.

Before buying something new, check whether the current tools can support the process you need.

Can the system capture the right information?

If the team cannot record an important status or next action, check whether the existing system can be configured to include it.

Can people see what needs attention?

A team may not need a new dashboard. It may need a useful view of open tasks, overdue actions or requests waiting for a response.

Can ownership be made clearer?

If work is being missed between people, assigning responsibility and making the next action visible may be more important than adding another feature.

Is the information reliable?

If records are incomplete or duplicated, cleaning up the data and agreeing how it should be maintained may solve part of the problem.

Are people using the system consistently?

A tool can only support the process if people understand what needs to be recorded and when. Training may help, but it should follow a clear process rather than asking people to follow unclear rules.

The aim is not to make your current software work at any cost. It is to find out what it can reasonably do before assuming it needs to be replaced.

Understand why people use workarounds

If your team maintains separate spreadsheets, personal trackers or WhatsApp conversations alongside its main system, do not immediately insist that everyone stop using them.

First, ask why they exist.

A spreadsheet might be the only place where someone can see all outstanding requests. A personal tracker might help an employee remember tasks that are not visible in the CRM. A WhatsApp group might be used because the formal handover process is too slow.

These workarounds may create their own problems, but they often reveal something useful.

They show where the existing process or system is failing to meet a practical need.

Removing the workaround without addressing that need may simply lead people to create another one.

Instead, understand what the team is trying to achieve, then decide whether the same need can be met more reliably using the tools already available.

Know when new software really is necessary

Starting with existing tools does not mean keeping them forever.

Sometimes the current system genuinely cannot support the business's requirements.

You may need new software when:

• An essential capability is missing and cannot reasonably be added.
• The business has outgrown the system's capacity or limitations.
• Important information cannot be shared reliably between the tools you need.
• Manual work remains excessive even after the process has been clarified.
• The cost and risk of maintaining the current setup outweigh the benefits of changing it.

The important point is to make that decision based on a defined need.

Write down what the current setup cannot do, what the business needs instead and what a replacement must support.

That gives you a clearer basis for comparing options and reduces the risk of choosing software because its features look impressive rather than because they solve the problem.

A practical exercise before buying anything

Choose one recurring problem in your business and work through these steps.

1. Describe the problem clearly.

Instead of saying, “We need a better CRM,” try, “We cannot reliably see which enquiries are waiting for a follow-up.”

2. Follow the current process.

Look at a few real examples. Identify where the work waits, information is repeated or responsibility becomes unclear.

3. Check the existing system.

Find out whether the necessary feature already exists and whether it is configured appropriately.

4. Identify the smallest useful change.

This might be agreeing who owns each enquiry, defining a few clear stages or creating a view of outstanding actions.

5. Test the change.

Use it on real work and check whether the original problem improves. If it does not, investigate what is still missing.

Only then decide whether new software or an integration is needed.

This approach will not prevent every unnecessary purchase, but it gives you a better reason to invest when a new tool is genuinely required.

Solve the problem before choosing the tool

Software matters. The right system can make work easier to manage, reduce repetitive tasks and give people better visibility.

But software is only part of how a business operates.

The process, responsibilities, information and habits around the system matter just as much.

When something is not working, start by understanding how the work moves from one person to the next. Find out what the current tools can do, where they fall short and what needs to change.

The answer may be a better configuration, a clearer process, more reliable data or a small amount of automation. Sometimes it will be new software.

The aim is not to avoid buying tools. It is to make sure the tool addresses the problem you actually have.

At Opriva, that is where the work starts: understanding where work gets stuck and finding the simplest practical fix.

If your team is struggling with a process or system, tell us where work is getting stuck.