Everywhere else we spend the first meeting explaining what the AI Act says. In Brussels the client often has a better sense of it than we do, because someone down the corridor worked on it. That changes the conversation for the better: it starts at classification, obligations and dates rather than at whether any of this is allowed, and it leaves more time for the two things that are genuinely hard here — languages and record-keeping.
Brussels produces a kind of work that barely exists elsewhere: organisations whose core output is understanding, positioning and responding to text. Associations, federations, public affairs practices and policy teams all live in consultations, position papers, transpositions and correspondence, in several languages, on deadlines set by someone else.
The useful system for that is not a chatbot. It is retrieval done properly over a corpus that the organisation already owns — with citations back to the source paragraph, with version awareness so that a superseded draft is not quoted as current, and with an honest signal when the answer is not in the corpus at all. The failure mode that matters here is a confident synthesis of two documents that contradict each other, and the defence against it is architectural rather than a matter of prompt wording. That is covered under retrieval systems, and the regulatory frame under the EU AI Act.
Logistics is the other Brussels constant. Belgium is a transit country with major ports and air freight on either side of the capital, and the resulting document flows have the same shape as anywhere else with an extra language or two attached. That work is described in our logistics document pipeline.
Chemicals and pharmaceutical organisations here bring regulatory dossiers, safety documentation and literature review, where the requirement is traceability rather than fluency: every assertion has to point somewhere. The life sciences version of that work is under life sciences research.
No. We have one office and it is in Barcelona. We travel to Brussels for discovery and handover and for anything that has to happen in a room. In a city where a great many organisations maintain an address purely to say they have one, we would rather not add to it.
Not directly through the large framework contracts — we are a small firm and we are not on them, and pretending otherwise would waste your time. What does work in practice is direct engagement with associations, federations and private organisations, or subcontracting to a prime who holds the framework. If the procurement route requires something we cannot meet, we will say so in the first call rather than after four weeks of paperwork.
No. We build software. We can build the system that finds, extracts, compares and tracks the documents your policy people work from, and we will not offer an opinion on what the policy should be. The division of labour is deliberate: you would not want engineering advice from a lobbyist either.
By treating each language as its own quality problem. Retrieval, extraction and generation quality all differ by language, and averaging them into a single accuracy figure hides exactly the case that will embarrass you. We build a labelled evaluation set per language, report per language, and where one is materially worse we say so and either fix it or scope it out rather than shipping a number that flatters the system.
Our ranges are on the pricing page, in euros and exclusive of VAT. We do not price by postcode. Multilingual work sits higher in a range than a single-language equivalent, because the evaluation effort multiplies even when the build does not.
Thirty minutes on the documents, the languages and what a retrieval system would honestly deliver.
30-minute technical call · no deck
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Apps, platforms and campaigns for these teams, long before the AI work. Every one is written up on the work page — what we did, and where our part ended.
