Guide / Strategy
Build vs buy software: how to decide
Buy when a product fits. Configure when it almost fits. Integrate when your tools work but don't talk. Build when the workflow is valuable, repeated, and generic tools force workarounds.
01
Four options
| Option | Use when | Trade-off |
|---|---|---|
| Buy | Standard process. Speed matters most. | Vendor's workflow, pricing and roadmap. |
| Configure | The product fits but is set up badly. | Heavy customisation gets brittle. |
| Integrate | Tools work alone; people copy data between them. | Depends on reliable connections. |
| Build | Valuable, repeated, poorly served by the market. | You own it, and its upkeep. |
02
Signals to build
- The work repeats daily or weekly.
- The cost is visible: hours, errors, lost revenue, slow decisions.
- Someone can explain the process, exceptions included.
- Configuring existing tools has been tried.
- A small first version can prove the value.
03
Hybrid usually wins
Keep commodity tools: accounting, CRM, payments. Build only the layer that is yours, the dashboard, workflow or integration that reflects how you operate.
04
Ask any software partner
- What would you buy before building?
- What goes in the first release?
- How are existing data and integrations handled?
- Who owns the code, deployment and access?
- What do we measure after launch?