We are based in Barcelona and share your working day exactly. Two things make Warsaw different from most of the cities we work in: Polish data can now genuinely stay in Poland, which changed what the regulated sector is able to consider at all — and whatever we hand over here will be read line by line by engineers who could have built it themselves.
Warsaw enquiries divide between organisations that must keep everything inside a controlled perimeter and organisations that must run enormous back-office volume cheaply. Occasionally both at once.
Banking and insurance. Polish retail banks are technically strong and have built a great deal in-house, so what arrives is rarely a request for a chatbot. It is usually a document or decisioning process where the constraint is that a customer-affecting outcome must be explainable and reconstructable afterwards, and where the data cannot leave a defined boundary. That combination points at open-weight models inside your own infrastructure more often here than anywhere else we work, and the boundary itself is the engineering — which is what secure data pipelines covers.
Business and shared services. The centres in and around the city process invoices, contracts, claims and HR paperwork for the rest of Europe, at volumes where a percentage point of automation is a headcount. These processes are already documented and already measured, which makes them unusually tractable, and the honest work is deciding where the system must hand back to a person rather than pushing the automation rate to a number that looks good in a report. That is the substance of internal operations agents.
Software companies. Product teams here want AI capability inside what they sell, evaluated properly, at a cost per user they can defend. The conversation starts at evaluation and architecture rather than at feasibility, which is a pleasant change.
Logistics. Poland sits on the road freight corridor between western Europe and the east, and the paperwork that comes with it is multilingual, high volume and full of exceptions. The pattern is much as it is in any freight-heavy city, described under the logistics document pipeline, with the added detail that a single consignment file here may contain three or four languages.
No. We have one office and it is in Barcelona. We travel to Warsaw for discovery, for handover and for anything where being in the room changes the outcome. There is no Polish entity, no local partner and nobody here representing us.
More often than it used to be, yes. There are Polish cloud regions now, and open-weight models can be self-hosted on infrastructure you already control, including with no external network path at all. The thing to verify before designing around it is that the particular services and hosted models you need are available in the Polish region of your provider, because coverage differs. Where a hosted model is used we document its retention and training terms at the time of writing, and you should confirm them against the provider's current terms.
Often you should, and we would rather say that than win the work. Warsaw has excellent engineers and if the problem is ordinary software, local hiring is cheaper and better. Where we are worth the flight is a narrow band: you need a system of a kind your team has not built before, you need it now, and you do not want to carry the specialism permanently once it is running. That is why the engagement ends with your people owning the code rather than with a retainer.
It has to be proven rather than assumed, and Polish is a genuinely harder case than English or Spanish — inflection, diacritics, and the fact that most models have seen far less of it. We evaluate candidate models on your own Polish material with your own people scoring the output before anything is chosen, and the evaluation stays running afterwards so a model update cannot quietly degrade it. Where the honest answer is that quality is not sufficient for an unsupervised path, we will design a supervised one instead.
The same as anywhere else — the ranges are on the pricing page, in euros and exclusive of VAT. We do not price by postcode, in either direction: we do not add for a western European address and we do not discount to compete with a local day rate.
Thirty minutes on the problem, and an honest read on whether we are the right team for it.
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.
