An assistant that knowswhat it does not know.
This sits beside the ladder rather than on it. An assistant is only as good as the material underneath it, so it attaches to a build — and it is evaluated against real questions with known answers before it ever faces a visitor, refuses when it has no basis, and hands over to a person.
What it costs
Three tiers, each a starting figure rather than a fixed one — what is already underneath the assistant moves the number, the same way the build ladder does. Every one of them is evaluated before release and reviewable afterwards.
Assistant
Grounded in the site itself — its pages and the documents you give it.
from€350
Answers out of your own pages and documents, and says so when it cannot. A visitor gets the answer that is actually written down rather than a plausible one.
- Grounded in your pages and documents, not in general knowledge
- Refuses when it has no basis, and hands over to a person
- Evaluated against real questions with known answers before release
- Conversations reviewable, so the material behind it gets corrected
- A visible boundary: it never invents a price, a date or a policy
Assistant + Records
Grounded in the system behind the site as well — live records, not a snapshot taken at launch.
from€600
The same assistant, reading the records the site already runs on — products, bookings, entries — so what it says is what the system currently holds.
- Everything in Assistant
- Reads the live records behind the site, not an export of them
- Answers stay current when the records change, with nothing to re-upload
- Enquiries captured straight into your admin, with the conversation attached
- Access rules enforced on the server: it can only read what that visitor could
Automation
Work that happens without anybody pressing anything.
from€900
Workflows that run on their own: an enquiry arriving becomes a record, a message and a task, and a job that fails tells somebody rather than failing quietly.
- Everything in Assistant + Records
- Lead intake routed to inbox, sheet or CRM as it arrives
- Document handling — read, filed and passed on without retyping
- Scheduled jobs with failure handling, so a silent failure is not possible
- A written map of every workflow you own, which you keep
All prices exclude VAT.
True of every tier
Evaluated before it is seen
A set of real questions with known answers, run against the assistant before release and again after every change to the material. An assistant that has never been tested is a demo.
It refuses
Where there is no basis in your material, the answer is that it does not know and here is a person. That refusal is the feature — an assistant that always answers is an assistant that sometimes invents.
Reviewable, not opaque
The conversations are yours to read. That is how you find the questions your site does not answer, which is worth having even in the months nothing goes wrong.
A person at the end of it
Handover is designed in, not a dead end with a form. The assistant exists to answer the easy nine and route the tenth, not to stand between a buyer and you.
Your material stays yours
The documents and records it reads are yours, and so is the written map of what runs where. Nothing here is a black box you would have to rebuild from scratch elsewhere.
It attaches to something real
This runs on a build we can see and keep — which is why it is priced beside the ladder and not on it, and why it needs a retainer under it.
How it runs
- [ 01 ]
Material
What the assistant is allowed to know: which pages, which documents, which records, and — just as important — what is deliberately out of scope. Written down before anything is built.
- [ 02 ]
Evaluation set
Real questions with known answers, written with you, including the ones it must refuse. This is what separates an assistant from a demo, and it comes before the build rather than after it.
- [ 03 ]
Build and grounding
Wired to the material, with access rules enforced on the server so it can only read what the visitor asking could. Then run against the evaluation set until it passes it.
- [ 04 ]
Review
Conversations read, gaps in the material fixed, the evaluation set re-run. That is the monthly work the retainer covers, and it is why there is no version of this without one.
Questions
Why does it need a retainer?
Because the work does not stop at launch. There are model costs every month, the evaluation set has to be re-run whenever the material changes, and somebody has to read the conversations and fix what the site failed to answer. An assistant left alone for a year is answering out of last year’s prices. Care or Active covers that, which is why one of them is a condition rather than a suggestion.
Can it make something up?
It can be made much harder, and that is what the grounding and the evaluation set are for: it answers out of your material, it is tested against questions whose answers are known, and where it has no basis it refuses and hands over. What we will not tell you is that it is impossible — anyone who does is selling. What we will do is show you the evaluation results before it goes live and keep the conversations readable afterwards.
Can I have one without a website from you?
Not usefully. The assistant is grounded in a site and the records behind it, so if we did not build that we have no material to ground it in and no way to keep it current. If you have a site you are happy with, the honest answer is that the first job is the site, not the assistant.
What can the automation tier actually do?
The ordinary work that currently costs somebody an hour a day: an enquiry becoming a record, a message and a task without retyping; documents read, filed and passed to whoever needs them; jobs on a schedule that report when they fail instead of failing quietly. It is deliberately unglamorous, and you get a written map of every workflow so you know what runs, when, and what happens when it does not.
Where does the data go?
The material stays in your system. What goes to a model is the part of it needed to answer the question in front of it, and we tell you which model, where it runs and what is retained before anything is wired up — written down rather than described in a call.
Start with the questions you answer twenty times a week.
No sales pressure and no generic proposal. Tell us what you are trying to build and you will get a straight technical read on it and a clear next step.