Establish whether AI is the right answer for a specific workflow, and if so, what a measurable first version should look like.
Workflow architecture and baseline is a two-to-three-week engagement that establishes whether AI is the right answer for a specific workflow, and if so, what a measurable first version should look like.
Who it is for
CTO, Head of AI, or the operating leader who owns the workflow. You have a process that is important enough to fund but not yet reliable enough to trust, and you need a decision you can defend.
What you get
- A process map with steps, handoffs, exception paths and volumes.
- A comparison with a deterministic or conventional alternative.
- A data and access review covering sources, permissions, freshness and provenance.
- A failure-cost estimate for the current process and for an AI-assisted version.
- An evaluation plan with acceptance criteria and owners.
- Architecture options with a recommendation, including, where warranted, a recommendation not to build.
How it runs
- Week 1
workflow owner interviews, system access, process observation.
- Week 2
data and permission review, alternative comparison, failure-cost model.
- Week 3
architecture options, evaluation plan, written recommendation and a read-out with the sponsor.
Duration and commercials
Typically two to three weeks after access is ready. Fixed scope, fixed price, stated in the proposal with direct cost, margin and value measure. Duration is indicative, not a service-level guarantee.
Boundary
The engagement does not promise that AI is the right answer. A recommendation not to build is a valid outcome and is delivered with the same care. This is not a certification and not a promise of return.
Questions buyers ask
How long does a workflow architecture and baseline take?
Typically two to three weeks after access is ready. It is fixed scope and fixed price, stated in the proposal. Duration is indicative, not a service-level guarantee.
Can the answer be not to build?
Yes. A recommendation not to build is a valid outcome and is delivered with the same care.
What do we get at the end?
A process map, a comparison with a deterministic or conventional alternative, a data and access review, a failure-cost estimate, an evaluation plan with acceptance criteria and owners, and architecture options with a recommendation.
How to start
Bring one workflow and four facts: the business process, its current baseline, the systems involved and the cost of failure.
Start with one workflow →Related client stories
Client stories are published as permissions are confirmed. Until then, the method we hold every story to is on How you can check us.
How you can check us →