Have a Product Idea? Test Demand Before You Pay to Build It

A step-by-step guide to finding out who wants your product, what they might pay for, and what to build first.

You’ve been exploring an idea with ChatGPT. Maybe you have a name, a feature list, and a few screens. Now you’re wondering: “How do I make this real, and how do I know it’s worth spending money on?”

Before committing to a full build, gather evidence that a specific group of people has a problem important enough to act on. Start with conversations, a simple offer, and a website that tests interest. Then invite interested people into a small pilot.

Y Combinator’s guidance emphasizes talking to users, launching a small first version, and learning from actual use. This guide applies those principles. The landing-page and advertising test is our practical approach, not a prescribed YC formula. Watch YC’s How to Plan an MVP.

What should you validate before spending money?

You don’t need perfect answers. You need enough evidence to justify the next step.

1. Choose one customer and one problem

“An app for small businesses” is too broad to test well. Start with a narrower statement:

We help [specific customer] achieve [desired outcome] when [specific problem happens].

For example: “We help independent interior designers collect client approvals without chasing decisions across email and text messages.”

Now you know whom to talk to, what situation to ask about, and what a useful outcome might be.

Your task: Write your statement in one sentence. Avoid listing features.

2. Find out how people handle the problem today

Start with five conversations as a manageable first batch. That’s a starting point, not a validation threshold. Speak with people who fit your intended audience. Ask them to describe a recent experience before showing your idea.

• When did this problem last happen?
• Can you walk me through what you did?
• What tools or people were involved?
• What was the hardest part?
• What did the delay or mistake cost you?
• Have you tried fixing it? What happened?
• Who decides whether to pay for a solution?

For the interior-design example, ask someone to show you how a real approval moved through their project. Observing the workflow can reveal needs people forget to mention. YC’s user-observation guidance recommends investigating actual behavior while keeping your own talking to a minimum. Read YC’s Practical Design: User Observation.

Your task: Record each person’s problem, current workaround, consequences, and willingness to take a next step.

Keep investigating if: People like the idea but cannot describe a recent situation where they needed it.

3. Check the alternatives, including doing nothing

Your competition includes whatever people already do: a spreadsheet, a shared inbox, an assistant, an existing app, or accepting the inconvenience.

Write down why someone would switch. For example: “They can approve a decision from a link without creating another account, and the designer gets a clear record.” That is a testable reason to change behavior.

“A cleaner dashboard” may look attractive, but you still need to learn whether it solves something customers care about.

Your task: Compare your proposed approach with three current alternatives. Include switching effort, not just features.

4. Define an offer someone can respond to

Explain who it is for, what it helps them accomplish, how it works, what it costs or the pricing you want to test, and what they can do next.

Client approvals, without the chasing.
We’re inviting independent interior designers to test a simpler way to send options, collect decisions, and keep an approval record. Apply to join the pilot.

Your task: Write the offer and choose one primary action.

Be clear when a product is in development. Don’t present mockups as an available product or imply that joining a waitlist means receiving immediate access.

5. Build a landing page that tests the offer

You don’t need the entire product to explain the value and invite a response. A useful test page needs:

• A clear headline: What can the customer accomplish?
• A specific audience: Who is this designed for?
• A short explanation: How would it work?
• A visual: A relevant mockup, walkthrough, or prototype.
• Honest availability: Concept, upcoming pilot, or available now.
• One main action: Request access, book a conversation, or apply.
• A useful confirmation: What happens after someone submits?

Our example headline could be: “Get client decisions out of your inbox and into one clear approval flow.”

The form might ask for an email and one qualifying question: “How many active client projects are you managing?” That helps distinguish relevant interest from casual curiosity.

Your task: Make sure someone can understand the offer and next step without you explaining it.

6. Bring the right people to the page

Start where you can reach likely customers: personal outreach, a professional network, relevant communities, or a small paid campaign.

Ads can help test whether a defined audience responds to a particular offer. They don’t establish demand on their own.

A paid test is useful when you can reach a reasonably specific audience, explain the value clearly, track a meaningful next step, and follow up with the people who respond.

Direct conversations may be more useful when buyers are hard to target, purchases require lengthy approval, or the product needs explanation.

