The first field is the hardest
«Describe your task» is a blank sheet with a deadline. Most people close the page there — not because they lost interest, but because they did not want to write an essay in a text box on a Tuesday evening.
Ari asks a visitor one question at a time, the way a good manager would — and by the end of the conversation you have a filled-in brief, a contact and a registered account instead of a line that says «hello, how much for a website».
Tell me what you do — and what should happen after the launch?
A cafe in Gyumri. We want to take orders online
Got it. When do you need to launch, and is there a budget frame?
In a month, the budget is open to discussion
It is not that people are lazy. A form asks a person to formulate a task they have not formulated yet — and then punishes them for it with eight empty fields.
«Describe your task» is a blank sheet with a deadline. Most people close the page there — not because they lost interest, but because they did not want to write an essay in a text box on a Tuesday evening.
«Need a website, how much?» costs you two days of clarifying letters before you can name any figure at all — and half of those conversations die inside those two days.
The usual widget either answers questions nobody asked or invents a price it has no right to name. A conversation that ends with a figure you then have to walk back is worse than no conversation.
Four steps. The visitor sees only the first two — the rest happens on your side and is the reason the product exists.
Not with «how can I help you» but with a question about the person's business, in the language of the page they are reading. The first answer is a click, not typing — that is the whole difference in whether a conversation starts at all.
One question at a time, in an order that makes sense: what the business is, what has to happen, when and roughly for how much. A person answers that in three minutes and never feels interrogated.
When the person steps off the script — asks about a case, a technology, a guarantee — the answer comes from the model on your knowledge base. And when the model is unavailable, the scripted path keeps working: the request still gets collected.
The conversation turns into a brief, the brief into a request in the panel, and the person into a client with a cabinet where the correspondence continues. Nothing has to be re-entered — for you or for them.
The point is not the model. The model is a component you can change; the value is in everything that happens around the conversation.
The questions, their order and the answer options are yours: a studio, a clinic and a builder need different things from a first conversation. Editing the script does not require a developer.
Armenian, Russian and English, and the conversation switches together with the page. Not a translation layer bolted on afterwards — the script exists in all three from the start.
Along with the answers you get the whole conversation, the pages the person read before it and where they came from. A manager opens the request already knowing what to say.
At any moment, on the visitor's word or on your manager's, the conversation moves to a live person in the same window — with the history already in front of them, so nothing has to be repeated.
The name, the greeting, the degree of formality and the colours are settings. Ari should sound like your studio, and a visitor should never suspect they are talking to a widget bought off a shelf.
The provider is down, the key expired, the limit ran out — the scripted path continues and the request is still collected. A sales channel that depends on somebody else's uptime is not a sales channel.
An assistant on the first screen speaks on behalf of your company. Three rules below exist so that it never says anything you would have to retract.
Estimating work is your job, not a model's. Ari collects what is needed for an estimate and hands it over — a figure said in a chat is remembered as a promise, and there is no arguing with it later.
It says what it is from the first line. Trust lost at the moment the truth comes out costs more than the conversation it bought — and it always comes out.
They are stored in your CRM, not in someone's cloud service. If the model runs on your own hardware, the whole loop closes inside your network — nothing about your clients leaves it at all.
Ari lives inside Arevian CRM — the requests have to land somewhere. It can also be put on a site you already have.
For those who already keep their clients with us: the requests are already going to the right place.
When the site is not ours and the requests have to go where you already read them.
When conversations with clients are not allowed to leave the perimeter at all.
Ari collects our own requests every day. What is ahead is making the script something a client can edit without us.
Live on arevian.studio: the script, the live model, the brief, registration and the handover to a manager.
A script editor in the panel: questions, options and branches without a developer.
Voice and appearance settings, embedding into sites that are not ours, a Telegram version of the same conversation.
Analytics of the conversations themselves: where people stop answering, which question loses them, what they ask that the script has no answer for.
By what it is for. A chatbot answers questions; Ari asks them. Its goal is not to satisfy the visitor's curiosity but to end the conversation with a brief, a contact and an account — and that changes every design decision inside it.
It does not open by itself, does not chase the cursor and does not interrupt reading. It is a circle in the corner that waits to be clicked. An assistant that jumps out on the third second is not a sales tool, it is a reason to leave.
Whichever you point it at: GigaChat, YandexGPT, anything OpenAI-compatible, or a local one on your own hardware through Mimir. Changing the provider is a setting, not a migration — and the scripted part works without any model at all.
It says so and offers to bring in a person — and that conversation shows up in the panel with the whole history. Making something up is the one thing it is not allowed to do, and that rule is not a setting.
You are on a page where it is running. Talk to Ari the way your own client would, and see for yourself where the conversation ends up — that is a better test than any demo we could arrange.
The circle in the corner is Ari. Start the conversation the way a client of yours would start it — and if you want the same thing on your own site, tell him that too. He will collect the brief himself.