SaaS & AI: from technical debt to orchestration

Writing code is becoming almost free. A “thin wrapper” around a language model can be replicated in a matter of days, when it is not absorbed by the model provider itself. For a software vendor, the conclusion is clear: the AI feature is no longer a moat.

But this observation conceals another, more actionable one. If generating code costs almost nothing, then the real battle shifts to two fronts that most vendors neglect: clearing decades of technical debt to become modernisable again, and turning developers into orchestrators rather than replacing them. That is where, not in the umpteenth “AI” button, the transformation is won.

---

The productivity paradox: coding faster ≠ delivering faster

The data from spring 2026 is unambiguous: individual productivity is soaring, while value for the business does not follow.

• The individual gain does not convert into value for the business. The WRITER survey (April 2026, 2,400 respondents) shows individual productivity multiplied many times over, but only 29% of organisations draw significant ROI from generative AI (23% for agents) [1].
• Very few scale up. The KPMG Global AI Pulse Q1 2026 (2,110 business leaders) classifies only 11% of organisations as “AI leaders”, capable of operating agents and capturing their advantage [2].
• Failure comes from execution, not from the model. HCLTech (May 2026, 467 decision-makers at companies above $1 billion) anticipates that 43% of large AI initiatives will fail, for lack of ownership, trained users and integrated workflows [3].
• And the cost shifts downstream. The Faros “Acceleration Whiplash” telemetry (April 2026, 22,000 developers, 4,000+ teams) confirms it: throughput rises (epics per developer +66%), but bugs per developer climb by 54%, code churn by 861%, and 31.3% of pull requests are merged without review [4].
• Value follows a J-curve. The DORA report from Google Cloud (May 2026) models a “verification tax” and an “instability tax”: value falls before rising again, and a ROI of around 39% in the first year (with a return on investment in ~8 months for an organisation of 500 developers) arrives only with a redesign of the process, not with tooling alone [5].

The takeaway, anti-hype: the cost of writing code is collapsing; the cost of delivering reliable software is not. This is the 10-20-70 rule (BCG, 2026) applied to software: 10% technology, 20% data, 70% people and processes. Technology alone does not produce performance.

---

The real battle: technical debt, revealed and amplified by AI

AI is a merciless revealer. Plugged into a fragmented information system, it brings to light, at speed, the flaws in architecture and the lack of engineering discipline. And what is new in 2026 is that it manufactures debt as fast as it can clear it.

The empirical study “Debt Behind the AI Boom” (arXiv, 30 March 2026) analyses roughly 302,600 commits authenticated as AI-generated, across 6,299 repositories: the technical debt introduced by AI tends to accumulate rather than be corrected [6]. The +861% code churn measured by Faros is the operational trace of this. And the “Triple Debt” framework from Margaret-Anne Storey (March-April 2026) broadens the notion: to technical debt are now added a cognitive debt (no one any longer understands the code produced) and an intent debt (the gap between what the code does and what it was meant to do) [7].

For a vendor, six classic forms of debt directly block AI:

Type of debt	Blocking impact on AI
Architecture (coupled monoliths)	Impossible to insert AI services without destabilising the whole
Code (duplication, zero documentation)	Agents learn and propagate the bad practices
Process (no CI/CD)	Iteration and correction too slow
Infrastructure (legacy, no containers)	Neither the power nor the latency required
Security (archaic access rights)	Exfiltration risk, GDPR / AI Act non-compliance
Tests (low coverage)	Hallucinations and regressions shipped to production

To this is added the invisible twin, the data debt (dark data, duplicates, absence of a reference repository): an AI plugged into a contradictory database produces fragile and biased answers.

---

Ultracoding to the rescue of legacy, provided it is governed

Here is the decisive reversal: the AI that reveals the debt is also the best tool for eradicating it. Claude Opus 4.8 (Anthropic, 28 May 2026) reaches 88.6% on SWE-bench Verified and 69.2% on SWE-bench Pro; its maximum-effort mode, “ultracode”, pushes reasoning further and orchestrates a swarm of sub-agents in parallel. Above all, its central argument is not speed but reliability: around 4 times less likely to let a defect slip through [8], precisely the downstream cost (review, bugs, churn) that Faros quantifies.

In concrete terms, ultracoding and specialised agents finally make it possible to reverse-document a legacy estate (traversing millions of lines, reconstructing the business rules, mapping the dependencies), to isolate dead code, to accelerate refactoring, to generate non-regression tests and to secure the migration. Debt ceases to be an invisible ball and chain and becomes a measurable and steerable asset.