Paul Graham’s advice to recruit early users manually is relevant here: founders shouldn’t assume that launching a website will bring customers automatically. Read Do Things That Don’t Scale.

Your task: Choose one audience, one offer, and one primary channel for the first test. Avoid spreading a small budget across many unrelated experiments.

7. Decide what success means before running ads

Write down your test plan before spending. Otherwise, it’s easy to interpret any activity as progress.

Define your criteria around the business you’re testing. There is no universal conversion rate that proves an idea is viable. A few qualified conversations could be useful for an expensive business product. A low-price consumer app requires different economics.

Your task: Agree on a spending cap and decision criteria before the campaign starts. Test the form, confirmation, and tracking first.

8. Measure the whole journey, not just clicks

A worked example

This is an illustrative example, not a benchmark: $300 in ad spend brings 150 visitors, 12 inquiries, four qualified inquiries, two attended pilot conversations, and no paying customers yet.

• Cost per inquiry: $300 ÷ 12 = $25.
• Cost per qualified inquiry: $300 ÷ 4 = $75.
• Cost per attended conversation: $300 ÷ 2 = $150.

You have useful information about acquisition and interest. You have not yet established customer acquisition cost because nobody has become a paying customer.

Your task: Track qualified responses and follow-through alongside traffic. Keep ad spend separate from website, creative, and campaign-management costs.

9. Talk to the people who responded

Every relevant inquiry is a chance to learn. Ask:

• What caught your attention?
• What were you hoping this would help you do?
• How are you handling that today?
• How soon do you need a solution?
• What would you need to see before trying it?
• Who else would need to approve a purchase?

Then propose a concrete next step: a prototype session, a pilot discussion, or a small paid engagement with clearly defined scope.

If people sign up but won’t take the next step, investigate why. The timing, price, trust, offer, or perceived effort may be wrong.

Your task: Record objections in customers’ own words. Use them to improve the offer and decide what to test next.

10. Deliver the smallest useful outcome

When you see credible interest, test whether you can actually solve the problem. You may be able to run a pilot using simple tools and some manual work before building a complete application.

For the approval tool, that might mean:

1. Helping a designer prepare a real decision request.
2. Sending it through a simple review interface.
3. Recording the client’s response.
4. Checking whether the process reduced confusion or follow-up.

Measure the outcome you promised. Did the client complete the approval? Did the designer use the process again? What still required help?

YC’s MVP guidance favors a limited first version that gets into users’ hands quickly and improves through feedback. Some products need substantial technical or safety work before they can be tested responsibly; the smallest useful version depends on the problem. YC: How to Plan an MVP.

Your task: Define one complete customer outcome. Build only what you need to deliver and evaluate it.

How to decide what to do next

One weak campaign doesn’t prove there is no market. One strong campaign doesn’t prove the product will succeed. The purpose is to reduce uncertainty before making a larger commitment.

Your checklist before commissioning a full build

Tick the statements you can support with evidence. This checklist stays on this page and resets when you reload. Use the download to keep your notes.

• I can identify the first customer group.
• I have heard recent, specific examples of the problem.
• I understand their current alternatives.
• I can explain why someone would switch.
• I have tested a clear offer with relevant people.
• I have evidence stronger than compliments or clicks.
• I understand who uses the product and who pays.
• I have tested pricing or had concrete purchasing conversations.
• I know what the first useful version must accomplish.
• I have a realistic plan for reaching early customers.
• I know which assumptions remain untested.

Unchecked boxes aren’t a reason to abandon the idea. They tell you where your next experiment should focus.

How UX Signal Studio helps you test demand

If you have an idea but aren’t ready to commit to a full product build, we can help you test the offer first.

We help shape the proposition, design and build a focused landing page, and run targeted ads that bring potential customers to it. We set up the inquiry flow and measurement so you can see who responds and what they do next.

Together, we look at:

• Which message attracts relevant people.
• Whether they take a meaningful next step.
• What questions and objections come up.
• What the results suggest you should test or build next.

The outcome is a clearer decision about where to invest. An ad campaign cannot guarantee demand, and early interest still needs to be tested through conversations and real use.