AX

Commercial orchestration · coming soon

From capability fit to a procurement path that works.

Once a capability fits, the hard part is rarely the technology. It is the licence, the services, the diligence and the procurement route — each owned by a different party. AI Exchange aims to carry context, evidence and attribution forward so that none of it has to restart from zero, without collapsing the parties into one.

Coming soonCommercial orchestration is a product direction, not yet an end-to-end transaction layer. This page says what it aims to ease, what already works, and what stays outside AI Exchange’s role.

Back to overview

What AI Exchange is — and is not

An orchestrator between the parties, never one of them.

AI Exchange is an orchestrator. It is not a seller of record, holds no funds and operates no payment rail. Licensing, implementation services, procurement, tax and payment remain the responsibility of the parties to each engagement. That is the same statement the Trust Center makes about the platform, and it is the frame for everything below.

Read it in the Trust Center

Whichever side you are on

Looking to buy?

Keep procurement on the route you already trust. Our intended model is to continue through your hyperscaler marketplace private-offer path — the vendor relationship, spend commitments and terms you already have — keeping the licence and the implementation services clearly separated, each contracted with the party that provides it.

Publishing a capability?

Your licence stays yours, on your terms. The exchange brings a qualified buyer, the evidence you attached, and the route the buyer can actually purchase through — and records your attribution for every engagement it originated.

Delivering the last mile?

Your services are contracted as yours — integration, adaptation, operations — separate from the licence they build on, attributed to you, and visible to a buyer who has already seen what the capability is and what remains to be done.

The friction we aim to reduce

Six places where a good fit stalls before it becomes a contract.

Each of these is a goal, stated as the problem it addresses. None of them is a promise that the work disappears; the aim is that it is not repeated.

  1. 01

    Software and services, muddled together

    A reusable core is a licence; the work to make it run in your context is a service. When the two arrive as one number from one party, neither can be evaluated or contracted properly. The aim: keep the reusable core and the implementation delta separate, each attributable to the party that provides it.

  2. 02

    Diligence, repeated for every vendor

    Security, legal and procurement each start their review from a blank questionnaire. The aim: evidence already attached to the capability — by class, with absence stated — can be carried forward as input to security, legal and procurement review, so the review starts from what is established rather than from nothing.

  3. 03

    The buyer’s procurement route is the route

    Enterprises buy through the routes their policies allow: a cloud-marketplace private offer, a reseller, a direct vendor contract. The aim: AI Exchange records the commercial intent and the references that connect the match to the contract, and never replaces the route.

  4. 04

    Cross-border, and partner to partner

    A builder in one country, an implementation partner in another, a buyer in a third — and no one knows who is accountable to whom. The aim: verified identities, a relationship intermediated through the exchange, and attribution recorded for each party’s part of the engagement.

  5. 05

    Confidentiality, on the buyer’s terms

    A need cannot be proposed against without saying something about it; saying too much exposes the organization. The aim: a sanitised brief in which the buyer decides what is disclosed — identity, budget range, integration topology, procurement route — and the exchange never widens what was authorised.

  6. 06

    What a builder shares before a contract

    Code, a specification or an architecture shared to qualify against a brief must not become someone else’s asset. The aim: ownership stays with the submitter, the material is used only for the stated purpose, and a positive result is not an award or a commitment.

How responsibilities stay separated

Every commercial responsibility has an owner, and it is not the exchange.

Licence of the reusable core
The builder or vendor who owns it
Implementation and support services
The builder, boutique or implementation partner who delivers them
Procurement and contracting
The buyer, through its approved route
Tax and invoicing
The parties to the contract, and the rail they use
Payment
The parties; where facilitation is used, a licensed payment partner — never AI Exchange holding funds
What the exchange holds
Context, evidence, attribution and the references that connect a match to what the parties agreed

Where this stands

Three lists, kept apart on purpose.

Available today

  • Discovery, fit assessment and evidence by class, for every published capability.
  • A sanitised brief that builders and partners propose against, and a buyer who selects.
  • A provider’s own commercial statements may appear in a capability’s page as the provider’s, never as AI Exchange’s price, offer or entitlement.
  • After selection, the parties contract outside the platform; the exchange records the match.

Designed direction

  • Structured commercial intent and attribution, recorded with the match rather than reconstructed later.
  • Continuation over the buyer’s external procurement rails, with the exchange keeping the references.
  • Where payment facilitation is used, the intended model is a licensed payment partner rather than AI Exchange holding funds. The target design may support release on agreed acceptance conditions.

Outside AI Exchange’s role

  • Seller or merchant of record.
  • Employer of record for anyone delivering the work.
  • Escrow provider, or any party that holds funds.
  • The runtime that operates the capability in your environment.

The first two lists change as the product does; the third is the posture the platform is built on. If a page ever says otherwise, the Trust Center is the record to check.

Talk to us

Does your procurement have a question this page does not answer?

Ask it. The questions reviewers bring are how this direction gets designed — and how the next statement gets written, with its source, or not at all.

Ask a question Start with a business problem