Product & MVP
The shortest honest path from an idea to something real people use. We cut scope hard, ship early and let usage decide what comes next.
What the work covers
Deciding what to build is the expensive part. This is the work that happens before anyone writes a line of production code — and the weeks right after.
Discovery
Who has the problem, what they do about it today, and what would have to be true for a new product to be worth the switch.
Cutting the scope
A first release small enough to ship in weeks, with the cuts written down so nobody thinks they were forgotten.
Clickable prototype
A prototype real enough to test with users before the cost of building it properly is committed.
Ship to real users
A working product in front of people who did not help design it — the only test that counts.
Metrics that answer something
A small number of measures tied to the decision you are actually trying to make, not a dashboard of everything.
The next iteration
What the data said, what to change, and what to stop doing — written as a roadmap you can argue with.
What you end up with
- A written scope with the explicit list of what the first release leaves out.
- A working product in production, used by people outside the team.
- Instrumentation and a short report on what the first weeks of usage showed.
- A roadmap for the next cycle, ranked by evidence rather than enthusiasm.
The stack we reach for
- Figma
- Flutter
- React
- Supabase
- Vercel
- PostHog
- Feature flags
How it runs
Frame the problem
A week of questions, not answers. We come back with the problem stated in a way that can be tested.
Prototype and test
Something clickable in front of five or six real users, early enough that changing it is cheap.
Build the first release
Weeks, not quarters. Narrow on purpose.
Learn and decide
Usage data and interviews, then an honest conversation about whether to push, pivot or stop.
Questions we get asked
How long until something is live?
For a genuinely narrow first release, usually six to ten weeks. If a scope cannot be cut to that, that itself is worth knowing early.
What if the idea does not work?
Then you find out for the price of an MVP instead of the price of a full product. We would rather tell you that in month two than in month twelve.
Can you work alongside our own team?
Yes. We can lead the first release and hand it over, or work as part of a team you already have. The handover is planned either way.