Understand
We look at the task, the people involved and the tools you already use. We assess whether a simpler process, existing software or a bespoke build is appropriate.
How we work
From the first conversation to the handover, you should understand what is being built, why it is useful and who is responsible.
The shape of every project
We look at the task, the people involved and the tools you already use.
You hold: A written summary of the problemYou receive the scope, deliverables, exclusions, dependencies, price and review points.
You hold: Scope, exclusions and price in writingWe configure or build the solution, test realistic examples and review it with you.
You hold: A tested build you have reviewedWe explain how to use it, document the important details and agree who maintains what.
You hold: Documentation, access and a handoverWe look at the task, the people involved and the tools you already use. We assess whether a simpler process, existing software or a bespoke build is appropriate.
You receive the scope, deliverables, exclusions, dependencies, price and review points. Support and third-party costs are discussed before work begins.
We configure or build the solution, test realistic examples and review it with you. AI outputs and consequential actions need the checks agreed for that workflow.
We explain how to use it, document the important details and agree who maintains what. Further improvements and ongoing support have their own defined scope.
Working principles
AI can make mistakes. We design checking and handover around the decisions your system makes.
We agree what information and permissions are needed, and avoid collecting or exposing data without a purpose.
Ownership, changes, support and any cancellation terms belong in the agreement. No vague promise of unlimited work.
Start with the problem
You do not need a technical brief. Tell us what keeps taking time, getting missed or holding you back.