or leave a request via the form below — we reply within 30 minutes
A bot answers exactly the way its script was written — and that script is the whole job.
Chatbots and voice scripts
The cost of a ChatGPT subscription and the cost of putting it to work are two different things. You pay the subscription to the service directly; our job is to make the model answer by your rules, know your price list and not invent things that are not in it.
“Buy a chatbot” is how the request usually arrives, but there is no box to buy: a website chatbot is written around your price list, your customers' objections and your enquiry logic. That is exactly how we build AI to order — first we unpack the task, then we assemble the model around it, not the other way round.
A voice bot makes sense where calls are many and much alike: bookings, order confirmations, answers to common questions. The script is written in advance, together with the branches for when a caller says something the robot was not expecting.
The chatbot script is written before the code: on paper you can see straight away where a person will get stuck, where they need a live operator and where one button is enough. Building an AI bot without that step almost always ends in a rebuild. A prompt is designed the same way, except the instruction is written for the model: its role, its limits and what it must not do — otherwise the model starts answering beyond your price list. We consider an AI rollout finished not when the bot replies, but when the team is actually using it: we hand over the instructions and go through the first real conversations together.
What a chatbot costs and what the job includes
“Buy a chatbot” is how the request usually arrives, but there is no box to buy. A bot that answers by your price list and your rules differs from a token bot in exactly one thing: how much time went into the script — what it can do, what it cannot, and what it does when somebody asks something unexpected.
How the work begins
With the script on paper, not with code. On paper you can see immediately where a person will get stuck, where they need a live operator and where one button is enough. Development without that step almost always ends in a rebuild: the bot answers briskly and beside the point, and you end up working out why on real customers.
What gets ordered most often
A website bot that answers common questions and carries a visitor through to an enquiry. A messenger bot that takes orders instead of a manager outside working hours. AI tuned to one specific company task — from sorting incoming messages to drafting standard documents. Instructions and prompts for the team, so that staff use AI the same way rather than each in their own.
What the price is made of
From the number of branches in the script and from where the bot gets its answers. A bot covering ten common questions is one job. A bot that reads your price list, checks availability and creates an order in your system is another: that brings integrations, and with them the handling of moments when an external service is down.
How long it takes
The script takes two or three days, and you see it before development starts. A simple bot takes a week. A bot with a database and integrations takes two to three. We show intermediate results rather than disappearing until delivery day: changing your mind at the script stage is far cheaper than changing it in finished code.
About API keys and paying for services
We never put an AI access key inside an app or a bot — keys get extracted from there, and the bill for somebody else's requests lands on the owner. Requests go through a server and the key stays on it. Where the service is paid, you pay it directly and see the spend yourself rather than through us.
What you get at the end
A working bot on your account rather than ours, the source code, restart instructions and the script as a document. Transfer of ownership is part of the job: the product is yours, and it should not depend on whether we are still answering emails a year from now.
Where to start
Tell us which questions you are asked most often and what a person currently answers. The script grows out of that list — and from the script both the deadline and the price become clear.
Frequently asked questions
Will a bot replace a manager? No. It takes the routine off their plate — questions about prices, deadlines and availability, and enquiries outside working hours. Difficult conversations, negotiation and unusual cases stay with a person, and the script has to know when to call them in. A bot that tries to handle such a conversation itself loses the customer politely and invisibly.
What if the bot answers incorrectly? It can happen, and we design for it: on sensitive branches — enquiries, prices, commitments — the bot relies on your data rather than inventing. Where it is not certain, it openly offers to put the person through to a human. That is better than a confident answer you then have to stand behind.
Do we need an AI subscription? It depends on the task. Some scripts work without one entirely. Where one is needed, you pay the service directly and see the spend yourself; we do not resell access and take no percentage.
Frequently asked questions
How are your prompts different from free collections online?
Ready-made collections are written for an abstract business and then have to work in a real one. We go through your actual tasks and data and build the instructions around them, with examples from your own documents inside. We also write a short guide for staff, so that the prompt is usable by more than the person who commissioned it.
What does launching an AI chatbot cost, and what happens afterwards?
Development is a one-off cost, while the AI charges per request by volume. We work out in advance what a thousand conversations will cost you — that discussion is better had before launch than after the first invoice. If the numbers do not work out, we will say so plainly.
Could our company data leak into the AI?
The knowledge base is stored on your side; only the text of the specific question goes to the model. Major AI providers do not use business-tier data for training. If your information is sensitive, tell us and we will design a setup where such data never leaves your perimeter at all.
Will the bot make things up?
Nobody can rule it out entirely — what matters is how the system is built. We confine the bot to your knowledge base and write in an explicit rule: if there is no answer, admit it and hand over to a person. That is more reliable than trusting that “the model will work it out”.
Will you run the bot afterwards and answer our customers for us?
No — running someone else's accounts on an ongoing basis is not what we do. We build and hand over a working tool together with its documentation; talking to your customers stays with you. We say this up front so it does not come up halfway through the work.
Who will train our staff?
Every job comes with a guide in plain language — no jargon, with screenshots. If you want to go deeper, we have a separate learning app about working with Claude. Answering questions about work already delivered is never charged extra.
