ERP Suite or Best-of-Breed? Choosing Your Systems Strategy
Key takeaway
Use the suite for the functions where standard processes are fine — finance, procurement, core operations — and best-of-breed where the function is a competitive differentiator and the suite's module is visibly weaker. The decision is per function, not a single company-wide philosophy.
This debate is usually framed as a religious choice. In practice, almost every organisation of any size runs a hybrid, and the useful question is which functions belong where.
The case for the suite
- One data model — a customer or a product means the same thing everywhere, with no reconciliation.
- Integration between modules is the vendor's responsibility, including through upgrades.
- One contract, one support route, one set of credentials and access controls.
- Reporting across functions without building a warehouse first.
The case for best-of-breed
- Specialist products are usually years ahead of the equivalent suite module in the functions where they compete.
- You can replace one component without touching the rest of the estate.
- Faster to procure, faster to deploy, and often far better user experience — which drives adoption.
- Pricing that scales with the function you're using rather than with a whole-suite licence.
Decide function by function
- Is this function a source of competitive advantage, or is standard good enough? Differentiators justify specialists.
- How visibly weak is the suite module? Ask current users, not the vendor's demonstration.
- How much data must flow between this function and the core? Heavy, real-time coupling favours the suite.
- Who will own the integration, and do you have that capability in-house or on retainer?
Price the integration honestly
Best-of-breed strategies fail when the integration cost is treated as a footnote. Every connection is a build, plus ongoing maintenance as both ends release changes, plus a reconciliation process for when they disagree. Budget for an integration layer as a permanent capability rather than a one-off project — and recognise that the third and fourth specialist system cost more to connect than the first two, because the number of relationships grows faster than the number of systems.
A workable default
Suite for finance and the transactional core, specialists for the customer-facing and differentiating functions, and a deliberate integration layer between them with the suite as system of record for shared entities. That shape survives both vendor changes and growth, which is more than can be said for either purist position.