Lawrence @ Fast Revops, 2025-05-01
TLDR: This is OUR One-Page Customer Development Interview framework
This interview is designed to validate a lot of our hypothesis about our clients. It evolves - as yours should too - as we are getting into deeper and deeper layers of our ICP mind.
Steal it, adapt it, use it. There's no free lunch though, you got to learn the underlying principles to get good at this. Read the books, or at least spend a few days researching and cross-referencing the concepts in them.
We put together our interview framework using the principles of the following books:
Rob Fitzpatrick – The Mom Test → field‑tested rules for asking customer questions without bias and spotting truthful, behaviour‑based answers. (The Mom Test)
Eric Ries – The Lean Startup → core concept of validated learning, hypothesis testing, pivot/persevere gate. (The Lean Startup)
Ash Maurya – Running Lean & Lean Canvas → problem/solution fit stages, experiment backlog, canvas blocks. (LeanFoundry)
Steve Blank – Customer Development (esp. discovery & validation interviews) → “get out of the building” question style. (CMU, Steve Blank)
Jobs-to-Be-Done (Christensen, Ulwick, etc.) → progress-forces diagram used to frame “triggers” and “switching anxieties.” (Jobs to be Done)
Secondary seasoning came from Lean Analytics (Croll & Yoskovitz) for the metrics emphasis and standard B2B-SaaS/RevOps playbooks (Predictable Revenue, Winning by Design) for ICP, pricing, and hand-off nuances.
You can not adapt this without building a painfully long list of your untested assumptions. Tell any AI everything you think you know about your business, and ask for a detailed list of assumptions that needs to be validated to guarantee a GTM strategy free from all wishful thinking and biases. Mention it the books in this article.
We have printed that list, stick it up, named it "The Wall of Our Radiant Ignorance" and we look at it in terror every time we walk by. "You got to do what scares you."
So - here is the Customer Development Interview Framework we use today to validate many of our current assumptions.