How we work
Six stages, with a decision point after each
- 01
Discovery
We learn how the work is done today, who is involved, and where time or quality is lost.
- A short conversation about the process and its goals
- A look at the tools and data involved
- An early view on whether automation is a sensible fit
- You provide
- Someone who knows the process well, and an hour or two of their time.
- You receive
- A plain-language summary of the opportunity, or an honest view that automation is not the right answer.
- 02
Workflow assessment
We map the process step by step and identify which steps can be automated, which need judgement, and which should stay as they are.
- Step-by-step process map
- Data, access and integration checks
- Risks, constraints and approval points identified
- You provide
- Example cases, sample documents or records, and read access where appropriate.
- You receive
- A workflow map with the proposed automation points and human checkpoints marked.
- 03
Solution design
We agree the scope of a first version, how it will be measured, and what it will deliberately not do.
- Scope, success measures and exclusions
- Architecture and tool choices
- Estimated running costs and a written proposal
- You provide
- Decisions on scope, approval rules and acceptable providers.
- You receive
- A written proposal with scope, approach, timeline estimate and pricing before any build begins.
- 04
Implementation
We build against your real tools in small increments, so you can see progress and adjust early.
- Incremental build with regular reviews
- Integrations configured with least-privilege access
- Logging and alerting included from the start
- You provide
- Access to the systems in scope, and feedback at each review.
- You receive
- Working increments you can try, rather than a single reveal at the end.
- 05
Testing and validation
We test on real examples before anything runs unattended, and record the known limits.
- Testing against representative cases
- Approval rules and failure handling checked
- Accuracy and limitations documented
- You provide
- Representative test cases and someone to review results.
- You receive
- A record of what was tested, what passed, and where human review remains necessary.
- 06
Handover and support
You receive documentation, training for the people who run it, and support terms agreed in writing.
- Operating guide and technical documentation
- Training for the people who use and oversee it
- Agreed support and improvement arrangements
- You provide
- The people who will own the workflow day to day.
- You receive
- A system your team understands, with a clear owner and support scope.
Working principles
What you can expect from us
A written proposal before any build
Scope, exclusions, timeline estimate and pricing are agreed in writing first.
No guaranteed savings
We describe expected effects and how they will be measured, not promised results.
Honest fit assessments
If a simpler tool or a process change would serve you better than AI, we will say so.
Your data, your accounts
We prefer to build in accounts you control, with credentials kept out of code.
Start with discovery
Describe the process you want to improve. The first conversation is about whether automation fits, not a sales pitch.