The cheapest way to test a product idea is to avoid building the wrong one. Here are five low-cost validation techniques we recommend before starting a 90 Day MVP.

Every founder we meet has a product idea they believe in. Most of them are right that a problem exists. Where they get into trouble is assuming their specific solution is the one people will pay for, use and recommend.

That gap between “a real problem” and “the right solution” is where most software budgets disappear. You can spend six figures building something nobody wants, or you can spend a weekend figuring out whether the idea has legs before a single line of code gets written.

Here are five validation techniques we walk founders through before any 90 Day MVP begins. None of them require a development team, and most cost nothing but time.

1. Talk to ten potential users

This sounds obvious, and almost nobody does it well. The goal isn’t to pitch your idea and count nodding heads. People are polite. They will tell you your idea sounds great and then never use it.

Instead, ask about their current experience. Find people who match your target user and ask them how they handle the problem today. What tools do they use? What frustrates them? What workarounds have they cobbled together? If they aren’t already spending time or money trying to solve this problem, your product may not have a market yet.

A good validation interview has three rules:

Ask about the past, not the future. “When was the last time this came up?” beats “Would you use a tool that did this?”
Listen for pain, not interest. A mild “that sounds nice” is useless. A frustrated description of a broken process is gold.
Watch for skin in the game. If someone offers to pay for a solution that doesn’t exist yet, or asks when they can beta test, you have a real signal.

2. Build a landing page before a product

A landing page is the fastest way to test whether strangers care about your idea. You describe the product as if it exists, explain the core value, and give visitors a way to express interest: an email signup, a waitlist, or a “request early access” button.

Then you drive a small amount of traffic to it. Fifty dollars in targeted ads or a few posts in relevant communities will tell you something real. If nobody clicks through and nobody signs up, you have learned something important for very little money.

The landing page also forces you to articulate your value proposition in plain language. If you can’t write a headline that makes the benefit obvious in five seconds, your product positioning needs work. This guide on what your website should answer before sales does covers the questions every page needs to address, and those questions apply to landing pages just as much as they apply to full websites.

3. Run a concierge test

A concierge test means doing the job manually for a few real customers before automating it with software. You act as the system. A spreadsheet, some emails, and your own time replace the app you would eventually build.

This works because it tests the core value without the core cost. If you’re building a scheduling tool, manage bookings by hand for five clients. If you’re building a reporting dashboard, compile their reports yourself each week. If you’re building a web application or a mobile app , figure out whether the manual version of the workflow actually solves the problem before you automate it.

The concierge test answers the question that matters most: will people use this consistently once it exists? If your five manual clients stop engaging after two weeks, that pattern will likely repeat with software. If they keep coming back and refer others, you have strong evidence to invest in building the real thing.

4. Study what already exists

Competitors are free market research. If someone is already solving this problem, that’s validation that the market exists. Your job is to figure out what they’re getting wrong.

Sign up for competing products. Use them as a real user would. Note every moment of friction, every confusing screen, every feature that feels bolted on. Read their reviews and support forums. Customers publicly complain about exactly what they wish existed instead.

This research also sharpens your differentiation. In a crowded market, the question isn’t whether you can build a better version. It’s whether you can articulate, in one sentence, why someone should switch. These strategies for standing out in a crowded market are a good starting point for thinking through that positioning.

5. Test the workflow on paper

Before interactive prototypes, try paper. Sketch the three or four screens that make up your core workflow. Show them to someone who fits your target user and ask them to walk through a simple task: “You just signed up. Show me how you would do X.”

Watch where they hesitate. Watch where they tap the wrong thing. Watch where they look for something that isn’t there. You will learn more from five minutes of watching someone struggle with a paper mockup than from a week of building screens nobody tests.

The goal here isn’t to refine the design. It’s to find the dead ends in your mental model of how the product works. Dead ends are cheap to fix on paper and expensive to fix in code. Reducing friction early is far easier than removing it after launch, when users have already formed their first impression.

What validation tells you

After running even two or three of these techniques, you will know one of three things:

The idea is ready. You have evidence of real pain, a clear value proposition, and users who want it. Time to scope an MVP.
The idea needs work. The problem is real but the solution or positioning is off. You saved months of building the wrong thing.
The idea isn’t there yet. The market isn’t ready, the pain isn’t strong enough, or the economics don’t work. You saved the most money of all by not building.

None of these outcomes is a failure. The only failure is skipping validation and discovering the answer after you have already spent your budget.

Validation is not procrastination

There’s a fine line between validating and stalling. Some founders research forever because building feels risky, and research feels safe. The point of validation is to reach a confident decision, not to achieve certainty.

That’s why we recommend a time box. Give yourself two weeks to talk to users, build a landing page, and run a concierge test. If the signals are positive, start building. If they aren’t, adjust or move on. Two weeks of validation against twelve weeks of building is a trade any founder should make.

When the signals say go, a 90 Day MVP turns that validated idea into a live product with real users, real analytics, and a roadmap built on evidence. That’s a much stronger starting position than a blank slate and a gut feeling.

Already validated your idea and ready to build? Tell us about it . We’ll help you scope a focused MVP that launches in 90 days.