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.
About
Eleven people, no account managers
Everyone who writes your code is on your calls. There is no layer between you and the person making the decisions, because that layer is where the context goes to die.
Our story
Started by people who kept inheriting the problem
The code was fine. The tests were fine. What was missing was always the same: nobody who had been in the room could explain why it was shaped that way, because the people who had known were gone.
So we started building the opposite. Small teams, all senior, all present. We write down the reasoning while it is still cheap, we hand over on purpose rather than as a tactic, and we price engagements so that neither side needs a lawyer to survive one.
The measure of our work is how quickly you stop needing us.
That sounds like a poor business model. It has worked for every client we have ever had.
The whole idea
Senior people, in the room, until you no longer need them.
Everything else on this page is a consequence of that one sentence.
By the numbers
The record, plainly
We would rather show you the numbers than ask you to trust the adjectives.
11
People
All senior. No juniors billed at senior rates, no account layer.
96%
Clients who re-engage
Most work comes from teams we have already delivered for.
5 wks
To first real release
From kickoff to something running in front of users.
0
Lock-in
Every engagement ends with you owning all of it.
The team
Three of the eleven
All senior, all on the calls. These three carry most of the work in a first engagement.
Booking from March
Anna Bergström
Engineering lead
Takes the rescue engagements — the codebase someone else started and stopped explaining.
Khaled Haddad
Platform engineer
Infrastructure, pipelines and the handover documentation nobody else wants to write.
How we work
Four commitments
These are the things clients most often tell us they noticed.
None of this is remarkable on its own. It is just an unusually complete list of things that are routinely claimed and routinely not delivered.
- You talk to the people writing the code, in your standups
- Fixed price for a fixed outcome, agreed before we start
- Your repositories, your cloud, your credentials from day one
- A handover plan written at kickoff, not improvised at the end
Engagement
What the first month looks like
So you can see the shape of it before you commit to anything larger.
1
Week one — we read everything
Repositories, tickets, the analytics, and a conversation with the people closest to the problem. No workshop, no discovery invoice.
2
Week two — we say what we think
A written recommendation with the reasoning, the cost, the risk, and our honest view on whether to do it at all. This document is yours.
3
Weeks three and four — something runs
A thin vertical slice in the real stack, behind a flag, with instrumentation. Not a prototype — the actual thing, small.
4
After that — you decide
Extend, hand back, or stop. Most clients extend on the strength of the first month rather than a proposal written months earlier.
Client words
What it is like to work with us
They pushed back on our first proposal, which nobody else had done. The second one was half the size and twice as likely to work.
The handover was the best part. We run the platform ourselves now and still have them on call for the things only they know.
Eleven people, all senior, all in the calls. That is not a staffing model, it is a decision about how work gets done.
Next step
Come and argue with us
The first conversation is a working session, not a pitch. Bring the problem you are stuck on and we will tell you what we would do about it.