Engagement — Strategic AI Programs, Scoped to Your Objective

Xpdeep programs are not subscriptions. They are scoped engagements built around a specific operational, certification, or competitive objective in your business — designed, delivered, and operated in partnership with an implementation partner. The structure of each engagement reflects the scope and the criticality. There is no off-the-shelf tier, and no public price list, because there are no off-the-shelf engagements.

Request a program briefing Talk to our team

Three Modes of Engagement

Most programs map to one of three engagement modes, sized and structured around the customer's stage and objective.

Pilot Program

A scoped engagement to validate Xpdeep on a high-value use case. Typically three to six months. Covers natively explainable model design, KPI alignment, prescriptive engine, and a deployment-readiness assessment. The right entry point when a specific operational or certification objective needs to be validated before committing to scale.

Production Deployment

An end-to-end engagement to bring an Xpdeep program into operational production. Covers model architecture, training, governance integration, certification documentation generated during the lifecycle, operator-facing prescriptive interface, and post-deployment operation in collaboration with an implementation partner.

Multi-Year Strategic Program

Long-horizon engagement to deploy Xpdeep across multiple use cases, sites, or business units. Includes shared model architecture work, sector-specific operational redesign, ongoing optimization and re-certification. The mode for enterprises that have moved beyond proving the technology to embedding it as a structural component of operations.

Sovereign Deployment — On-Premise and Air-Gapped

Xpdeep supports fully on-premise and air-gapped deployment for defence, intelligence, national security, and regulated-industry contexts where data, models, and audit trails cannot leave customer infrastructure. The Sovereign track is a distinct procurement path with engagement structures shaped by the relevant national or sectoral compliance regime. Supported deployment patterns include MIL-STD, GxP, and national defence software assurance frameworks.

Discuss sovereign deployment

How Engagements Are Sized

Three factors set the structure of an Xpdeep engagement: the operational scope (one use case, multiple use cases, or systemic redesign), the criticality (regulated, mission-critical, or operationally consequential), and the implementation partner's role (whether the program is partner-delivered, jointly delivered, or Xpdeep-led).

Pricing reflects these dimensions and is structured in three components: a program design and delivery component (covering model architecture, training, certification artifacts), a platform component (covering Xpdeep Hub, governance infrastructure, and operational tooling), and a value-capture component on programs where Xpdeep deployment unlocks a quantifiable economic outcome (success fee tied to the documented OpEx reduction, throughput improvement, or asset-availability gain).

All three components are scoped jointly with the customer and the implementation partner during the briefing phase. There is no public list price because there is no standard engagement — the structure of each program reflects what the program is designed to achieve.

For Technical Evaluation

A limited-volume developer workspace is available for technical teams who want to evaluate the Xpdeep platform before initiating an engagement conversation. Self-serve, no commitment. Not a path to production deployment — production deployments are program-scoped.

Request developer access

Every Xpdeep program is scoped around a specific objective. The right next step is a briefing — typically a 60-minute conversation with our team and, where relevant, the implementation partner already working in your sector. We come prepared; we send a written program scope after the conversation.