Map the task
Find the inputs, failure points, source systems, approvals, and the simplest useful shape.
Services
Clear packages for turning repeat tasks into working systems.
Start with a mapped task, a focused build, or a wider operating system. Each option has a defined outcome, visible pricing, and a practical handover.
01 Map, build, hand over
Build the loop
Create the first reliable version with prompts, scripts, logs, schedules, and operator controls.
Operational handover
Document the setup, train the owner, and leave a path for future changes and debugging.
Prices and packages
Pick the size of the first step.
Fixed scope
Task Map
£250
Best when you know something should be automated, but the exact build shape is still unclear. This turns one repeat task into a scoped plan.
- One discovery session
- Current process, owner, inputs, and output map
- Failure points, approval moments, and edge cases
- Recommended build shape, tools, and next-step estimate
Most common
First Build
£500
A focused first implementation for one use case. The aim is to prove the task can run with useful controls before it becomes part of the business.
- Task map and implementation plan
- Working automation using real inputs and outputs
- Prompts, logs, review rules, and failure handling
- Run guide plus two review sessions after first use
Larger build
Operator System
£1,000
For work that has more than one step, owner, or system involved. This creates a more complete operating setup around the automation.
- Multiple task paths or departments
- Monitoring, alerts, reporting, and exception handling
- Documentation, owner training, and change notes
- 30-day improvement period after launch
Prices are guide prices for May 2026. VAT, third-party software, model usage, and hosting are separate if they apply.
Optional retainer
Ongoing support from £100/month
For teams that want a light monthly support layer after launch: monitoring, small improvements, fixes, usage checks, and one review call.
Start the conversation
Send the task you want removed from the week.
Useful detail: what happens now, which tools are involved, who checks the output, and what a good result would look like.
Good-fit tasks
Best for work that is frequent, structured, and annoying.
Inbox and intake triage
Classify, route, summarize, and prepare responses while keeping the final send under human control.
Research and monitoring
Watch sources, deduplicate results, score importance, and produce a short decision-ready brief.
Reporting loops
Collect recurring inputs, check them for gaps, and produce a consistent operational report.
Internal coordination
Turn meeting notes, tickets, calendars, and docs into follow-ups that do not rely on memory.
Live system shape Prompts, logs, controls, and owner notes kept visible.
What you leave with
A working setup, not a dependency.
The deliverable includes the task map, prompts, run commands, logs, review rules, failure states, and a short operator guide. The point is simple: your team should understand what the system does and how to change it.