We are based in Barcelona and work with Austrian companies remotely, in the same hour. The thing that makes a Vienna project different is almost never Austria itself: it is that a Viennese group of any size usually has operations in eight or ten other countries, and the system has to be lawful in all of them.
Almost every Vienna enquiry we take has the same underlying shape, whatever industry it comes from: a process that already works in Austria, and a question about whether it can be made to work the same way in nine other countries without becoming nine separate systems.
Banking and insurance groups bring this most sharply. The document a Slovak branch produces is not the document the Austrian branch produces, the retention rules differ, and the language changes. The engineering that matters is the boundary — one model serving many entities, with per-entity control over what data reaches it and per-entity records of what it did. Our secure data pipeline work is largely about that boundary, and regulatory reporting is where it usually earns its keep first.
Energy and utilities arrive with a different problem: grid, plant and metering data that was captured for operations and is now wanted for planning. That is an integration project wearing an AI hat, and we say so early.
Industrial groups in and around the city hold decades of maintenance history in systems nobody wants to touch. Making that history answerable is unglamorous and reliably valuable.
Life sciences teams bring regulatory and research documents, where the requirement is not fluency but traceability back to the source paragraph. That is the pattern behind our life sciences research work, and where a system stores that trace decides most of the residency conversation.
No. We have one office and it is in Barcelona. We travel to Vienna for discovery, for handover and for anything where being in the room changes the outcome. A team our size claiming an Austrian office would be describing a mailbox.
For the Austrian entity, usually yes — there are Austrian cloud regions, and open-weight models can be self-hosted inside your own perimeter, so a system where no personal data leaves the country is a configuration decision rather than a special build. Frankfurt is the more common answer where the full service catalogue is needed, and it is still the EU. For subsidiaries in markets with no local region, in-country means self-hosting, and we will say so rather than quietly routing the traffic somewhere else.
One system with per-entity boundaries, in almost every case we have looked at. Several systems means several evaluation regimes, several sets of prompts drifting apart, and no way to answer a group-level question. The work is in making a single system honest about which entity it is acting for at any moment, and in keeping the records separable afterwards. For the entities outside the EEA, that boundary is also where the transfer question is answered.
The Datenschutzbehörde for data protection in Austria, plus whichever sectoral supervisor already covers you — for a large bank that means the ECB and the FMA rather than instead of them. For subsidiaries, each country has its own data-protection authority, and the group-level answer has to survive the strictest of them. Your DPO and counsel own that analysis; we build so it is not made harder.
The same as anywhere else — the ranges are on the pricing page, in euros and exclusive of VAT. We do not price by postcode. Multi-country scope changes the estimate because it is genuinely more work, not because the invoice has Vienna on it.
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.
