AI chatbots · Warsaw
I build AI chatbots for business that answer only from your price list, documents and FAQ - on your website, WhatsApp, Messenger, Instagram and Telegram. Every answer shows where it came from, and anything unusual goes to a human with the conversation attached.
24/7
answers, no days off
<5s
avg response time
4 languages
EN · PL · UA · RU in one bot
You are chatting with an AI assistant
The problem
Three ways a business loses someone who was ready to buy, all of them before anyone on your side has read the message.
The message lands at 22:40 on a Saturday. You read it on Monday at nine. By then the person has asked two other companies and one of them replied the same evening. Nobody is angry about it, they just went elsewhere.
A subscription bot answers from a generic script: our team will get back to you shortly. It has never seen your price list, your lead times or your terms, so the customer gets a polite non-answer and closes the tab. That's worse than a plain contact form, because it wasted their time first.
Wire a raw model into a chat with nothing to read and it fills the gaps with plausible fiction: a discount you never offered, a delivery date you can't hit. Then someone turns up with a screenshot of a promise made in your name. A wrong answer costs more than no bot at all.
See it live
A demo built on a made-up price list. Two conversations: the easy one, and the one every vendor demo quietly skips.
Hi, I'm Ava, the assistant on this demo site. Ask about prices, lead times or delivery and I'll answer from the price list I was given.
You are chatting with an AI assistant. A person takes over the moment you ask for one.
A demo on an invented price list for an invented company. Your bot answers from your documents in exactly this shape.
Where the bot lives
Not sure which one is yours? Tell me on a call where the questions actually pile up. If a cheap off-the-shelf widget on a subscription covers it, I'll say that instead of selling you a build.
Answers questions about services, prices and terms from your own documents, and takes a contact when the person is ready.
For services, B2B and anyone with a long FAQ
The same knowledge base answering where people already write to you, with one customer history across all the channels.
For businesses that sell in chat, not on the phone
Product questions, delivery and returns, answered from your catalogue and your policies instead of a canned menu - the same knowledge base as the website widget.
For stores where support drowns in the same questions
Industries
A bot earns its keep where the same questions arrive daily and the answer already exists somewhere in writing. These are the places where that is usually true.
Scope, prices, lead times and what you need from the client before anything starts. The bot quotes the terms as written and leaves the negotiating to you.
Document lists, procedures and current processing times, answered from your own materials in the client's language. No legal advice: anything case-specific goes to the lawyer with the thread attached.
Prices, how to prepare for a visit, opening hours and rescheduling. The bot gives no medical advice and sends anything about symptoms or treatment to reception.
Delivery, returns, sizing and order status, all from your own policies. It won't promise stock or a date your rules don't allow.
Check-in and check-out, house rules, parking, pets and extras in four languages, including the night hours when the desk is empty.
What is in the listing, the paperwork, the fees and what a viewing involves. Anything about a specific deal goes to the agent.
Programme, schedule, price, payment options and what happens if someone misses a class. The bot answers at the hour people actually decide, which is late in the evening.
Service terms, the documents required, shipment status by number and what you do not carry at all. A quote for a specific route goes to a person.
First line on repeat tickets, drawing only on your manuals and procedures. Whatever it cannot close goes to the team with the conversation and the customer's own wording.
A chatbot pays back where the same questions arrive in volume. If you get a dozen enquiries a month and every one of them is different, a bot won't fix anything, and I'll tell you that on the call rather than after the invoice.
RAG over your price lists, pages, policies and FAQ. The bot searches your material first and writes the reply from the passage it found, with a link to the source underneath. Nothing in the knowledge base means nothing invented.
Website, WhatsApp, Messenger, Instagram Direct and Telegram on one knowledge base. Someone who wrote on Instagram and came back on WhatsApp keeps a single history instead of five separate threads.
It takes a name and a contact when the person is ready to talk. The moment it is unsure, or the customer asks for a human, the thread goes over with a short summary of what was asked.
English, Polish, Ukrainian and Russian in one bot, replying in whatever language the question arrived in. You don't maintain four copies of the knowledge base - the answers come from the same sources.
Disclosure in the first message, conversation logs with a retention window you set, personal data masked before the request reaches the model, a data processing agreement signed before I start. Article 50 has applied since 2 August 2026 and it covers any company running a bot that talks to customers.
It loads after the page instead of blocking it, keeps a reserved slot so nothing jumps and CLS stays flat, and waits for your consent banner rather than writing to storage before the visitor agreed to anything. A chat bubble shouldn't undo what you paid SEO for.
Zero risk
Not promises made on a call - clauses in the contract we sign before the work starts.
The number is agreed and written into the contract before I open an editor. If the scope grows past what we planned, we agree a new figure first and I build after that, not the other way round.
Strict citation mode: no passage in the knowledge base, no answer - the bot says it doesn't know and calls a human. Before it goes live I run it against a set of real questions pulled from your inbox and your chat history, and it meets no customer until those answers hold up.
Processing on EU servers, models called through European endpoints, conversations excluded from model training, a data processing agreement signed before the build. Retention and masking of personal data we set on the call, to your rules.
API keys are registered to your company and the provider bills you directly, with no markup from me. Prompts, knowledge base and configuration export in full. Change contractor and the bot keeps answering.
The process
A typical plan for a website bot. Messengers add a week for verification in Meta. Your side of it comes to two or three hours spread across the build.
Thirty minutes on what customers actually ask, how much of it is already written down somewhere, and where the bot should live: site, WhatsApp, Messenger. Then a quote and a contract with the price and the launch date in it.
I assemble the base from your price lists, pages, policies and FAQ, and we go through what is missing or wrong: last year's price list still in circulation, two versions of the same procedure, and the answers that live only in one employee's head. That check usually turns up more than the build itself.
I run the bot against real questions from your inbox and chat, then the awkward ones: typos, half-sentences, off-topic, people fishing for a discount. The same week I wire up the AI Act disclosure, the logs, the handover rule and the widget inside your consent banner.
It goes live on real customers and I read the conversations daily and fix whatever reads badly. At the end you get a report: how many chats, how many contacts left, and which questions your knowledge base still cannot answer.
Pricing
EU agencies: €2,000-8,000
A bot on your knowledge base answering on the site: prices, terms, delivery, the FAQ you retype every week.
EU agencies: €2,000-8,000
Everything the website bot does, plus a proper route to a person and a report on what it could not answer.
EU agencies: €8,000-20,000
The same bot on your site and in messengers, with one customer history across the channels.
EU agency prices are shown for comparison - the same build billed at €100-200 an hour. On top of the build you pay API usage only, roughly €20-60 a month, and there is no mandatory retainer. Changes later are €35 an hour with a one-hour minimum. The final number is fixed after a 30-minute call. Prices current as of September 2026.
Describe the task in two sentences. You get a fixed price, a timeline and a plan. If it isn't a fit for us, we say so straight away and point you elsewhere.
Comparison
All three sit in the corner of a website and open with a hello. The second question is where they part ways.
| Chatbot by buildbyalex | Subscription chat widget | ChatGPT plugin, no knowledge base | |
|---|---|---|---|
| Upfront | €890-1,490 one-time | nothing upfront, it all sits in the subscription | next to nothing, you set it up yourself |
| Monthly cost | €20-60 for API | a subscription that climbs with the number of chats | you pay the model API by usage |
| Knows your prices and procedures | canned replies | guesses from general knowledge | |
| Shows where the answer came from | no | no | |
| Hands over to a human with context | forwards the chat, no summary | no | |
| Website, WhatsApp, Messenger, Instagram, Telegram | depends on the plan | website only | |
| Data in the EU, DPA, conversation logs | read the terms closely | entirely your problem | |
| Knowledge base and prompts stay yours | no, you rent the platform | there's nothing to keep |
If you get few questions and they are simple, a cheap off-the-shelf widget on a subscription is a fine answer and I'll say so. A build starts making sense when the same questions arrive every day and the answers already exist in your documents.
A website bot on your knowledge base starts at €890, a support bot with handover to a human at €1,190, and a bot on the site plus WhatsApp, Messenger and Instagram at €1,490. The price covers assembling the knowledge base, tone of voice, testing against real questions, the AI Act disclosure and the launch. After that the only running cost is API usage, usually €20-60 a month, and later changes are €35 an hour. The final figure is fixed after a 30-minute call, before anything is signed.
A website bot takes 1-2 weeks, the same bot with handover and logs 1-2 weeks, a bot across the site and messengers 2-3 weeks. Messengers are the part that can stretch: WhatsApp needs your business verified in Meta and that queue is not mine to hurry. The clock starts the day I have your documents and site access, and the launch date goes into the contract.
A button bot hands you a menu and breaks on the first question its author didn't think of. An AI chatbot reads a question written in the customer's own words, typos included, finds the answer in your documents and replies in plain language. Someone who types "hi is the blue one still in stock and how much to Gdansk" gets both answers in one reply instead of "please choose an option".
A chatbot answers. It reads your documents, tells the customer what is in them, shows the source and passes the conversation to a person when the question goes past what is written down. An AI agent acts: it creates the deal in your CRM, books the slot in the calendar, issues the invoice, moves the lead through the pipeline. Most companies start with the first and find out later whether they need the second. If the acting part is what you're after, that is the AI agents service, a separate page and a separate build.
Not when it is built on your base and run in strict citation mode. The bot searches your documents first and writes the answer only from the passage it found, with the source shown underneath. No passage, no answer: it says it doesn't know and offers a person. Invented answers come from wiring a bare model into a chat with nothing to read, which is a build decision, not a property of the technology.
It says so and hands the conversation over. The thread lands in your inbox, Telegram or team chat with a short summary of what the customer wants, so whoever picks it up isn't starting from scratch. Every unanswered question also goes into a report, and the ones that keep coming back get added to the knowledge base. After a month or two most of those gaps have closed.
One line of script before the closing body tag, which on WordPress means a snippet plugin or the theme footer. No development on your side: I install it myself if you give me access, or send you the line with a screenshot of where it goes. The same line works on Tilda, Webflow, Shopify, Wix and a custom build. It loads after the page and waits for your consent banner.
Yes, and it is worth knowing what is involved before you plan the budget. Automation runs on the WhatsApp Business API, not the free WhatsApp Business app, and you reach that API through a Meta partner, a BSP. You need a Meta Business account with the business verified and a phone number dedicated to the bot that is not logged into the app at the same time. Replies within 24 hours of a customer writing to you are free; anything sent after that window has to be a template Meta approved in advance, and Meta bills those per conversation, straight to your account. Verification usually takes a few days, which is why the multi-channel build is 2-3 weeks rather than one.
Conversations are processed on EU servers and models are called through European endpoints. Nothing sent to the model is used to train it, personal data is masked before the request leaves your perimeter, and you decide how long chat logs are kept. I sign a data processing agreement before the build starts, and your privacy policy gets a line saying that AI processing happens and which provider sits behind it.
Article 50, the transparency part, has applied since that date, and it covers any company running a bot that talks to customers, one-person businesses included. Four things in practice: the bot tells people it is an AI at first contact, not in grey text in the footer; its purpose is described; conversations are logged; and there is an obvious way to reach a human. You can give the bot a name, you just cannot pass it off as a named employee. All four are built in by default, and I also retrofit bots that went live before the rules did. I'm a developer, not a lawyer - for anything borderline, take EU-law advice.
Not if it's loaded properly. The script goes in after the page has rendered rather than blocking it, the bubble keeps a reserved slot so nothing jumps and your CLS stays where it was, and the widget waits for the consent banner instead of writing to local storage before the visitor has agreed. Most subscription widgets do none of this, which is how a site that scored well in PageSpeed ends up slower a week after the chat went in.
Yes, and in Russian as well. One bot, one knowledge base, replying in the language the customer wrote in. You don't need four copies of your documents: the answers come from the same sources whichever language the question arrives in. That matters most for hotels, clinics and legal services in Poland, where the same week brings questions in all four.
API usage, typically €20-60 a month, and €30-80 once you are past a thousand conversations a month on a cheap model. There's no mandatory retainer: if nothing needs changing, you pay me nothing. Changes later are €35 an hour with a one-hour minimum, and updating a price in the knowledge base is usually well inside that hour.
That's the normal starting point. Almost nobody hands over a tidy knowledge base - what exists is a price list in Excel, a policy nobody has opened since 2023, and the real answers living in someone's head and in the sent folder. I pull the base together from what you have, flag the contradictions (two different lead times for the same service is the usual one) and ask you the ten or fifteen questions only you can answer. That is the part of the project that needs your time, and it comes to a couple of hours spread across the build.
Yes. API keys are registered to your company from day one and the provider bills you directly. Prompts, the knowledge base and the configuration export in full, and the code lives in your repository rather than on my machine. Hire someone else and the bot keeps answering while they read the documentation.
What clients say
A few words from founders and teams we've shipped for.
Launched our store in 11 days - multilingual, fast, and already on page one for three of our main keywords.
The Telegram bot handles the first conversation with every lead now. My sales rep only steps in when the deal is hot.
Leads land in our CRM with every field already filled. No more copy-pasting from chats - the pipeline moves itself.
Shipped to the App Store and Google Play in three weeks. The handover docs let my team take it from there without me.
Set up our Google and Meta ads from zero. Cost per lead dropped by about a third in the first month.
He rebuilt the site and six weeks later ChatGPT was recommending us by name. Didn't know that was even possible.
Free 30-minute call. No sales pitch - just a real conversation about what you need and whether we're the right studio to build it.
No sales pitch - just a clear read on your scope.
