What if instead of adding features first, SaaS products were designed by removing everything unnecessary first?
Start with one core action, then only add features if they truly support that action.
I wonder how many tools would look completely different if built this way.
Would people prefer fewer features but cleaner workflows, or more control with complexity?
It’s interesting how many SaaS products are basically solving:
But the real difference is how they approach the user experience and workflow.
Feels like the competition is less about “what it does” and more about “how it feels to use.”
I'm doing customer research for a SaaS I'm building.
Curious what makes you go from this is cool to actually pulling out your credit card.
Is it:
I'd love to hear what convinced you to subscribe to your favorite SaaS product.
A few months ago I knew almost nothing about launching a SaaS.
Today, it's live.
Some things I learned:
I'm now focused on talking to users instead of endlessly adding features.
For those who've launched before:
What's the one thing that helped you get your first 100 users?
I've noticed a trend with software:
A $10/month tool that wastes my time is actually more expensive than a $50/month tool that saves me hours every week.
Do you mostly choose software based on:
Or something else?
Curious how everyone decides when there are so many alternatives available.
I spent months polishing features before talking to potential users.
When I finally launched, people wanted something completely different.
It taught me that validating demand is much more important than building the "perfect" product.
For those who've built (or tried to build) a SaaS:
What's the biggest lesson you learned the hard way?
Everyone talks about scaling, but getting those first few customers seems like the hardest part.
If you've built a SaaS, I'd love to know:
What worked, and what ended up being a complete waste of time?
I've seen a lot of founders spend months building before getting any real user feedback.
For those who've launched a SaaS:
Interested in hearing both success stories and mistakes.
Hypothetical question.
If someone gave you a laptop and six months to build another SaaS, but you couldn't build in the same niche you're in today...
What would you build?
Not looking for billion dollar ideas.
I'm more interested in patterns industries that still have obvious pain points or workflows that haven't been modernized yet.
Curious to hear what experienced founders would pick.
One thing surprised me after dozens of customer interviews.
People rarely care about your technology.
They care about:
I spent weeks explaining how my app worked.
The moment I started explaining what problem it removed, conversations became much easier.
What lesson completely changed how you sell your SaaS?
There are thousands of SaaS products out there, but only a handful become part of your daily workflow.
For you, what's the one tool you'd recommend to almost anyone?
Mine are usually:
I'm looking to discover underrated tools that save time or solve a real problem.
What's on your list, and why?
I've been looking at a lot of early stage SaaS products, and I keep noticing the same pattern: founders spend months building features before talking to potential customers.
It made me wonder:
I'd love to hear real experiences, especially from people who've launched a SaaS.
A year ago I believed consistency alone would solve most problems.
Now I think learning what to ignore is just as important.
Founding a product has changed a lot of my assumptions.
What's one opinion or belief you've completely changed since starting your journey?
I see a lot of founders sharing updates on Reddit, X, LinkedIn, and other platforms.
Some swear by it.
Others say it mostly attracts other founders rather than actual users.
For those who've tried building in public:
What benefits did you actually get from it?
And what downsides don't get talked about enough?
I'm curious how other founders recognized the signal that their idea had potential.
Was it:
Looking back, what moment made you think, "Okay, maybe this is actually worth building"?
I recently noticed people using my tool for something completely different from its original purpose.
It wasn't a bug or misuse they genuinely found a use case I never considered.
Now I'm debating whether to embrace it or stay focused on the original vision.
Have your users ever surprised you with how they used your product?
An AI powered customer support copilot for small SaaS companies.
Instead of hiring support agents early, founders can:
The twist:
The AI explains why it gave an answer and cites the source document.
Target audience:
Questions:
Trying to kill bad assumptions early.
For the last 2 years, I've been running projects using a combination of:
Eventually, I realized I was spending more time organizing work than actually doing work.
So I spent the last few months building a tool that:
Before I spend more time on it, I'm curious:
How are you currently managing tasks and priorities?
And what's the most annoying part of your current workflow?
Looking for honest feedback, not validation.
I'll start:
A common mistake I see is spending months building features before talking to enough customers.
Many founders optimize for product perfection when they should be optimizing for validation.
What's the biggest mistake you've made while building or scaling a SaaS?
Could be:
The lessons are usually more valuable than the wins.
Everyone talks about the big names, but I'm interested in the tools that genuinely save you hours every week.
For example:
What's one SaaS product that delivers way more value than its monthly cost?
Would love to discover some hidden gems.