Skip to main content

Validate Demand

Does anyone actually want this, or are you building for an audience of one?

Listen for psychological triggers that instigate decision chains. What people say they want and what they actually do are different data sets.

Awareness Levels

Where your customer sits determines what you say to them.

LevelThey KnowYour Job
UnawareNothing about the problemShow the problem exists
Problem AwareThe pain, not the solutionName it better than they can
Solution AwareSolutions exist, not yoursDifferentiate
Product AwareYour product, not convincedRemove the hidden objection
Most AwareEverything, ready to actReduce friction to zero

Intent Signals

IntentBehaviourContent Strategy
LowBrowsing, not seekingLead with why — make the problem vivid
MediumComparing, could actWhy + how — show the path
HighReady todayHow to start + what to expect

The Validation Stack

Before committing resources, validate in this order:

TestMethodKill If...
Problem existsInterviews, observationNobody describes the pain unprompted
People payLanding page, pre-orders, depositsAttention without wallets
You can deliverPrototype, pilot, manual versionYou can sell but can't build
Unit economics workCost vs revenue per customerRevenue doesn't cover cost at 10x

Context