Consulting service
Workflow Automation Implementation
Building the automation an assessment established as practical, including what happens when it fails, plus handover documentation.
What you need to know first
- What problem does this solve?
- An assessment has confirmed which steps can be automated and how, and now it needs building — correctly, with failure handling, and in a way your team can operate without the person who built it.
- What exactly do I receive?
- A working automation for the agreed workflow, with the human decision points preserved where they belong, defined behaviour when a step or a system fails, a record of what it did, and documentation your team can operate from.
- How is it priced?
- Custom quoteThe fee is quoted for your requirement, because scope, systems and complexity differ in every case.Quoted from the assessment findings. The effort is determined by how many systems are involved, what they support, how many exceptions the process has and how clean the existing data is — so a published figure would be a guess in either direction.
- How long does it generally take?
- Confirmed in the written scopeStated in the written scope, from the assessment findings. Dependent on access being granted and on third-party platforms behaving as documented.
- What happens next?
- Send an enquiry describing the requirement. We confirm whether an assessment is the right starting point, then set out its scope and fee in writing before any work begins. An enquiry is not an order: an engagement becomes binding only when it is expressly accepted, as set out in the Terms of Service.
Deliverables
- The working automation for the agreed workflow
- Human decision points preserved where the assessment said they belong
- Defined failure handling: retries, alerting, and what a person must do
- An audit record of what the automation did and when
- Handover documentation covering operation, failure modes and how to change it
Included
- Implementation of the agreed automation
- Connections to the systems in scope
- Failure handling and duplicate protection
- Testing against real cases, including the documented exceptions
- Two adjustment rounds after go-live
- Handover documentation
Not included
Stating the boundary is part of the offer. Anything here can usually be arranged separately.
- The assessment — an implementation is not quoted without one
- Software licences, subscriptions or platform fees, which stay in your accounts
- Ongoing operation, monitoring or support, unless separately scoped
- Automating steps the assessment identified as needing a human decision
- Any guarantee about a third-party platform continuing to offer the access this depends on
- Staff training beyond the handover, unless separately scoped
Customer prerequisites
- A completed assessment with specific, implementable findings
- Scoped access to the systems involved
- A named owner on your side who will operate the automation afterwards
Information and access we need
We will ask for these. Where the work needs access to a system, access is arranged and scoped with you rather than assumed.
- Scoped credentials issued through your own identity and access management
- A test or sandbox environment, where one exists
- Confirmation of the agreed exceptions and how each should be handled
- Who receives alerts when the automation needs a person
Expected process
Assessment first
An implementation is quoted from an assessment, not from a description. If no assessment exists, that is the starting point.
Written scope and fee
What will be built, what is excluded, the revision allowance, the indicative timescale and the fee — agreed in writing before work starts.
Access and environment
Scoped access is arranged through your own identity and access management. We work in a test environment where one exists.
Build and review
Implementation with review points, so you see it working against real cases rather than at the end.
Handover
Documentation of what was built, how it behaves when something fails, and what you need to know to operate it.
Meetings, revisions and scope
- Meetings
- Meeting optional, at the delivery review (about 60 minutes)
- Revisions
- 2 revisions included. Two rounds of adjustment after the automation is running against real cases. New steps or new systems are a scope change.
- Scope
- Deliverables are limited to those expressly included in the agreed scope. Additional revisions, meetings, research or services outside that scope may require additional fees — see the Consulting Terms.
Frequently asked questions about this service
What happens if a proposed implementation is not feasible?
You are told, with the reason, and you are not charged for an implementation that cannot be delivered.
This is the main reason the Consulting catalogue separates an assessment from an implementation. The assessment is the paid piece of work that establishes whether something is practical, what it would take, and what it would cost. Its output is useful even when the answer is "not this way": it will say what does work, what the blockers are, and what a smaller or different change would achieve.
Where a recommendation depends on software, platforms, vendors, APIs or external suppliers, their availability and their decisions are outside our control — stated in Third-Party Dependencies.
What kinds of workflows can you automate?
The recurring, rule-based ones that currently depend on somebody remembering: moving information between systems, producing and circulating a document, routing something for approval, generating a recurring report, keeping two records in step, triggering a notification when a state changes.
What is deliberately not automated is judgement. A good automation keeps the decision with a person and removes the clerical work around it, which is also what makes it safe to operate when something unexpected arrives.
Feasibility is established by an assessment rather than assumed up front — Workflow Automation Assessment.
Will you need access to our systems?
For most Consulting work, some access is needed — but it is scoped and agreed with you, never assumed. Each service page lists what it needs under "Information and access we need".
The principle applied is least privilege and shortest duration: read-only where reading is enough, a sandbox or test environment where one exists, access limited to the systems in scope, and removal at the end of the engagement.
The Consulting Services Terms record that the client provides reasonably necessary access and credentials, and that each party will use reasonable safeguards for confidential information received in connection with the engagement.
Why do some services require a quote?
Because their effort is determined by your environment, not by our method. An implementation depends on how many systems are involved, what those systems support, how clean the existing data is, how many exceptions the process has, and who has to approve what.
A published figure for that kind of work would be a guess, and a guess in a price list is either too high for the simple cases or a source of change requests for the complex ones. Quoting it means the number you receive describes your requirement.
A quote-required service never displays a price on this website — not a "from" figure, and not a zero.
Next step
Reference workflow-automation-implementation is added to your enquiry automatically so it reaches the right place.