Custom software or standard product: the make-or-buy decision
When does bespoke development pay off—and when should you buy? A practical guide with checklist, cost comparison and hybrid options for mid-market companies.
Make-or-Buy Software
What the make-or-buy question is really about
Almost every mid-market company eventually asks: do we buy a ready-made product or have software built for us? The make-or-buy decision (also called build vs buy) is one of the most strategic IT choices—and it is often made on incomplete numbers. Standard software looks cheaper in procurement; custom software looks expensive and risky. In practice, many ERP and SaaS rollouts spend a large share of licence budget again on customisation and integrations—money that a well-scoped custom build might avoid from day one.
Conversely, custom projects fail when requirements drift or architecture is treated as disposable. This page helps you decide for your situation—not ours. We advise neutrally: sometimes the right answer is Salesforce, Odoo or a vertical SaaS, not a greenfield build. When you need depth on delivery models, see our in-house vs agency comparison and the dedicated custom vs standard software comparison.
When to build, when to buy
Choose custom software when …
- Processes differ materially from market standard
- Data and logic are a competitive advantage
- Vendor lock-in is unacceptable
- Tailoring a product costs more than building
- Data sovereignty rules out US-only clouds
- You want to offer your own product (SaaS) to customers
- No suitable standard product exists
Choose standard software when …
- The process is generic with no differentiation upside
- Market tools cover 85 %+ of requirements
- Speed to go-live matters more than perfect fit
- Regulatory updates must come from the vendor
- Your IT team cannot maintain custom code long term
- Budget for development is not available
- Best practice beats bespoke logic
Total cost of ownership over five years
The classic mistake is comparing one-off build cost with monthly licence fees. What matters is total cost of ownership (TCO) over five to seven years—including implementation, integrations, operations and exit cost. Our ROI calculator for custom software and software development cost overview help quantify typical ranges for mid-market projects.
| Cost category | Custom software | Standard software |
|---|---|---|
| Entry cost | €30,000–500,000 development | €5,000–50,000 implementation |
| Ongoing licence | None | €20–200 / user / month |
| Customisation | Low (you own the code) | Often 30–40 % of licence spend |
| Maintenance | ~10–20 % of build cost p.a. | Included in licence (until it is not) |
| Vendor lock-in | You own the asset | Switching can mean full re-implementation |
Hybrid: buy the core, build what differentiates
The best answer is often neither pure make nor pure buy. A best-of-breed hybrid uses standard ERP or CRM for finance, purchasing and HR—then a tailored app for your distinctive sales or configuration workflow, connected by APIs. Example: Odoo as operational core plus a custom quoting tool for complex B2B sales. The challenge is clean interfaces and ownership of integration logic; we help you draw the system boundary in a short workshop.
If the outcome is a product for your customers—not only internal tooling—read our SaaS development solution page or start with an MVP to validate demand before a full platform investment.
Neutral make-or-buy advice before you sign a licence or SOW
We have recommended standard products when they were the better fit—and walked away from build projects that should not start yet. Bring your process map, licence quote and integration list; we will give you an honest build-vs-buy recommendation with rough TCO bands, not a sales pitch for custom code.
Björn Groenewold – Managing Director
Frequently Asked Questions
Make-or-buy: software decision FAQ
Cost, risk and decision criteria
When does custom software beat off-the-shelf products?
Custom development pays off when at least one of these applies: your processes differ materially from market standard and tailoring a product costs more than building; data or logic is a competitive asset and must not sit in a vendor cloud; vendor lock-in is unacceptable; or the standard tool covers
only 60–70 % of requirements and the missing share is business-critical. Rule of thumb: if you spend more than 30 % of licence fees each year on workarounds and integrations, custom software is often cheaper over three to five years.
How do upfront and running costs compare?
Custom software needs higher upfront investment (often €30,000–500,000) but no per-user licence and fewer forced upgrades. Standard products start cheaper but accumulate licence, customisation and integration cost—typical €20–200 per user per month plus 30–40 % of licence spend on tailoring. Break-even for mid-sized user counts is often year three to five. We model total cost of ownership before you commit.
How long does custom development take?
A focused MVP with core features can ship in 8–16 weeks. Multi-module applications with roles and ERP links often need four to nine months. Large platforms with heavy integration and compliance can take twelve to twenty-four months. We always recommend iterative delivery so you learn from real usage before funding the next scope.
What are the main risks of building in-house or with a partner?
The three usual risks are technical debt from weak architecture, project overrun from scope creep, and dependency on one supplier. We mitigate with clear standards, automated tests, sprint reviews, full source handover and documentation so another team can continue. We will also tell you honestly when buying standard software is the better call.
When is standard software clearly the right choice?
Buy when the process is generic and offers no differentiation—accounting to local GAAP rules, email, simple project tools, video calls, standard HR. Build what differentiates you; buy what everyone needs the same way. Many mid-market companies succeed with a hybrid: ERP or CRM as standard core plus custom apps for distinctive workflows.
Discuss your situation
Free initial call: we analyse requirements and recommend build, buy or hybrid—even when buy wins.
Make-or-buy: structured software decision
„A individualsoftware oder standardsoftware solution only pays off when processes, roles, and integrations are end-to-end—not another silo.“