AI workflow consultancy, proportionate to a real operational decision
Codance offers two focused starting points within a broader workflow and integration consultancy. Each launch package examines one defined operational workflow and one principal business function. Neither assumes that AI is the answer, and neither requires you to buy implementation from Codance.
Compare the services
| AI Workflow Readiness Assessment | AI Integration Blueprint | |
|---|---|---|
| Principal question | Should we proceed, where and why? | How should the selected integration operate? |
| Best for | A workflow where the opportunity or readiness is still uncertain | A sufficiently understood workflow that needs a solution-level design |
| Core output | AI Workflow Readiness Report | AI Integration Blueprint and supporting workflow diagrams |
| Evidence included | Up to five relevant supplied artefacts | Up to ten relevant supplied artefacts |
| Structured discussion | Up to 30 minutes | Up to 90 minutes, normally divided into no more than two sessions |
| Delivery | Seven calendar days after complete requirements | Ten calendar days after complete requirements and discovery scheduling |
| Introductory project fee | £95 | £295 |
| Implementation | Not included | Not included |
Final scope and any applicable tax are confirmed before work begins.
Focused scope, wider awareness
A defined workflow boundary keeps the evidence, risks and recommendation specific enough to support a real decision. Codance still considers relevant system dependencies, neighbouring processes and foreseeable future needs where they affect readiness, compatibility or implementation sequencing.
If the question spans several connected workflows, Codance can identify the relationships and recommend a staged or separately scoped route. Wider opportunities are not silently absorbed into a launch package.
AI Workflow Readiness Assessment
Choose the Assessment when the important question is whether the workflow is ready, where AI could add value, and what should happen before anybody commissions a build.
The report examines:
- the business objective and real current workflow;
- information, systems and sources of truth;
- decisions, exceptions and human judgement;
- AI suitability and non-AI alternatives;
- readiness constraints, risks and prerequisites;
- the safest, most valuable first opportunity;
- the recommended next action.
The conclusion may be ready for bounded integration, ready with prerequisites, not ready yet, or AI is not the best first solution.
AI Integration Blueprint
Choose the Blueprint when the workflow and objective are sufficiently clear, but a credible future-state design is needed before internal approval, supplier quotation or prototype work.
The Blueprint defines:
- the current and proposed future workflow;
- the roles of AI, deterministic software and people;
- information, sources of truth and system interactions;
- human approval, authority and durable records;
- exception, failure, fallback and recovery paths;
- risks and implementation prerequisites;
- staged implementation and acceptance measures.
It is a solution-level design, not code-level engineering or implementation.
Not sure which service fits?
Start with the decision, not the package.
If you need to know whether and where to proceed, the Readiness Assessment is normally the right first step.
If you already understand the workflow and need to know how the integration should operate, the Blueprint may be appropriate.
If the request concerns several connected workflows, wider architecture, detailed engineering, supplier assurance or implementation management, Codance may propose a staged or separately scoped engagement—or explain why specialist support or another route is more appropriate.
What is outside both launch packages
- software development or workflow-platform configuration;
- production deployment or production access;
- organisation-wide AI strategy;
- multiple unrelated workflows;
- detailed database or API specifications;
- legal, regulatory, privacy, security or safety certification;
- guaranteed savings, efficiency, revenue or compliance;
- supplier management or ongoing support.
These boundaries protect the usefulness of the work. Some needs may suit a separately scoped Codance engagement; others require specialist providers. A focused engagement can still contain serious thinking when the question and workflow are properly defined.
See what the work looks like
The Westmoor worked example shows how Codance changed the question from “How do we automate quotation generation?” to “What is the safest first integration, and what must be true before we build it?”