Three people, one decision
Most projects run with a lead engineer, a designer who codes and one more engineer. No account managers relaying messages.
AboutThe studio manual
We started Formwork because good products kept being built like campaigns: launched loudly, then left to rot. We build the other way — structure first, then the parts people see, with the same team from the first sketch to the last deploy.
01Point of view
Software is a building, not a campaign.
It should still stand — and be easy to extend — five years after launch.
Small, senior teams beat big, busy ones.
Fewer handovers, faster decisions, and the person who designed it is in the room when it ships.
Working software every week. Not slides.
Progress you can click is the only progress report that matters.
Leave every codebase easier to change.
Tests, docs and boring, well-named code are part of the job, not an extra.
02How we work
Habits, not slogans. Each one shows up in how a project is staffed, scheduled and handed over.
Most projects run with a lead engineer, a designer who codes and one more engineer. No account managers relaying messages.
Every sprint ends with something you can use on a real device, and a preview link for every change in between.
Performance budgets, accessibility checks and product analytics replace opinions about what's “fast enough”.
We refactor as we go and hand over runbooks, so your next hire can ship on their first week.
03People
No account managers or hand-offs: the people below run your project day to day.
Sample team · fictional people
Inês Carvalho
Founder · Engineering lead
Architecture, Postgres, mentoring
Marcus Oyelaran
Founder · Design lead
Design systems, prototyping
Hana Sato
Senior engineer
Commerce, payments, performance
Theo Lindqvist
Product designer
Research, interaction design
Priya Raman
Senior engineer
APIs, integrations, data pipelines
Joel Mensah
Engineer
Accessibility, testing, front end