The two options at a glance
| Off-the-shelf product | Custom software | |
|---|---|---|
| What it is | Software built for many companies, licensed to you | Software designed and built for your process |
| Time to first use | Short, since the product exists | Longer, since it has to be designed and built |
| Fit to your process | You adapt your process to the product | The software is shaped to your process |
| Cost shape | A recurring fee, usually per user | A larger first cost, then maintenance |
| Who maintains it | The vendor | You, with your team or a partner |
| Control over direction | The vendor decides what is built next | You decide |
| Leaving | Depends on data export and contract terms | You hold the code and the data |
Test the fit before you compare prices
The decision turns on one question. Is this process something every company in your field does in much the same way, or is it part of how you win? Accounting, payroll and email are the first kind. The way you quote, schedule, price or serve customers may be the second.
- 01
Write down the process as you run it today
Step by step, with the exceptions. The exceptions are where products fail to fit.
- 02
Try two or three leading products against it
Use real cases, not the vendor's demonstration. Count the steps that fit, the steps that need a workaround and the steps that cannot be done.
- 03
Ask what each workaround costs
A manual step, a spreadsheet beside the system or a second tool is paid for every day by your staff.
- 04
Ask whether you could change the process instead
Sometimes the product's way is better than yours. Adopting it is cheaper than defending a habit.
A rough guide. If a product covers nearly everything and the gaps are habits, buy it and adapt. If the gaps are in the part of the work that customers pay you for, look at custom or at a combination.
When each one fits
Buy a product when
- The process is standard in your industry
- You need it working soon and can accept its way of doing things
- A mature market exists, with several credible vendors
- You have nobody to own software over the years
- The vendor's roadmap points where you are going
Build custom when
- The process is specific to you and is part of your advantage
- Products force workarounds in the work that matters most
- You need deep integration between several systems
- Per-user fees would grow faster than the value you get
- You plan to sell the software, or it is the product itself
How the cost behaves over time
A product looks cheaper at the start, and often is. The fair comparison looks several years ahead and counts everything.
| Cost | Off-the-shelf product | Custom software |
|---|---|---|
| At the start | Setup, configuration, data migration and training | Discovery, design, build, data migration and training |
| Every year | License fees that grow with users and modules | Hosting, maintenance and improvements |
| Hidden | Workarounds, extra tools, consultants for customization, price increases | The attention of your own people, and keeping knowledge when staff change |
| When you grow | More users means more fees | More users costs little, and new features cost engineering time |
| When you leave | Export, migration and retraining | Little, since you already own it |
Neither column is cheaper in general. A small team with a standard process will rarely recover the cost of building. A large team paying per user for a product that fits poorly often will.
The middle routes most teams overlook
Build or buy is usually presented as a choice of two. In practice there are four, and the two in the middle are often the best value.
| Route | What it means | Fits when |
|---|---|---|
| Buy and adopt | Use the product as designed and change your process | The product's way is good enough |
| Buy and configure | Use the product's own settings, fields and workflows | The gaps are small and the product is flexible |
| Buy and extend | Keep the product as the core, and build custom tools around it through its API | The core is standard and your difference sits at the edges |
| Build | Design and build the whole system | The core itself is what makes you different |
The third route deserves attention. A standard accounting or CRM product with a custom quoting tool, customer portal or scheduling system connected to it gives you the vendor's maintenance where your needs are ordinary and your own software where they are not. That connection work is what our system integration service covers.
A worked example
A service company with three systems to choose
A field service company with forty technicians reviews its software. The company is invented, and the reasoning is what matters.
- AccountingStandard in every respect. Decision, buy and adopt.
- Customer recordsMostly standard, with two extra fields and one approval step. Decision, buy and configure.
- Job schedulingThe company wins work by fitting urgent jobs into existing routes, using rules about skills, parts and travel that no product handles. Decision, build, and connect it to the other two.
- ResultOne custom system instead of three, built for the part of the business that customers notice.
The company did not ask whether it was a build company or a buy company. It asked the question once per process.
A checklist to decide
Before you choose
0 of 8 checkedWhat to do next
Run the fit test on your most important process this week. It costs a few hours and usually settles the question. If spreadsheets are what you are replacing, our guide on how to replace business spreadsheets with software starts one step earlier.
If the result points to custom or to a combination, our custom software development page explains how we work. And if you would like a second opinion on the fit test, send it to us. We will tell you when buying is the better answer.
Common questions
Is custom software always more expensive than buying?
At the start, almost always. Over several years, not necessarily. License fees grow with every user and module, while custom software costs little to extend to more people. The balance depends on how many users you have, how well the product fits and how long you will use the system.
How do I know whether a product will fit my process?
Test it with your own cases, including the awkward ones, and let the people who do the work run the test. A vendor demonstration shows the product at its best. A trial with last month's real orders, jobs or cases shows where it bends and where it breaks.
Can we start with a product and move to custom later?
Yes, and it is often wise. A product lets you run the process and learn what you need. Keep your data exportable and note every workaround. When the list of workarounds is long and stable, you have a specification for the custom system.
What about low-code platforms?
Low-code tools sit between the two. They let you build something specific faster than writing code, inside the limits of the platform. They suit internal tools with simple rules and a moderate number of users. They become costly when logic is complex, integration is deep or per-user pricing grows.
Where to go from here
Related serviceCustom Software DevelopmentSoftware that fits the process you already run