Every growing business eventually faces the question: do we build software ourselves, or buy something that already exists? There is no universal answer, but there is a sensible way to decide. This guide gives you a framework.
The short version
- Buy when your need is common and a good product already solves it.
- Build when the software itself is part of what makes you different.
- Combine when a product covers most of it and you need some custom parts.
Why buying is usually the starting point
Ready-made platforms have advantages:
- Speed. You can start in days or weeks.
- Lower upfront cost. You share development costs with other customers.
- Proven. Real users have found and fixed many problems.
- Ongoing improvements. The vendor keeps developing it.
- Support. Someone else maintains it.
For things like a CRM, messaging inbox or HR system, buying is usually sensible. The problems are common and the products are mature.
When building makes sense
- It is your competitive edge. A unique pricing engine or workflow that customers value.
- No product fits. Your process is unusual and adapting to a product would harm the business.
- Integration needs are extreme. You need deep, custom links between systems.
- Scale or cost changes the maths. Very large usage can make custom cheaper over time.
Weigh the real cost of building
The build cost is only the start. Include:
- Design, development and testing.
- Hosting and infrastructure.
- Security and updates.
- Bug fixing and support.
- Changes as the business evolves.
- The people needed to maintain it after the project ends.
A common rule of thumb is that maintenance over the years exceeds the initial build. Plan for it.
Weigh the real cost of buying
- Subscription fees that rise with users or usage.
- Features you pay for but do not use.
- Limits on customisation.
- Dependence on the vendor's roadmap.
- Effort to migrate if you leave.
A simple scoring approach
Rate each option from 1 to 5 on these questions.
| Question | Buy | Build |
|---|---|---|
| How well does it fit our process? | ||
| How fast do we need it? | ||
| What is the total cost over three years? | ||
| Who maintains it? | ||
| How much risk are we taking? | ||
| Does it give us an edge? |
Discuss the scores with the people who will use it.
The hybrid approach
Many businesses do best by buying a platform and adding custom pieces, such as an integration, a special report or an automation around their unique process. This gets you speed and fit at moderate cost. It is also how we recommend approaching many projects.
Questions to ask before deciding
- Is this problem common to many businesses?
- Have we seen a product that solves 80 percent of it?
- What would we do with the time saved by buying?
- Who would own and maintain a custom system?
- What happens if the key developer leaves?
Avoid these traps
- Building because it feels more "yours". Own the outcome, not the code.
- Buying without checking fit. Test with real data first.
- Underestimating maintenance.
- Customising a product so much that upgrades become painful.
If you want a CRM, our choosing a CRM guide helps with the buying side. To discuss custom work, see our services or read how to choose a technology partner.
Frequently asked questions
Is custom software more expensive than a subscription?
Upfront, usually yes. Over many years the answer depends on scale, maintenance and how well the subscription fits.
Can I start with a product and build later?
Yes, and it is often wise. It lets you learn what you really need before committing to a custom build.
What if the product does not do everything I need?
Consider integrations and small customisations before building from scratch.
Talk to our experts
Alongside our platforms, our team plans, builds and runs custom technology for businesses, from AI and automation to software, cloud and data.