Offers

Four offers. One maturity path.

Each offer begins from a distinct evidence base, answers a different client question, has a deliberate boundary, and produces a defined next decision. Completion of one offer does not oblige either party to enter the next.

At a glance

Four offers. One maturity path.

At a glance
Offer	Starting point	Question answered	Primary outcome	Typical duration
Offer A — Mining Application Framing Sprint	Credible technology or concept; no sufficiently defined mining application or demonstration context.	Where can this technology create practical value in mining, and what must a first demonstrator prove?	Chosen mining use case and demonstration context, stakeholder and adoption map, proof plan, and a 90-day validation roadmap.	1–2 weeks of effort, normally within 2–3 calendar weeks.
Offer B — Mining Demonstration Platform Definition	Tested technology or early prototype; approved application and demonstration context.	What demonstrator should we build, what mine workflow must it support, and what evidence must it produce?	Field-deployable demonstration platform specification, modular configuration and interface definition, validation plan, traceability matrix, risk register and executive build decision package.	Normally 5–7 calendar weeks after the context is approved; combined A + B normally 7–10 calendar weeks.
Offer C — Mine-Ready Productization Assessment	Defined application and a representative working or field-validated demonstrator or prototype.	What must change before the demonstrator can be validated, manufactured, installed, serviced, supported and scaled?	Evidence-based productization baseline, scorecard, prioritized gap register, demonstrator-to-product transition view, indicative 18–24 month roadmap and a recommended execution model.	Up to 4 calendar weeks, remote-first.
Offer D — Prototype-to-Channel Readiness Program	Approved productization baseline or equivalent evidence, executive sponsor, funding path and a named product owner.	How do we convert the roadmap into an executable program and build the delivery capability required for scale?	Governed execution plan, high-leverage technical leadership, partner technical coordination, readiness-gate progress and capability transfer.	Surge normally 2–6 months; Execute normally 6–18 months; Maintenance ongoing.

The offers

What each engagement produces.

Offer A · Define the mine problem

Mining Application Framing Sprint

Where can this technology create practical value in mining, and what must a first demonstrator prove?

Best for: Credible technology or concept; no sufficiently defined mining application or demonstration context.
Primary outcome: Chosen mining use case and demonstration context, stakeholder and adoption map, proof plan, and a 90-day validation roadmap.

Full offer detail

Offer B · Build the proof

Mining Demonstration Platform Definition

What demonstrator should we build, what mine workflow must it support, and what evidence must it produce?

Best for: Tested technology or early prototype; approved application and demonstration context.
Primary outcome: Field-deployable demonstration platform specification, modular configuration and interface definition, validation plan, traceability matrix, risk register and executive build decision package.

Full offer detail

Offer C · Productize for the mine

Mine-Ready Productization Assessment

What must change before the demonstrator can be validated, manufactured, installed, serviced, supported and scaled?

Best for: Defined application and a representative working or field-validated demonstrator or prototype.
Primary outcome: Evidence-based productization baseline, scorecard, prioritized gap register, demonstrator-to-product transition view, indicative 18–24 month roadmap and a recommended execution model.

Full offer detail

Offer D · Scale with confidence

Prototype-to-Channel Readiness Program

How do we convert the roadmap into an executable program and build the delivery capability required for scale?

Best for: Approved productization baseline or equivalent evidence, executive sponsor, funding path and a named product owner.
Primary outcome: Governed execution plan, high-leverage technical leadership, partner technical coordination, readiness-gate progress and capability transfer.

Full offer detail

Progression

How offers connect.

A team with credible technology but no defined mining application normally begins with Offer A.
Offer B begins after Offer A is approved, or when equivalent documented and client-approved application and demonstration context already exists.
Offers A and B may be sold together as one milestone-gated engagement, with a formal context-approval gate between them.
A team with a defined application and a representative working demonstrator may begin directly at Offer C.
A team with a completed productization baseline may be considered directly for Offer D, subject to fit and scope validation.
Offer D normally begins with a scoped Surge phase; progression to Execute requires separate client authorization.
Progression is based on evidence, maturity, readiness, decision authority and separately approved scope — never on an automatic upsell.
One offer is never allowed to substitute for required work in the next maturity stage.

Row of identical ruggedized equipment enclosures on an assembly bench

Start a conversation

Which offer fits your evidence?

If the answer is not obvious, the pathway page sets out the routing logic, trigger events and fit criteria in detail.

Start a conversation See the pathway