Deployment and markets

This is not an eleventh layer. It is the commercial system that surrounds the ten technical ones and decides whether any of their capability becomes an adopted workflow, a measured outcome and a return. It sits beside the physical map, not above it — and a product can be technically available and commercially undeployable for reasons that have nothing to do with whether it works.

What this section answers

Who buys the system. Which business problem it solves. Who integrates and operates it. Who carries implementation and liability risk. How value is measured and monetised. And, separately from all of that, who captures the economic surplus — because a technically essential supplier can capture very little, and an integrator who invented none of the technology can capture a great deal.

1 · The adoption pipeline

Eleven stages between a customer problem and a renewal. Technical readiness gets a deployment to about stage three; everything after that is integration, approval and change management.

    2 · Buyer and stakeholder map

    The buyer is not always the beneficiary, and the beneficiary is not always the person affected. Seven roles with genuinely different incentives, any of which can stop a deployment.

    3 · End markets

    Fifteen markets with different regulatory gates, integration costs and willingness to pay. They are listed in rough order of how quickly capability has converted into deployment, not by size.

    4 · Systems integrators and the channel

    The participants that turn a product into a working deployment. Most of them are not technology companies, and in physical markets they capture more of the value than the vendors do.

    Who is actually in the value chain

    Consultants and engineering firms; systems integrators; managed-service providers; distributors and channel partners; industry-specific software providers; robot integrators and automation specialists; training and change-management providers; certification, testing and audit organisations; insurers and financiers; and maintenance, repair and lifecycle-service providers.

    None of these appear in the ten technical layers, and no deployment at scale happens without several of them. Their margin comes out of the same customer budget as the vendor's.

    5 · Business models

    Eleven ways the same capability gets sold. The model chosen decides what the vendor is exposed to far more than the technology does.

    6 · Unit economics and return

    What has to be measured before a deployment can be called economic. Deployment and integration costs are the lines most often under-counted.

    Additionally, for embodied systems

      7 · Regulation, safety and liability

      The gate that decides which markets open, and in what order.

      Three separate questions, routinely merged

      Is it permitted? Sector regulation — medical device approval, financial supervision, automotive type approval, aviation certification. Is it safe enough to deploy here? A safety case for this specific installation, which is site work rather than product work. Who pays when it is wrong? Liability allocation between vendor, integrator, operator and insurer, which is unsettled in most markets and will determine which business models are viable in several of them.

      A capability can clear the first and fail the third. Insurance pricing can remove a technology from a market without any regulator banning it.

      8 · Operation, maintenance and lifecycle

      What happens after the deployment, which is where most of the lifetime cost and most of the durable revenue both sit.

      The part that is not a launch

      Monitoring and support; incident response; exception handling by people; spares, repair and refurbishment; recalibration and requalification after any change; software and model updates, staged and reversible; retraining of staff as procedures change; and eventually replacement, resale or disposal. For physical systems the maintenance line is higher in year three than in year one, and it is the line that decides whether a leasing or as-a-service structure works at all.

      9 · Value capture by layer

      Where the surplus lands. Technical necessity and pricing power are different properties, and this is the distinction the whole report is built to make.

        10 · Investment implications

        What follows from the sections above, stated as claims that can be argued with.

        Claims this section refuses to make

          Each is common, each is convenient, and each fails on contact with an actual deployment. Market sizing built by multiplying jobs or wages by an assumed automation percentage is the most persistent of them, and it is not a method.

          Every market-size and productivity claim in this section is deliberately qualitative. A defensible one would need the use case, customer, geography, adoption rate, price, implementation cost, time horizon and source stated together — and where this report cannot state all of those, it does not give a number.