Aviana Le · Creator + Founder · Building in publicInstagram @avianaleMogul Mastery waitlist

Mogul Maxxing  /  Blog  /  Offer Validation

06 · Offer Validation

How to validate an offer before you build it, and why views are not demand

Likes, comments and "I'd buy that" feel like proof. They usually aren't. Here is what the research says about the gap between what people say and what they pay for, and a step-by-step way to test an offer with real commitments before you spend months building it.

By Aviana LeOctober 202620 min read
Woman founder at a cream studio desk sketching an offer outline on index cards beside a closed laptop in soft afternoon light
An offer starts as a few cards on a desk. The goal is to find out whether anyone will commit before it becomes a product.

To validate an offer before you build it, you test whether specific people will commit something real, such as their time, their reputation or their money, to a clearly described promise, before you create the full product. Opinions, compliments and views don't count. Past behavior and commitments do. In practice that means talking to people about the problem rather than your idea, writing a one-page offer, and asking a small number of the right people for a concrete next step, ideally a pre-order or a paid pilot, with a clear refund if you don't deliver.

The short answer

Validation is evidence that someone will trade something they value for your offer. Research on the intention–behavior gap and on "hypothetical bias" shows that what people say they'll do and what they actually do are different things. So the strongest validation signal is a commitment, not a comment. Start with conversations about the problem, move to a one-page offer, then ask for a commitment. Build only after the commitments arrive.

This is the sixth theme in the Mogul Maxxing series, and in some ways it's the one the others have been leading to. The decision fatigue article was about protecting a limited work window. The founder operating system piece was about deciding things once. The creator-to-founder article ended on the point that an audience is not yet a business. This article is about the step in between: finding out whether an offer is wanted before you pour your windows into it.

I'm building my first offer in public, so this isn't theory for me. I'm not going to tell you my offer is validated, because it isn't yet, and I won't claim numbers I don't have. What I can share is the research on why early signals mislead, the process I'm using, and the rules I've set for myself about what counts as proof. I'm testing this in the build, and I'll report what happens.

What does it mean to validate an offer?

An offer is more than a product. It's a specific promise to a specific person: who it's for, the outcome it delivers, how it's delivered, what it costs, and what happens if it doesn't work. "A course about productivity" isn't an offer. "A four-week implementation program for solo founders with under ten hours a week, ending with a working weekly plan, for a stated price, with a refund if you do the work and don't get the plan" is much closer.

Offer validation is the process of collecting evidence that this promise is wanted, by enough of the right people, at a price that works, before you build all of it. The word that matters is evidence. Validation isn't a feeling of confidence; it's something you could show another person.

It's worth separating three things that often get blurred together:

  • Problem validation: do these people actually have this problem, and is it painful or frequent enough that they've already tried to solve it?
  • Offer validation: will they commit to your specific promise, in your format, at your price?
  • Delivery validation: can you actually produce the promised outcome, repeatedly, without it eating your life?

Most founders skip straight from "this problem seems real" to building. The middle step, offer validation, is the cheap one, and it's the one that saves the most time.

Why build first, ask later is so expensive

The research firm CB Insights analyzed 111 startup post-mortems, essays founders wrote after their companies shut down, and tallied the reasons they gave. "No market need" was cited as a factor in 35% of them, second only to running out of cash or failing to raise money at 38%. That makes it one of the most frequently named reasons for failure.

Two honest caveats. First, this is a small sample of self-reported reasons, written by founders after the fact, and each failure could list several causes, so the percentages add up to more than 100%. Second, CB Insights itself notes that "ran out of cash" is often a symptom of something deeper, which may include the market not wanting the product. So the figure isn't a precise measure of anything. But the pattern it points to is consistent with decades of startup practice: building something nobody needs is a common and avoidable way to lose time and money.

For a solo founder or creator with limited work windows, the cost isn't only money. It's months of evenings and weekends. If your windows are the scarcest resource you have, building the wrong thing is the most expensive mistake available to you.

Every hour spent building an offer nobody committed to is an hour taken from one somebody would have.

Why views are not demand: what the research says

