Build the smallest product that can test a real need.
Scope, design, and engineering of a launchable first product around one core user journey and a learning goal.
Describe the product ↗When this is useful
The idea has many possible features, but the first buyer, critical workflow, and success signal are unclear.
What we examine
User problem, intended buyer, existing evidence, journey, technical constraints, and operational requirements.
How the engagement moves
We frame the test, cut the scope to a coherent journey, build and launch, then examine use and feedback.
What you receive
A defined first release, working software, basic instrumentation, and a next-decision plan.
Agree what completion means.
Before work starts, we confirm the scope, access, deliverables, fee, and the person who reviews the result. Findings and remaining unknowns should support a clear next decision.
What remains under your control
The founder owns customer discovery, commercial decisions, and whether to expand after launch.
One possible application
A WhatsApp-first ordering concept may test demand before asking every customer to install an app.
This illustrates the kind of work; it is not a claimed client result.
Before we begin
How is the scope agreed?
We start with your context and the decision you need to make. We confirm the work, access, deliverables, turnaround, and fee before beginning. A larger implementation is a separate scope decision.
What should I bring?
A named owner, access to likely users, and a clear decision the first release should inform.
What does your review or build leave with us?
A defined first release, working software, basic instrumentation, and a next-decision plan. The founder owns customer discovery, commercial decisions, and whether to expand after launch.
Show us what needs to change.
Share the current workflow, the result you need, and what you have already tried.
Describe the product ↗