Navigation

Explore Stratal

Infrastructure delivery. Under control.

Request a demonstration

Commercial & licensing

Enterprise licensing built around the way you deliver.

Stratal is commercially scoped around the operation being controlled — programmes, teams, modules, integrations and deployment requirements — rather than forcing infrastructure businesses into a generic software package.

For utilities, telecoms, fibre and civil infrastructure contractors. UK-based commercial discussions.

Proposal-led pricingClear commercial scope before commitment
Deployment alignedLicence follows the operating model
Procurement readyCommercial, security and rollout information
Designed to scaleFrom one programme to group-wide control

Licensing routes

A commercial model for each stage of adoption.

Start around a defined operational requirement or scope Stratal as the controlled operating environment across multiple teams and programmes.

Programme licence

Control a defined contract, programme or region.

For organisations that want to prove the Stratal operating model against a clearly bounded delivery scope.

Best suited toPilot, new contract or regional rollout
  • Defined users and operating teams
  • Selected Stratal modules
  • Configured workflows and permissions
  • Implementation and adoption plan
  • Route into broader licensing
Discuss programme licensing →

Enterprise agreement

Standardise control across programmes and business units.

For organisations adopting Stratal as a strategic operating platform across a larger delivery estate.

Best suited toMulti-programme or group-wide adoption
  • Enterprise operating scope
  • Multiple programmes or business units
  • Governance and access model
  • Integration and deployment planning
  • Commercial roadmap for expansion
Discuss an enterprise agreement →

Commercial scope

What determines the proposal.

Every proposal is built from the practical requirements of the deployment, so procurement can see what is being licensed and why.

01

Users & access

Internal users, field workforce, supervisors, management and any client or external access requirements.

02

Platform coverage

The Stratal modules and workflows needed across operations, planning, GIS, workforce, fleet, assurance, commercial and BI.

03

Operating footprint

The number of programmes, contracts, regions or operating units that will be controlled through the platform.

04

Data & integrations

Existing data migration, API requirements, SSO, external services and any controlled integration work.

05

Deployment model

Configuration, onboarding, phased rollout, training and the level of implementation support required.

06

Service requirements

Support expectations, governance, environments and any commercial or operational requirements agreed for the term.

Licence comparison

Compare the deployment routes.

The exact scope is confirmed in your commercial proposal. This comparison shows the typical operating shape of each route.

Commercial areaProgrammeOperatingEnterprise
Typical footprintDefined contract or regionMulti-team operationMulti-programme / group
Module scopeSelectedBroadEnterprise-wide
Field & management usersIncluded as scopedIncluded as scopedIncluded as scoped
Client / external accessOptionalAvailableAvailable
IntegrationsAs requiredPlanned scopeStrategic scope
Rollout governanceDefined pilot planOperational rolloutEnterprise roadmap
Commercial reviewAt expansion pointAt agreed reviewStrategic account review

Procurement & governance

A commercial conversation your procurement team can use.

Stratal can structure the evaluation around operational scope, deployment responsibilities and the information required for an internal buying decision.

Commercial proposalLicence scope, term and agreed commercial basis
Deployment scopeImplementation boundaries, responsibilities and rollout approach
Security informationSecurity, access and deployment information for review
Service definitionSupport and operational expectations aligned to the agreement

Buying process

From requirement to commercial scope.

A straightforward evaluation path designed for operational and procurement stakeholders.

  1. 01

    Discovery

    Review your delivery model, current systems, users and the operational issues Stratal needs to solve.

  2. 02

    Solution scope

    Confirm modules, workflows, integrations, deployment boundaries and the appropriate licensing route.

  3. 03

    Commercial proposal

    Receive a defined proposal covering the agreed licence and deployment scope for internal review.

  4. 04

    Deployment plan

    Agree mobilisation, configuration, onboarding and the controlled path into production.

Commercial questions

Common procurement questions.

Why does Stratal use proposal-led pricing?

Infrastructure operations vary significantly in user populations, module requirements, programmes, integrations and rollout needs. Proposal-led pricing keeps the commercial scope aligned to the operation being licensed rather than presenting a misleading one-size-fits-all figure.

Is Stratal priced only per user?

No. User volume forms part of the scope, but the commercial proposal can also reflect platform coverage, operating footprint, integrations, client access, deployment and service requirements.

Can procurement receive a detailed commercial breakdown?

Yes. The licensing conversation is intended to establish a defined scope that can be reviewed by operational, technical and procurement stakeholders before commitment.

Can we start with a pilot before wider licensing?

Yes. A suitable programme, contract or region can be used as a controlled first deployment where the objective is to validate the operating model before wider adoption.

Can Stratal support multi-programme or enterprise agreements?

Yes. Enterprise licensing can be scoped for organisations that need a consistent operating environment across multiple programmes, regions or business units.

How do we receive an exact price?

Request a commercial proposal with your approximate workforce, sector, operating footprint and main requirements. Stratal can then define the licensing and deployment scope required for a meaningful quotation.

Commercial proposal

Put a defined Stratal scope in front of your decision makers.

Tell us how your operation is structured and what you need to control. We will use that to shape the licensing conversation.