AI agents in Brussels: what it changes for a small business
Flows Studio is based on avenue Louise, in 1050 Brussels, and deploys AI agents for Belgian small and medium businesses. A Brussels base changes three concrete things. The agent answers by default in French, Dutch and English, because Brussels customers arrive in all three without warning. The contract is Belgian, with a GDPR data processing agreement, a public sub-processor register and conversation storage inside the European Union. Scoping meetings can happen on site, which matters when you need to watch a front desk actually work. Pricing, on the other hand, does not depend on the municipality: €350 setup and €100 per month for an FAQ widget.
What proximity really changes, and what it does not
A conversational agent is deployed remotely, technically speaking. Proximity does not make the software better, and it would be dishonest to pretend otherwise. What it changes sits before and after go-live, at the two moments where projects usually fail.
- Scoping. Half of what a front-desk agent answers is written nowhere: who handles what, what you never promise on the phone, how you phrase a refusal. An hour on site surfaces more of that than any questionnaire.
- Applicable law. The processing agreement is governed by Belgian law, the competent authority is the Belgian Data Protection Authority, and the contract is in your own language. If there is a dispute, nobody has to litigate abroad.
- Availability. An incident on a public widget is handled within the working day, in the same time zone, with the same public holidays. That sounds anecdotal until the first bug on a Friday afternoon.
What proximity does not change: the price, the quality of the language model, and the need for a written knowledge base. An agency selling you proximity as a technical argument is selling you nothing.
Three languages are not optional in Brussels
This is the most measurable difference between an agent deployed for a Brussels business and the same agent deployed elsewhere. A visitor may open the same page in French, Dutch or English, and sending them to a single-language form is enough to lose the enquiry.
Agents we deploy in Belgium offer Dutch, French and English by default, derived from the country of the business rather than from the language of its website. A Spanish company gets Spanish and English, a French company gets French and English. The rule lives in the code, not in an editorial guideline, so it does not get lost from one deployment to the next.
What a Brussels business deploys first
In practice, two needs come up before all others, and they map to two distinct agents.
| Need | Agent | Setup | Monthly |
|---|---|---|---|
| Repetitive questions on the public site | FAQ Widget | €350 | €100 / mo |
| An inbox that keeps overflowing | Email Secretariat | €500 | €240 / mo |
Amounts excluding VAT, generated from the same grid that produces our quotes. Setup covers the knowledge base, tone calibration and testing, not just installation.
The choice between the two is not a budget decision but a question of where the load actually sits. If the phone rings about opening hours and prices, it is the widget. If the load is in quote request emails, the widget will not touch it.
Pricing does not depend on the municipality, the return does
We apply the same public grid in Brussels, in Wallonia, in Flanders and abroad. What varies from one business to the next is the return, because it depends on a volume and an hourly cost that are specific to each.
The method comes down to three numbers: how many requests per month, how many minutes each one costs today, and the loaded hourly cost of whoever handles them. A hundred repetitive questions a month, at five minutes each, is eight hours of work. Against a €100 subscription, those eight hours compare directly. We set out that calculation, assumptions included, on the pricing page.
How a deployment runs, in order
- A scoping conversation, on site in Brussels or remote, to identify the saturated channel and the answers you never want automated.
- Writing the knowledge base from your existing content, completed with everything that is written nowhere.
- A private demonstration on your own content, before any commitment to go live. This is where you see whether the agent answers correctly.
- Go-live on your site, followed by a supervision period during which answers are reviewed and the knowledge base corrected.
The control point is the demonstration: until an agent has answered your own difficult questions correctly, it has no business on a public site.
Do we need to be in Brussels to work with Flows Studio?
No. We deploy agents for businesses in Belgium, France and Luxembourg, and most of the work happens remotely. The Brussels base matters for three specific reasons: the option of an on-site scoping session when the need is hard to describe in writing, a processing agreement under Belgian law with the Belgian Data Protection Authority as competent authority, and support on the same time zone and the same public holiday calendar as you. For a company located elsewhere in Europe, those three points still hold except the first, which becomes a video call instead. The pricing grid itself is identical regardless of location, and no local premium applies.
Can an AI agent really answer in Dutch as well as in French?
The quality of the language itself is no longer an issue, current models write correct Dutch. The real risk lies elsewhere: factual accuracy. If your knowledge base only exists in French, the agent will translate on the fly content that may never have been validated in Dutch, and produce a fluent but potentially wrong answer about a price or a condition. So we treat Dutch as a content language, not as an interface language: sensitive information is written and reviewed in every language offered. That work, and not the model, is what decides the quality of the final result on a public site.
How long before an agent is live on our website?
Expect one to two weeks between the first conversation and go-live for an FAQ widget, with most of that time going into the knowledge base rather than the technical work. Installing it on your site is a single line of code, which your developer or web agency adds in minutes. Timelines stretch in two cases only: when the reference content does not exist yet and has to be written, and when the agent needs to connect to a business application, which assumes the vendor exposes an interface. We would rather announce a longer timeline than go live early with an incomplete knowledge base.
Agents covered on this page
Each page details the deployment, the pricing and a live demonstration.