How We Deliver
A simple method that keeps cost and risk low. Five stages, from a free call to a handover that leaves you free to carry on without us.
Why a method matters
AI projects go wrong in predictable ways. The goal is vague, so nobody can say whether it was met. The scope grows without anyone agreeing to it. Results arrive all at once, at the end, when it is too late to change direction. And when the work is done, the client cannot run or change what was built. Our method is designed to prevent each of these: a clear goal first, a written scope, small stages with visible results, a check against what was agreed and a handover that leaves you in control.
The method
- 1
Free ROI call
We learn the goal and tell you honestly if we can help. We ask how the work flows today and where the time goes.
- 2
Scope
A written scope, a fixed price where possible and the cheapest option first. It says what is included, what is not and how success will be measured.
- 3
Build in small steps
You see working results early and often, so you can correct course while it is cheap.
- 4
Check
We test against what was agreed and review with you. If something falls short, we say so.
- 5
Hand over
You get the work, documents and training. You are not locked in.
What you receive at each stage
| Stage | What you get |
|---|---|
| Free ROI call | Three opportunities, a rough view of return and our honest opinion |
| Scope | A written scope and quote, with exclusions and assumptions |
| Build | Working results at each stage, and a say in what happens next |
| Check | A review of results against the measure agreed at the start |
| Hand over | Documentation, training and the ability to carry on without us |
Principles
- Cheapest workable option first.
- Plain language.
- No surprises on price.
- A person stays in control of AI.
- Limited access to your systems, agreed in writing.
- A clear measure of success, set at the start.
How we scope
A good scope is short and exact. It names the task, the systems involved, the people who will use the result and the measure of success. It lists what we will deliver and what we will not. It states our assumptions, such as the state of your data, and says what happens if an assumption turns out to be wrong. We write it so that someone who was not on the call could read it and know what to expect. If a scope cannot be written clearly, the project is not ready, and we say so.
How we run the build
We build in short stages. Each stage ends with something you can see and test. We ask you to look at it, and we adjust before moving on. We keep you informed of what we are doing and of anything unexpected. If we find that the cheapest route has changed, for example because a simpler tool would do, we tell you, even if it reduces the work. If we reach a point where continuing is not sensible, we say so and agree what to do.
How we hand over
Handover is part of the work, not an afterthought. We document what we built in plain language, show your people how to run it and agree what support, if any, continues. We make sure you have access to what you need, and we remove our access to your systems unless you want us to keep it. You should be able to change, extend or replace what we built without needing us. If you want ongoing help, we can quote it, but it is your choice.
A worked example (illustrative)
This is invented. A small firm wants an assistant that answers staff questions from its policy documents. On the free call we agree the goal and ask who will use it. The scope names thirty documents, one chat tool and a measure: staff find the answer in under a minute in most cases. In the first stage, we build a version with ten documents. Staff try it and find that two answers are wrong because the documents contradict each other. The firm fixes the documents. In the second stage, we add the rest. We check against the measure and show the results. At handover, we give the firm a short guide to adding documents. The firm runs it from there.
Pricing
Contact us for pricing. A fixed scope and a fixed price are our preference. Where that is not possible, we agree a limit before work starts. Nothing paid begins until you have read and approved a written quote.
Questions to ask any supplier about how they work
- How will I know what has been done, and what remains?
- How are changes agreed and priced?
- Who will do the work, and who will I talk to?
- What do I receive at the end, and can I run it without you?
- What happens if either of us wants to stop?
What we ask of you
The method works best when you take part. We ask for access to the people who understand the work, a timely answer to questions and honest feedback on results. We ask you to tell us early if priorities change, and to review what we show you rather than assuming it is right. And we ask you to name someone who can make decisions, because projects slow down when nobody can say yes. The more engaged you are, the cheaper and better the result tends to be.
Delivery questions
What if I want to stop part-way?
Usually you can. Work is staged, and the quote says what each stage delivers.
Who owns what you build?
Ownership and license terms are written into each proposal. Please read them before you approve.
Do you work on site?
Please ask. How we work with you is agreed as part of the scope.
How do you handle changes?
We agree them with you before doing the work, and quote them as changes.
Find out what AI would cost you
Book a free call. We will map three opportunities and give you a rough idea of cost and payback.