One workflow, done properly. A fixed price at every step.
AI and automation consulting, done in fixed-price steps: from a free conversation to an operating workflow. Nothing is built without a written scope, and the outputs of Discovery are yours whether or not you build with us.
Thirty to forty-five minutes. No deck, no obligation.
Tell us how the work happens today, where the effort goes and what your team could be doing with the time instead. We decide together whether there’s something worth investigating properly.
Good things to bring
A request that needs the same investigation every time
A report that leaves no room for the analysis
A process that depends on somebody remembering every detail
Start with an anonymised example. We agree a secure route before any confidential information is shared.
The current-state workflow and its pain points, including the exceptions your team handles by instinct. The industry rules, accreditations and customer commitments it must respect. A measurable baseline: time, volume, rework, cost, delay.
02
What should change?
An automate, augment or leave-with-people assessment, the target workflow design, and the responsibility and human-review boundaries that go with it, paced to what your team can absorb.
03
Can it be built?
Systems, data and access requirements, technical feasibility and the likely approach, and the risks, dependencies and exceptions that would need handling.
04
How much time comes back?
The capacity we would expect to release, measured against your baseline, the commercial case behind it, and an implementation scope with a fixed-price proposal.
05
What is the time for?
A plan for the capacity released: what the team wants to do with it, who owns that change, and how we will know whether it happened.
Step 03 · Complete
Build around your business. Nothing without a written scope.
Quoted per workflow from the Discovery & Design output, at a fixed price.
Existing systems first
Where practical the work runs in the background or appears in familiar tools. Where it can live in Microsoft 365, your CRM or your service-management platform, that’s where it starts. Reusing what you have reduces additional software, training and administration.
Controls and compliance from the start
Permissions, validation, review points and recovery are part of the build, not added afterwards. The accreditation and audit requirements agreed in Discovery are designed in and tested. Missing information, failed connections and uncertain outputs follow an agreed exception route.
You receive
A tested operational workflow with agreed controls, documentation and a named owner.
The technology follows the requirement
APIs
Power Platform
Python
AI
RPA
Lightweight interfaces
Step 04 · Operate
Keep it dependable. Prove it’s holding.
Optional, and agreed separately. The workflow keeps running as your business changes, and the hours returned stay measured against the original baseline.
01
Monitor
Check that integrations, automations and AI-assisted steps run as expected.
02
Handle exceptions
Surface failed runs, unusual inputs and missing access to the right person.
03
Maintain
Update connections, rules, prompts and logic as the business changes.
04
Measure
Track hours returned against the original baseline, so you can see the improvement is holding.
05
Improve
Use live evidence to refine the workflow and find the next worthwhile change.
06
Agree it explicitly
Scope, service windows, ownership and change allowances, in writing.
Transparent from the first conversation.
The conversation is free. Every paid step has a fixed fee or a written scope before work begins.
Where most engagements begin
Discovery & Design
£2,500 + VAT, fixed
Two to three weeks
One priority workflow, taken apart and put back together on paper.
Do we have to build with you after Discovery & Design?
No. The outputs are yours whether or not you build with us. If the economics do not stack up, the recommendation will say so.
Will you replace our software?
Rarely. Existing systems come first. Where the work can live in Microsoft 365, your CRM or your service-management platform, that is where it starts, which keeps additional software, training and administration down.
What technology do you use?
The technology follows the requirement: APIs, Power Platform, Python, AI, RPA and lightweight interfaces, chosen for what the workflow needs rather than what is fashionable.
How do you handle confidential information?
Start with an anonymised example. We agree a secure route before any confidential information is shared, and permissions are limited to what the workflow needs.
How do you measure success?
Against the baseline taken in Discovery: time, volume, rework, cost and delay. We do not promise savings from website-level assumptions.
What if something goes wrong once it is live?
Missing information, failed connections and uncertain outputs follow an agreed exception route to a named owner. With Operate, we monitor, handle exceptions and maintain the workflow as your business changes.
What would your team do with their time back?
A free conversation, thirty to forty-five minutes. No deck, no obligation.