What to take away
Use standard software for standard work
Protect workflows that create advantage
Price the lifetime of workarounds, not only licence cost
Run a fit assessment before procurement
Start with operating fit, not features
Feature checklists make unlike systems look comparable. The better question is whether the software can represent your roles, approvals, commercial rules and data relationships without constant export, re-entry or exception handling.
A standard ERP is strongest when your process is mature, widely understood and close to the product's assumptions. Custom development becomes rational when important work is genuinely specialised or the cost of adapting people exceeds the cost of adapting software.
Three viable choices
Most companies are not choosing between only two extremes. They can adopt a standard product, configure and integrate a platform, or build a purpose-designed operational layer.
The right answer may be hybrid: keep commodity accounting or communication tools and build the workflow that differentiates the business.
- Standard product: fastest path when process fit is high
- Configured platform: useful when variation is rules-based
- Custom system: appropriate when workflows and data relationships are strategic
Calculate the cost nobody puts in the proposal
Licence and build estimates are visible. Workarounds are distributed across every employee and month. Count duplicate entry, spreadsheet reconciliation, delayed decisions, missed handoffs, shadow systems and dependency on one person who understands the workaround.
For custom software, include discovery, migration, adoption, maintenance and ownership. For standard software, include configuration, implementation partners, licence growth, integration and process compromise.
A decision test
Document the five workflows with the greatest effect on revenue, risk or customer experience. Ask each vendor to demonstrate those exact scenarios using your roles and exceptions.
Choose the option that produces the lowest long-term operating friction with acceptable delivery and ownership risk—not the one with the longest feature list.
Common questions
Is custom ERP always more expensive?+
The initial investment is usually higher than a simple subscription, but total cost depends on implementation, user count, integration and the ongoing workarounds a poor-fit system creates.
Can we start with standard software and customise later?+
Often yes, but confirm data access, APIs and extension limits before adoption. Some platforms make future integration straightforward; others make leaving or extending expensive.