Spin, Embed, or Buy?
The Three Playbooks Technology Services Companies Are Quietly Using to Chase IP Productization and Services‑as‑Software.
She spent fifteen years building the technology services delivery pyramid that now sits in her way.
The agentic AI platforms launching right now (from pure-play startups with nothing to cannibalize, from hyperscalers and platform incumbents with captive distribution, and from frontier model providers building domain agents to move into the services layer) are selling performance and outcomes at a fraction of the cost of her delivery pyramid. Her clients are running the numbers. Some have stopped scheduling the QBR.
She has options. Her board calls them “the Services-as-Software platform opportunity.” She knows they are three different wagers on what her organization is capable of. Most firms narrate one and run another. There is a default. She doesn’t know it yet. That clarity is still ahead of her.
This essay is about that honesty.
OldCo vs. NewCo: The Gap
Before the playbooks, a precise understanding of the gap.
Business outcomes that used to be delivered primarily through bespoke human professional services are now codified into software platforms, AI agents + human delivery mechanisms, and automated workflows, sold on a recurring or outcome basis, and continuously improved through data feedback
OldCo, the typical technology services firm today, runs on billable headcount. Employee costs consume 54–58% of operating income. EBIT margins cluster at 15–25%, structurally capped because more revenue requires more people. A revenue-per-employee number that has not moved meaningfully in a decade, despite years of automation investment and internal AI platform development. Platforms like Accenture SynOps and TCS Cognix exist as internal tools and improve delivery efficiency. They are not sold as standalone products. They are OldCo getting marginally better at being OldCo.
NewCo, a genuine Services-as-Software business, runs on ARR, NRR, gross margin expansion, and cost-per-outcome. Its talent mix inverts OldCo’s: roughly 60% product and engineering, 30% domain and delivery, 10% sales and customer success. Revenue per employee is not a ceiling. It is a variable that rises as the platform scales, because the marginal cost of serving the next customer approaches zero while the marginal value of the accumulated operational data approaches infinity.
Seven criteria define whether a technology services business has actually made the transition to a Services-as-Software business:
The distance between OldCo and a business that meets all seven criteria is not primarily a technology problem. The distance is organizational, commercial, and structural. The three playbooks are three different answers to the same question: what actually stops transformation, and how do you get around it?
One framing clarifies the stakes: call this the Vertically Integrated Services bet. Start as a services company, then build or buy software platforms to radically transform the P&L.
Pull it off, and a mediocre services business crystallizes into a software-services hybrid with expanding gross margins, growing reinvestment capacity, and a defensible data moat. Miss, and the outcome is permanent: an undifferentiated, capital-intensive services asset with no path to non-linear economics. There is no partial credit.
The three playbooks are three different mechanisms for attempting the same bet.
Playbook 1 – Embed & Evolve: “We can transform the core from within”
The Embed & Evolve thesis is appealing in its elegance: don’t fracture the organization. Embed AI and platform economics into every service line simultaneously. Redefine KPIs across the firm. Retrain the workforce. Shift commercial models deal-by-deal. No NewCo. No brand confusion. No organizational civil war between OldCo and a competing internal entity.
The strongest proof point is in banking
DBS Bank executed this successfully, and its transformation is among the most studied and most misread case studies in enterprise technology.
In 2014, CEO Piyush Gupta made a specific decision: no separate digital bank. He would transform the whole institution. The mechanism: 33 technology platforms rebuilt from the ground up; a “2-in-a-box” leadership model pairing every business head with a technologist counterpart; 60-plus customer journeys redesigned from customer backwards rather than system forwards. No ring-fenced lab. No innovation theater. The bank became the digital unit.
Why It Fails
DBS had three things that almost no technology services company has simultaneously.
A decade-tenured CEO with complete board alignment. Gupta has been in the chair since 2009. He did not manage the transformation by consensus. He decided and executed. The average technology services CEO tenure is four to six years. That is not enough runway for Embed & Evolve, which requires sustained, consistent pressure against every organizational incentive that pulls toward the status quo.
A relatively homogeneous core product. Banking services are banking services. DBS was improving the delivery of a stable product set, not dismantling and rebuilding what it sold. Technology services companies typically span twenty or more service lines with different clients, different competitive dynamics, and different degrees of platform readiness. The coherence requirement scales with complexity, and at that complexity it exceeds most leadership teams’ capacity.
A culture that could be induced to self-cannibalize. Partner compensation in technology services is built around revenue attribution. Asking a partner to shrink their attributed FTE revenue in order to grow a platform P&L they don’t control requires institutional altruism that partner incentive structures actively punish. DBS had employment-based compensation, not partner-model attribution. That difference matters more than most analyses acknowledge.
Clayton Christensen’s core insight applies here with precision: the resource-allocation process of a successful incumbent systematically defunds initiatives that cannot meet the profitability thresholds of the existing model. Every quarter in a technology services firm, utilization must hit 80%, the bench must be filled, and the $30M SAP deal must be staffed. Every quarter, the platform initiative loses that fight.
In technology services, Accenture is making the equivalent bet. June 2025: CEO Julie Sweet collapsed five business units into a single entity called “Reinvention Services.” No structural separation. No NewCo. In October 2025, it went further: appointing its first-ever Chief Offerings and Products Officer, mandated to productize offerings and embed AI into every engagement. A CPO inside a $70 billion technology services firm is an organizational declaration that product economics now require a dedicated C-suite owner. Whether Accenture can hold the coherence that Embed & Evolve demands is still the test.
The honest verdict: Embed & Evolve works if you have a decade-tenured CEO, exceptional board alignment, a relatively homogeneous product set, and a compensation model that can actually reward self-cannibalization. For most technology services companies, at least two of those four conditions are absent. When they are absent, Embed & Evolve becomes a sophisticated cover story for incremental improvement.
Playbook 2 – Disintegrate → Operate → Integrate: “Create the NewCo you intend to be eaten by”
If the immune system will kill the new model, give the new model a separate body. But if you only separate, you have two companies rather than a transformed one. The point is not independence. It is gravity shift. D→O→I is a staged sequence designed to create a protected space where new economics can develop, prove themselves through real commercial discipline, and then pull the center of the whole firm toward them.
The Three Phases
Phase 1: Disintegrate. Carve a new entity with a separate P&L, its own leadership, distinct metrics (ARR, NRR, gross margin, not utilization and bill rates), its own talent brand, and genuine commercial autonomy. NewCo’s charter: build services-as-software products, including verticalized agent platforms, outcome-priced workflow bundles, and domain-specific AI services. The legal structure can vary: a full spinoff, a joint venture with external investors, or at minimum a ring-fenced business unit with protected multi-year capital. What it cannot be is virtual. A virtual NewCo with shared leadership and shared metrics is a cost center with a rebrand.
Phase 2: Operate. OldCo becomes a paying customer of NewCo. The structural architecture is Hub-and-Spoke: NewCo is the hub, owning the platform, the IP, and the data learning loop; OldCo’s service lines are the spokes, embedding NewCo’s capabilities into client engagements and providing the domain expertise and change management that the platform cannot supply alone. Transfer pricing is at arm’s length. NewCo charges OldCo the same rates it would charge any external client, minus a modest internal discount. This is not a courtesy arrangement. It is a commercial forcing function. If OldCo won’t pay a real price for NewCo’s platform, it means NewCo hasn’t built something worth buying. Internal subsidy produces internal tools. Arm’s-length pricing produces products.
Phase 3: Integrate. When NewCo’s economics clear the thresholds (ARR exceeding 20–25% of combined revenue, gross margins above 40%, platform adoption across a majority of major client engagements) you shift the firm’s center of gravity toward the NewCo model. Integration at this stage is more economic and cultural than legal. The firm’s identity, talent investment, go-to-market, and capital allocation all reorient toward platform-delivered outcomes. FTE-based work doesn’t disappear. It becomes the supporting layer: the human judgment, domain expertise, and exception handling that the platform’s learning loop depends on to stay defensible.
The Precedents
IBM’s 2021 spinoff of Kyndryl offers a technology services example of benefits of full seperation. Kyndryl entered independence with operating margins around 15.6%, weighed down by unprofitable long-term contracts and the governance friction of operating inside a parent with different strategic priorities. Three years post-separation: margins expanded toward 18.8%. Not because the underlying work changed, but because Kyndryl had permissions IBM would never grant. It fired unprofitable clients. It became hyperscaler-agnostic, signing partnerships with AWS, Microsoft, and Google that were structurally impossible inside a company selling its own cloud. Full separation created the conditions for margin discipline that protected separation had consistently prevented.
The construction industry offers a structural template that maps more precisely to this playbook than any tech analogy. Construction ownership transitions: a NewCo takes on new contracts while OldCo provides labor, equipment, and bonding via lease arrangements; profit shifts from OldCo to NewCo over five to seven years; if NewCo succeeds, it absorbs OldCo’s assets and capabilities. If it stumbles, OldCo’s assets remain protected. Replace “construction equipment” with “client relationships and delivery workforce” and the template is almost exact.
Why It Fails
Cannibalization paralysis. OldCo leaders resist routing revenue through NewCo because it shrinks their attributed P&L. Without explicit incentive redesign (rewarding OldCo leaders for total client value, not just FTE-based revenue) this quietly kills the Operate phase.
Capital drain without patience. NewCo burns cash for three to five years before breakeven. Public services companies with quarterly earnings pressure discover that the CFO’s patience is shorter than the timeline requires.
Atos as the cautionary tale. Atos’s attempted separation of Tech Foundations from Eviden happened from a position of severe financial stress. Debt levels made asset sales structurally difficult. The separation dragged, the debt ballooned, and the firm spent years fighting for survival. The lesson is brutal: D→O→I requires strength. It cannot be the answer to financial distress.
Integration timing. Integrate too early and OldCo reabsorbs NewCo, defaulting to FTE pricing. Integrate too late and NewCo develops its own identity and resists. The ARR and gross margin thresholds are guideposts, not formulas. This remains a judgment call.
The honest verdict: D→O→I is the most structurally honest playbook for most technology services companies, because it is the most honest about organizational physics. It does not assume the core will self-cannibalize. It does not assume an acquisition will be protected. It creates a structure designed to force the behaviors that culture cannot be trusted to generate. But it requires a CEO with a seven-plus year horizon, ring-fenced capital, explicit cannibalization incentives, and the discipline to not integrate before the thresholds are real.
Playbook 3 – Acquire & Protect: “Buy the non‑linear economics”
If building product DNA organically takes too long and transforming the core culture is too hard, buy a company that already has both, and protect it from the immune system that will immediately try to absorb it.
The Canonical Examples
Cognizant’s 2014 acquisition of TriZetto for $2.7 billion is the case study. TriZetto managed healthcare benefits administration for roughly 180 million covered lives, half the insured US population. At acquisition: approximately $700 million in trailing revenue, EBITDA north of $190 million, deep clinical and administrative domain data that no new entrant could replicate on any reasonable timeline. Cognizant kept TriZetto semi-autonomous within its healthcare practice. Product leadership retained. Engineering culture retained. Software-centric metrics retained. Cognizant wrapped its services distribution around TriZetto’s platforms and projected $1.5 billion in cumulative revenue synergies over five years.
The explicit goal was non-linear software revenue attached to a domain-defensible platform. The distribution flywheel worked because Cognizant’s healthcare client relationships were deep enough to accelerate adoption of a platform that already had proven unit economics.
Accenture Song is the second instructive example. Accenture Interactive, founded in 2009, spent thirteen years running a disciplined Acquire & Protect strategy: buying creative and experience agencies (Droga5 in 2019 being the largest and most notable) to accumulate brand, design, and creative DNA that its consulting culture could not generate organically. For years it protected individual agency identities and kept acquired leadership intact. The strategy worked. By the time Accenture rebranded the practice as Song in 2022, it had assembled the world’s largest creative agency network inside a technology services firm.
The Three Conditions
Three conditions must hold simultaneously for Acquire & Protect to work.
Genuine product-market fit, not just interesting tech. The acquired company has paying customers, measurable unit economics, and a product roadmap driven by market demand. Platforms with genuine penetration come with the operational data and learning loops that make domain defensibility real. If the technology has never competed for an external budget and won, it has not been tested.
Genuine operational autonomy. Separate leadership. Separate P&L. Separate engineering cadence. The acquisition target keeps its soul, its compensation structure, and its hiring standards. The moment the acquired company’s product roadmap becomes subject to OldCo’s governance calendar, the acquisition begins dying.
A real distribution flywheel. OldCo’s sales force can cross-sell the acquired platform into existing accounts, and the sales team is compensated for platform signings at rates comparable to services signings. Without this, you have paid a software premium for a business you will run as a services business.
Why It Fails
The failure mode here is well-documented and consistent: the mothership absorbs the acquisition. The acquirer imposes its governance cadence: quarterly reviews, utilization targets, partner approval gates. The acquired company’s best engineers leave when they realize they are now in a consulting company. The product roadmap gets colonized by bespoke client requests. Within three to five years, the platform is a tool, not a product.
The honest verdict: Acquire & Protect is the fastest path to non-linear economics. It is also the most fragile, because it depends entirely on a discipline (leaving the acquisition alone) that every process and incentive inside a services firm works against. The acquisition is worth more the less you integrate it. The more you integrate, the more you destroy what you paid for. Most services firms cannot hold that discipline for five years. The ones that can are worth studying.
The Diagnostic: Which Play Are You Actually Running?
Three playbooks. Three bets on organizational reality. The diagnostic is not which box you want to occupy. It is which box your incentive structure, your capital allocation, and your governance calendar are actually putting you in.
Strip away the language in the strategy deck and ask three questions:
Where is the new model’s capital coming from? If it is competing quarterly for budget against utilization-driven P&Ls, you are running Embed & Evolve regardless of what you call it.
Who owns the platform roadmap? If the answer involves account leaders, partner committees, or client escalation paths, you are building a delivery tool, not a product, regardless of whether you have a NewCo on the org chart.
How are OldCo leaders compensated when FTE revenue shifts to platform revenue? If they are penalized, the transformation will not happen. The incentive structure is the strategy.
In the next essay of this series, Two Machines Cannot Share One Throttle, I step out of the neutral analyst role and build the comparison framework, makes the explicit case for D→O→I as the default starting position, and examine the counterintuitive signals that reveal whether a transformation is compounding or quietly decaying.
Get no-fluff signals on enterprise software, AI, and professional services by subscribing to Digital Faultlines.