Discovery sprints, roadmap shaping, KPI framing, competitive teardowns, monetisation work. We help you decide what not to build — usually the most expensive decision in the room.
We bring a strategist, a researcher, and an engineer to every discovery call. The engineer asks the questions that turn pretty plans into real ones.
Six recurring archetypes cover most of what we get asked to build. Pick the one closest to yours, or describe your own — we've probably done a cousin of it.
Workshops, interviews, teardown, prototype of the riskiest interaction. Output: a costed, sequenced plan and a written argument for it.
From quarter-by-quarter wishlists to bets-shaped roadmaps. We replace "feature lists" with hypotheses and exits.
One number. Three input metrics. Five anti-metrics. The tree that lets your team argue productively about what to build next.
Packaging, tiers, willingness-to-pay research, expansion mechanics. The part of the product that earns the rest of the product.
The 30-page document we make for ourselves before every project. Now we make it for you, and the room reads it together.
A quarterly two-day review with your leadership. Outside-in critique, written. We say the things no one inside will.
Every engagement ends the same way: a production system, a team that can run it, and a written record of every decision we argued about.
A deliberately conservative core. We swap in sharp tools when the problem requires them, never because they're trending.
Pick the one that maps to where you are. Or hop between them — most clients start at one and end at another.
Architecture review, prototype of the riskiest interaction, and a costed roadmap. You walk away with a plan whether or not we build it.
Senior pod of 3–5: tech lead, full-stack, design, QA. Two-week cycles, demo every Friday, you own the repo from week one.
Once it's live. A reduced pod stays in your stand-ups, owns the on-call rota, and ships the roadmap quarter-over-quarter.
If yours isn't here, just ask. We respond to most enquiries within a working day.
Yes — most of our work is alongside in-house teams. We default to your repo, your code review, your standup. Where we run our own pods, we still pair-program weekly so the knowledge transfers from day one rather than at handover.
Frequently. We start with a one-week audit: code, infra, team, runway. Output is a frank document — what to keep, what to throw out, what to rewrite — and a costed path to stable. About a third of those projects we then take on. The rest we hand back with a plan they can execute themselves.
You own everything we write — code, designs, infra, docs — assigned on first commit. We keep no kill-switches and no exclusivity clauses. Our standard MSA is six pages and we'll happily redline yours.
For well-shaped, mostly-known scopes — yes, we offer fixed-fee with milestone billing. For genuinely exploratory work we recommend time-and-materials with a hard cap, because anyone who quotes you a fixed price for an unknown is either lying or building you something cheap.
A two-week discovery sprint. Below that we're not adding much value over a good freelancer, and we'd rather refer you to one of the four we trust than do it badly ourselves.