Postmodern ERP
Postmodern ERP is the architecture concept popularised by Gartner from 2014 onwards: a smaller core ERP (financials, basic operations) integrated with specialist best-of-breed applications for HR, CRM, e-commerce, supply chain, expense management and other functions. Postmodern ERP rejects the monolithic-suite paradigm where one vendor provides everything in favour of a composable architecture where each domain runs the best tool available, connected through APIs and integration platforms.
The postmodern ERP concept
Three driving forces produced postmodern ERP. (1) Specialist excellence: dedicated Salesforce CRM, Workday HCM, NetSuite ERP, Coupa procurement, ServiceNow ITSM each outperform the equivalent modules in monolithic ERP suites in their specific domain. (2) Cloud-native delivery: specialist SaaS vendors reach faster innovation cycles than monolithic suite vendors burdened by backward compatibility. (3) API standardisation: well-documented APIs make multi-vendor integration practical without the ESB-era integration cost. Postmodern ERP architectures typically run a smaller ERP core (often SAP S/4HANA Cloud, Microsoft Dynamics 365 F&O or Oracle Cloud ERP) for financials and core operations, plus 5-20 specialist applications integrated through iPaaS for the remaining functions.
Typical postmodern stack
- Core ERP (financials, core operations) — SAP, Microsoft Dynamics 365, Oracle, NetSuite, weclapp
- CRM — Salesforce, HubSpot, Microsoft Dynamics 365 Sales
- HCM — Workday, SAP SuccessFactors, Personio (DACH SMB)
- Procurement and source-to-pay — Coupa, SAP Ariba, Ivalua, JAGGAER
- Expense management — SAP Concur, Pleo, Spendesk
- E-commerce — Shopify Plus, Shopware, commercetools, Salesforce Commerce
- Supply chain visibility — project44, FourKites, Transporeon
- PIM — Akeneo, Pimcore, Contentserv
- Treasury — Kyriba, Cashforce, HighRadius
- BI and analytics — Power BI, Tableau, Qlik plus data-warehouse infrastructure
Benefits and trade-offs
Benefits: best-in-class capability in each domain, faster innovation cycles, easier replacement of individual components, vendor-lock-in reduced. Trade-offs: integration complexity higher, operational responsibility scattered across more vendors, data-master ownership requires careful governance, total subscription cost often higher than monolithic suite, user-experience inconsistencies between systems. The trade-offs are real, not just marketing. Mid-market in DACH typically lands at moderate postmodern: 5-10 specialist systems beyond the ERP core, with disciplined integration architecture. Pure-postmodern with 20+ specialist apps requires enterprise-grade integration team and governance — valuable at large scale, expensive at mid-market scale.
DACH practical adoption
DACH mid-market adoption of postmodern ERP follows a typical pattern. Around the ERP core (often SAP S/4HANA for upper mid-market, Business Central or NetSuite for lower mid-market), specialist systems gradually replace ERP-native modules where the business case justifies it. Most common first replacements: CRM (Salesforce or HubSpot replacing ERP-CRM), HCM (Personio or SuccessFactors replacing ERP-HR), expense management (Concur, Pleo replacing ERP-T&E), e-commerce (Shopify, Shopware integrating with ERP rather than ERP-native e-commerce). The pace of adoption accelerated during 2020-2024 with cloud-first IT strategies and the general maturity of integration platforms.
Related Topics
Frequently Asked Questions
How many specialist systems is too many?
Above 30-50 connected systems, integration overhead and master-data drift typically exceed the benefits. The right number depends on integration capability, governance discipline and organisational complexity. Mid-market organisations typically operate well with 10-20 specialist systems plus the ERP core; larger enterprises operate 30-100 systems with dedicated integration teams.
Is postmodern ERP cheaper than monolithic suite?
Often not, in pure subscription terms. Multiple best-of-breed subscriptions add up. The cost case for postmodern is qualitative: better fit in each domain, faster innovation, reduced vendor lock-in. Mid-market organisations evaluating both should compare 5-year TCO carefully.
How does postmodern ERP relate to composable enterprise?
Postmodern ERP is the application-layer expression of the broader composable-enterprise vision. Composable enterprise applies the same principle (best-of-breed components composed flexibly) at all architectural layers — data, integration, identity, application. The underlying philosophy is shared; postmodern ERP focuses specifically on the application portfolio.