But this is the golden rule, and the whole lesson of the “Acceleration Whiplash”: this power has value only when governed. Without a control plan, ultracoding repays the old debt by creating a new one, faster. One never presumes the reliability of an agent: Plan → Execute → Verify, one measures it.

---

Modernising the foundations and prioritising by processes

The engine does not move without reliable fuel, nor without knowing where to apply it. On the data side, the target is an “AI-ready” platform: Data Fabric (integration and governance automated across silos) or Data Mesh (data treated as a product, under contracts, decentralised to the business domains). On the process side, one maps reality (because the declared version lies) through Process Mining on ERP/CRM traces, then prioritises through a value × effort matrix: two to four cases with high impact and low effort, and any project without ROI within less than 12 months is deferred. This is the discipline that separates the 11% of “AI leaders” from the 43% of initiatives that fail: not more AI, but AI where the ROI is incontestable.

---

The human pivot: from developer-producer to orchestrator

This is the heart of the matter, and the most poorly handled. When code generation becomes commoditised, the value of the developer does not disappear: it moves upward. The historical parallel is crystal clear: Dorothy Vaughan, at NASA at the turn of the 1960s, saw IBM computers destroy her task as a “human computer”; by learning FORTRAN, she became a pioneer and a leader.

Recent data validates the shift. The CodeSignal survey (April 2026, 450 engineers) shows that 91% already use agentic coding tools, and that 73% judge that non-adopters risk becoming uncompetitive: the profession explicitly moves “from coder to AI orchestrator” [9]. The BCG Henderson Institute (April 2026), across roughly 165 million jobs analysed, projects 50 to 55% of positions substantially transformed within two to three years, with a net effect: senior roles expand while junior roles contract, exactly the signature of an economy of orchestration and supervision [10].

The paradigm therefore shifts from producing code to critical supervision: scoping the intent, contextualising the outputs of the swarm of agents, validating reliability and compliance, arbitrating the architecture, keeping the stop rule. Three levers, in order:

1. Rewrite the narrative. Banish the “cost reduction” rhetoric (synonymous with fear of layoffs) in favour of augmentation: AI as an “exocortex” that absorbs the tedious mental load and gives back time for expertise.
2. Structure the cultural adoption (ADKAR model: Awareness, Desire, Knowledge, Ability, Reinforcement): involve developers from the scoping stage, rely on ambassadors, teach the limits (bias, hallucinations) as much as prompting, learn in a sandbox with no risk to production.
3. Move up a maturity level: from anecdotal use (summarisation, translation) to tactical use (semi-automation via dedicated assistants), then strategic (reinvention of entire swathes). This steering falls within strategic workforce planning; it is not left to the IT department alone.

---

Where the moat lies now

If functionality becomes commoditised, the defensible advantage shifts to five assets that your competitor’s model does not reproduce:

1. Proprietary data and network effects.
2. Distribution, the brand, the channel.
3. Deep integration into the customer’s workflow (switching costs).
4. Compliance and sovereignty: AI Act provider status, ISO/IEC 42001 certification.
5. Reliability in production: AgentOps, operated by developers turned orchestrators.

---

Business model and FinOps: do not bill at a loss

AI embedded in the product turns tokens into a cost of goods sold (COGS) that erodes the SaaS gross margin. The signal of June 2026 is clear: the phase of blind spending is over, value now takes precedence. Vendors are switching to usage-based pricing because the inference bill is becoming the line item that decides profitability (one major player consumed its annual AI budget in four months) [11]. And the order of magnitude of the problem is documented: the gross margin of AI products rises from 41% (2024) to 45% (2025), projected at 52% in 2026, that is, 23 to 33 points below the benchmark of a mature SaaS (75-85%), with inference already accounting for ~23% of revenue among B2B AI vendors in the scaling phase (ICONIQ, January 2026) [12].

To bill by usage without controlling the cost of inference is to bill at a loss. The lever: heterogeneous architecture (small specialised models by default, the frontier model reserved for difficult reasoning), aggressive caching, an LLM Gateway to measure the cost per request and per customer, and pricing aligned with cost.

---

Compliance as an advantage, not a constraint

