Every growing business reaches the point where spreadsheets and copy-pasting between systems stop working. Orders get entered twice, reports take a day to assemble, and the person who understands the master spreadsheet goes on holiday.
The instinct is often to build something. Sometimes that is right. Often the better answer is to buy an existing product, or to connect the tools you already pay for. This guide gives you a simple way to decide.
Start with the problem, not the solution
Before deciding anything, write down:
- The job to be done. For example: "When an order is paid, create the invoice, update stock and notify the warehouse."
- Who does it today, how often, and how long it takes.
- What goes wrong: errors, delays, duplicated work.
- What "good" looks like: faster, fewer errors, a report available on demand.
A clear problem statement often makes the answer obvious.
Option 1: Buy
Buy when the need is common to many businesses: accounting, payroll, CRM, helpdesk, project management, HR. Mature products have solved the edge cases, handle security and updates, and cost less than building the same thing.
Questions to ask:
- Does it cover most of the need out of the box, or only with heavy customisation?
- Can it connect to your other systems (does it have an API or built-in integrations)?
- Can you export your data if you leave?
- How does pricing grow as you add users or volume?
Heavy customisation of a bought product can end up costing as much as building, with less control. If you find yourself fighting the product, that is a signal.
Option 2: Integrate
Integrate when you already have good tools that do not talk to each other. This is the most underused option. Connecting systems through their APIs, or through a workflow automation platform, often removes most of the manual work for a fraction of the cost of a new system.
Good integration work:
- Moves data automatically in one direction with a clear source of truth for each type of data.
- Handles failure: retries, alerts when something cannot be synced, and a way to fix it.
- Logs what happened so problems can be traced.
Option 3: Build
Build when the process is specific to how your business works and gives you an advantage, or when nothing on the market fits without bending your process out of shape. Typical examples are internal dashboards that combine data from several systems, tools for a workflow unique to your industry, or a customer-facing feature that sets you apart.
The risks of building are real: someone has to maintain it, secure it, and update it when the systems around it change. A custom tool that nobody can maintain becomes a liability.
A quick decision guide
| Situation | Usually the best choice |
|---|---|
| A standard business function many companies need | Buy |
| Good tools already in place, but manual work between them | Integrate |
| A process specific to your business that creates value | Build |
| Unsure, and the need is still changing | Start with the smallest integration or a simple prototype |
How to keep a custom build healthy
If building is the right answer, keep it small:
- Build the smallest useful version first and put it in front of real users quickly.
- Use boring, well-supported technology your future team can maintain.
- Use your existing identity system (for example Microsoft 365 or Google Workspace sign-in) rather than separate passwords.
- Write down how it works: what it connects to, where it runs, how to deploy it.
- Plan for maintenance from the start: updates, security patches, monitoring and backups.
- Own the code and the data. Make sure the source code is in your repository and your data can be exported.
Where to start
If manual work between systems is slowing your team down, the answer may be simpler than a new system. If you would like an honest view on whether to buy, integrate or build, including the option of doing nothing yet, book a free consultation and we will look at the process with you.