To validate an app idea, prove three things before anyone writes code: real people have the problem, they will change what they do to fix it, and some of them will pay or commit time. You can test all three in four to six weeks with conversations, a manual version of the service, and a simple pre-sale. None of it needs a developer.
Owners usually skip straight to "how much to build it?" That question comes later. A validated idea gets cheaper quotes too, because you can describe it in a paragraph instead of a wish list.
Key Takeaways
- Validation means watching behavior: what people already do, what they sign up for, what they pay for. Compliments don't count.
- Run the tests in order. Each one is cheaper than the next and can stop you early.
- A manual version (a form, a spreadsheet, you doing the work by hand) is the strongest test most owners never try.
- Eric Ries defined the minimum viable product as the version that gets "the maximum amount of validated learning" with "the least effort." Often that version isn't software.
Five Ways to Validate an App Idea This Month
| Test | Typical cost | Time | What it proves |
|---|---|---|---|
| 1. Ten problem conversations | $0 | 1 week | The problem is real and frequent |
| 2. Search and competitor check | $0 | 1 day | Others look for it; what exists already |
| 3. Landing page with a sign-up | Low (free site builders exist) | 1 week | Strangers care enough to leave an email |
| 4. Manual version | Your time | 2-4 weeks | People will change their routine |
| 5. Pre-sale or deposit | $0 | 1 week | People will pay |
1. Talk to ten people who have the problem. Ask what happened last time, what they did, what it cost. Keep your idea out of it. Y Combinator's advice in How to Talk to Users is to "not introduce your idea until maybe at the end of the call or maybe not at all." If fewer than half describe the problem without prompting, stop here.
2. Check search interest and what already exists. Google Trends shows relative interest on a 0 to 100 scale, so it tells you whether interest is rising or flat, not how many people search. Then search the app stores. Finding competitors is usually good news; see our guide on what to do if your app idea already exists.
3. Put up a one-page site. Describe the outcome, add a sign-up button, and send it to the people you interviewed plus a few groups where your customers gather. Count sign-ups from strangers, not friends.
4. Run the service by hand. This is the test that separates real demand from polite interest. If the app would let clients reorder supplies, take orders through a shared form and fulfill them yourself for a month. If people use it every week, you have demand. If they forget about it, an app won't fix that.
5. Ask for money. A deposit, a signed letter of intent, or a paid pilot at a real price. Y Combinator's essential advice puts it bluntly: "you must launch something, talk to your users to see if it serves their needs, and then take their feedback and iterate."
A Concrete Version
Marco owns a commercial cleaning company with 40 office clients. His idea: a client portal where office managers reorder paper towels, soap and trash bags without emailing him.
Week 1: he called 12 office managers. Eight described reordering as a recurring annoyance before he mentioned any portal.
Weeks 2 to 5: he set up a free online form for 5 of those clients and filled the orders himself. Over four weeks they sent 31 orders, about 1.5 per client per week.
Week 6: he offered the portal at $40 a month. Three of the five said yes. That is 3 x $40 x 12 = $1,440 a year in new revenue, plus the email back-and-forth he no longer handles.
What he learned: the demand is real, but $1,440 a year won't fund a custom build on its own. His next step is to keep the form, roll it out to all 40 clients, and see how many pay. If even 15 of the 40 pay, that is 15 x $40 x 12 = $7,200 a year, and a small custom portal starts to make sense.
That decision (keep the tool, one developer, or a small team) is exactly what an Honest Read gives you. Sol asks a few questions, one at a time, and writes a report whose verdict is one of three: "Keep going with the tool," "One developer for a few weeks," or "A small team, fixed price."
The Honest Counterpoint
Validation can kill good ideas. People are bad at imagining new habits, so a truly new product can fail interviews and still succeed once people can use it. If your idea depends on a behavior nobody has yet, lean on tests 4 and 5 and go light on test 1.
Validation also takes discipline that many owners don't have. It is easy to keep "testing" for six months to avoid a decision. Set a budget (say six weeks) and a pass line before you start, such as "three paying customers," and decide when the clock runs out.
Finally, internal apps for your own staff skip most of this. You don't need a landing page to know your dispatcher wastes 10 hours a week. You need the time math.
Frequently Asked Questions
How long does it take to validate an app idea?
Four to six weeks for most small-business ideas: one week of conversations and a quick search, two to four weeks of a manual version, and a week to ask for money. Much longer than two months usually means you are avoiding a decision.
Can I validate an app idea without building anything?
Yes, and you should start that way. Conversations, a landing page, a manual service and a pre-sale all work with no code. Build only after people use the manual version. Our guide on what to leave out of the first version helps when you get there.
What should I do after I validate my app idea?
Get a written read of what it takes. A free Honest Read lists the screens, the hard parts, what to leave out of version one, and three ways to get it built with real cost ranges, and you can hand it to any developer for a quote. Read what the Honest Read includes before you start.
The Bottom Line
Prove the problem, prove the habit change, prove someone will pay. In that order, cheapest first. When the tests pass, get an Honest Read from Sol to see what the build really takes, then compare quotes using what a good software quote looks like.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
