A practical guide to validating a software idea before you build: customer interviews, landing pages, concierge MVPs, and what each method costs.
The cheapest reliable way to validate a software idea in 2026 costs $1,000 to $5,000 and takes two to six weeks: customer interviews, a landing page, or a concierge MVP, all before you write production code. If you want a development partner to run a structured sprint with research, a clickable prototype, and a go/no-go recommendation, plan $5,000 to $20,000 and two to four weeks. You do not need to build the product to learn whether people will pay for it.
A full build is expensive: a focused SaaS MVP runs $20,000 to $60,000 and a FinTech or payments MVP starts around $80,000. Spending a few thousand dollars first to confirm real demand is the highest-return step in a project and usually changes the scope you would otherwise have built.
| Validation method | Typical cost | Time to a signal | What it tests |
|---|---|---|---|
| Customer interviews (10-15) | $0-$1,000 | 1-2 weeks | Problem frequency and pain |
| Landing page + waitlist | $300-$2,000 | 2-4 weeks | Demand and messaging |
| Concierge MVP (manual delivery) | $500-$5,000 | 4-6 weeks | Willingness to pay |
| Clickable prototype (Figma) | $2,000-$10,000 | 2-4 weeks | Workflow fit and usability |
| Validation sprint with a dev partner | $5,000-$20,000 | 2-4 weeks | Scope, cost, go/no-go |
These are planning ranges, not quotes.
Interviews are nearly free if you do them yourself; the cost is your time, about 30 to 45 minutes each across 10 to 15 conversations, plus a scheduling tool or a small incentive. A landing page with a waitlist runs a few hundred dollars on a site builder plus a small ad budget. A concierge MVP costs more because you hand-deliver the service to five to ten paying pilots for four to six weeks, mostly operating hours, not software.
When you bring in a development partner, the price reflects their seniority and what they produce. A sprint that ends in a clickable prototype and a written scope typically runs $5,000 to $20,000 over two to four weeks. Agencies usually price discovery at 10% to 15% of the eventual build, so a $100,000 platform implies $10,000 to $15,000. That money usually saves more than it costs by cutting features nobody asked for.
Customer interviews come first because they are cheap and they expose the problem, not your solution. Aim for 10 to 15 conversations in your target market, asking about their current process, what it costs them, and what they already tried. Do not pitch your idea in the first half of the call, or you will collect politeness instead of signal, the point of The Mom Test.
A landing page with a waitlist tests demand at slightly larger scale. Write the offer clearly, run a small paid campaign, and measure how many visitors leave an email. That number is weak because an email costs nothing to give; it becomes useful when you compare it to a benchmark or follow up for a deposit.
A concierge MVP tests the strongest signal: willingness to pay. You deliver the service manually to five to ten paying customers with spreadsheets and existing tools. Airbnb's founders rented out air mattresses by hand before writing production code. If people pay for the manual version, the problem is real; if they will not, software will not fix it.
A clickable prototype tests workflow fit. If the idea involves an approval chain, a dashboard, or a booking flow, a Figma prototype shown to real users reveals where they get stuck. Prototypes are right when the risk is usability or workflow, not demand. At this stage proof of concept, prototype, and MVP start to blur, so know which one you are paying for.
Signups, likes, and "I would totally use this" are not validation. They cost the user nothing and predict nothing. Real validation is an action that has a cost: a paid pilot, a signed letter of intent, a deposit on a waitlist, or a customer who switches an existing workflow to your manual service. A landing page that collects 300 emails proves people like the headline, not that they will pay. Treat anything below a paid commitment as a lead, not proof.
B2B ideas validate differently: a B2B buyer needs one reason tied to cost, time, or compliance, and five to ten prospects in your network is often enough. Consumer ideas need a larger sample and a clear distribution path. Either way, the paid test beats the free test.
You do not need a finished spec, but have five things before you spend on a build: a one-page problem statement, 10 to 15 recorded interviews, a single core feature you are confident in, a target price point, and a rough budget and timeline. These turn your idea into a scope and an estimate instead of a guess. For shaping the interviews into a plan, read how to define an MVP before hiring developers and our guide to hiring a software development company.
A short discovery phase pays off here. GlobeSoft runs a one-to-three-week sprint ending in a prototype, a prioritized feature list, and a written estimate. That is the difference between quoting a project and quoting a hope.
Validation is not a religion. An internal tool that replaces a spreadsheet your team already uses every day does not need interviews; the demand is visible in the frustration. A compliance-driven build, something the law or a client contract requires, has no demand question to answer. And when a competitor has already proven the market and you have a distribution or pricing edge, waiting to validate a second time burns the advantage.
Even then, do the cheap version: write the one-page problem statement and talk to three people.
Two to six weeks for interviews, a landing page, or a concierge MVP; two to four weeks with a development partner. Complex B2B products can take longer because the paid pilot is slower to close.
Mostly yes. Interviews cost only your time, and a concierge MVP can start with five paying customers and a spreadsheet. The first real dollar usually goes to landing page traffic or interview incentives, and both are optional.
When you have a paid signal: a deposit, a signed pilot, or a customer using a manual version of the service for more than a week. A handful of "maybe" responses is not enough. Five paying pilots is a common threshold before an MVP.
A test where you deliver the product's core value by hand to a small group of paying customers, using spreadsheets and off-the-shelf tools instead of custom software. It proves people will pay before you spend on development.
No. A landing page measures interest, which is weak because an email address is free to give. It helps test messaging and build a list, but you still need a paid commitment before you call the idea validated.
B2B validation usually means 10 to 15 direct interviews and a few paid pilots, leaning on a clear cost, time, or compliance reason. Consumer validation needs a larger sample and a distribution plan. Both hinge on a paid action, not a verbal yes.
Validation is the step where a small amount of money removes the largest risk in your project. If you have an idea and want it pressure-tested before you build, GlobeSoft can run a short discovery sprint ending in a prototype, a scope, and a realistic estimate. We are a software development company based in Shenzhen, China, with 40+ engineers and 300+ delivered projects, and we take founders from first interview to launch. See our custom software development services, or get in touch.
GlobeSoft builds custom software, AI applications, SaaS, FinTech and enterprise systems for clients worldwide. Message us on WhatsApp for the fastest answer, or email us — we typically reply within 24 hours.
Keep reading
What AI compliance actually requires before you build: the EU AI Act, GDPR, HIPAA, SOC 2, and the engineering work they add to AI projects in regulated industries.
11 min readThe clauses that decide who owns the code, who carries the risk, and when you actually pay. A plain-English guide to software development contracts and SOWs.
10 min readDeciding between an MVP and a full product is the most expensive call a founder makes. Here's a practical framework for deciding what to build now and what to defer.
10 min readDefine the MVP before you talk to developers and your quotes become comparable, your build gets shorter, and you stop paying for features nobody asked for.
5 min readCloud migration services go wrong when teams lift servers before they understand the data. What decides the schedule, the cost, and the rollback.
5 min readWeb application development spans a landing page and a SaaS product. The gap is scope. Here is how to pin it down before you spend.