If you create content, you have a special version of this problem. You get a constant stream of signals: views, likes, saves, comments that say "I need this". They feel like demand. The research on how people's stated intentions relate to their actual behavior suggests treating them with real caution.

The intention–behavior gap

Psychologists Paschal Sheeran and Thomas Webb reviewed the evidence on how often people act on what they intend. Their 2016 review in Social and Personality Psychology Compass concludes that the intention–behavior gap is large, and that current evidence suggests intentions get translated into action approximately one-half of the time. They describe a group they call "inclined abstainers": people who sincerely intend to act and then don't. These are the people mainly responsible for the gap.

That matters for offers because most early "validation" is a collection of intentions. "I'd definitely buy that." "Sign me up when it launches." The person isn't lying. They're expressing a real intention in the moment. The research just tells us that intentions are a weak predictor of what happens when it's time to act, and the moment of paying is exactly that kind of moment.

Sheeran's earlier meta-analysis did find a meaningful correlation between intentions and later behavior. So intentions aren't worthless; they're a starting point. They just aren't proof.

Hypothetical bias: people overstate what they'd pay

Economists have studied a related effect called hypothetical bias: when people are asked what they would pay for something, their answers tend to be higher than what they actually pay when real money is on the line. A 2005 meta-analysis by James Murphy and colleagues in Environmental and Resource Economics pooled 28 studies that measured both hypothetical and real willingness to pay. The median ratio of hypothetical to actual values was 1.35, meaning people's stated amounts were, at the middle of the distribution, about a third higher than what they really paid.

This is worth reading carefully, because it's more nuanced than the popular version. The authors note that the median overstatement is smaller than the two- or three-fold bias often assumed, and that the distribution is heavily skewed: a few studies show very large overstatements, which pull the average up. They also found that the way you ask matters, with choice-based questions reducing the bias. Most of these studies valued things like environmental goods, not online courses or services, so the exact figure won't transfer to your offer. The direction will: asking "would you pay?" overstates the answer.

What this means for creators

Put those findings together and a view, or even an enthusiastic comment, is at most a weak intention, given at no cost, in a moment when nobody is asking for anything. That doesn't make audience signals useless. They're excellent for finding which problems people care about. They're poor evidence that people will pay you to solve them. Validation has to move from "they reacted" to "they committed".

SignalWhat it costs themHow much it tells you
A view or likeA second of attentionThe topic caught attention, little more
A save or shareA small action, some reputationThe content was useful; says little about buying
"I'd buy this" commentNothingA stated intention; often not acted on
Joining a free waitlistAn email addressInterest in hearing more; weak purchase signal
Booking a 20-minute callTimeThe problem matters enough to give up time
An introduction to someone elseReputationThey'll put their name next to yours
A deposit, pre-order or paid pilotMoneyThe strongest early evidence of demand

The principle: commitments, not compliments

The clearest practical framework I've found for this comes from Rob Fitzpatrick's book The Mom Test. The title comes from the idea that you should be able to talk about your business even with your mom, who loves you and will lie to make you feel good, and still learn something true. His rules, summarized:

  • Talk about their life, not your idea. Pitching invites politeness. Asking about their problems, goals and constraints gets facts.
  • Ask about specifics in the past, not opinions about the future. "Would you use this?" gets optimism. "When did this last happen, and what did you do about it?" gets behavior.
  • Talk less, listen more. And end with a request for a specific next step.

Fitzpatrick's most useful idea for offer validation is that real interest shows up as a commitment: the person gives up something they value. He describes three currencies of commitment: time (a follow-up meeting, a trial, feedback on a draft), reputation (an introduction to a colleague or decision-maker) and money (a pre-order, a deposit, a letter of intent). Compliments and "let me know when it's ready" are not commitments, because they cost nothing.

This lines up neatly with the research above. Commitments close the gap between intention and behavior by asking for the behavior now.

How to validate an offer in seven steps

This is the process I'm using in the Mogul Maxxing build. It's designed for someone with limited time: each step is small enough to fit in one or two work windows, and each one ends with a decision.

