Skip to content
← Back to Insights

BUSINESS STRATEGY

Before investing in technology, ask these five questions.

A new website, booking platform or business system can be a useful investment. But choosing the tool is rarely the best place to start. Before looking at features, take a step back and define the business problem you want to solve.

Business professional reviewing plans with a notebook and laptop at a sunlit desk

1. What business outcome are we trying to achieve?

“We need a new system” describes a purchase, rather than a result. A clearer aim might be to reduce missed enquiries, make booking easier or give the team a reliable view of outstanding work. These outcomes help you judge whether a proposed solution is relevant.

Be specific about who should benefit and what should change. For an independent garage, the aim could be to let customers request a service without waiting for someone to answer the phone. For a retailer, it might be to stop selling products that are no longer available.

Choose a primary outcome and write it in plain language. If several people are involved in the decision, ask them to agree on that sentence before discussing suppliers. Otherwise, each person may be expecting a different benefit from the same investment.

2. What is currently preventing that outcome?

Follow the work as it happens today. Where does a customer request arrive? Who sees it? What information is missing? Where does the process slow down? Talking with the people doing the work often reveals more than a list of software requirements.

An enquiry might be missed because it reaches several inboxes with no clear owner. A booking might stall because customers cannot see the information they need. A report might be unreliable because the same details are typed into two places. Each problem calls for a different response.

Separate symptoms from causes. More website traffic will not resolve a confusing booking process. Automation will not clarify an unclear responsibility. Identify the part of the journey that needs attention before deciding how technology should support it.

3. Can we improve what we already have?

Existing tools may be capable of more than the business currently uses. Before replacing them, check whether better configuration, clearer processes or a connection between systems could solve the problem. Ask the team which features they avoid and why.

A shared enquiry list with an owner and a next-action field could be enough to make follow-up more consistent. A simpler form might remove friction from an existing website. These options deserve a fair comparison with a larger replacement project.

Keeping an existing tool is not always the right answer. It may be unreliable, difficult to maintain or unable to support the required work. The point is to assess it against the outcome, rather than assuming that newer automatically means better.

4. What will implementation require from the business?

The price of software is only one part of implementation. Someone must prepare information, make decisions, test the process and help colleagues adopt it. Even a small project can become difficult if no one has time to own these tasks.

Discuss who will approve changes, which records need moving and what training people need. Plan how customers and staff will be supported during the transition. If the business has a busy seasonal period, choose a timetable that reflects that reality.

Ask what happens after launch as well. Who handles updates, questions and unexpected problems? A solution that depends on knowledge held by one person can create a new operational weakness. Clear ownership and practical documentation are part of the investment.

5. How will we know whether the investment worked?

Decide what evidence would show progress before the project begins. Useful measures might include the time needed to respond to an enquiry, the number of requests awaiting action or the amount of repeated administration. Choose measures connected to the original aim.

Record how the process works now so you have something meaningful to compare. Combine simple measurements with feedback from staff and customers. A faster process is not necessarily a better one if it creates confusion elsewhere.

Set a review point after the team has had time to use the solution. Look at what improved, what remained difficult and what needs adjustment. Technology decisions become easier to assess when the business outcome stays visible from the first conversation to the review.

Discuss what this means for your business.

If this topic raises a question about your next step, we'd be happy to talk.

Get in touch ↗
← Back to Insights