A small studio, a slow practice, and the rules we have decided not to bend.
BuildLogicStudio was founded in Täby in 2021 by Anders Lindqvist and Elin Bergström, after fifteen years working at larger product companies and consultancies. Henrik joined in 2023; Astrid joined later the same year. The four of us are the studio. There are no offshore contributors, no overflow agencies, no junior contractors filling gaps. The engineer who answers your first email is the engineer who pushes the deploy.
The shape of the studio was a deliberate decision, not an accident. We had both worked at agencies where the senior engineer who scoped the project rarely wrote any of the code, and we had both watched what happens to deliverables when the scoping conversation and the implementing conversation are held by different people. The whole point of BuildLogicStudio was to keep those two conversations in one person's head.
The practical result is that we are smaller than we could be and slower than we could be, on purpose. The studio runs at most one Atelier Build, one Structure Build, and two Foundation Builds in flight at any given time. That cap is the reason every engagement we take gets a senior engineer rather than an account manager, and the reason we ship on the date in the engagement letter rather than the optimistic date we both wanted.
The kind of work we take has narrowed since we started. We do not do branding from a blank page; we have other studios we recommend for that. We do not run paid acquisition, content marketing operations, or SEO retainers. We do not build mobile applications. We build production web software — marketing sites, content systems, internal tooling, small customer-facing applications, and the careful piece of infrastructure that holds the whole thing together. We have a clear idea of what we are good at, which is the second-best argument for being able to say no to the rest.
We work mostly with Swedish and Nordic teams — Stockholm-based fintechs, Värmland utilities, an Örebro physical-therapy clinic — but a third of our engagements are now with teams further afield: Berlin, Copenhagen, Helsinki, occasionally Amsterdam. We work in English by default, in Swedish on request, and the engagement letter has always been bilingual.
The four people.
Every engagement is owned end-to-end by one of these four. Atelier Builds pair two of us; Foundation and Structure Builds are run by one. There is no fifth hidden contractor.
Anders Lindqvist
Principal engineer · co-founder
Anders has shipped production software for fifteen years — at Spotify, at a Stockholm fintech, and freelance — before starting BuildLogicStudio with Elin. He runs every Atelier Build and writes the runbooks himself.
Elin Bergström
Senior front-end engineer · co-founder
Elin has been writing HTML and CSS for two decades. She runs the Foundation and Structure Builds, owns the studio component system, and is responsible for the fact that every site we ship is under one-hundred-fifty kilobytes of JavaScript.
Henrik Nyström
Senior back-end engineer
Henrik joined in 2023 from a Gothenburg infrastructure team. He handles the application half of every Atelier Build — databases, integrations, deployment pipelines — and is the calmest person on the call when something is on fire.
Astrid Holm
Project lead · operations
Astrid runs the schedule, the engagement letters, the change requests, and the calendar that keeps four engineers from over-committing. She joined at the end of 2023 and the studio has been operating quietly ever since.
A short list of opinions we will not argue about.
Six operating rules. Each one is on the list because at some point we tried operating without it and the result was a project we still remember unfondly.
-
§01
The engineer who scoped it ships it.
The engineer who answered your first email is the one who writes the engagement letter, runs the kickoff call, makes the design routes, and pushes the code that goes live. There are no mid-project handoffs from senior to junior and no anonymous off-shore contributors.
-
§02
Two routes, never twenty references.
We do not present a mood board of pinned images. We present two distinct, fully-considered visual routes — each one a complete hero, a complete secondary page, and the foundational components — and you pick one to commit to. The decision is faster, the rationale is clearer, and the work has a centre of gravity.
-
§03
A documented hand-off is part of the deliverable.
Every Build closes with a written runbook: how to deploy, how to roll back, how to add a page, who to call when something breaks. We are not the only people who can operate what we built. If we stopped answering tomorrow your team would be fine.
-
§04
Performance is a feature, not an afterthought.
Every site we ship runs under one-hundred-fifty kilobytes of JavaScript on the first page load and scores above ninety on every Lighthouse axis. We measure during development, not after, and we walk away from frameworks that make the budget impossible to hold.
-
§05
No subcontractors, no AI-written code, no surprises.
Every line of code that ships is written by one of the four people in the studio. We use AI for our own scaffolding — call transcription, research notes, the boring bookkeeping — but the production code is hand-written. Nothing leaves the studio without one of us reading it through.
-
§06
A calm pace is a competitive advantage.
We take one Atelier Build, one Structure Build, and at most two Foundation Builds in flight at any time. That cap is the reason we ship on the date in the engagement letter and the reason every client gets a senior engineer rather than an account manager.
Read the work, then begin a conversation.
If anything you have read sounds like the kind of studio you would want to work with, the next step is short: send us a paragraph about the project, the rough budget, and the deadline. We reply within two working days.