Process first. Then the tool. Then the price of the next step.
We don’t start by rebuilding your whole business. We start with one process, check it on real examples and only then extend it. You can stop at any stage.
Five steps of working together
- 1
£0first conversation
Discovery
You describe a process that eats time today. We check whether it suits automation and what the first step should be.
Result: change nothing, map the process, or go straight to a build.
- 2
£395map one process
Process map
We describe the process from input to result: data, rules, exceptions, who is responsible, integrations and acceptance criteria.
Result: a build plan — or a clear explanation of why it isn’t worth it right now.
- 3
from £1,450build one process
Build and test
We build an agreed, limited scope and check it on sample data and failure scenarios.
Result: you know what the system does on its own, when it hands over to a person and what gets built.
- 4
Included in the buildcontrolled launch
Controlled launch
The system goes live in a limited scope. Your team sees every step, and exceptions go to a named person.
Result: the process works in real work, not only in a demo.
- 5
support from £195 a monthstabilise and extend
Stabilise
We fix bugs, respond to changes in your tools, and only then extend the scope to new situations.
Result: the system still has an owner after launch.
“Let’s do something with AI” is not a process.
Automation works where the work repeats and someone owns the result. Elsewhere the process needs sorting first — and a spreadsheet is sometimes cheaper than a language model.
Where we start
- The same kind of job comes back every week.
- The data passes through a phone call, an email, a document or a system.
- Someone is named to decide when an exception turns up.
- The process can be checked on a handful of real examples.
Where we tidy up first
- Everyone does the same job slightly differently.
- Nobody knows who owns the result.
- There is no data or no examples for a safe test.
- The only requirement is “let’s do something with AI”.
Questions about working together
Do I have to start with a process map?
No — not if the process is well documented, the data is available and the scope is clear. Otherwise the map fixes the scope and the acceptance criteria before you pay for a build.
Who on my side needs to be involved?
Someone who knows the process and can decide about exceptions. For the map and the tests we need real examples: emails, documents or requests.
What if the map shows it isn’t worth it?
You get that in writing, with the reason. That’s a result too — usually cheaper than a system built to solve a problem you don’t have.
How long does a build take?
It depends on the data, the integrations and the number of exceptions. We give a specific timeline after the process map, in the proposal.
When do I see a price?
Before every paid stage, in writing. Nothing starts until you have agreed the scope and the figure.
Does this apply to the £79 package too?
No. The AI receptionist package has a fixed scope and price — no process map needed. See the AI receptionist.
The first step costs £0.
Describe the process. If it isn’t worth automating, you’ll hear that in the first conversation.
Or call +44 7822 000220 · email info@sitco.uk