Why we build in Stockholm.
Nordic languages, European data rules and a small team close to the problem. What that means for the product.
Company · 28 July 2026 · 4 min
People sometimes ask why a meeting-intelligence company is in Stockholm rather than somewhere with more venture capital and fewer months of darkness. The honest answer is that this is where the problem we are solving is hardest, and where the constraints that shaped the product come from.
Meetings here switch languages mid-sentence.
A sales call in Sweden can start in Swedish, switch to English when a colleague from Finland joins, and end with a Norwegian customer explaining their requirements. Most meeting tools treat that as an edge case. For us it is the first test every release has to pass.
Getting Nordic languages right means more than transcription. It means understanding that a short, flat “ja” can be agreement, acknowledgement or polite disagreement depending on who said it and when. The models we use are evaluated on exactly these conversations, because they are the ones our customers have.
European rules are a design input, not a compliance step.
Our customers ask where their data goes before they ask what the product does. That is a Nordic habit and a European one, and it is a reasonable question for a tool that listens to every meeting. Building here meant we answered it before we wrote the first line of code. Data stored in the EU, EU-only subprocessors, retention you control, and no training on customer data.
Those are not features we added for a security questionnaire. They are the reason the architecture looks the way it does.
Small, close to the customer, in the room.
We are a small team and we intend to stay close to the people who use the product. Most of our customers are within a train ride. When a customer success team in Gothenburg tells us the follow-up draft is too formal, someone from the product team has usually heard it in person, in their office, with the draft on the screen.
That is harder to do from far away. It is the main reason we are here, and the main reason the product works the way it does. Stockholm is not a strategy. It is where the customers are, where the languages are hardest and where the questions about data come first, and the product is better for all three.
