Mats Lindqvist
Principal engineer
Writes the first reply, then does the work if it goes ahead. Twenty years of platform teams, most of them inherited.
Contact
The more concrete the problem, the more useful our first reply. A paragraph and a link to something that is not working is plenty to start.
Who replies
Every enquiry is answered by one of these people, not by a queue. Whoever replies is the person who would do the work.
Mats Lindqvist
Principal engineer
Writes the first reply, then does the work if it goes ahead. Twenty years of platform teams, most of them inherited.
Anna Bergström
Engineering lead
Takes the rescue engagements — the codebase someone else started and stopped explaining.
Before you write
We would rather set the expectation up front than have you wonder whether anyone read it.
Everything starts with a short written exchange. You describe the problem; we reply with what we think it is, what we would do about it, and roughly what that costs. No call is scheduled before you have seen that reply.
If the answer is that you do not need us, we will say so, and usually say why. Roughly one enquiry in five ends that way, and those are the ones we tell other people about.
Enquiry
No account to create and no call to book. This goes straight to the team, and you will hear back from someone who can actually answer it.
We use what you send here to answer your question and nothing else. No list, no newsletter, no follow-up sequence.
Practical
Everything below is real — the address is a mail room and the phone is answered by whoever picks up.
Email — the fastest route. [email protected] reaches all of us, and it is read by a person rather than a queue.
Phone — +46 8 121 470 00, weekdays 09:00–17:00 CET. Someone who can actually answer technical questions is always reachable during those hours.
Before you ask
Answered here so you do not have to spend an email exchange on them.
A two-week strategy engagement is around SEK 60,000. Build work is priced per outcome rather than per day, and the number is fixed before we start. We will give you an indicative figure in the first written reply, so you are not choosing between us and a guess.
Especially then. Roughly one enquiry in five gets a reply saying the right move is to do less, do something else, or nothing yet. You keep that reply either way — there is no obligation attached to having asked.
Go, TypeScript and Postgres are what we reach for by default, but we have worked in Java, Python, Ruby, Elixir and .NET without complaint. The stack is your decision; the bias toward boring and typed is ours.
Yes, and it is a large part of what we do. Send whatever handover documentation exists, plus access to the repository. The first two weeks are spent reading and stabilising, not changing. We will tell you within a fortnight whether the codebase is something we want to keep working on.
Fixed price for a fixed outcome, once we agree what that outcome is. Time and materials only for genuinely open-ended platform work, and even then we cap it. Nobody likes a discovery phase that quietly becomes the whole project.
Gladly, and before you tell us anything. Send yours if you have one; if you do not, ours is a mutual one and takes a few minutes to review.
Still deciding
If you are not ready to write to anyone yet, the services page is a fair description of what we do and the work page is the evidence.
No newsletter, no automated follow-up. If we write again, it is because you asked us to.
Vi använder cookies för att förbättra din upplevelse, analysera trafik och visa personliga rekommendationer. Läs mer i vår integritetspolicy.
Nödvändiga
Krävs för att webbplatsen ska fungera (session, CSRF-token).
Analys & statistik
Sidvisningar, klick, sökningar — hjälper oss förbättra.
Marknadsföring
Personliga rekommendationer och kampanjer baserat på ditt beteende.