1. Write the problem down before the solution

Start with one paragraph: who has the problem, what it looks like on a normal day, what it costs them, and what they've already tried. If you can't name what they've tried, you don't yet know whether the problem is painful enough to act on. People who care about a problem have usually spent time or money on it already. That past behavior is your first piece of evidence.

2. Have five to ten problem conversations

Talk to people who fit the description, without pitching. Ask about the last time the problem came up, what they did, what it cost, and what they'd change. Take notes in their words, not yours. You're looking for repeated patterns: the same frustration, the same failed workaround, the same phrases. Stop when you start hearing the same things. The point isn't a big sample; it's to stop guessing. Steve Blank, whose customer development method shaped much of the modern startup playbook, famously sums this step up as "get out of the building": the answers aren't in your notes app, they're with the people who have the problem.

If you have an audience, this is where it helps most. Invite a small number of people who've engaged with the topic to a short call. Booking the call is itself a small commitment of time, which already filters for people who care.

3. Write a one-page offer

Turn what you heard into a single page. It should state, plainly:

The one-page offer

  1. Who it's for and who it isn't for.
  2. The outcome: what will be true at the end that isn't true now, in their words.
  3. How it's delivered: format, length, what they do, what you do.
  4. The price and what's included.
  5. The guarantee or refund terms.
  6. The start date and how many places, if limited.

Writing this is a test in itself. If you can't state the outcome clearly, or you notice you're describing features instead of a result, the offer isn't ready, and no amount of building will fix that.

4. Decide your success criteria in advance

Before you show the offer to anyone, write down what result would count as validation and what would count as a no. For example: "If at least a set number of the people I ask commit to a paid founding place within two weeks, I build it. If fewer do, I change the offer or the audience before building anything." Choose your own numbers based on what the offer needs to be worth your time.

This step matters because of a very human tendency: once you've done the work, almost any result can be read as encouraging. Setting the bar first protects you from your own optimism. It's the same principle as the decision rules in the founder operating system article: decide once, before the moment, not during it.

Overhead view of handwritten interview notes on cream paper sorted into three columns beside a pen and a ceramic cup on a linen tablecloth
Notes from problem conversations, sorted by pattern. The same frustration showing up again and again is the signal to look for.

5. Ask for a commitment

Show the one-page offer to the people you spoke with, and to others who fit, and ask for the strongest commitment that is honest at this stage. In order of strength:

  • A paid founding place or pre-order, with a clear delivery date and a full refund if you don't deliver.
  • A paid pilot, where you deliver the outcome by hand to a small group before you build anything scalable.
  • A deposit that holds a place and is refundable.
  • A specific time commitment, like joining a scheduled working session, if money isn't appropriate yet.

Asking for money early can feel uncomfortable, especially if you're used to giving content away for free. But it's the clearest way to close the intention–behavior gap. A no is useful too. It tells you something about the offer, the price, the timing or the audience, and it costs you far less than a launch nobody buys.

6. Deliver the first version by hand

If people commit, don't disappear for three months to build. Deliver the first round manually, as directly as you can: live sessions, personal feedback, templates you make as you go. In The Lean Startup, Eric Ries describes this kind of hands-on approach as a "concierge" minimum viable product: serving early customers personally to learn what actually produces the outcome before automating it.

Delivering by hand is how you validate the third thing on the list above, that you can actually produce the result. It also tells you which parts of the offer matter and which you'd have built for nothing.

7. Build only what the commitments justify

Once people have paid and you've delivered, you'll know what to build: the parts that were used, asked for and repeated. Build those. Leave the rest. This is the point where a course platform, a membership or a software tool might make sense, because you're building for known demand instead of hoped-for demand.

Mogul Mastery · founding waitlist

Watch an offer get validated in public

Mogul Mastery is the implementation program I'm building in the open, and it's going through this exact process. The founding waitlist is how I'm learning what founders with limited work windows actually need before anything gets built. It's in development and shaped by founding members.

Validation tests compared

There are many ways to test demand. They vary in how much they cost you and how much they tell you. Here's how the common ones compare.

