Skip to content
AI Customer Research & ValidationLesson 8 of 13

8 · Building and testing an MVP or landing page

Talking to people tells you a lot — but the strongest validation is watching what people do when something feels real. That's the job of an MVP (minimum viable product) and its smallest cousin, a landing-page test: put a real-looking offer in front of real people and measure whether they act, before you build the whole thing.

The cheapest valid test: a landing page. A single page that explains your offer and has one clear action — "Sign up," "Join the waitlist," "Pre-order" — can test demand in days. Drive a little real traffic to it and watch what fraction of strangers take the action. This is exactly the "test your concept against real demand" discipline the SBA points to, done early and cheaply (SBA, n.d.).

A ladder of tests, cheapest first:

  • Landing page / waitlist — do strangers give you their email for this?
  • Pre-sell — will they put money down before it exists? (The strongest early signal short of a sale.)
  • Concierge MVP — you deliver the value manually behind the scenes for a few real customers before automating anything.
  • A real, minimal product — the smallest thing that tests your riskiest assumption.

Where AI accelerates you: AI can draft the landing-page copy, headline, and FAQ, and (as F4 / Building with AI covers) help scaffold a simple prototype — getting you to "something testable" in hours. That's a great use of AI.

The line you can't cross: the page must be truthful. It's tempting to overstate what your not-yet-built product does to juice sign-ups. Don't. The FTC is explicit that claims must be truthful and substantiated — you can't promise capabilities (including "AI-powered" features) you can't back up, even on a test page (FTC, 2023). Validate real demand with an honest offer; a sign-up you got by lying validates nothing and can get you in trouble.

Check yourself. Why can a simple landing page sometimes teach you more than a finished product — and what's the one rule your test page must follow no matter what?

Sources

Sign in to track your progress