Use case
Build the smallest version that tests the riskiest assumption. For most products the risk is whether anyone wants it, and that is answerable with far less than a full build.
The visible symptom is rarely the cause. These are the underlying reasons we find most often.
A working product in real users' hands early, with a roadmap directed by observed behaviour rather than by the original specification.
How we solve it
Eight to twenty weeks to a usable first version, depending on the domain and integration needs.
Usually that a specific group will pay for this specific thing. Everything else is secondary until that one is tested.
The least that produces a real answer. Sometimes that is software; often it is a landing page, a manual service, or ten conversations with people who would buy.
One complete workflow that a real user can finish, rather than a broad set of partial features. A narrow product that works teaches you more than a wide one that does not.
Release to real users early and let the evidence redirect the roadmap. Assumptions written before anyone used the product are the least reliable input available.
How it works
A process before and after automation
Before: five steps, four of them manual. After: the same outcome with one human decision point and a defined exception path for when the system is unsure.
Capabilities
Context
Most product failures are demand failures, not engineering ones. Finding that out after twelve months of building is the most expensive way to learn it.
Small enough to reach real users quickly, complete enough that one workflow genuinely works end to end. A product that does one thing properly produces usable feedback; one that does five things partially produces complaints.
That is the cheapest possible outcome. It is the same answer you would have received after a full build, arrived at for a fraction of the cost and with the budget still available.
Build the smallest version that tests the riskiest assumption. For most products the risk is whether anyone wants it, and that is answerable with far less than a full build.
Most product failures are demand failures, not engineering ones. Finding that out after twelve months of building is the most expensive way to learn it.
A product idea has been discussed for months without a decision; The proposed scope keeps growing as more people are consulted; Nobody has spoken to a potential buyer about paying for it; and The business case rests on assumptions nobody has tested
The riskiest assumption has not been identified, so everything is being built at once; Success is defined as launching rather than as being used; Feedback is planned for after launch rather than during the build; and Internal enthusiasm is being read as market demand
A working product in real users' hands early, with a roadmap directed by observed behaviour rather than by the original specification.
Eight to twenty weeks to a usable first version, depending on the domain and integration needs.
Connected
If the before state above reads like your operation, the next step is establishing which part of it is actually costing you. Describe it and we will tell you where launch a digital product would and would not help.
