Custom software vs off-the-shelf software: should you build or buy?
By Sarmed, co-founder of Impleko
The short answer: Buy off-the-shelf software when it fits most of how you work: it's fast to start, and someone else maintains it. Build custom software when the tools you can buy force workarounds, you're paying for several subscriptions that each do part of the job, or your process is what sets you apart. Many businesses do both: they buy the standard tools and build custom software that connects them.
Custom vs off-the-shelf software at a glance
| Off-the-shelf software | Custom software | |
|---|---|---|
| Fit | You adapt your process to the tool | The software adapts to your process |
| Time to start | Days | Weeks, often with a working prototype first |
| Upfront cost | Low | Higher: a one-time build |
| Ongoing cost | Per-user fees that grow with your team | Hosting and support |
| Ownership | The vendor owns it; you rent access | You own the code and the data |
| Changes | Wait for the vendor's roadmap | Change it when your business changes |
| Integrations | Only what the vendor supports | Built around the tools you already use |
| Maintenance | Done by the vendor | Done by your developer or support plan |
| Risk | Price rises, feature changes, the vendor shutting down | A poor build or a developer who disappears |
What's the difference?
Off-the-shelf software is a ready-made product sold to many businesses: think of a CRM, a booking app or an accounting package. Most of it is now SaaS (software as a service), which you rent by the month and use in a browser.
Custom software is built for one business's own processes, customers and data: a client portal, an internal tool, a custom CRM or a system that connects the apps you already use. You own it, and it does what you need, nothing more.
Cost: compare over three years, not one month
Off-the-shelf software looks cheaper because you see the monthly fee, not the total. A fair comparison looks at three years.
An example: a team of 20 on a tool that costs $50 per user a month pays 20 × $50 × 36 months = $36,000 over three years, before price increases, add-ons and the hours spent working around what the tool can't do. If the team also pays for two more tools to cover the gaps, the total climbs further.
To compare, add up for each option:
- Licenses or the build: monthly fees × users × 36, or the fixed quote for custom software
- Add-ons and extra tools you need to fill the gaps
- Setup, data migration and training
- Hosting and support for custom software
- Time lost to workarounds: hours per week × hourly cost × 156 weeks
Custom software usually wins when the team is large enough that per-user fees add up, or when workarounds eat hours every week. Off-the-shelf usually wins for small teams with standard needs.
Benefits and risks of each
Benefits of custom software
- It fits how your business actually works
- No per-user fees as the team grows
- You own the code and the data
- It connects the tools you already pay for
- It can become a competitive advantage that rivals can't buy
Risks of custom software
- A higher upfront cost and a few weeks before it's ready
- A poor build is hard to fix; choose a team that tests and documents its work
- If the code isn't in your name, you depend on one developer
Benefits of off-the-shelf software
- Ready in days, with no build risk
- The vendor handles updates, security and hosting
- Lower upfront cost
Risks of off-the-shelf software
- Price rises and per-seat fees that grow with your team
- Features change or disappear on the vendor's schedule
- Your data and workflows are tied to the vendor
- Workarounds that cost hours every week
The third option: buy, then connect
You don't have to choose all or nothing. Many businesses buy standard tools for standard jobs, like accounting, email and payments, and build custom software only where their process is unique, or to connect the tools so data moves on its own. A client portal that pulls from your CRM and your invoicing tool is a common example. This keeps costs down and puts custom work where it pays off most.
SaaS vs custom software
SaaS is off-the-shelf software you rent and use in a browser, such as most CRMs and project tools. Custom software can also run in a browser, so the difference isn't the technology; it's who it's built for and who owns it. A SaaS product serves thousands of businesses the same way. Custom software serves one business its own way, and that business owns it.
Build vs buy: a checklist to decide
Build custom software if you answer yes to three or more:
- Does your team copy data between three or more tools every day?
- Do you pay for several subscriptions that each do part of one job?
- Have you outgrown a tool, or hit features it will never have?
- Do per-user fees grow every time you hire?
- Do clients ask for updates you could show them in a portal?
- Is your process what makes your business different?
- Do workarounds cause mistakes or delays?
- Will you still need this in three years?
Buy off-the-shelf if most answers are no, or if a ready-made tool covers almost everything you need.
How Impleko helps you decide
We'll tell you if you should buy instead of build. When custom software makes sense, we scope the smallest version that solves the main problem, show you a clickable prototype in 1 day, build and test it, and put the code in your GitHub from the first commit. When a ready-made tool fits, we connect it to your other systems instead. See custom software development.
Questions about custom and off-the-shelf software
Is custom software more expensive than off-the-shelf?
Upfront, yes. Over three years, not always. Per-user fees, add-on tools and time lost to workarounds add up, so compare the three-year total of both options, not the first month.
How long does custom software take to build?
Impleko shows a clickable prototype in 1 day and delivers the first working version in weeks for most projects, starting with the smallest version that solves the main problem. Larger systems are built and released in stages.
Who maintains custom software after launch?
Either your own developer or the team that built it, through a support plan. Because the code is in your name and documented, any developer can pick it up later.
What is vendor lock-in?
Vendor lock-in is when moving away from a software product is so costly or difficult that you stay, even when prices rise or features change. Owning your code and data is the main way to avoid it.
Should a startup build or buy?
Buy for everything that isn't your product, like accounting, email and CRM. Build the product itself, starting with an MVP. See MVP vs prototype.
Can custom software work with the tools we already use?
Yes. Custom software is usually built to connect with your CRM, payments, website and other tools through APIs and webhooks, so data moves between them on its own.