Trying a new approach: talk to users before building đ
Iâve launched a few small tools before, but I usually skipped the whole âtalk to people firstâ step. Iâd just build, ship, and hope something stuck.
This time, Iâm trying something different. I started asking around about a pain I kept noticing, SaaS free trials and how hard it is to get meaningful feedback from users.
To my surprise, people actually responded. Some said itâs a real pain, and a few even said the idea made sense.
Itâs the first time I feel like I might be solving a real problem, not just building for fun. Right now Iâm working on a small MVP, nothing fancy. Just testing the waters and learning from feedback.
Curious how others in here validated early ideas. Anything that worked for you? Or mistakes to avoid? Would love to learn from your experience.
Replies
Kalyxa
Love that you're flipping the script! Talking to users early saved me months of building the wrong thing. Biggest lesson: don't just ask if they like the ideaâask if theyâd pay for it or have tried solving it already. Thatâs where the gold is. I would recommend reading The mom test if you havenât already.
@helton_silva We posted about this on our newsletter (https://ideatbd.com/):
The $0 Validation Script
Step 1: Pick a friend
Not your cofounder, not your mom - someone who might actually have the problem your idea solves.
Step 2: Ask these 5 questions
(Ask them casually, like you're just curious - not running a user research lab.)
1. Can you walk me through the last time you did [X]?
2. What was the hardest or most annoying part about it?
3. What did you end up doing instead?
4. If someone built a fix for that, what would it have to include?
5. Is this problem annoying enough that you'd pay for a fix?
Donât pitch your idea yet.
Just let them talk. Youâre trying to understand the problem, not sell the solution.
---
Step 3: Spot the Signals
Youâre looking for one of these:
- They light up emotionally - "Ugh yes, thatâs the worst."
- They already hacked a solution together - huge signal.
- They describe a pain your idea actually solves - naturally, without prompting.
If you hear crickets or confusion, good. You just saved yourself 3 months of wasted work.
---
Step 4: Talk to 5 People
Thatâs it. Not 100.
Just 5 people who might deal with the problem.
Ask yourself:
- Did at least 3 describe a version of the same pain?
- Did your idea actually solve that pain?
- Was it significant enough that theyâd care - or even pay - for a fix?
If yes â green light to MVP.
If no â either refine the problem or kill the idea.
---
TL;DR
Ideas donât need a prototype. They need a diagnosis.
Before you build, ask 5 real people how theyâre surviving without you.
If theyâre fine, your app isnât needed.
If theyâre frustrated - youâre onto something.
The accelerator I'm in stresses that before you build your MVP, do the "100 Challenge." As in speak to 100 random people (not friends nor family) about their pain points. Don't even bother building the MVP until you've talked to 100 people and can nail down the problem in a simple sentence.
@jWell said. "Brilliant advice! The '100 Challenge' forces real validationâno assumptions, just data. If you can't crisply define the problem after 100 conversations, your MVP is just a guess. Talk first, build second."
Had the same habit of skipping validation and building solo. Talking to folks early felt awkward at first, but it definitely saved me from wasting months on stuff no one needed.
Where/How did you find the first people to talk to?
In late 2023, we started our startup journey and answered 9 questions to go from idea to $$$ in 30 days:
Are people talking about the problem or looking for a solution?
Will people pay to solve this problem?
Who will be our primary customer?
Can we develop a solution that addresses the core problem within 2-3 days?
Will this solution add value either by saving time or money for the user?
How will we reach our primary customers to get feedback and first 10 sales?
How will we collect testimonials from early adopters?
What data do we need to track to gain insights?
How can we bring 1,000+ users to our website?
I have shared our personal experience here. I hope this helps.
PS: We answered these questions for building a productized service, but I guess they are pretty much valid if you are building a SaaS as well.
Validation mistake I made early on: pitching the solution instead of probing the problem.
What helped was running 15-min user calls where I never mentioned my idea I just asked how they currently tackled the problem and where they got frustrated. The patterns that surfaced there were gold. I realized if they donât feel the pain unprompted, the idea probably isnât worth building.
Curious how youâre running those early convos are you framing the problem openly or showing the MVP already?