Custom system or standard software?
Choose between a platform, integration and custom development based on process, risk and total cost.
Standard software is usually the right starting point. Custom software makes sense when a core workflow creates competitive value, manual workarounds are expensive, or essential rules and integrations cannot be handled reliably.
Signs that it is time to act
- The platform needs spreadsheets beside it
- The process is central to business value
- Several systems lack one shared workflow
- Licensing grows faster than usefulness
A sensible way forward
Compare improving the current tool, connecting existing tools and building. Calculate five-year ownership including licences, implementation, support, change, migration and risk.
- 01
Describe the need
Document user, task, rules and outcome without choosing technology.
- 02
Test the market
Run critical flows with real data, not only sales demos.
- 03
Limit the custom scope
Build unique value and integrate commodity capabilities.
Make sure this is covered
- Critical workflows
- Integration and data ownership
- Five-year cost
- Support and vendor risk
- Export options
Common pitfalls
- Rebuilding commodity features
- Underestimating maintenance
- Ignoring exceptions during platform trials
Questions and answers
Is custom always more expensive?
It costs more initially but can cost less over time if it replaces large licences or substantial manual work. Calculate the actual case.
Can we combine both?
Yes. A focused custom layer around mature payment, email or accounting services is often the strongest approach.