France asks a question about AI systems that most of Europe only gestures at: where, precisely, does this run, and under whose control. Sovereignty is not a talking point in Paris procurement — it is a line in the tender. Answering it well is a design decision made in the first week, and answering it badly is a rebuild.
Paris concentrates several industries that rarely share a city: the largest banks and insurers on the continent, the luxury groups, aerospace and defence, energy, and a very substantial public sector. Each produces a different AI problem, but the constraint they hold in common is that the output has to be explainable in French, to a French counterparty, sometimes under a regulator's eye.
Banking and insurance arrive with decisioning and with documents, usually both at once. A file is read, a judgement is made, and eighteen months later somebody asks how. The engineering that matters is the trace rather than the model, which is the whole subject of our risk and compliance architecture and of credit decisioning.
Luxury and retail groups have a harder version of an ordinary problem. Product search has to work across languages and across a vocabulary that the house itself defines, and the tone of any customer-facing text is a brand asset that a generic model will quietly destroy. That is a retrieval, ranking and evaluation problem before it is a generation problem — see merchandising and search.
Aerospace, energy and the public sector tend towards the deployment question first and the use case second. If the conclusion is that nothing may leave a controlled environment, then the model has to come to the data, and the sizing conversation becomes real: what runs on what hardware, at what cost, at what quality. Deployment options lays out the choices without pretending they are free.
French-language work also affects model selection. Open-weight families developed in Europe are frequently strong on French and can be self-hosted, which makes them a serious candidate rather than a patriotic one — our notes on Mistral models cover where that holds and where it does not.
No. We have one office and it is in Barcelona. We come to Paris for discovery, for handover and for anything that goes better in a room. In a city with this many real agencies, inventing a French address would be both unnecessary and obvious.
We can build a system that deploys into it, and we design so that nothing in the architecture depends on a service that would fail the requirement. What we cannot do is supply the qualification: we hold none, and the qualified provider would be contracted by you rather than by us. If a tender requires the integrator itself to be qualified, we are not the right supplier and will say so at the first call.
Yes. There are three in-country regions between the major providers, and open-weight models can run on infrastructure you control if the requirement goes further than location. Where a hosted model is part of the design we document its retention and training position at the time of writing, and you should verify it against the provider's current terms.
Our working languages are English, Spanish and Catalan, so workshops and documentation run in English unless your team prefers otherwise. That is a different question from whether the system works in French: it does, and we test it that way, with French-speaking reviewers on your side scoring real outputs rather than us assuring you it reads well.
The ranges on our pricing page, in euros and exclusive of VAT, the same in every city we work in. We do not price by postcode. Sovereign or on-premise deployment changes the infrastructure bill, which is yours and which we will size honestly, not our fee.
Thirty minutes on what the clause actually requires and what it does to the architecture. We will tell you if it rules us out.
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.
