The Wrong Question
“Should we build or buy this?” is the wrong question. The right one is: “Is this software a competitive advantage or a commodity?”
If the software differentiates your business — if it represents processes your competitors don’t have — custom development is a strategic investment. If it fulfills a standard function (email, CRM, accounting), custom development is waste.
The Four Quadrants
Quadrant 1: Buy (Standard + Non-differentiating)
Examples: Email, office suite, CRM, HR system, accounting, project management
There’s no competitive advantage from building these. Off-the-shelf software is cheaper, better maintained, and faster to deploy.
Common mistakes:
- “Our process is so unique that no CRM fits” — rarely true
- “We can build it cheaper ourselves” — true only for version 1.0, not over 5 years
Quadrant 2: Build (Unique + Differentiating)
Examples: Core algorithm, proprietary platform, unique customer process, industry-specific logic
This is where competitive advantage is created. Standard software can’t provide this by definition — otherwise your competitors would have the same advantage.
Common mistakes:
- Building too early (before the process is validated)
- Building too much (the entire platform instead of just the differentiating core)
Quadrant 3: Configure (Standard + Differentiating)
Examples: ERP with industry-specific customization, CMS with custom workflows, BI platform with custom dashboards
Standard software as the base, configuration and extensions for differentiation. The middle ground.
Quadrant 4: Eliminate (Unique + Non-differentiating)
Examples: Internal tools that grew historically and no longer deliver business value
The most honest question: do we even need this? Often the answer is no.
The True Costs
Build — Total Cost of Ownership
Development costs are just the tip of the iceberg:
| Cost Factor | Year 1 | Year 2-5 (per year) |
|---|---|---|
| Development | $$$ | — |
| Maintenance & bug fixes | — | $$ |
| Infrastructure | $ | $ |
| Security patches | — | $ |
| Feature development | — | $$ |
| Opportunity cost (team) | $$$ | $$ |
| Total | $$$$$ | $$$$ |
Buy — Total Cost of Ownership
| Cost Factor | Year 1 | Year 2-5 (per year) |
|---|---|---|
| License/subscription | $$ | $$ |
| Implementation & configuration | $$ | — |
| Integration | $ | $ |
| Training | $ | — |
| Customizations | $ | $ |
| Vendor lock-in risk | — | $? |
| Total | $$$$ | $$$ |
Decision Checklist
Lean toward Build when:
- The software represents a unique business process
- No standard product covers >70% of requirements
- You have a strong internal engineering team
- The software is a long-term strategic advantage
- You can validate the MVP in less than 3 months
Lean toward Buy when:
- The requirement is a solved problem (CRM, ERP, email)
- More than 3 established products fulfill >80% of requirements
- Your engineering team is small or already at capacity
- Time-to-market is critical
- Compliance/certification is complex (the vendor already has it)
Lean toward Configure when:
- A standard product fits 60-80%
- The differentiation lies in configuration, not code
- The product offers an extension/plugin system
- You need the base quickly and the differentiation iteratively
The Hybrid Strategy
Most successful companies run a hybrid strategy:
- Core platform: Build (the differentiating core)
- Horizontal services: Buy (auth, payments, email, monitoring)
- Business tools: Buy + configure (CRM, ERP, BI)
- Integration layer: Build (API gateway, middleware)
Conclusion
Build vs. buy is not a technical but a strategic decision. It doesn’t depend on your team’s capabilities (they can build anything) but on the question of where your company deploys its limited engineering resources most effectively. The answer is almost always: where your unique business value is created.