Pilot as a design partner

The system is not finished. That is not small print, that is the offer: you help decide what it gets calibrated on, and after handover you own what stands.

Why a design partner

A generic model does not know your suppliers.

The moat on this product is not an algorithm. It is the calibration: knowing which certifications are hard requirements for you, which supplier delivers more reliably despite a higher price, and which deviation from the specification is acceptable in practice. None of that is in a handbook. It is in your procurement history.

So at this stage we work with a small number of design partners rather than as many customers as possible. Whoever joins now joins while the shape can still change.

The track

Four phases, one handover.

Intake and process mapping

We map your current procurement process: which systems, which suppliers, which decision criteria, and where approval comes from. This is what tells us whether a layer on your existing software makes more sense than a separate deployment.

Data intake and fine-tuning

The system is trained on your ERP procurement history and supplier data. This is what makes the output specific to your organisation instead of generic to the sector.

Deployment on your infrastructure

Locally, on your own servers. No cloud connection required. Your data does not leave your network, not even during training.

Handover: you own the system outright

After handover no subscription is required for it to run. Maintenance and retraining are bought when you find them useful, not because the system stops otherwise.

Terms

What each side puts on the table.

You bring

Access to procurement files and to the buyer doing the daily work, not only to their manager. That buyer’s time, on the order of a few hours a month. And the willingness to say when the output is wrong.

We bring

Deployment, calibration on your data, and the handover after which you own the system. A non-disclosure agreement before any data moves, and a written data boundary setting out what the system touches and who can reach it.

You decide

The system advises and documents. The buyer reviews and signs. Responsibility for the procurement decision stays with your organisation, and we put that in the contract too.

What we cannot promise yet We have no pilot data, so we cannot guarantee a saving. The research supports the problem and the local deployment model. It does not prove that this approach buys more cheaply in practice than your best buyer. That is exactly what a pilot has to establish, and anyone joining knows that up front.

Apply

See whether it fits.

A pilot starts with a conversation, not a quote. Tell us briefly what kind of organisation you are, which procurement problem costs you most, and who decides on procurement tooling.

Four ways in

Where you come in depends on what you need.

Open now

Pilot as a design partner

A generic model does not know your suppliers.

Four phases, one handover.

Intake and process mapping

Data intake and fine-tuning

Deployment on your infrastructure

Handover: you own the system outright

What each side puts on the table.

See whether it fits.

Where you come in depends on what you need.

Become a research partner

Pilot as a design partner

Procurement scan

A 30 minute conversation