Take one workflow from decision to running live.
Redesign a single high-value workflow and run it in your live operation.
You get a measurable result in real use, with the economics agreed up front and the outcome proven against your own numbers.
One engagement, two stages you commit to one at a time. The Blueprint is sold under the Acceptance Guarantee - criteria agreed in Week 1, no fee if outcomes are not accepted. From $28,300 CAD.
Who the Transformation Blueprint is for
Operations leaders who have committed to a workflow and need a deployable plan
COOs, CFOs, and all other executives who own the outcomes the workflows must deliver
Teams that have run AI pilots without converting them into real use
Organizations whose AI Task Force has produced an inventory but not a plan of record
Leaders who want measurement infrastructure in place before transformation begins, not after
Why organizations start with a Transformation Blueprint
A committed workflow does not deploy itself. The Blueprint produces a deployable plan, anchored to your real numbers, with measurement built in from day one - grounded in 22 years of building the systems large operations run on.
Convert a decision into a plan of record
Deciding on a workflow names what to do. The Blueprint sequences how to do it, with named owners, dependencies, and 30/60/90 milestones a delivery team can execute against.
Anchor projections in your real numbers
Generic ROI estimates collapse on contact with reality. The Blueprint pins down what the work costs you today and the impact projected against your operational data, with confidence levels documented.
Capture today's numbers before anything changes
The Blueprint defines what gets measured and captures the numbers you have today before transformation begins. Without that starting point, you cannot prove the improvement afterward.
You only pay if the Blueprint delivers
Acceptance criteria are agreed in Week 1 and written into the Outcome Spec. If Blueprint outcomes are not accepted, no fee is charged. The guarantee applies to the Blueprint phase only, not to the Build. So you commit real money only once you have seen it work.
What the Transformation Blueprint is
The Transformation Blueprint is a focused three-week phase that converts a committed workflow into a deployable plan, with today's numbers captured, named owners, and the Build's fixed price.
It is where a decision becomes a plan you can act on: one workflow, redesigned, with the economics proven against your own numbers before the Build begins.
It is a focused process that produces decision-ready artifacts and the measurement in place to deploy AI workflows into real use.
How the Blueprint works
It runs three weeks, and one team stays with you from the first interview to the signed plan, so nothing gets dropped in a handoff.
Week 1. Discover
Workflow shadowing with operational teams. Data extraction from your operational systems. Interviews with workflow owners and AI program leaders. Acceptance criteria confirmed under the Acceptance Guarantee. The workflow's system and data requirements verified against your existing foundation, including data-quality blockers like duplicate records for the same customer across systems.
Week 2. Quantify
Current-state cost modeled per sub-workflow. We capture the numbers you have today, straight from your own operation. The Outcome Spec built with a sourced assumptions log. Impact projections stress-tested against named risks. Change-readiness assessed.
Week 3. Sequence
Initiatives prioritized by impact, confidence, and readiness. Named-owner recommendations. 30/60/90 milestones defined. Sponsor sign-off on the Outcome Spec. Final readout to leadership.
Your team's involvement: an executive sponsor who signs off on the Outcome Spec, workflow owners for shadowing and interviews, and access to operational data. Heaviest in Week 1, tapering as the Blueprint moves from discovery to sequencing.
What you leave with
A plan you can execute. A starting point you can measure against.
Every Blueprint ends with the same things in your hands: a plan you can execute and a starting point the Build is measured against.
Outcome Spec
What the Build is held to: a committed economic case with a sourced assumptions log and sponsor sign-off, re-confirmed after the Build with any variance traced to specific assumptions.
Sub-Workflow Deep Dive
Process maps, what the work costs today, redesign options, and impact projections with documented confidence levels for each workflow in scope.
Workflow Transformation Atlas
Your map of where AI pays off next: a prioritized inventory across the workflow areas in scope, and the input for any transformation work that follows.
Prioritized Sequencing Plan
Deployment order, dependency resolution, named-owner model, and 30/60/90 milestones. Adopted as your plan of record and the basis for scoping the Build.
Your Starting Numbers
So you can prove the change later: today's numbers captured before anything moves, for each workflow in scope. Without this, outcomes cannot be measured after.
Acceptance Criteria
Documented criteria for each deliverable, agreed in Week 1. The basis for the Acceptance Guarantee.
Working demonstration
The Blueprint concludes with a working demonstration built from one slice of the redesign - which may include an AI agent, application, or workflow experience - enough for your stakeholders to see the essence of the new workflow before the Build begins.
The Acceptance Guarantee
The Acceptance Guarantee
Acceptance criteria are agreed in Week 1 and written into the Outcome Spec. If the Blueprint's outcomes are not accepted at the end of the phase, no fee is charged.
The scope is unambiguous. The Acceptance Guarantee applies to the Transformation Blueprint only. It never extends to the Build, to Activation, or to any business outcome.
The Blueprint's plan of record, starting numbers, and fixed Build price feed directly into the Build.
The Build: deploy the redesigned workflow into your live operation.
The Blueprint produces the plan of record, the numbers you have today, and the Build's fixed price. The Build deploys the redesigned workflow into your live operation: simple workflows in weeks, complex ones within 90 days.
The Build is the second stage, committed only after you have accepted the Blueprint, and priced to scope from the Blueprint's sequencing plan.
The starting numbers and acceptance criteria the Build runs against come from the Transformation Blueprint.
A system that runs live, not a pilot.
The Build ships a working system into your operation - built in your own cloud, in your repository, behind your own access controls. You own the code.
Agents and workflow components
The AI agents, copilots, and supporting automation that run the redesigned workflow - that sort the work, route it, pull the right records, draft the first version, and carry out the routine steps, assembled from patterns proven in real use.
Integration into your core systems
The workflow runs inside the systems your operation already uses - ERP, CRM, contact centre platforms, document repositories - through a secure access pattern verified against your systems in Week 1 of the Blueprint - or reused from your AI Foundations Blueprint's Reference Architecture where one exists.
The decisions that stay with a person
The decisions that need a person keep one, with review queues and escalation paths built into the flow itself, not bolted on.
How we keep the result honest
From day one we measure the redesigned workflow against the numbers the Blueprint captured, check its answers against a known-good set of examples, and put the results on a dashboard you can watch.
How Outcome Assurance worksIt runs against your real day-to-day workload, keeps a full audit trail, and meets the security standards your own team signs off on.
Launch and Hypercare
The Build ends with two named milestones that move the workflow into your live operation and stabilize it there.
Launch
The switch to running live, role-based training, and a go-live runbook, released only once go-live sign-off is complete against the numbers the Blueprint captured.
Hypercare
The final four weeks of the Build, included in the fixed fee: elevated support, daily usage monitoring, fast-cycle fixes, and adoption triage.
Four weeks of Hypercare inside a 90-day warranty after you go live
If something we built does not perform to specification, we fix it at no additional cost, for the full 90 days after the workflow goes live and is signed off.
Where the Build's promise ends, honestly
Acceptance is against the agreed specification and the numbers you started with. Business outcomes are measured through Outcome Assurance and Activation. The Build does not promise them.
The Outcome Spec, re-confirmed
After the Build, the Outcome Spec is re-confirmed as part of the go-live sign-off story. The committed economic case set in the Blueprint is checked against what was delivered, and any variance is traced back to specific assumptions in the assumptions log.
The project was delivered on time and the business, the team and our customers were happy with the results.
Where Workflow Transformation fits in the Work Redesign System
Workflow Transformation is one engagement in two stages you commit to one at a time. The Blueprint produces the plan, the starting numbers, and the Build's fixed price. The Build follows only when you accept the Blueprint - no build capital is committed before the plan is in hand.
The Blueprint produces the plan. The Build delivers it into your live operation.
When the Transformation Blueprint is the right starting point
Start with a Transformation Blueprint when
You have decided on a workflow but have no plan of record
AI work has been identified but not deployed into real use
You need your starting numbers and metrics defined before transformation begins
An AI Task Force, working group, or program lead exists to drive plan adoption
Capital is available for transformation work but sequencing is unclear
Start somewhere else when
You have not yet identified where AI applies. Start with AI Jumpstart
Systems questions - security, access, governance - are blocking everything else. Start with the AI Foundations Blueprint
You have a defined plan and validated foundations and are ready to build. Speak with AI Engineering
What is the status quo costing you?
Pick the workflow that matters most and set the sliders to how the work actually runs. Every figure is built from your own numbers, not our projections.
No savings promises. A structural read on how much of one workflow's annual cost sits in the steps AI typically touches.
Built entirely from your own numbers. The diagnostic later opens pre-filled with what you set here, so nothing is asked twice.
What you get
- A dollar figure for what one workflow costs to run for a year, at your settings
- The cost of waiting, projected over the months until you act
- The share of that cost sitting in the steps AI typically touches: sorting, routing, looking things up, and drafting
- A one-page summary you can download and forward to a CFO or CEO
- A direct hand-off into the diagnostic, pre-filled with what you set
What buyers ask about the Blueprint and the Build
They are one engagement in two stages, committed separately. The Blueprint comes first and produces the plan of record and the Build's fixed price. The Build follows only when you accept the Blueprint, which keeps the pricing honest and gives you a built-in off-ramp: you decide to proceed with the full plan and the full number in hand.
It is the Blueprint's success-based promise. Acceptance criteria are agreed in Week 1 and written into the Outcome Spec, and if the Blueprint's outcomes are not accepted at the end of the phase, no fee is charged. The guarantee applies to the Transformation Blueprint only. It does not extend to the Build, to Activation, or to any business outcome.
The Outcome Spec is the committed economic case built during the Blueprint, with a sourced assumptions log and sponsor sign-off. It is the spec every acceptance test hangs on. After the Build, the Outcome Spec is re-confirmed and any variance is traced back to specific assumptions. The Outcome Spec is the written record of what the workflow is meant to return; Outcome Assurance is how we keep measuring it once the workflow is live.
Launch is a named milestone in the Build. It covers the switch to running live, role-based training for the people who will use the workflow, and a go-live runbook. It is released only once go-live sign-off is complete, measured against the numbers the Blueprint captured.
Hypercare is the final four weeks of the Build, included in the fixed fee. During Hypercare you get elevated support, daily usage monitoring, fast-cycle fixes, and adoption triage. It is the stabilization period that carries the workflow from go-live into steady operation.
For 90 days after the workflow goes live and is signed off, if something we built does not perform to the agreed specification, we fix it at no additional cost. The four weeks of Hypercare sit inside that window. The warranty covers defects and non-conformances against the specification, not changes to the business outcome the workflow is meant to influence.
The Build is scoped from the Blueprint's sequencing plan, so timing depends on the workflow. Simple workflows ship in weeks. Complex ones are delivered within 90 days. Ninety days is the outer bound, not the typical duration, and the Blueprint gives you the fixed number before the Build begins.
Convert one workflow into a plan of record.
Start with the Blueprint under the Acceptance Guarantee. Move into the fixed-fee Build, paid milestone by milestone as each is accepted, when you accept the plan.
Measured in real use: 35% faster resolution, documents and approvals completed 60% faster, 3x faster information retrieval.
Systems questions blocking the work?
Explore the AI Foundations Blueprint