Product development for founders who need working software.
Discovery, a narrow first version, and the unglamorous work after launch.
An agency builds what the brief says. A product team argues with the brief first. We take an idea through discovery, a narrow first version, and the unglamorous work after launch, the part where a product either finds users or quietly does not.
What this actually covers.
Discovery: user interviews, scope cutting, and an honest first version
Prototypes built to be thrown away, so decisions cost days not months
End-to-end delivery across web, mobile and backend
Analytics and instrumentation, so the next decision has evidence behind it
Post-launch iteration on what usage actually shows
How it runs, week by week.
Cut the scope
We find the smallest version that can succeed or fail informatively, and we say no to the rest out loud.
Build the narrow version
One flow, finished properly, in front of real users, before the second flow starts.
Iterate on evidence
Instrumented from day one, so the next sprint argues from usage rather than opinion.
What you get.
A launched product with real users, not a feature list
A clear read on what to build next and what to abandon
Questions we get asked.
- What does discovery actually produce?
- A written scope with an explicit list of what is not being built, a rough timeline, and the one metric that will tell us whether the first version worked. Usually a week, sometimes two.
- Can you work with our in-house team?
- Yes. We are used to being one part of a larger team, and we would rather leave your engineers able to maintain the work than hold onto it.
- What happens after launch?
- We instrument the product from day one, so the weeks after launch are spent on what usage shows rather than what the roadmap guessed. Ongoing work is a separate, optional arrangement.
Need product development?
Send us the problem and any constraints you already know about. We will come back with scope, a rough timeline, and whether we are the right fit.
Start a project