SHORT ANSWER
Validate a startup idea by testing willingness to pay, not enthusiasm. Run ten to fifteen interviews about what people did last time they faced the problem, then ask for a commitment — a deposit, a paid pilot, a signed letter of intent. Set your pass thresholds before you start. Two weeks of this routinely prevents six months of building the wrong thing.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
People are polite. Interest costs nothing, so it tells you nothing; commitment costs something, so it tells you almost everything.
Validation also defines the segment, which is what makes every later prioritisation decision easier.
'Operations managers at 20-100 person logistics firms will pay £200/month to remove manual reconciliation.' Specific enough to be wrong.
e.g. at least six of fifteen describe the problem unprompted, and at least three commit. Deciding thresholds afterwards guarantees a pass.
What did you do last time? What did it cost? What did you try? Never ask whether they would use a hypothetical product.
Deposit, pilot fee, letter of intent, or a scheduled onboarding slot. Money is best.
A landing page with a real price and a real call to action, driven by direct outreach to the exact segment.
Pass, iterate the problem statement, or drop it. Write the decision down.
FROM EXPERIENCE
The clearest validation I have seen in B2B is a small paid pilot agreed before anything exists: a defined scope, a start date and an invoice. It converts a conversation into a business decision on the customer's side.
In consumer, the equivalent is a pre-order or a deposit. Everything softer than that — sign-ups, likes, 'definitely interested' — is noise.
Ten to fifteen in one segment. Patterns repeat quickly; if they do not, your segment is too broad.
Yes, and you should try. A clear offer, a price and a commitment ask need no product.
That is a successful validation. You bought the information for two weeks instead of six months.
IN SHORT
Prove demand before you spend the build budget.
Read moreContinuous discovery that tells you what to build next.
Read moreFree check on whether you have enough evidence to build.
Read moreA validated, instrumented first product in front of real users.
Idea to MVP in six weeksTHE FRAMEWORK
MORE ANSWERS
Start a SaaS company by choosing a narrow, expensive, recurring problem for a specific group you can reach, validating that they will pay before you build, then shipping the smallest product that solves it end to end. Get to first paid customer before hiring, raising or automating anything. Distribution — how you reach that group repeatedly — matters more than the software.
Technical co-founders come from people who already know you — former colleagues, communities you contribute to, and open-source or startup circles — far more often than from matching platforms. What makes them say yes is evidence: a validated problem, early customers, and a prototype you built yourself. In 2026, many founders should first ask whether they need a co-founder or a contractor plus AI tooling.
First-time founders consistently build before validating, scope too wide, hire too early, price too low, chase funding instead of revenue, and measure activity instead of outcomes. Each individually is survivable. Combined, they burn a runway cycle before anyone learns whether the core idea works. The counter-move is uncomfortable focus: one segment, one problem, one metric, one channel.
Founders need one sequence, not a shelf of frameworks. A workable one: discover the problem, validate willingness to pay, prototype the flow, build the MVP, launch narrow, get first revenue, then scale what works. Borrow specific tools where they help — jobs-to-be-done for framing, opportunity solution trees for discovery — but a framework that produces artefacts instead of decisions is overhead.