Embedding AI makes the vendor a provider within the meaning of the AI Act (Article 50, applicable from 2 August 2026): informing the user that they are conversing with an AI, marking generated content in a machine-readable manner, disclosing deepfakes, with exceptions for standard assistive editing. Coupled with the ISO/IEC 42001 standard, compliance becomes a barrier with respect to large accounts, all the more so as the primary barrier cited by business leaders remains the security and confidentiality of data (75% in the KPMG Q1 2026) [2]. On sovereignty, EU law does not impose general localisation but rather safeguards (GDPR, Data Act); a sovereign framework (SecNumCloud) turns it into a moat of trust, decisive in the public sector, healthcare and finance.

---

The roadmap, in five phases

The MATIA Method™ frames the transformation over 12 months: 360° diagnostic (DORA metrics, audit of technical debt and data debt, AI Act exposure, team maturity) → Scoping (one internal case of clearing legacy through ultracoding + one product case, prioritised by value and effort) → Preparing the foundations (AI manifesto, Data Fabric/Mesh, LLM Gateway + FinOps, AgentOps control plan, AI Act register, sandboxes for developers) → Pilot deployments (measuring the net gain: coding time saved minus review time added, developers moving up towards orchestration) → Consolidation (industrialising AgentOps, aiming for ISO 42001, revising pricing, institutionalising the orchestrator role).

Every use case in production passes through the triptych Plan → Execute → Verify: one never presumes the reliability of an agent, one measures it.

---

In summary

When the feature no longer makes the moat, the winning vendor does not add “AI” buttons. It does two things that no one copies in a weekend: it clears its technical debt through ultracoding, without creating a new one, because it governs it; and it raises its developers to the rank of orchestrators. The figures of spring 2026 confirm it: individual productivity is soaring, but only those who rethink process, reliability and skills draw value from it. AI in the code is 10% of the matter. The 70% decide everything.

To build your roadmap and industrialise your AI use cases, see the MATIA Method™, the white paper “From POC to industrialisation” and the AI Express Audit & Roadmap.

---

Sources

1. WRITER (with Workplace Intelligence), “2026 AI Adoption in the Enterprise”, 7 April 2026, 2,400 respondents: 29% significant ROI (generative AI), 23% (agents).
2. KPMG International, “Global AI Pulse Survey, Q1 2026”, April 2026, 2,110 business leaders: 11% “AI leaders”; security and confidentiality = primary barrier (75%).
3. HCLTech, “AI Impact Imperatives 2026”, May 2026, 467 decision-makers (companies above $1 billion): 43% of AI initiatives judged doomed to fail.
4. Faros AI, “The AI Engineering Report 2026, The Acceleration Whiplash”, 12 April 2026, 22,000 developers / 4,000+ teams: bugs per developer +54%, code churn +861%, 31.3% of PRs without review.
5. Google Cloud (DORA team), “The ROI of AI-Assisted Software Development”, May 2026: J-curve, verification and instability tax; ~39% ROI in the first year, return in ~8 months.
6. Liu, Widyasari, Zhao, Lo et al. (SMU), “Debt Behind the AI Boom: A Large-Scale Empirical Study of AI-Generated Code in the Wild”, arXiv, 30 March 2026, ~302,600 AI commits across 6,299 repositories.
7. Margaret-Anne Storey, “From Technical Debt to Cognitive and Intent Debt”, arXiv / ACM Queue, March-April 2026: “Triple Debt” model.
8. Anthropic, “Claude Opus 4.8”, 28 May 2026: 88.6% SWE-bench Verified, 69.2% SWE-bench Pro, “ultracode” mode, reliability around 4×.
9. CodeSignal, survey on agentic coding, April 2026, 450 engineers: 91% use agentic tools, shift “coder → orchestrator”.
10. BCG Henderson Institute, “AI Will Reshape More Jobs Than It Replaces”, April 2026, ~165 million jobs: 50-55% transformed within 2-3 years; senior roles rising, junior roles falling.
11. CIO (Foundry), “The AI adoption spending spree is over. Time to focus on value”, 12 June 2026: tokens become a COGS, shift towards metered pricing.
12. ICONIQ Growth, “State of AI”, January 2026: gross margin of AI products (41%→45%→52%), inference ~23% of revenue among B2B AI vendors in scaling.

Regulation cited: Regulation (EU) 2024/1689 (AI Act), Article 50, transparency obligations applicable from 2 August 2026; ISO/IEC 42001; GDPR; Data Act (Reg. EU 2023/2854); SecNumCloud (ANSSI).