TestWhat it isBest forWatch out for
Problem interviewsConversations about past behavior, no pitchingFinding the real problem and the words people useSlipping into pitching and collecting compliments
Audience poll or questionAsking followers which problem is most pressingRanking topics quicklyResponses are opinions, not commitments
Landing page with waitlistA page describing the offer with an email sign-upTesting which message gets attentionAn email is a weak signal of buying
Explainer or demo videoShowing how the offer works before it's fully builtOffers that are hard to describe in wordsMust reflect what you can really deliver
Pre-order or founding placeTaking payment for a future start date, with refundsThe clearest early evidence of demandOnly promise what you can deliver on time
Concierge pilotDelivering the outcome by hand to a small paid groupLearning what actually works before buildingDoesn't scale; that's the point at this stage

The most famous example of the explainer-video approach is Dropbox. In an excerpt from The Lean Startup published by TechCrunch, Eric Ries recounts how founder Drew Houston released a short demo video aimed at early adopters before the product was widely available. Houston said the beta waiting list went from 5,000 people to 75,000 people literally overnight. It's a striking story, and worth keeping in proportion: a waitlist is still an intention, and Dropbox's later success depended on a product that worked. The lesson isn't "make a video". It's "show people the promise clearly, then measure what they do."

A note on honesty: test demand without misleading anyone

Some validation advice suggests "fake door" tests: advertising something that doesn't exist to see who clicks. There's a version of that which is fine, such as a waitlist page that clearly says the offer is coming, and a version that isn't, such as taking money for something you have no plan or ability to deliver.

The rules I'm using are simple. Be clear about what exists and what doesn't. Give a real start date or say there isn't one yet. Only take money for something you can deliver, and offer a full refund if you don't. Never invent testimonials, results or scarcity to push a decision. Validation is about learning the truth. Tricking people into a signal defeats the purpose, and it damages the trust an audience-based business depends on.

Woman entrepreneur on a phone call at a window seat with an open notebook on her knee in a warm minimal room
Most validation happens in plain conversations: about their problem, in their words, ending with a clear next step.

Common mistakes when validating an offer

Treating engagement as a yes

This is the creator's trap. High engagement tells you a topic resonates. It doesn't tell you anyone will pay. Use content to find problems, and use commitments to find buyers.

Asking leading questions

"Wouldn't it be great if…?" has only one polite answer. Ask about the last time the problem happened instead. If you notice yourself explaining your idea, you've stopped learning.

Validating with the wrong people

Friends, family and fellow creators are kind, and often not the customer. A yes from someone who doesn't have the problem tells you nothing. Talk to people who fit your one-page description.

Moving the goalposts

If you didn't set success criteria in advance, you'll be tempted to call any result a win. Write the bar down first, and respect it when the results come in.

Building during validation

It's tempting to "just start" on the platform, the branding or the curriculum while you wait. That's the work the validation is meant to decide about. Keep your windows for conversations and the one-page offer until commitments arrive.

Giving up after the first no

A no is information about this version of the offer. Change one thing, the audience, the outcome, the format or the price, and test again. The goal is to learn, not to be right the first time.

How this fits limited work windows

If you only have a few focused hours a week, the validation process fits into them more easily than building does. A rough rhythm:

WeekWork windows go toDecision at the end
Week 1Problem paragraph; booking and holding conversationsIs the problem real and repeated?
Week 2More conversations; writing the one-page offer; setting success criteriaIs the offer clear enough to show?
Week 3Sharing the offer and asking for commitmentsDid enough people commit?
Week 4 and onDelivering by hand, or revising the offer and retestingWhat, if anything, should be built?

An AI second brain helps here in a specific way: paste your interview notes in and ask it to group them by pattern and pull out repeated phrases, then check its grouping against the notes yourself. If you run more than one project, the multifaceted entrepreneur rule applies too: validate one offer at a time, so the evidence doesn't get muddled.

Frequently asked questions

What does it mean to validate an offer?

It means collecting evidence that specific people will commit something they value, such as time, reputation or money, to a clearly described offer before you build the full product. Opinions and compliments don't count as validation. Commitments do.

