Blog / Digital growth /
Validating a digital product idea before building
Building a digital product is a lovely way to avoid one uncomfortable question: will anyone use it, or pay for it?
I know the temptation. A sketch turns into a feature list. The feature list turns into a weekend of work. And suddenly the product feels too real to question.
Validation won’t guarantee success. Nothing does. It’s a way to cut the uncertainty before you spend more time and money.
Describe the problem without mentioning the product
Write down who has the problem, what they are trying to do, what gets in the way and how they handle it now. If the problem only makes sense once you explain your clever feature, it may not be a strong problem yet.
Look for evidence in conversations, existing workarounds, recurring requests and the tools people already use. Compliments are pleasant. Repeated behaviour tells you more. I’d rather hear about one workaround someone actually uses than ten people saying “nice idea”.
Talk to people who fit the audience
Ask about recent experiences rather than hypothetical buying intentions. “When did this last happen?” is more useful than “Would you buy my idea?” People are generous with imagined future decisions. Their current behaviour is harder to fake.
Do not treat a few conversations as proof of a market. Use them to uncover language, constraints and edge cases. If a product could affect money, security or compliance, get the right expertise before making claims.
Test the smallest useful version
A short guide, template, service, prototype or manual workflow can test whether the problem deserves attention. The test should expose the uncertain part: can people understand the offer, complete the task, or pay for a solution?
Set a clear stopping point. If no one takes the next step, learn why before adding features. The answer might be a weak audience, unclear positioning, poor distribution or a problem that is not urgent enough.
Think about distribution and support
A product is not only the thing you build. Consider how people will find it, what they need to set it up, how often it will need updates and what support they will expect. A product with a small scope can still carry a large support burden.
Start with the smallest test that can answer a real question. Keep the cost of being wrong low.
Start with a real problem
A product idea can feel obvious while it is still in your notes. The harder question is whether people have the problem often enough, care enough to solve it and understand the proposed solution. Validation is not a way to guarantee success. It is a way to learn cheaply before spending weeks building something nobody has asked for.
Describe the intended user and the task they are trying to complete. Be specific. “A tool for designers” is too broad to test; “a way for a Framer designer to check a repeated launch detail without leaving the editor” is a hypothesis that can be discussed. Do not start with a feature list. Start with the frustration or job.
Talk to people before pitching
Speak with people who resemble the intended user. Ask what they currently do, when the problem last occurred, what makes the task difficult and what they have already tried. Let them explain their process before showing your solution. If you lead with a polished pitch, many people will be polite instead of candid.
Listen for specifics: a workaround, a repeated delay, a cost or a consequence. One enthusiastic response is not proof of demand. Keep notes without collecting unnecessary personal data, and do not publish quotations or identifying details without permission. Separate what someone said from what you inferred.
Test the riskiest assumptions
List assumptions about the problem, audience, willingness to pay, distribution and support. Which one could make the idea fail? Design a small test for that assumption. A landing page with a clear description can test whether people want to learn more, but a sign-up does not prove they will pay. A prototype can test usability, but praise for a prototype does not prove someone will adopt it in daily work.
Use honest language. Do not imply the product already exists if it does not. If you ask for an email address, explain what the person will receive. If you propose a price, make clear whether it is a hypothetical price or an actual offer. Keep the test proportional to the decision you need to make.
Think about the work after launch
A digital product needs more than a build. Consider how customers will discover it, how they will receive it, what support they may need and how you will handle updates or refunds. A small product can still create ongoing obligations. Estimate the time and tools needed, and decide what you can realistically maintain.
If the product depends on another platform, check the relevant rules and technical limitations before committing. Keep the first version narrow enough to support and learn from. Avoid building several features to compensate for uncertainty about the core problem.
Decide what evidence would change your mind
Before running a test, write down what you expect and what result would make you continue, revise or stop. That protects you from explaining away every weak signal after the fact. Look at behaviour as well as comments: did people complete the test, ask a follow-up question or take a clearly explained next step? The sample may be small, so describe it honestly and do not generalise beyond what it shows.
Validation is useful even when the idea changes. A conversation may reveal a different problem, a better audience or a reason not to build. That’s progress if it saves you from investing in the wrong solution.
Related reading
So, before you open your editor this weekend: write down the one assumption that would sink your idea if it were wrong. Then plan one small test for it. What’s yours?