OH/02 · Services
Choose a mapping sprint, a focused build or a wider operator system. Each option has visible scope, pricing and handover.
METHOD.01 · Working sequence
Each layer names the decisions, operating controls and owner material needed by the next.
Name the trigger, inputs, owner, approvals and failure states.
Create a narrow loop with review, logs and clear stop conditions.
Leave the prompts, logs, run instructions and change notes with the owner.
SPEC.02 · Packages
Scope expands only when the task needs it. Every option states the work and the owner outcome before implementation begins.
£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.
The process map and build recommendation, so the next decision is clear before implementation starts.
Focused implementation
£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.
Prompts, run instructions, logs, review rules, failure states and owner notes.
£1,000
For work that has more than one step, owner, or system involved. This creates a more complete operating setup around the automation.
Prompts, run instructions, logs, review rules, failure states and owner notes.
from £100/month
For teams that want a light monthly support layer after launch: monitoring, small improvements, fixes, usage checks, and one review call.
Monitoring, small improvements, fixes, usage checks and one review call.
Guide prices. VAT, third-party software, model usage and hosting are separate where they apply.
TOL.03 · Good-fit tolerance
The first boundary should be useful enough to test without hiding uncertainty inside a larger programme.
A useful first candidate has a named trigger, repeat inputs, an expected output and a person who can review it.
The task happens often enough for repeatability to matter.
The trigger, inputs and expected output can be named.
A person can inspect the result and approve what happens next.
The first useful boundary is small enough to map and test.
OWN.04 · Handover packing list
First Build and Operator System leave the operating material needed to run, inspect and change the system.
Task Map ends with the process map and build recommendation, so the next decision is clear before implementation starts.
ENQ.01 · Enquiry handover
Tell me what happens now, which tools are involved, who checks the output and what a useful result would look like.
If the form is unavailable, email Oliver directly at oliverhitch2008@gmail.com.
