Why we're not a dev shop
There’s a sentence we keep saying, and it tends to land: a dev shop sells you hours; a studio bets on outcomes — starting with our own.
It sounds like a slogan. It’s actually an operating model.
The dev-shop default
Most agencies are paid to finish a scope. You write a spec, they bill against it, everyone optimises for the contract. Nobody is rewarded for whether the thing actually works in the market — that risk stays with you.
It’s a fine business. It’s just not ours.
What a studio does instead
We build and own products. Weightless. Fooofi. Weightless AI. When we ship one, we carry the outcome — the retention, the growth, the brand, the bugs. There’s no client to hand the risk back to.
That changes how we work on everything, including partner projects:
- We push back on scope that won’t move the number.
- We design for the second month, not the launch screenshot.
- We bring both engines — Tech and Creative — because real outcomes need both.
Why two engines matter
A design-only studio hands you a beautiful thing and waits. A build-only shop ships a grey thing nobody loves. Outcomes live in the overlap: a product that’s both made well and cared about.
We kept the overlap in-house on purpose. It’s the whole point.
So no — we’re not a dev shop. We’re operators who happen to be very good at design and engineering, and who’d rather bet alongside you than bill against you.