A founder came to us ready to build a bookkeeping platform. They had wireframes. They had a feature list. They had a budget. They were ready to go.
We asked one question: "What's the core assumption you're testing?"
Silence.
The assumption was that small business owners wanted a new way to do their books. But nobody had asked them yet. The founder had extrapolated from their own frustration — which is a fine starting point, but a terrible ending point.
We suggested calling 20 potential users before writing a line of code. Not to pitch them. To listen. What's frustrating about your current bookkeeping? What have you tried? What would make you switch?
Those 20 calls changed everything. The real pain wasn't bookkeeping software — it was reconciliation between their accounting tool and their bank. The founder pivoted from "build a new QuickBooks" to "build a reconciliation bridge." Smaller scope, sharper value prop, faster to build, easier to sell.
The phone calls cost nothing. They saved months of building the wrong thing.
An MVP tests an assumption. Before you build the test, make sure you're testing the right assumption.
