Most enquiries don't arrive during office hours. They arrive at 21:40, from someone comparing three suppliers in one sitting, and the one who replies first usually wins. A Superbot answers immediately, in your words, and aims to book the meeting while the visitor is still on the page.
The default website chatbot does the opposite. It answers from a generic model, invents details it has no basis for, can't see your pricing or availability, and hands the visitor a form when they ask anything real. Buyers have learned to close it on sight.
| What Matters | Standard Chat Widget | A Superbot |
|---|---|---|
| How it decides | Fixed decision-tree branches | Reasons over your actual content, live |
| What it knows | A short predefined FAQ list | Your full site, documents and pricing rules |
| Qualifying leads | A form dressed up as chat | Scores fit and intent as the conversation happens |
| What it can do | Sends messages, nothing else | Books calls, creates CRM records, escalates |
| How it sounds | Generic, off-the-shelf tone | Trained on your brand voice |
| Tier | What's Included | Investment |
|---|---|---|
| Core | One knowledge base, one site. CRM and calendar integration, lead qualification and booking, monthly retraining. | €500 setup+ €1,000/month |
You're not buying a launch — you're buying something that answers every enquiry at 21:40 for as long as you keep it running, so the price sits where the work actually is. At €1,000 a month, Core costs around €33 a day. If your average job or contract clears that, work out what one recovered enquiry a month is worth to you, and judge it against that. It covers the nights and weekends nobody is staffing.
Running multiple bots across departments, locations or languages? That's scoped on the audit — the architecture is the same, the volume isn't.
Every answer is grounded in source material you approved. Where the bot doesn't know, it says so and routes to a human instead of improvising — which is the single most common way chatbots damage trust. Conversation data runs under a data processing agreement, behind your existing consent settings, and is never used to train public models.
The same architecture, three common jobs. Which one matches how buyers actually reach you:
A Superbot is trained on your own material — site, documents, product data, pricing rules — and connected to your CRM so it can book, qualify and hand off. A widget chatbot answers from a generic model and forgets you the moment the tab closes.
Typically two to three weeks from kickoff: one week to structure the knowledge base, one to train and test, then a supervised soft launch before it handles traffic unattended.
It says so and hands off. We'd rather it route a visitor to a human than invent an answer — every response is grounded in your approved source material, and anything outside that scope escalates instead of guessing.
Yes — booking, CRM record creation, lead scoring and hand-off are the point. A bot that only answers questions is a search box with a personality.
Conversations are processed under a data processing agreement, hosted in the EU where the stack allows, and the bot runs behind your existing consent settings. We don't train public models on your customer conversations.
Hosting, model costs, monitoring and monthly retraining as your offer changes. A bot left untouched for six months starts giving out last season's answers — the monthly is what stops that.
A free AI visibility audit, back within 48 hours: your technical SEO health, how ChatGPT, Perplexity and Google AI Overviews currently describe your business, and the three fixes we would prioritise first. Specific to your site, and yours to keep whether or not we work together.