Co-development

Two airports, not two customers.

TAM is in MVP. That is a fact, not a disclaimer: the applications are built and running, and what remains is the hardest part of any operational platform, which is meeting two real estates and surviving contact with them. We are looking for the two airports that shape general availability.

Start the conversation See what is built

The two profiles

Chosen for contrast, on purpose.

Two airports that could not be more different, because a product that only works at one of them is not a product.

A small airport that runs everything in house

One organisation, the whole loop visible: operations, credentialing, rostering and handling under one roof. It proves the complete operational picture in its simplest form, and it gets a platform sized to its reality rather than to a hub's.

A major airport with many providers and many silos

Many organisations, many systems, politics in every interface. It proves the coordination problem at full difficulty, where source authority and provenance are not architecture diagrams but daily survival. Solve both and the product generalises across the industry.

The terms

What a design partner gets.

Roadmap influence

The partnership shapes what general availability looks like. Your workflows are the requirements, not a ticket in a queue.

Partner grade commercials

Terms that reflect the fact that you are building the product with us, not buying it off a price list.

A named sponsor

One accountable person on our side who knows your operation, your regulators and your deadline.

A clean answer

The ninety day exploration ends in a go or a no go, with the evidence either way. No zombie pilot.

The pathway

Ambition first. Then the honest route to it.

The full ambition is one operating platform across airport operations. This is the order we get there, and what has to be true before each step earns the next one.

1 Now

Agree the operational data model, the data rights, the security boundary and the co-development scope with a design partner.

2 First platform step

Build the canonical operational view: event provenance, identity, explicit source authority, and a narrow set of real inbound connectors.

3 Mandate aligned step

Add the connector plane and the visibility and planning services that map to Airport Operations Plan and operations centre workflows.

4 After 2027

Add controlled actions and operational modules, in a sequence set by customer value and safety risk.

The ninety day exploration

What actually happens first.

Weeks one and two We map your systems, your silos and your regulators. You tell us where the picture breaks today.

Weeks three to six One operational slice goes live on the record: the data model, source authority and the first real connector for your estate.

Weeks seven to twelve The slice runs against a real operation with your people. Evidence in, verdict out: go, no go, or go with conditions.

If you run an airport, we would like to build this with you.

Not a software sale. A ninety day exploration, a named sponsor on both sides, and an honest answer at the end either way.

Start the conversation Read the evidence chain