Why does enterprise delivery stop scaling?

What history suggests

• Delivery work that scales with revenue tends to cap growth before sales capacity does.
• Standardizing the product and standardizing the deployment are separate problems, and the research shows companies that solved one while the other stayed bespoke.
• Complexity is rarely removed. It usually moves, into the product, into the customer, or into a services layer, and the choice of location changes the economics more than the total volume of work.
• A service becomes product-like when the variable parts are narrowed to a known set of options, not when the work stops varying.
• Where software takes over the operating steps, the delivery burden shifts rather than disappears, toward configuration, exception handling, and oversight.

What changes the answer

Conditions and contexts where the evidence differs.

• Where variation can be narrowed to a defined option set, productizing changes the cost curve. Where it cannot, productizing relocates cost rather than reducing it.
• Automation does not settle the question. When software runs the operating steps, the work reappears as configuration, exceptions, and oversight.
• Two companies carrying the same volume of delivery work can hit different limits, because the placement of complexity, not its quantity, drives the economics.

What to look at in your business

Practical application, not historical finding.

• Delivery hours per unit of revenue, tracked as a curve over time rather than a single figure.
• What share of implementations required work outside the defined option set?
• Where does complexity currently sit, in the product, the customer, or services, and is that placement priced?
• How much of the delivery team's time goes to exceptions versus new deployments?
• Is sales capacity or delivery capacity the binding constraint this quarter?
• Which bespoke steps have now recurred often enough to become standard options?
• After automating a delivery step, did total delivery hours fall or move?

Core evidence

• Fieldwork / 011When Internal Implementation Scales, and When It BreaksWhen internal implementation capacity scales with revenue and when it breaks.PDF
• Fieldwork / 023Where Should Customer Complexity Live?Where customer complexity can be placed, and what each placement costs.PDF
• Fieldwork / 026When Does a Service Become a Product?What has to change for a service to behave like a product.PDF
• Fieldwork / 040Can Enterprise Software Scale Without Making the Deployment Standard?Whether enterprise software can scale while deployments stay non-standard.PDF