Is Your App Idea Ready to Build? A Practical Founder’s Check
A grounded way to test whether an app idea has a clear user, a painful enough problem, and a sensible first release before you spend on development.
By Aleksej Djokic ·
Start with the problem, not the feature list
A promising idea is more specific than “an app for everyone.” Write down who has the problem, what they do today, and what becomes easier if your product works. For example, “independent tutors lose track of lesson follow-ups across text messages and spreadsheets” gives a build team something to investigate. “A better education app” does not.
Five questions worth answering
- Who will use the product first, and in what situation?
- What workaround do they use today: a spreadsheet, inbox, phone call, or another product?
- How often does the problem happen, and what does it cost in time, money, or missed opportunity?
- What is the smallest useful outcome the app can deliver?
- How will you know the first release helped? Choose a behaviour or business signal, not a download target alone.
A low-cost reality check
Interview five likely users
Ask about their last real example rather than pitching your solution. Listen for repeated language and workarounds.
Sketch the critical path
Draw the few screens or actions between the problem and the useful outcome. If the path is unclear, the product is not ready to scope.
Name the riskiest assumption
Decide what could make the idea fail: willingness to pay, access to data, a marketplace’s supply, or a hard technical constraint.
A useful decision rule
You do not need proof that the whole business will work before building. You do need enough evidence to choose a narrow first problem and a way to learn from the release. If you cannot name the first user and their first useful outcome, keep researching before commissioning a full app.