How is a Compsia engagement priced?

The installation is scoped as a fixed or milestone-based fee from the production perimeter, integration and control burden. Managed operation is a recurring fee based on usage, support, infrastructure and improvement needs. There is no universal public price card.

When is a paid blueprint required?

A deeper blueprint is used only when discovery cannot responsibly support a fixed build proposal. The agreed blueprint fee may be credited when the recommended build proceeds within the proposal validity period.

When does managed-operation billing begin?

The contract defines the acceptance or production milestone. Recurring operation should not begin merely because a prototype exists.

Design → build → launch → operate

From one business result to an accepted, operated system.

Compsia owns the complete delivery path: architecture, agents, automations, integrations, interfaces, controls, production testing, rollout and managed operation. The result and its operational perimeter come first.

Scoped quotationSystem-specific acceptanceUpdated 2026-08-24

Direct answer01

One offer.
Five accountable stages.

A customer buys a custom AI system integrated into its operations, accepted for production and managed after launch. Design, build, launch, operation and evidence-led expansion are stages of that single offer—not separate software packages.

The architecture may include deterministic automation, model-assisted tasks, agents, retrieval, user interfaces and approval paths. Compsia selects only the components required for the result.

01 · Design

Define the production perimeter.

Business result, baseline, owner, users, data, actions, controls, architecture, fallback and acceptance plan.

02 · Build

Implement the complete path.

Agents, automations, integrations, interfaces, rules, environments, documentation and the required operating evidence.

03 · Launch

Accept reality, not a demo.

Expected, ambiguous, access-boundary and failure cases; rollout; training; manual fallback; accepted residual limits.

04 · OperateRecurring managed service

Keep the system useful.

Monitor use, quality, cost, provider health, incidents and business measures. Maintain integrations, support users and change the system deliberately.

05 · Expand—or stopWritten change control

Let evidence govern scope.

A new result, business unit, data category, integration, support level or acceptance requirement is separately scoped. What does not earn its place is narrowed or retired.

Method proof02

The release record makes the claim testable.

This is the minimum structure Compsia expects for an action-capable production release. It is an illustrative method artifact, not evidence that an unnamed customer system has passed these gates.

Release identityRequired

Result, version and owners

Name the business result, operational perimeter, release version, environment, executive sponsor, system owner, users, approvers and incident owner.

Data pathRequired

Sources, providers and retention

Record data categories, authority, source and destination systems, provider regions, context copies, access scope, retention, export and verified deletion.

Action policyRequired

Permitted, gated and prohibited

List exact actions, identities, account scope, approval enforcement, confidence behaviour, idempotency, retry handling and manual fallback.

Acceptance evidenceRequired

Tests, limits and decision

Preserve expected, ambiguous, access-boundary and failure results; known limitations; customer corrections; final acceptance and the operating measures to review.

Commercial path03

Scope determines price.
Acceptance determines production.

Installation. A fixed or milestone-based design, build and launch fee reflects the perimeter, integration and data complexity, controls, testing, rollout and delivery risk.

Managed operation. A recurring fee reflects users and volume, provider cost, monitoring, support coverage, review effort and included improvement capacity. Skybridge access is included without an additional platform licence fee within the agreed limits.

Optional blueprint. If discovery cannot responsibly support a fixed proposal, a deeper design engagement maps the architecture, controls and acceptance plan first. It is not the flagship product or an automatic prerequisite.

Qualified when

Material and bounded

A meaningful consequence, named sponsor and owner, achievable access, credible timing and an expectation of implementation plus operation.

Not a fit when

Exploratory or licence-only

Generic AI exploration, a standalone platform request, unlimited custom development, no accountable owner or no evaluable result.

Customer provides

Access and decisions

Lawful source access, process truth, test accounts, users, security and procurement participation, timely acceptance and ownership of business decisions.