When SAP announced on 3 December 2011 that it would acquire SuccessFactors for $40 per share in cash — an enterprise value of roughly $3.4 billion and a 52% premium over the previous day's close — the immediate commentary focused on the price.[1] It was an enormous multiple for a company with a few hundred million dollars of revenue, paid by a vendor with a reputation for building rather than buying. The price was not the interesting part. The interesting part was the admission behind it. SAP had an HR product. SAP HCM was mature, deeply integrated with the ERP, installed in thousands of large enterprises, and generating substantial maintenance revenue. Paying billions for a smaller competitor's cloud offering was a public statement that the existing product could not be made into what customers now wanted — not on the timeline the market was setting.
Why HR Unbundled First
Of all the modules in the ERP suite, human capital management was the first to be pulled out and replaced with a separate cloud product. That was not an accident of vendor strategy. Five structural features made HR the natural entry point for best-of-breed cloud. The user population is everybody. Finance systems are used by finance. HR systems are used by every employee, for onboarding, leave, performance reviews, goals and expenses. When the whole workforce is a user, interface quality stops being a preference and becomes an adoption problem. Cloud HR products were designed for that audience; ERP HR modules were designed for HR administrators. The integration surface is narrow. HR connects to finance through a small number of well-defined interfaces — payroll postings, cost centre allocations, headcount. Compare that to attempting to detach inventory from procurement and manufacturing, where the data is continuously interdependent. HR could be lifted out with comparatively modest integration work. Talent management had become a competitive question. Recruiting, performance and succession were increasingly viewed as differentiating rather than administrative, and the functionality gap between specialist products and ERP modules in those areas was wide. Nobody selected an ERP for its applicant tracking. The buyer was not IT. HR leaders had their own budget and, increasingly, their own willingness to buy a SaaS product without a twelve-month IT programme. That changed the sales motion entirely and bypassed the incumbent's relationship. Regulatory change is constant and local. Employment law, payroll rules and reporting requirements change frequently and differently in every country. A cloud product that absorbs those changes centrally has a genuine structural advantage over an on-premise system requiring a patch and a test cycle in each country.
What Workday's Timing Proved
Nine months after the SuccessFactors deal, Workday filed for its IPO — founded by Dave Duffield and Aneel Bhusri, the people who had built PeopleSoft before Oracle acquired it, and built this time entirely for the cloud.[2] Workday's significance was not that it won every deal. Oracle's Fusion HCM was reported at the time to be winning a substantial number of deals per quarter, and the incumbents retained enormous installed bases. What mattered was the demonstration that a company with no ERP suite, no on-premise legacy and no transaction backbone could take the HR module out of large enterprises and run it independently. Once that was proven for HR, the question became obvious. If the suite could lose HR, what else could it lose? The answer, over the following decade, turned out to be: expenses, procurement, CRM, planning, service management, e-commerce, and eventually significant parts of financial reporting. The suite did not collapse. It did lose its assumption of completeness.
The Costs Nobody Priced Into the Business Case
Unbundling was sold on functionality and user experience. Both were real. The costs were also real and generally discovered later. Integration becomes a permanent operating function. Two systems means an interface, and an interface means ongoing maintenance, monitoring, exception handling and a recurring cost every time either vendor releases an update. Organizations that budgeted the integration as a project cost and not an operating cost were wrong by an order of magnitude over five years. Employee master data fragments. Two authoritative-looking lists of employees, cost centres and organizational structure. Which one is right on any given day becomes a genuine question, and reconciling them becomes somebody's monthly job. Cross-domain reporting gets harder. Headcount cost by project, labour variance, workforce planning against financial forecast — all straightforward in a single system, all requiring a data warehouse and a mapping layer once the data is split. Upgrade cycles stop aligning. The cloud vendor releases quarterly on their schedule. The ERP releases on another. Every combination has to work, and the testing burden is multiplicative rather than additive. Total cost frequently exceeds the suite. Two subscriptions, an integration platform, additional administration and a reporting layer. The unbundled architecture is usually better and it is rarely cheaper.
| Operating concern | Work created by unbundling |
|---|---|
| Interfaces | Ongoing monitoring, maintenance and exception handling |
| Shared entities | Name a system of record for employees, cost centres and positions |
| Cross-domain reporting | Plan the reporting layer and entity mappings |
| Release cycles | Retest the interface when either vendor changes |
| Local payroll | Account for country-specific calculation and statutory support |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
Practical Guidance for Suite Versus Best-of-Breed
- Decide which domains are differentiating and which are not. Best-of-breed is worth its integration cost where capability creates competitive advantage. Where a process is a commodity, integration simplicity usually wins.
- Cost the integration over five years, not as a project line. Build, monitor, maintain, handle exceptions, retest at every release on both sides. This number determines most best-of-breed decisions and it is almost always understated.
- Name the system of record for every shared entity before signing. Employee, cost centre, organizational unit, position. Ambiguity here produces reconciliation work indefinitely.
- Check the integration, not just the application, during selection. Ask for reference customers running the same ERP and talk to them about the interface rather than the product.
- Plan the reporting layer at the same time. Cross-domain questions become difficult the moment the data splits. Deciding how to answer them later means answering them badly for two years.
- Test the vendor's release cadence against your change capacity. A quarterly forced upgrade is a commitment of testing effort every quarter, permanently, from a team that has other work.
- Account for localisation properly in multi-country operations. A global product with weak local payroll and statutory support will be supplemented by local systems, which reintroduces exactly the fragmentation you were trying to avoid.
- Revisit the decision periodically. Suite vendors closed much of the capability gap over the following decade. A best-of-breed choice made on a 2014 comparison may no longer be the right answer.
What Happened Next: Re-Bundling
The incumbents did not accept unbundling passively. Oracle acquired Taleo and RightNow in the same period, SAP followed SuccessFactors with Ariba and later Concur and Qualtrics, and both rebuilt their suites as collections of acquired cloud products connected by integration layers of varying quality. The outcome is a market that is neither fully unbundled nor genuinely integrated. Most large organizations now run a suite plus several best-of-breed applications, with an integration platform holding the arrangement together and a data warehouse trying to reconcile the reporting. That is more capable than the 2010 suite and considerably more complex to operate.
The Payroll Exception, and the Gulf Version of It
One part of HR proved stubbornly resistant to global cloud products, and it matters a great deal in this region: payroll. Payroll is where global HCM meets non-negotiable local rules. In the UAE, the Wage Protection System requires salary payment through approved channels in a prescribed file format, and end-of-service gratuity is calculated under specific statutory rules that no global product handles natively. Saudi Arabia has its own WPS, GOSI contributions and Saudisation requirements that affect hiring decisions directly. Each GCC country differs. The standard regional architecture that emerged is a hybrid: a global HCM platform for core employee records, recruiting, performance and self-service, with a local payroll engine or an outsourced provider handling statutory calculation and filing. That works, and it means the integration discipline described above is not optional for organizations here — it is the architecture.
The Pattern Repeating
The unbundling logic that took HR out of the ERP suite is now operating on a different axis. AI-native applications are emerging that do one process very well — document processing, forecasting, contract review, customer service — and connect to whatever systems the organization already runs. The pitch is familiar: the incumbent's built-in capability is adequate but unremarkable, the specialist is substantially better, integration is straightforward. So are the trade-offs. Capability versus coherence, specialist depth versus a single version of the data, and an integration burden that is easy to underestimate at the point of purchase. The organizations that navigated 2012 well applied one test: is this domain differentiating enough to justify permanently operating another interface? That question has aged better than any vendor's architecture.
Common Questions
Why did SAP acquire SuccessFactors?
Because it needed a credible cloud HCM product quickly. SAP's existing on-premise HR module could not be rearchitected on the timeline the market demanded, and buying the capability for roughly $3.4 billion was faster than building it.
Why was HR the first ERP module to unbundle?
Because every employee uses it so interface quality drives adoption, its integration surface with finance is narrow, talent management had become competitively important, HR leaders controlled their own budgets, and constant local regulatory change favours a centrally maintained cloud product.
Is best-of-breed cheaper than a suite?
Usually not. Two subscriptions, an integration platform, additional administration and a separate reporting layer typically exceed the suite's cost. Best-of-breed is justified by capability in differentiating domains, not by price.
Why do global HCM platforms struggle with GCC payroll?
Because regional statutory requirements — UAE and Saudi wage protection systems, end-of-service gratuity calculations, GOSI contributions, Saudisation rules — are highly specific and change locally. Most organizations run global HCM for core HR alongside a local payroll engine or outsourced provider.
Navigate ERP Vendor Landscape — Outpace works out which parts of your suite are worth replacing, what the integration will really cost you, and where the answer is to stay put.