Should you build or buy software? The question comes up in every company replacing an ageing tool, structuring its sales or finally leaving its Excel files behind. There is no universal answer, but there is a method: compare your processes, the total cost over several years, the integrations you need and who owns your data.
Buying software: fast, but standard
Off-the-shelf software — ERP, CRM, invoicing — has one decisive advantage: it is available now. Common features are there, the vendor handles updates and many users have already tested it.
- Fast go-live for standard needs
- Low entry cost, often as a subscription
- Maintenance handled by the vendor
The downside shows over time: per-user licences that grow with the team, costly configuration, extra modules, and above all processes bent to the vendor’s logic. When Excel workarounds multiply, bought software costs more than it returns.
Building custom software: fitted, but needs scoping
Custom software mirrors your real processes, screen by screen. It evolves with your business, has no per-user licence, and belongs to you: code, database and documentation.
In return it needs proper scoping. A successful custom project starts with the data model and ships in short increments, beginning with the module that wastes the most time. That is our approach for a custom ERP and for the business applications built by our Symfony agency.
5 criteria to decide whether to build or buy software
1. Are your processes standard?
If the way you sell, buy or produce looks like your competitors’, off-the-shelf software is often enough. If it is what sets you apart, standardising it may cost you that edge.
2. How many users in 3 years?
Beyond about twenty users, cumulative licence cost becomes a major factor. Calculate it over five years, not just the first.
3. Which integrations do you need?
A CRM that reads ERP orders, a website showing real-time stock: every connector adds cost and risk. When integrations are numerous, a shared foundation — one database for ERP, CRM and website — becomes simpler than a chain of connected tools. See our comparison iPaaS vs custom development.
4. Who owns the data?
With bought software your data lives at the vendor, in its format. With custom development it sits in your database, usable by your analytics and AI tools.
5. What is the 5-year total cost?
Compare full costs: licences, configuration, modules, integrations, training and time lost to workarounds on one side; development, hosting and maintenance on the other. The difference rarely shows in year one.
The right time to build is when your tools cost you more in workarounds than in licences.
What about an ERP or a CRM?
For an ERP, the question arises as soon as your processes are specific or you run your business across several spreadsheets. Our article custom ERP vs software package covers the break-even points.
For a CRM, most SMEs start with a well-configured market tool. Custom makes sense when the sales cycle is complex or quotes and orders must live in the same database as the ERP — see custom CRM vs Salesforce / HubSpot.
The third way: buy, then build around it
Build or buy is not always binary. Many companies keep a market tool for accounting or payroll and build what makes them different: the core business, the customer portal, the integrations. What matters is a consistent data model.
Build or buy software: FAQ
Is building always more expensive?
Up front, yes. Over five years, not necessarily: with no per-user licences or workarounds, custom software can cost less than bought software.
Can bought and custom software be combined?
Yes, and it is common: a market tool for accounting or payroll, custom software for the core business, connected through APIs.
Where to start
List your processes, tools and pain points, then cost both options over five years. For an outside view, take the 2-minute audit or book 30 minutes with an expert: we will tell you honestly if a market tool is enough.