There are two expensive mistakes in business software. The first is building something that already exists. The second is buying a tool that never fits and then paying staff to work around it for years.
Both mistakes start the same way: someone decided before testing. This guide gives you a way to test first.
Three signs you probably need custom software
- You pay for several tools and copy data between them by hand. Typing the same order into a spreadsheet, a billing tool and a messaging app is a sign that nothing talks to anything else.
- Your workflow has steps no product supports. If your people keep "working around the software", the software is not designed for your process.
- The software is the product you sell to your own customers. If you are building a SaaS or a platform, you cannot rent your core product from someone else.
Two signs you probably do not need it yet
- An existing tool covers most of what you need, and the gaps are minor. Living with small gaps is almost always cheaper than building.
- You have not tested your idea with real users. Do not build a full system on a guess. Start smaller.
What each route really costs
People compare the price of a subscription with the price of a build and stop there. That is not a fair comparison.
| Cost | Buying a ready-made tool | Building custom software |
|---|---|---|
| Starting cost | Low | Higher |
| Ongoing cost | Usually a fee per user or per month, which grows as you grow | Hosting and maintenance, which you control |
| Fit to your process | You adapt to the tool | The tool adapts to you |
| Time to start | Quick | Longer |
| Flexibility later | Limited to what the vendor allows | High |
| Data and exit | Check whether you can export everything | You own the code and the data |
| Hidden costs | Workarounds, add-ons, staff time | Maintenance, a team to improve it |
The honest way to compare is to add up three to five years. A tool that charges per user can become very expensive as your team grows. A custom system that nobody maintains becomes a liability. Neither is automatically the winner.
The third option: buy, then customise
Many businesses do best with a hybrid. If a tool like Zoho or Odoo covers most of what you need, you can customise it and connect it to your other systems instead of starting from nothing. A good development partner should be willing to recommend this when it is the better route, even though it means a smaller project for them.
If someone only ever tells you to build, ask why they dismissed the existing tools.
A one-week way to test before you spend
You do not need a consultant to do this. Give yourself a week.
- Write down your workflow from first customer contact to money in the bank. Be specific about who does what.
- List the ten steps that matter most. Ignore the rare exceptions for now.
- Shortlist two or three existing tools. Most offer free trials.
- Run real work through each one, not demo data. Use actual orders, actual customers.
- Count the workarounds. Every time someone says "we would have to do that by hand", mark it.
- Ask what the gaps cost. Hours per week, errors, delays, lost sales.
If the workarounds are few and cheap, buy. If they are many and the gaps cost real money every week, you have the business case for custom work.
Start with the smallest useful version
If you do build, do not start with everything. A minimum viable product, or MVP, is the smallest version that solves the core problem for real users. For new products, starting there is almost always right. It gets feedback in weeks rather than months, and it keeps your risk small.
For internal systems the same idea applies. Pick the one module that hurts most, such as billing or stock, get it working properly, then add more. A single module is often a sensible first budget, and quoting per module lets you spread the spending.
Ownership and the exit door
Whether you buy or build, ask two questions before you commit.
- Who owns the code and the data? With custom software you should own both once the project is paid for. You should receive the repository, the cloud accounts and the documentation.
- What happens if we part ways? With a bought tool, find out how you export your data. With custom software, make sure the code is documented well enough that another team could take it over.
Common mistakes
- Building a CRM from scratch. Unless your CRM is your product, there are good ones to buy.
- Underestimating maintenance. Software needs hosting, updates and fixes forever. Budget for it.
- Having no internal owner. Someone in your business must decide priorities and answer questions. Without that, projects drift.
- Buying for features instead of fit. A long feature list does not matter if your actual process is not on it.
- Changing the scope in every meeting. Small changes can go into the current work. Larger ones should get a written estimate first.
Questions people ask
Is custom software more expensive than buying?
At the start, yes. Over several years, it depends. A per-user subscription grows with your team, while custom software has fixed hosting and maintenance costs. Compare the three-to-five-year total, not the first invoice.
How long does custom software take to build?
It depends on the scope, so be wary of anyone who quotes a date before understanding your process. Starting with an MVP or a single module shortens the time to something useful.
Can you work on software someone else built?
Yes. A sensible start is a short code review, followed by a plain recommendation on whether to continue, fix or rebuild. Sometimes the right answer is to keep what exists.
Who owns the code?
You do, once the project is paid for. The repository, cloud accounts and documentation should be handed over.
What does it cost to run after launch?
Hosting, third-party services and maintenance. Ask for a monthly running-cost estimate with the quote, not after.
Where to go from here
If you are somewhere between "this tool nearly works" and "nothing fits our process", we can help you work out which side of the line you are on. We will tell you honestly if buying is the better route.
Read about our approach on the custom software development page, look at how we handle business software like CRM and ERP, or talk to us about your project.