COMMERCIAL PATHWAY

From fit assessment to governed production

CONTROLTOWER OS is priced around the consequential pathway, deployment scope and assurance required — not tokens, generic API calls or user seats.

Engagement progresses through controlled commercial stages so that scope, evidence and execution boundaries remain explicit before production commitment.

Request a controlled discussion

CONTROLLED COMMERCIAL PROGRESSION

A defined route from initial fit to production scope

Each stage is bounded by the pathway, evidence, integrations, operating environment and assurance requirements agreed for that engagement.

  1. Stage 01Fixed fee

    Execution Control Fit Assessment

    €4,500 fixed

    One defined consequential AI-to-action pathway. Boundary identification, authority/control-condition assessment, current evidence/control review and written CTOS fit determination.

    • One defined consequential AI-to-action pathway
    • Boundary identification
    • Authority and control-condition assessment
    • Current evidence and control review
    • Written CONTROLTOWER OS fit determination
  2. Stage 02Bounded evaluation

    Controlled Evaluation

    From €9,500

    One bounded governed pathway; frozen proposition; defined evidence inputs; CONTROLTOWER OS governance conditions; controlled disposition logic; evidence preservation; written result and proof boundary.

    • One bounded governed pathway
    • Frozen proposition and defined evidence inputs
    • CONTROLTOWER OS governance conditions
    • Controlled disposition logic
    • Evidence preservation
    • Written result and proof boundary
  3. Stage 03Pre-production

    Governed Pilot

    From €30,000

    Customer-specific controlled pilot before production commitment, including scoped configuration/integration, governance controls, evidence handling, acceptance criteria, controlled testing and final pilot record.

    • Customer-specific controlled pilot
    • Scoped configuration and integration
    • Governance controls and evidence handling
    • Defined acceptance criteria
    • Controlled testing
    • Final pilot record
  4. Stage 04Annual production service

    Production Deployment

    From €60,000 annuallyImplementation from €15,000

    Annual enterprise CONTROLTOWER OS production service for an agreed production scope, including the governance, policy, evidence and execution-control capabilities required by that contracted scope, plus controlled change management and standard written support.

    • Agreed enterprise production scope
    • Governance and policy capabilities required by scope
    • Evidence and execution-control capabilities required by scope
    • Controlled change management
    • Standard written support
  5. Stage 05Complex / regulated

    Enterprise & Regulated

    Custom quotation

    Complex, multi-environment, regulated or high-consequence deployments involving enhanced security, assurance, integrations, governance or operating requirements.

    • Complex or multi-environment deployment
    • Regulated or high-consequence operating context
    • Enhanced security requirements
    • Enhanced assurance requirements
    • Additional integrations and governance requirements

PRICING BASIS

How CONTROLTOWER OS is priced

Commercial scope

CONTROLTOWER OS is not primarily priced by user seats, prompts, model tokens or generic API traffic. Commercial scope is determined by the governed consequential pathway, deployment complexity, required integrations, operating environment and assurance requirements.

External services

CONTROLTOWER OS fees cover the CONTROLTOWER OS service and contracted implementation scope. External model, audit, cloud, data or other third-party services are separate unless expressly included in a written quotation.

Where an external audit provider such as ViriSIM is used, its commercial relationship remains separate unless expressly agreed otherwise.

Evidence input boundary

External audit information is an evidence input. It is not automatically CONTROLTOWER OS authority for consequential progression.

Commercial qualification

Prices are stated in euro and exclude VAT, applicable taxes and third-party service charges unless expressly stated otherwise. Published prices are starting prices and do not constitute a binding quotation. Final fees depend on agreed scope, deployment complexity, integrations, assurance requirements and contractual terms. Payment does not itself satisfy technical, governance or production-acceptance requirements.

PROCUREMENT SUPPORT

What determines scope and what qualified buyers can request.

CONTROLTOWER OS pricing is shaped by the governed consequential pathway, deployment boundary, integrations, evidence and control requirements, assurance needs and contractual scope—not primarily by seats, tokens or prompts.

Scope drivers

Consequential pathway, required integrations, deployment environment, evidence controls, assurance obligations and contractual requirements.

Included CTOS scope

CONTROLTOWER OS service and the implementation scope expressly included in the written quotation or agreement.

Separate services

External model, audit, cloud, data and other third-party services remain separate unless expressly included in writing.

Enterprise materials

Qualified organisations can request appropriate commercial, trust, information-handling and technical-assurance material during controlled evaluation.

ENTERPRISE BUYER GUIDE

How to evaluate AI execution control.

Use these criteria when deciding whether an AI or automation pathway needs execution control, monitoring, audit, or a combination of controls.

Last reviewed: 6 September 2026

What is AI execution control?

AI execution control governs whether a machine-supported decision is permitted to progress into committed action. The control point sits between machine decision and operational consequence, before a workflow sends, approves, updates, dispatches, escalates or triggers a downstream system.

When should an enterprise consider it?

It is most relevant where an AI agent or automation can create operational, regulatory, financial or system-level consequence and a wrong progression cannot be treated as a routine reversible exception.

How is it different from monitoring or audit?

Monitoring observes behaviour and audit examines evidence or outcomes. Execution control determines whether progression is admissible before committed action. External audit evidence can inform the decision, but does not automatically establish authority to proceed.

When may monitoring or audit be sufficient?

Where output remains advisory, committed action is independently blocked by an existing control, consequence is low and reversible, or the primary requirement is observability, model assessment or post-event review, a separate execution-control layer may not be necessary.

What should buyers compare?

Permission boundaryCan the system prevent progression before action becomes real?
Authority separationAre evidence inputs kept distinct from the authority to proceed?
Enforcement timingDoes control operate before execution rather than only after the event?
Evidence and recoveryCan the organisation preserve the decision record, interruption state and controlled recovery path?
Deployment fitCan the control boundary be scoped to the actual workflow, integrations and consequential pathway?
Commercial scopeAre implementation, third-party services, assurance obligations and contractual boundaries explicit?

Is CONTROLTOWER OS priced per user, token or prompt?

No. Pricing primarily reflects the governed consequential pathway, deployment, integrations, evidence and control requirements, assurance needs and contractual scope.

How does an enterprise start?

The commercial route begins with a €4,500 fixed Fit Assessment, followed where appropriate by Controlled Evaluation from €9,500, Governed Pilot from €30,000 and Production Deployment from €60,000 annually plus implementation from €15,000.

Source and evidence context

For the public evidence boundary, review Evidence & Validation. For enterprise due diligence, review Trust & Assurance. For delivery method, review the Governed Pilot. For the contracting entity and disclosure posture, review Company.

REQUEST DISCUSSION

Define the pathway before defining the production commitment.

Use the existing controlled discussion route to identify the appropriate commercial stage and establish the scope that requires assessment.

Request Discussion