01 — Few projects
One or two at a time
We take on a small number of engagements so we can stay close to each. It means saying no often, and it means the work we say yes to gets our full attention.
About the studio
A small studio, deliberately so.
Miqori began in 2022 as a quiet experiment between two friends who'd spent a decade inside larger product teams and wanted to try working differently. Four years on, we're still small — and that has turned out to be the work, not a constraint on it.
Story
We started in a borrowed office above a print shop, with one client and a habit of working in long, uninterrupted afternoons. The studio has grown a little since — into a second room, into a small set of long-running clients, into a slow output of side projects — but the rhythm has stayed roughly the same.
Most of what we do still happens in conversation: with the people we work with, with each other, and with the work itself. We've never had a sales pipeline or a pitch deck. New work tends to arrive through old work.
We're based in two cities and meet in person every few weeks. The rest of the time the studio is an unhurried, mostly text-based place.
How we work
Four habits we've kept02 — Long arcs
Months, not weeks
Our best work has come from staying with a project long enough to see decisions land and be revised. We prefer extended retainers and quiet revisions over one-shot deliverables.
03 — Plain craft
Boring on purpose
We try to make interfaces that age well — quieter colour, careful typography, fewer flourishes. We'd rather build something that still feels right in three years than something that wins this quarter.
04 — Shared studio
Make a little for ourselves
A part of every year goes to small tools, notes, and experiments we make for the studio itself. Some find their way out into the world. Most don't, and that's fine too.
Tools of the trade
We design in the usual places — Figma for interface work, an iPad for sketching, and a pile of notebooks. On the engineering side we lean on plain HTML, CSS, and small bits of vanilla JavaScript wherever we can, and reach for a framework only when the work asks for it. Most of what we ship is simpler than the thing it replaced.
Working with us
We're a good fit for product teams that want a steady design partner for a longer arc, and for independent makers who need a thoughtful second pair of hands.