How we work

Define. Judge. Deploy.

The edge is no longer who has the model. It is where the new team runs, whether you can see that environment, and who is accountable when it acts. Three steps. Every engagement.

Define business reality

The Map · people, technology, data, cost

We sit with the work until we see how it really happens. Golden path and every exception. Who touches it, which systems, what data, what it costs today.

We also build the Mirror: a parallel team on approved data, read only, no production access, under NDA. You watch your own work run the new way before anyone commits to building anything. Data position and residency are decided here. That drives local and sovereign versus any frontier hop.

What you get

Process record, written down and agreed
Baseline: volume, cycle time, error rate, hours, cost
Decision rights: who initiates, approves, reverses, owns
Data position: classification, residency, what may never leave

Where we stop

If we cannot write down how the work happens today, nothing gets built.

Apply expert judgement

Where the system acts · where the human approves

We decide where AI belongs, and where it does not. Deterministic where it can be. Model-led where it must be. Human where it matters. We match local models to workloads, and use frontier only when the job clearly needs it.

Then we sequence: what is worth doing now, what waits for the data, and what should not be automated at all.

What you get

Intervention map, every step classified with the reason
No go list: what we will not build, and why
Economics: expected payback per candidate, before you spend

Where we stop

If the honest answer is do not build it, that is the deliverable.

Deploy the AI that works

Judged on ROI · economics · resilience · a place you can touch

On infrastructure you can see and govern: your environment, local and sovereign, or kit we set up and run with you, in your tenancy or on ours. Fully Australian where residency requires it. Ownership and keys stay with you. Three gates, and nothing moves without clearing the one before it.

Nobody gets replaced. Your team moves up to judgement, ownership and approvals while the new team carries the repeatable work underneath. When you want the run in-house, we do a full handover as required.

Proven

Real cases, failure taxonomy, pass threshold, cost per successful task. Zero unauthorised actions. No demo alone goes live.

Shadow

Runs against live inputs beside your people. Parallel, no consequences. Autonomy widens by evidence only.

Owned

Monitoring, runbook, incident owner, rollback. Your people hold the approvals. Exceptions feed the evidence set.

Where it runs

Your environment. Local and sovereign. Or we host and manage.

Hosting is optional. Visibility is not. Support is as required for the engagement.

Your environment

Build on the cloud and systems you already run when that is the right home.

Local and sovereign

Default for real work. Models and data stay where you can see them. Your boundary, your keys.

We host and run

Set up, host, and manage the infrastructure layer: redundancy, backups, full IT management of that layer. Your tenancy or ours. AU where required. Full handover when you take it.

Why this shape

Governance first. Not bolted on later.

Most firms deploying AI are engineers learning governance last. We came the other way. Twenty five years in cybersecurity, risk and governance, then deployed engineering.

If your industry has a framework, we have been assessed against it. Defence, government, critical infrastructure, financial services and health does not leave many we have not had to prove.

Your board will ask who approved a decision the new team made. The evidence you need that day is the evidence we produce on the way through.

What it costs

Not day rates.

Foundation first. Define the business reality, build the Mirror, hand you the judgement and the sequence, and a clear view of where the new team will run. One fixed fee, set when we scope the work.

Then Operating Tokens. One blended allowance for models, builds, workshops, governance, human led delivery, and the run when we host. Only approved work consumes it. One monthly statement.

See the packages

Questions, answered

Before you ask.

Do we have to replace our stack?

No. We build on what you already run when that is right. Tool change only when evidence says it pays.

What happens to our data?

Residency and keys decided up front. Local and sovereign when data should not leave your boundary. Mirror and read-only patterns as agreed. Sensitive actions pass a named human gate.

Do you only work on our cloud?

No. Default is local and sovereign when that fits. We can use your cloud, or set up and manage infrastructure in your tenancy or on ours. Fully AU where required. Hosting is an option, not the deal.

What do we get first?

Foundation: business reality, judgement, sequence, and a clear view of where the new team will run. One fixed fee, set when we scope the work.

How do we pay?

Not day rates. Operating Tokens: one allowance for humans and technology, including host and run when in scope. Only approved work consumes it. One monthly statement.

Do our people get replaced?

No. They move up to judgement, ownership, and approvals. The new team runs underneath, on infrastructure you can see.

What if we want to run it ourselves later?

Full handover as required: access, runbook, ownership path, clean exit from our manage scope.

Start here

Ready to move from experiment to operation.

Start in the engagement portal, or email both founders.

Get Started Email us