The main enabler is not AI writing code faster. It is AI lowering the cost and time of the whole cycle between an intention and an accepted advance: understanding the request, investigating, proposing, experimenting, building, verifying and preparing the next decision. That change may make it economically viable to offer smaller parcels of delivery.

Six capabilities, in causal order

1. From an incomplete intention to executable work. AI can help ask questions, examine existing systems, compare alternatives and produce a first specification or prototype. Repeating that human effort for every small demand used to cost more than the advance justified.
2. Cycles of attempt and correction. Agents can already use tools, change code, run tests and review their own attempt. That extends automation beyond procedures programmed in advance, although reliability still varies a lot with the task. METR
3. Useful information before committing to the whole build. Discovery, technical analysis and prototyping can become advances worth contracting on their own. The client can learn, pick a smaller version, move on to implementation or stop. AI did not invent paid discovery; the hypothesis is that it may make it affordable for more demands.
4. Evaluating and repeating with less waiting. Tests, explicit criteria and analysis of results can feed new correction cycles. Some passes may run autonomously; others will need specialist evaluation. The gain depends on the quality of that verification, not only on the speed of production.
5. Preserving and transferring context between executors. If intention, decisions, artifacts and delivery state are usable by people and agents, a demand can move through specialized resources without rebuilding everything at each handoff. That may make pools serving several demands viable, but the coordination cost has to be measured.
6. Lowering the cost of preparing the next offer and decision. After an advance, the service can update alternatives, risks, scope and price from what it learned. The client decides directly or delegates some decisions within set limits. Progressive commitment then stops requiring a heavy negotiation at every small step.

A factor that cuts across all six

The cost of using models has fallen sharply while their ability to carry out longer software tasks has advanced. That improves the economics of these cycles, but it does not show that any given operation is already profitable (Stanford AI Index,METR). Productivity results in real work are not uniform either: a controlled study found cases where experienced developers were slower with the AI tools of early 2025 (METR).

The claim, stated carefully

The model was not impossible two or five years ago. Staged delivery, shared specialists and outcome-based contracts already existed. What may be changing is the frontier of viability: how many demands can sustain, with acceptable quality and price, the whole cycle of learning, execution, evaluation and decision.

Software Delivery as a Service organizes that new capacity as a recurring consumption relationship. Stages, gates and pools are mechanisms to make it concrete, not the original cause of the change.

Read the full argument →