Why are views and likes not demand?

A view or like costs the person almost nothing and doesn't involve a decision to buy. Research on the intention-behavior gap suggests intentions turn into action only about half the time, and a reaction to content is weaker than an intention. Engagement shows what topics resonate, not who will pay.

What is the strongest signal that an offer is validated?

Money committed in advance, such as a pre-order, a paid founding place, a refundable deposit or a paid pilot. Commitments of time and reputation, like booking a call or making an introduction, are useful earlier signals but weaker than payment.

What is The Mom Test?

The Mom Test is a book by Rob Fitzpatrick about talking to customers without being misled. Its core rules are to talk about their life rather than your idea, to ask about specific past behavior rather than future opinions, and to treat commitments of time, reputation or money as the real signal of interest.

How many people do I need to talk to before building?

There isn't a fixed number. For problem conversations, many founders keep going until they hear the same patterns repeated, which can happen within five to ten conversations for a narrow audience. For the offer itself, set your own success threshold before you start and judge the results against it.

Is a waitlist enough to validate an offer?

A waitlist is a useful early signal of interest, but on its own it is weak evidence of demand because joining costs only an email address. Treat it as a list of people to talk to and ask for a stronger commitment, ideally a refundable pre-order or paid pilot.

What is hypothetical bias?

Hypothetical bias is the tendency for people to state a higher willingness to pay when asked hypothetically than they actually pay with real money. A 2005 meta-analysis by Murphy and colleagues found a median ratio of about 1.35 between hypothetical and actual values, with wide variation between studies.

Is it ethical to sell an offer before it exists?

It can be, if you are honest about what exists, give a clear delivery date, only sell what you can deliver, and offer a full refund if you don't. Taking money for something you have no plan or ability to deliver, or inventing testimonials or scarcity, is not validation and damages trust.

What is a concierge MVP?

A concierge minimum viable product is a way of delivering the promised outcome to early customers by hand, personally and manually, before building an automated or scalable version. The idea is described in Eric Ries's The Lean Startup and is a practical way to learn what actually produces results.

What should I do if nobody commits?

Treat it as information about this version of the offer. Revisit your notes and change one variable, such as the audience, the outcome, the format or the price, then test again. A no at the validation stage costs far less than a launch that doesn't sell.

Where this goes next

This completes the first pass through the six Mogul Maxxing themes, from decision fatigue to offer validation. From here the series goes deeper: how to decide what to work on first, what an AI second brain should actually do for a founder, the difference between a tool, a workflow and a business system, and the build notes from my own first offer as it goes through these steps, including the parts that don't work.

If you want those notes as they happen, join the Mogul Movement. If you want to be part of the offer being validated, the Mogul Mastery founding waitlist is open. You can browse every article on the Mogul Maxxing blog, or go back to the homepage for the full series.

Sources

  • CB Insights. The top reasons startups fail (analysis of 111 startup post-mortems), as reported in SmartCompany, 2021.
  • Sheeran, P., & Webb, T. L. (2016). The intention–behavior gap. Social and Personality Psychology Compass, 10(9), 503–518.
  • Sheeran, P. (2002). Intention–behavior relations: A conceptual and empirical review. European Review of Social Psychology, 12(1), 1–36.
  • Murphy, J. J., Allen, P. G., Stevens, T. H., & Weatherhead, D. (2005). A meta-analysis of hypothetical bias in stated preference valuation. Environmental and Resource Economics, 30(3), 313–325.
  • Fitzpatrick, R. (2013). The Mom Test: How to talk to customers and learn if your business is a good idea when everyone is lying to you. Summary: Sachin Rekhi.
  • Ries, E. (2011). The Lean Startup. Crown Business. Excerpt: How Dropbox started as a minimal viable product, TechCrunch.
  • Blank, S. (2005). The Four Steps to the Epiphany. Overview of customer development: Customer development.

This article is general information about research and common practice in testing business ideas, not professional, legal or financial advice. If you take payments before delivering, check the consumer protection and refund rules that apply where you and your customers are.