Start here.
Start by looking for existing software that handles the work you need to do. A custom build becomes worth considering when you can name the important things those tools cannot do, explain what those gaps cost your business, and take responsibility for the software after it launches.
- Write down the compromises you could accept before watching product demonstrations.
- Include the people who will use the software in the decision.
- Ask what your business would need to provide, including staff time and information.
What are you trying to make easier?
Imagine a small business that installs custom cabinetry.
A customer sends an enquiry. Someone visits the property, prepares a quote, confirms the details, orders materials, and books the installation. Along the way, the customer emails to ask when things will happen.
The business already has accounting software, a shared calendar, and a spreadsheet of current jobs.
“Put everything in one app” sounds appealing. But it leaves a lot undecided.
The most frustrating part might be that customers have no way to check their installation date. Or that the person preparing a quote has to ask three colleagues for information. Those are different problems, and they may need different solutions.
Before shopping for software, choose one recent job and follow it from beginning to end. Where did someone wait, repeat work, or make a mistake? That gives you something concrete to improve.
When is existing software a good fit?
Look for products designed to handle the job you’ve identified. Ask for a demonstration using an example from your business.
For the cabinetry company, that might mean taking a sample enquiry through quoting, scheduling, and customer updates. A polished demonstration is useful; seeing whether the product can handle a changed installation date is more revealing.
Some changes to how you work may be reasonable. Others may remove the very thing customers value about your business. Write those down so you can judge the fit. Pay attention to the compromises:
- Can your staff complete the job without keeping a second record elsewhere?
- Can customers use it without needing someone to explain every step?
- Can you get your information out if you decide to leave?
- Are the features you need included in the price you’re considering?
Could a smaller addition solve the problem?
You may be able to keep most of what you already use.
If the cabinetry company’s accounting and scheduling tools work well, a small customer area could give people access to their agreed plans, dates, and outstanding approvals.
That would still need careful planning. Someone must keep the information current, and customers need to know whom to contact when plans change. But it is a more specific project than replacing every system in the business.
Ask a prospective software partner to consider this option alongside buying a product and commissioning a larger build.
When does having something built make sense?
Custom software deserves a closer look when the missing capability matters to how your business earns money, serves customers, or gets work done.
You should be able to finish this sentence: “We need customers or staff to be able to ___, and the options we’ve tried fall short because ___.”
The stronger your answer, the easier it becomes to discuss a useful project.
For our example business, that might be letting customers review and approve a particular version of their cabinetry plans, with the agreed details available to the installation team. A general appointment tool may cover only a small part of that job.
A custom build also brings ongoing responsibilities: maintenance, support, access to business accounts, and decisions about future changes. Include those in the conversation before agreeing to the project.
What should you do before spending money?
Bring one ordinary example of the work and one that went wrong. List the tools involved and explain what you would like to happen differently.
Then ask for a comparison of the realistic options, including keeping your current setup.
A useful recommendation should explain what each option solves, what compromises remain, and what you would need to maintain. You should be able to understand that recommendation without learning how to develop software.
A starting point for your conversation.
You can describe the problem in everyday language. These prompts help someone understand what matters to your business.
- The moment you noticed it
- What happened recently that made you think something needed to change?
- The people affected
- Who deals with the problem, and who would need to be involved in choosing a solution?
- What you have tried
- Which products or workarounds have you considered, and what stopped them from being a good fit?
- Your practical limits
- Are there busy periods, existing commitments, or spending limits the project would need to work around?
A couple of common questions.
How should we involve staff in choosing software?
Ask the people doing the work to try a realistic task and describe what feels unclear or adds effort. Include someone who handles exceptions, such as a changed order or a missing approval. Give them time to test before asking them to recommend a choice.
What if we are not ready to decide yet?
Keep a short record of the next few times the problem occurs: what happened, who had to help, and how it was resolved. That can give you a clearer basis for a later discussion without committing to a project now.