Validating Demand Before You Build Anything

• Compliments and survey interest rarely predict real demand.
• Interview people about the problem before pitching any solution.
• Landing pages, waitlists and pre-orders test real commitment.
• Manual service can prove demand before you automate anything.
• Set success thresholds before testing, so results can't be explained away.
• If you take pre-order payments, follow the FTC's shipping and refund rules.

This guide covers ways to validate demand: problem interviews, search research, landing page tests, waitlists and pre-orders, ad tests, manual service, business commitments, price tests, success thresholds and pre-order rules. Put plainly: test what people do, not what they say, and decide your pass mark before you start.

People are polite. "I'd use that" costs nothing to say.

Surveys overstate interest. Saying yes is easy; paying is not.

Founders hear what they hope. Without clear tests, weak signals feel strong.

Look for actions. Sign-ups, deposits, time spent and referrals.

Ask about the past, not the future. "Tell me about the last time this happened" beats "Would you buy this?"

Avoid pitching. Learn how people handle the problem today.

Listen for spending. Money or time already spent on workarounds shows real pain.

Talk to enough people. Patterns appear after a series of conversations, not one or two.

Check what people search. Search volume for the problem and existing solutions shows interest.

Read the results. Competitors and forums reveal what people want and what's missing.

Problem-first searches. The searches buyers make before they know a product exists, as covered in SaaS SEO.

One page, one offer. Describe the product and ask for one action, as covered in one page, one offer, one action.

Be clear it's coming. Say the product isn't available yet.

Short forms. Ask only for what you need, as covered in form length.

Quick to build. Simple tools work well, as weighed in no-code, low-code or custom.

Waitlists. A first signal, stronger if people share or answer follow-up questions.

Deposits and pre-orders. Much stronger signals, because money is involved.

Follow the rules. If you take payment, the FTC's mail and internet order rule requires shipping within the time you state, or within 30 days if you don't state one, unless buyers agree to a delay or get a refund.

Make refunds easy. If plans change, refund promptly.

Test messages. Different headlines and offers to see what attracts interest.

Small budgets. Enough to see patterns, not to scale.

Measure actions. Sign-ups and deposits, not just clicks.

Do it by hand first. Deliver the result manually to early customers.

Learn what matters. See which parts customers value before building software.

Charge for it. Payment proves value better than free trials.

Letters of intent. Written interest from companies, with expected terms.

Paid pilots. A small paid trial shows serious intent.

Ask who approves budgets. Interest from someone without budget authority is weaker.

Show a real price. Interest at "free" says little about willingness to pay. For app products, store payment rules affect pricing, as covered in in-app payments.

Compare options. Different price points or packages on test pages.

Watch what people choose. Actions reveal value better than questions.

Decide the pass mark. Such as a target share of visitors joining a waitlist or a number of paid pilots.

Write it down. Before starting the test.

Act on results. Proceed, change direction or stop.

Then build small. Move into a focused first version, as covered in scoping an MVP.

Interview patterns. How many people describe the same problem.

Landing page conversion. Visitors who join or pre-order.

Paid commitments. Deposits, pre-orders or paid pilots.

Cost per sign-up. From small ad tests.

Follow-up engagement. People who reply, share or ask when it's ready.

Interview potential customers about the problem and how they handle it today. Research search demand and competitors, and write down success thresholds for the next tests.

Launch a landing page with a waitlist or pre-order, run small ad tests and try a manual version of the service with early customers.

Compare results with your thresholds. Proceed to a focused first version, change direction or stop, and refund any pre-orders you can't fulfill on time.

Astra Results Marketing helps founders and businesses test demand before building. We plan interviews, research search demand, build landing pages and waitlists, run small ad tests and set success thresholds in advance.

When the results justify it, we build the smallest useful product. Engagements begin with a demand validation plan through our MVP development team.

Related reading

• MVP Development: Launching the Smallest Useful Product
• Scoping an MVP: What to Cut and What to Keep
• MVP Timelines and Budgets: Weeks, Not Years

People are polite and saying yes costs nothing. Actions such as signing up, paying a deposit or committing to a pilot are much stronger signals.

Ask about the problem and past experiences, such as the last time it happened and what they did, rather than whether they'd buy your idea.

Yes, if you're clear the product isn't available yet. Waitlists and pre-orders show real interest.

The FTC's mail and internet order rule requires shipping within the time you state, or within 30 days if none is stated, unless buyers agree to a delay or get a refund.

Set a success threshold before you start, such as a sign-up rate or number of paid pilots, write it down and compare the results against it.

A focused first version that solves the core problem, built with the smallest useful scope.

Ready to know people want it before you build it? Astra Results Marketing plans interviews, landing page tests, waitlists and pre-orders with clear success thresholds, then builds the smallest useful product when demand is proven. ▸ CALL (786) 321-2866 · ▸ REQUEST YOUR CONSULTATION