One workflow in production and in use in 90 days

An AI-native operating model sets out how people and AI share the work: roles, decisions, accountability, controls and the evidence used to improve it. In the 90-day programme, we design the changes needed for the agreed workflow and build the system alongside them.

Yes, where the agreed workflow needs changes to roles, decision rights or governance. That design sits in weeks 1–2 of the 90-day outcome programme. An organisation-wide target operating model can be a larger scope; standalone design is available on request at the rate card.

The operating decisions depend on what the system can reliably do. Designing the workflow and technical approach together lets your people test those assumptions before the production build gets far ahead.

We can discuss an interim leadership responsibility as part of the agreed scope. The 90-day programme is bought for one production workflow, not a permanent placement. Programme and Delivery Management is a separate option when you need a delivery lead across existing teams and suppliers.

The programme offers two- and three-practitioner options, with partner oversight. The right mix depends on the engineering, operating-method and adoption work needed for the workflow. Your engineers also take part in the build; we agree the roles and availability before starting.

We walk through real cases with the people doing the work, including exceptions. Together we agree which actions can be automated, which need a person’s review and who remains accountable. Those decisions become tests, review gates and escalation routes in the workflow.

Both. Weeks 1–2 cover design, weeks 3–10 build with your engineers, and weeks 11–13 adoption, measurement and handover. The scope is one agreed workflow in production and in use in 90 days.

That monthly range described the retired standalone Design Team. The current 90-day outcome programme is £120,000 for two practitioners or £180,000 for three, fixed, in three monthly instalments of £40,000 or £60,000. Standalone design can be scoped on request at the published rate card.

Design is now the first two weeks of the 90-day outcome programme. We agree the workflow, pound value, operating decisions, technical approach and acceptance evidence, then build with your engineers in weeks 3–10 and complete adoption, measurement and handover in weeks 11–13.

Continuing is your decision. Standalone design can be scoped at the rate card if that is the work you need. The 90-day programme is a different purchase: one agreed workflow covering design through production, adoption and handover for a fixed fee.

Agree the shared platform decisions, ownership and review gates before separate teams build incompatible patterns. Within the 90-day programme we make those decisions for the agreed workflow with your architects and engineers, then record what later teams should reuse.

One workflow and one team can be an appropriate 90-day scope if the outcome is valuable and the people needed can take part. Use a proof of concept first if the workflow’s technical value is still uncertain, or Learn if the immediate need is a working method.

Agree the value baseline and acceptance evidence first. In the programme’s opening weeks, useful progress includes resolved decisions, a tested technical approach and the first build increments. The overall commitment is one workflow in production and in use in 90 days, with the outcome measured against the agreed baseline.

We bring the CTO and relevant architects into the decisions during design. We compare the options against the workflow, existing estate, security constraints and acceptance evidence, then record the choice with the people who own it.

The retired standalone design product no longer has a published monthly fee. The current 90-day outcome programme costs £120,000 for two practitioners or £180,000 for three, fixed. If you only need design, we scope it separately at the published rate card.

The 90-day programme is fixed-price work. If either party ends it on written notice, fees are due for work performed and committed costs incurred up to termination. You receive the work produced to that point, with ownership on payment. The Statement of Work records the scope and terms before starting.

Yes. If your architects have the time and authority to design the workflow and direct the build, they may be the right people. Our programme adds hands-on delivery and adoption support for a defined outcome, working alongside them.

Existing design can reduce the work still needed, provided it covers the actual workflow, operating decisions and technical constraints. We assess it during scoping. After a Tenhaw proof of concept, design already completed comes off the fixed programme quote; the audit has no credit against later work.

We agree sponsor and decision-maker availability before starting. Weeks 1–2 need timely decisions on scope, value, ownership and acceptance. The people who use the workflow and your engineers also need protected time during build and adoption.

The sponsor needs to resolve accountability with those directors. We make the competing decisions and their consequences visible during design, then record one agreed owner and escalation route before building the workflow around them.

We agree where the workflow sits in the existing programme, which decisions it depends on and who accepts it. The 90-day scope should support that programme’s outcome rather than create a separate governance track.

Yes. One division or one workflow can be the right boundary. We agree the systems, people, operating decisions and dependencies needed to put that workflow into production and use; it is not a promise to redesign the whole group in 90 days.

The new outcome programme is a fixed £120,000 or £180,000 commitment, paid in three monthly instalments. Procurement approves the agreed scope, deliverables, dependencies and acceptance evidence in the Statement of Work. Month-to-month continuation is a separate decision after day 90.

The fixed programme is scoped to one workflow, not a whole group’s operating model. Two or three practitioners work with your sponsor, engineers and users on that boundary. Broader organisation design needs its own scope and can be discussed at the published rate card.

We agree the minimum access needed to understand and test the workflow. Design may use masked data or representative examples where appropriate. Production access, controls and approval requirements are agreed with your security and engineering teams before the relevant work begins.

Yes, when the responsibilities and interfaces are clear. The first two weeks establish the decisions and review gates for the agreed workflow; weeks 3–10 are a joint build with your engineers. We make dependencies visible so parallel work does not rely on unresolved assumptions.

We design around the platform where it meets the workflow’s needs. During scoping and design we check integration, security, run cost and any constraints that affect the agreed outcome, then record the decisions with your technical owners.