Offer 02

Build one integrated workflow to a stated boundary, with the controls and evidence needed to run it.

Assured workflow engineering is a six-to-ten-week pilot that builds one integrated workflow to a stated boundary, with the controls and evidence needed to run it.

Six to ten weeks

Who it is for

The product or platform owner, with the CTO or Head of AI as technical sponsor. You have a workflow with a baseline (ours from Offer 01, or your own) and a budget to build the first version.

What you get

One integrated workflow connected to your identity, data and tools.
Context handling with permission filters and provenance logging.
Durable execution: state, checkpoints, retries, idempotency and timeouts.
Approval interfaces bound to exact actions and their expiry.
Test environments covering normal, ambiguous, adversarial and failure cases.
Recovery paths and an operations runbook.
An acceptance report and a documented handover.

How it runs

Autonomy is granted in stages: offline, shadow, supervised, limited.

Define and Bound
in the first two weeks: owner, acceptance criteria, data access, allowed tools, actions that need approval, risk owner.
Engineer
in weeks three to seven.
Verify
in weeks eight to nine against the agreed test set, with the resulting system state inspected, not the agent's report.
Operate
handover plan, monitoring, change control.

Duration and commercials

A pilot typically runs six to ten weeks. Fixed scope for the pilot; expansion only by the rule agreed at the start.

Boundary

No unrestricted autonomous action on financial, legal or physical systems. Any action with those consequences requires human approval. Authority is enforced in code outside the model.

Questions buyers ask

How long does an assured workflow engineering pilot take?

A pilot typically runs six to ten weeks, with fixed scope. Expansion happens only by the rule agreed at the start.

Can the agent act on financial, legal or physical systems on its own?

No. Any action with those consequences requires human approval, and authority is enforced in code outside the model.

Do we need a baseline first?

If you have a baseline, send it. If not, start with Offer 01, Workflow architecture and baseline.

How to start

If you have a baseline, send it. If not, start with Offer 01.

Scope a workflow →