How organisations engage with ActivityExchange
ActivityExchange is adopted as delivery infrastructure. Pricing reflects the scope, risk, and lifecycle complexity of the programme it supports — not a per-seat tariff applied to a generic tool.
Why we don't publish a price list
The platform is deployed into engineering programmes that vary widely in scale, regulatory exposure, contractor structure, and lifecycle horizon. A published per-user figure would either understate the configuration and assurance work involved, or overstate it for smaller scoped deployments. Neither is useful. Instead, we structure each engagement around what the programme actually requires, and we are transparent about the components that make it up.
The engagement model
Three components, applied in sequence, sized to the programme.
Annual platform licences
Licensing is established at the organisation or programme level and reflects the scale and lifecycle scope of the assets being managed. Renewal aligns with the delivery horizon, not an arbitrary calendar reset.
Project setup and configuration
Each programme is configured against its own model structure, disciplines, workflows, and assurance requirements. This is a deliberate phase, not a self-service exercise, and it is the work that makes the platform fit your delivery context rather than the other way around.
Enablement and delivery support
Engineering and field teams are supported through onboarding and into live delivery, with continued involvement from people who understand both the platform and the delivery context. Support scales with programme intensity.
What shapes the commercial conversation
These are the factors we work through with you to size an engagement honestly.
Programme scope
Number of assets, systems, and disciplines in scope, and the depth of the model structure being managed.
Lifecycle horizon
Whether the platform supports delivery only, or continues into handover, operations, and brownfield modifications.
Assurance & regulation
The level of traceability, audit, and compliance evidence the programme is required to produce and preserve.
Contractor & team structure
How many organisations contribute to the work, and how their access, workflows, and approvals are partitioned.
Integration footprint
What upstream and downstream systems the platform must exchange information with, and at what cadence.
Enablement intensity
The level of hands-on onboarding, training, and in-flight support your delivery teams need to operate confidently.
Pilots and scoped deployments
Pilots and scoped deployments are normal and expected as part of evaluating fit. We would rather have a substantive conversation about your delivery environment than publish a figure that misrepresents the work involved. If a smaller, time-boxed deployment is the right way for your organisation to assess the platform, we will scope it on that basis.
Let's scope an engagement that reflects your programme.
Tell us about your delivery environment and we will come back with a structured proposal — not a generic quote.