How to validate a SaaS idea without building more features
Validation is not something you build your way into. It is something you find in conversations - and most SaaS founders skip straight past it because conversations feel slower than shipping.
Validation is a conversation skill, not a coding skill
A feature cannot tell you whether people want your product. It can only tell you whether you were capable of building it. Whether the market wants it is answered by people, in their own words, describing a problem they already have and are already trying (and failing) to solve.
Real signals vs. false signals
Real signals
- Someone asks when they can pay, without you bringing up pricing
- A prospect describes the problem back to you more precisely than you described it
- People ask to be notified the moment it is ready
- Someone offers to pay before the product is even built
False signals
- "This is cool" with no follow-up question
- Likes and shares on a launch post
- People saying they would use it "eventually"
- Friends and family being encouraging
"Encouragement is free. Money, time and attention are not. Validate on the things people are not willing to give away for free."
A simple validation loop
Talk to 10 people who match your target customer. Ask about the problem before mentioning your solution. Note who describes real pain with specific, recent examples. Only then, show a rough version of the idea and ask what would make it worth paying for. Repeat weekly - validation is not a single milestone, it is a habit that should run alongside building, not before it just once.
Want to turn this into a daily habit? Join the GTM Gate beta.