We craft
strange software
for ambitious teams.
We are a five-person studio designing and shipping digital products that feel different — interaction-heavy dashboards, generative interfaces, and the kind of internal tools your team actually enjoys opening at 9 a.m.
Trusted by teams who measure twice
[01] Selected work
A narrow portfolio, on purpose. We ship four to six engagements a year — each one earns its place here.
Verdant & Co. — back office for a flower wholesaler, built around the rhythm of auction mornings.
North Noir — a slow editorial site for a Nordic audio magazine, set in Crimson Pro.
Alder & Fern — a pricing tool that lets a 4-person team run 2,400 SKUs without a spreadsheet.
[02] What we do
Three things, done slowly and properly. No retainers, no roadmaps-for-hire.
Strategy & discovery
Design & prototyping
Engineering & launch
Squarely in scope
- ✓ Internal dashboards, CRMs, admin tools
- ✓ Public marketing sites with custom CMS
- ✓ Data-heavy interfaces & pricing engines
- ✓ Design systems that survive team turnover
Politely declined
- — Native mobile apps from scratch
- — Full e-commerce migrations
- — Long retainers without clear exit
- — Anything we wouldn't use ourselves
[03] How we work
Four phases. No surprises on a Tuesday.
Dispersed listening
Week 01
We shadow your team for three days. No slide decks, no kickoff theater — just a notebook and the people who'll actually use what we build.
- → stakeholder interviews
- → workflow archaeology
- → problem framing doc
Frame & constrain
Week 02
We write a one-page scope with the things we will build, the things we explicitly won't, and the single metric we'll be measured against.
- → scope memo (signed)
- → success metric
- → kill-criteria
Build in the open
Weeks 03-08
Daily commits to your repo. Two pairing windows per week. A demo every Friday with real users invited, not just stakeholders.
- → staging from day 03
- → weekly demo ritual
- → shared Linear board
Hand-off, gently
Week 10
A 90-min walkthrough, a 12-page runbook, and 30 days of on-call for the code we shipped. Then we leave — no recurring seat to sell.
- → runbook + diagram
- → pair-handover session
- → 30d post-launch window
Principle 01
"Write the docs first. Then the code. Sometimes only the docs."
Principle 02
"If a feature needs a demo video to be understood, it's the wrong feature."
Principle 03
"We name a kill-date on day one. We've kept every one since 2019."
[04] Engagements
Fixed price. Fixed scope. No hourly anxiety.
We don't sell hours. We sell a finished thing, with a date on it. Every engagement below is one number — you'll see it before we start, and the same number on the final invoice.
Schematic
Strategy sprint
2 weeks · one fixed fee
For teams that already have engineering but need a sharp outside read on what to build next, and why.
- ✓ Stakeholder & user interviews (12)
- ✓ Workflow + data-flow mapping
- ✓ 1-page problem frame
- ✓ Buildable scope memo, in priority order
- ✓ Recorded walkthrough, yours to keep
Groundwork
Design & build
8-10 weeks · one fixed fee
The full arc — discovery, design, engineering, hand-off. Most clients land here. One team, one room, one shipped thing.
- ✓ Everything in Schematic, plus
- ✓ Clickable prototype from week 01
- ✓ Full engineering build on your infra
- ✓ Weekly demos with real users
- ✓ 12-page runbook & pair hand-over
- ✓ 30-day post-launch support
Atlas
Ongoing partner
per month · 3 month minimum
For teams who've shipped with us and want a quiet, low-ceremony relationship — one engineer on call, one designer in weekly orbit.
- ✓ 1 dedicated engineer, 20 hrs/wk
- ✓ Weekly design office hours
- ✓ Quarterly architecture review
- ✓ Pre-booked, never re-allocated
- ✓ 90-day exit clause, our side
All prices in GBP ex. VAT. Half-day money-back on day 03 of any engagement, no questions.
[05] Quiet answers
"Questions that came up twice on calls this year. We wrote them down here so we don't have to keep answering them."
— Iris, partner liaison
01
Why only five people? Couldn't you grow?
02
What stacks do you actually work in?
03
Do you sign NDAs? Work under contract?
04
Who owns the code, the design, everything?
05
Why won't you take retainers without an exit date?
06
What does "no questions on day 03" actually mean?
[06] Start something
Tell us about the thing that won't leave you alone.
We read every reply in-house, usually within two working days. If we're not the right fit, we'll tell you who is.
Direct
[email protected]Studio
Unit 4, Baird House
15-17 St. John's Lane
London EC1M 4AE
Hours
Mon–Thu · 09:30 → 17:00 GMT
Fri is for the quiet work