The test isn't "is this a good idea?" It's "does this solve a specific problem, completely, for a specific person?" Those are different questions, and most startups fail because they only ask the first one.
At WiSense, every feature proposal runs through the same filter before a single line of code is written: who has the problem, how often, and what does a complete solution look like? If we can't answer all three, we don't build it.
Most startups fail by building too much — by adding features for edge cases, by designing for imaginary future scale, by shipping three half-finished things instead of one complete one. The output is a product that does ten things poorly instead of one thing completely.
Utility-first means: pick one problem. Understand it deeply. Build the simplest complete solution. Then ship it. No stubs, no TODO scaffolding, no "we'll add that later." Later is where software goes to die.
Horizon doesn't have a social feed because couples planning a trip don't need one. Apex Scheduler doesn't have analytics dashboards because a brewpub manager at 6 AM needs to see the week's schedule, not a pivot table.
The filter isn't about minimalism for its own sake. It's about precision. A tool that does one thing completely is infinitely more useful than a platform that does ten things partially. That's the WiSense standard — and it's the reason we ship.