Take one workflow from decision to running live.
A committed workflow does not deploy itself. This is how one gets a plan, a price, and a launch date.
You get a measurable result live in your operation, with the economics agreed up front and the outcome proven against your own numbers.
One engagement, two phases you commit to one at a time. Transformation Blueprint: 3 weeks, from $28,300 CAD. Build: fixed fee, priced by the Blueprint.
What the Transformation Blueprint is
Three weeks that turn a chosen workflow into a plan with named owners and 30/60/90 milestones. The numbers you start from are written down, and so is the Build's fixed price.
Generic ROI estimates collapse on contact with reality. The Blueprint prices the work against what it costs you today, from your own data, with the confidence level of every assumption on record.
A plan a delivery team can run
Named owners, dependencies, and 30/60/90 milestones. Adopted as the plan and the basis for the Build's price.
Your starting numbers, captured before anything moves
Without them you cannot prove the improvement later. The Blueprint writes them down first.
The Build's full price before you commit to it
The Blueprint produces the fixed price. You decide to proceed with the plan and the number in hand.
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
We shadow the people who do the work, pull data from the systems they use, and interview the owners. We check the workflow's needs against your systems, including the unglamorous blockers, like the same customer existing three times across three systems. And we agree, in writing, what 'accepted' will mean at the end of week three.
Week 2. Quantify
Current-state cost modeled per sub-workflow. We capture your starting numbers, 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.
Outcome Spec
What the Build is held to: a committed economic case with a sourced assumptions log and sponsor sign-off. It is re-confirmed after the Build, with any variance traced to specific assumptions. The acceptance criteria agreed in Week 1 are written into it.
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.
prioritized workflow map
Where AI pays off next, ranked across the workflow areas in scope, and the input for whatever transformation work follows.
sequencing plan
Deployment order, dependency resolution, named-owner model, and 30/60/90 milestones. Adopted as the plan and the basis for scoping the Build.
your starting numbers
So you can prove the change later: your starting numbers captured before anything moves, for each workflow in scope. Without this, outcomes cannot be measured after.
Working demonstration
One slice of the redesign, working, so your stakeholders see the new workflow before the Build begins. It may be an agent, an application, or a screen your people will use.
If you do not accept the Blueprint, you do not pay for it.
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 and starting numbers feed directly into the Build.
The Build puts the redesigned workflow to work.
Simple workflows in weeks. Complex ones within 90 days. Fixed fee, priced by the Blueprint, committed only once you have accepted it.
What that looks like: a national logistics operator processed contracts and documents with manual review at every stage and several approval handoffs. The rebuilt workflow reads each document, applies the rules, and sends it to the right person to decide. Documents and approvals now complete 60% faster.
Twenty-two years of building the systems large operations run on stand behind every Build - See the systems we have built.
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. They sort the work, route it, pull the right records, draft the first version, and carry out the routine steps. Each is assembled from patterns already proven running live.
Integration into your core systems
The workflow runs inside the systems you already use: ERP, CRM, the contact centre platform, the document store. The way AI reaches them is verified 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 verify the result
From day one we measure the redesigned workflow against your starting numbers. We 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.
After go-live you get four weeks of Hypercare, then a 90-day warranty.
Launch
The switch to running live, role-based training, and a go-live runbook, released only once go-live sign-off is complete against your starting numbers.
Hypercare
The final four weeks of the Build, included in the fixed fee: elevated support, daily usage monitoring, fast-cycle fixes, and adoption triage.
Warranty
If something we built does not perform to specification, we fix it at no additional cost for the full 90 days after go-live sign-off.
Where the Build's promise ends, honestly
Acceptance is against the agreed specification and your starting numbers. Business outcomes are measured through Outcome Assurance and Activation. The Build does not promise them.
The Outcome Spec, re-confirmed
At go-live sign-off the Outcome Spec is checked against what was delivered. Any variance is traced to a named assumption in the 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 the middle stage. What the Build launches, Workflow Activation keeps paying off.
When the Transformation Blueprint is the right starting point
Start with a Transformation Blueprint when
You have chosen the workflow but have no plan, no owner list, and no price
A pilot worked in a demo and has never touched real volume
Your AI task force has an inventory of ideas and no sequence
You want the numbers you start from written down before anything changes
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 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 phases, committed separately. The Blueprint comes first and produces the plan and the Build's fixed price. The Build follows only when you accept the Blueprint, which keeps the pricing transparent. You decide whether to continue, 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. 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.
The warranty runs 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 the plan.
Three weeks to a plan, a price, and your starting numbers. Then a fixed-fee Build, paid milestone by milestone, if you choose to go.
Measured live in your operation: 35% faster resolution, documents and approvals completed 60% faster, 3x faster information retrieval.
Systems questions blocking the work?
Explore the AI Foundations Blueprint