Business software selection

Why it matters

Software shapes process. Whatever tool you choose for quoting, scheduling or stock will decide how those jobs are done, who can do them and what you can measure. The cost of a poor choice is not the subscription but the staff time lost to workarounds, the data trapped in the wrong shape and the switching cost two years later. A structured selection costs a few days of attention and usually pays for itself before the first invoice.

Start with the problem, not the product

Write down, in one paragraph, what is wrong today and what better would look like in measurable terms. "Quotes take two days and we lose work to faster competitors; we want same-day quotes from site" is a problem statement. "We need a CRM" is not. The problem statement becomes the test every candidate must pass, and it stops the project drifting into features nobody asked for.

Then map the process. Walk through how the work actually happens, who touches it, where it waits and where errors creep in. A whiteboard and an hour with the people who do the job is enough. The map shows which steps the software must handle, which it should connect to and which you should fix before any software is involved; automating a bad process just makes mistakes faster.

• One-paragraph problem statement with a measurable outcome.
• A simple process map: steps, people, handoffs, waiting points.
• A must-have list of no more than ten items, and a nice-to-have list kept separate.
• The systems the new tool must exchange data with, especially accounting.

Buy, configure or build

Off-the-shelf software does one job well for many businesses and is cheapest when your process is close to standard. Configurable platforms, such as low-code tools or flexible CRMs, let you shape forms, fields and workflows to your process without writing code, at the price of more setup and ongoing ownership. Custom-built software fits exactly, costs the most, and makes you responsible for maintaining it for as long as you use it.

The honest rule for a small business is to buy when a product covers at least most of the must-haves, configure when your process is a genuine point of difference that standard tools distort, and build only when the process is core to how you compete and nothing on the market comes close. Even then, build the smallest thing that works and connect it to standard products for everything else.

Scoring a shortlist

Aim for two or three candidates, not ten. Score each against the must-have list, then plot them on two axes: how well they fit the process, and what they cost in total over three years. The best choice is almost never the cheapest or the most feature-rich; it is the one in the top-right corner that fits well at a sustainable cost.

Trial the top one or two with real data and the people who will use them daily, for at least a week of normal work. Pay attention to how staff feel about it on day five, not day one. Test the export, test the mobile experience if the work happens in the field, and test the integration with your accounting software, because that is where most tools disappoint.

Total cost of ownership

The subscription is the visible cost. The real cost includes setup and data migration, the time staff spend learning it, integration with other systems, any customisation, ongoing administration and the eventual cost of leaving. For a small team, the biggest item is often staff time during the change, which is why a tool that is slightly less powerful but much easier to adopt frequently wins.

Plan the rollout as carefully as the choice. Name an owner, set a cut-over date, migrate clean data rather than everything, train people on their own tasks rather than on every feature, and switch the old tool off. Running two systems in parallel for months is the most common way a good selection turns into a failed project.

How to choose business software

1. Write the problem statement What is wrong, what better looks like, and how you will measure it.
2. Map the current process An hour with the people who do the work; capture steps, handoffs and pain points.
3. List must-haves and integrations No more than ten must-haves; name the systems it must connect to.
4. Decide buy, configure or build Buy unless your process is a genuine point of difference.
5. Shortlist and score Two or three candidates scored on fit and three-year total cost.
6. Trial with real work A week of real data and real users; test export, mobile and accounting integration.
7. Decide and plan the cut-over Named owner, migration of clean data, task-based training, old tool switched off.
8. Review after 90 days Measure against the problem statement and fix what is not being used.

Real-world example

A Hobart wholesaler chooses inventory software

Derwent Provedores supplies restaurants across southern Tasmania. Stock is tracked in a spreadsheet, orders arrive by text and phone, and twice a month a delivery goes out with items that were already sold to someone else. The owner, Tom, nearly buys a large inventory system after an impressive demo until his bookkeeper asks how it will talk to the accounting software.

Tom writes the problem down: eliminate double-selling and get orders into accounting without re-keying. He maps the order-to-delivery process with his two warehouse staff, lists eight must-haves including a mobile picking view and a native accounting connection, and shortlists three products. Two are trialled for a week with real orders. The cheaper one is strong on stock but weak on ordering; the mid-priced one fits the whole process and exports cleanly. He takes the monthly plan, migrates only current products and customers, trains staff on their own tasks, and retires the spreadsheet on a Friday. Double-selling stops within a month, and the bookkeeper’s month-end shrinks by a day.

Common mistakes

• Buying from the demo Demos are designed to impress. Only a trial with your data and your people shows whether a tool fits.
• A hundred requirements Long requirement lists favour bloated products. Ten must-haves and a clear problem statement choose better.
• Ignoring integration A tool that cannot connect to your accounting or CRM creates double entry forever. Check the connection during the trial.
• Building when you should buy Custom software for a standard process costs more, takes longer and leaves you maintaining it. Build only for genuine advantage.
• Running old and new in parallel Without a cut-over date and the old tool switched off, staff drift back and the project quietly fails.

KPIs to track

• Problem metric before and after The measure from your problem statement, such as quote turnaround or stock errors, compared at 90 days.
• Adoption rate Share of intended users actively using the tool each week. Below full adoption after a month means training or fit issues.
• Three-year total cost versus estimate Actual licences, setup, integration and support against the figure used to decide. Learn from the gap.
• Manual re-keying eliminated Hours per week no longer spent re-entering data between systems.

Frequently asked questions

How long should software selection take?

For a small business, two to six weeks is usually enough: a week to define and map, a week or two to shortlist, a week or two to trial. Longer processes rarely produce better decisions.

Should I hire a consultant to choose software?

For a core system such as job management or ERP, an independent adviser who does not resell software can save costly mistakes. For simpler tools, the process in this article is enough.

What if no product fits our process?

First check whether the process itself is unusual for a good reason. If it is, look at configurable platforms before custom development, and keep any custom part small and connected to standard tools.

How do I get staff to use the new system?

Involve them in the mapping and the trial, train them on their own tasks, fix the first problems fast, and switch off the old tool. People use systems that make their day easier and that they helped choose.

Key takeaways

• Write the problem and map the process before you look at any product.
• Buy unless your process is a genuine point of difference; build only for core advantage.
• Score a short list on fit and three-year total cost, and trial with real work.
• Test export, mobile use and accounting integration during the trial.
• Plan the cut-over, train on tasks and switch the old tool off.