u/Existing_Bowler1376

Every time I try a new SaaS tool, it feels like I need a full tutorial just to do basic things.

Most of them are packed with features, but the core workflow gets buried under menus, settings, and dashboards.

Shouldn’t software be simpler by default instead of requiring users to figure it out?

Curious how others feel about this do you prefer feature heavy tools or minimal ones that just do one job well?

I kept wasting hours every week doing the same repetitive process.

I looked for existing tools, but they were either:

• Too expensive
• Too complicated
• Missing one feature I really needed

So I built a simple SaaS to solve exactly that problem.

Now I'm wondering if it's just a me problem or something others experience too.

Has anyone here dealt with something similar?

If yes, how are you solving it today?

Curious to hear from founders, developers, and business owners.

What's one repetitive task in your work that still feels unnecessarily manual?

Something where you constantly think:

"There has to be a better way."

Could be related to marketing, finance, HR, content creation, customer support, or anything else.

Sometimes the best SaaS ideas come from everyday frustrations.

I've been auditing my monthly subscriptions and realized I was paying for 14 different SaaS tools.

I canceled 9 of them without noticing much difference.

But there are a few I wouldn't cancel even if the price doubled because they save me hours every week.

What's one SaaS product you'll probably keep paying for no matter what, and why?

I'm looking for tools that genuinely improve productivity not just the latest hype.

Every week I see new AI tools launching.

Some people say the market is overcrowded, while others argue there's still plenty of room if you're solving a specific problem.

What's your take?

• Are you still building AI products?
• Have you found a niche that's working?
• Or do you think it's becoming harder to compete?

Curious to hear perspectives from founders who are building right now.

I'm at the point where every customer asks for something different.

One wants AI.

Another wants integrations.

Someone else wants better reporting.

After a while it feels like you're building five different products instead of one.

How do you decide when to say no to feature requests?

Do you follow a framework, or is it mostly intuition?

Getting your first users is one challenge, but scaling seems like a completely different game.

For those who've grown a SaaS:

• What became the biggest bottleneck?
• Customer acquisition?
• Retention?
• Pricing?
• Hiring?
• Something else?

I'd be interested in hearing what actually surprised you once people started using your product.

When I started building, I assumed coding would be the biggest challenge.

Turns out the hardest part has been understanding what people actually want.

I've changed features multiple times because users used the product in ways I never expected.

For anyone building something right now: what's a problem you didn't expect to face when you started?

I’ve been thinking about this a lot while rebuilding my product from scratch.

If I started again, I would:

Pick a niche with existing spending (not “potential” demand)

Launch ugly but fast (2–3 weeks max MVP)

Focus on 1 acquisition channel only until it works

Avoid overbuilding features early

What I would NOT do again:

Spend months perfecting UI before launch

Ignore distribution until after product completion

Build general tools instead of painful niche problems

Would love to hear from founders:

What would you do differently if you started today?

I see a lot of founders obsess over tech stack, AI features, UI, etc.

But after trying 3 SaaS ideas, I’m convinced:

The real failure point is idea validation, not execution.

Two of my projects failed because:

I built before confirming demand

I assumed pain = willingness to pay (it’s not)

The one that worked:

Started with 15 customer interviews

Pre-sold before building anything real

Only then wrote a single line of code

Feels obvious now, but it wasn’t at the time.

How do you personally validate ideas before building?

I launched a very simple SaaS last month (no big launch, no ads). I just wanted to validate if anyone would actually use it.

What surprised me:

Cold outreach didn’t work at all

Twitter posts got likes but zero signups

Reddit actually brought my first 10 users

What worked on Reddit:

Posting without a link first

Talking about the problem, not the product

Replying to every comment like a normal user, not a founder

Still early, but lesson learned: distribution matters more than features.

Curious how did you get your first 10 to 50 users?

After talking to a few small business owners recently, I noticed something interesting.

Most SaaS founders (including me) start with:

"What can I build with AI?"

But customers start with:

"What annoying thing can I stop doing?"

The gap is huge.

Nobody wakes up wanting:

• AI agents
• RAG pipelines
• Vector databases
• Multi agent systems

They want:

• Fewer support tickets
• Less manual data entry
• Faster invoicing
• Fewer mistakes

I feel like we're in a phase where everyone is competing on technology instead of outcomes.

Every day I see:

• AI note takers
• AI writing tools
• AI chatbots
• AI sales assistants

Most seem like features rather than businesses.

So I'm curious:

If you had:

• $0 funding
• 1 technical founder
• 6 months runway

What AI SaaS would you build today?

Bonus points if:

• It's boring
• Solves a real business problem
• Can get paying customers quickly

Interested in seeing where people think the next opportunities are.

Curious about how other SaaS founders approached their first hire.

Some people seem to stay solo until $20k+ MRR, while others hire much earlier.

Questions:

• What was your MRR when you hired your first employee?
• What role was it?
• Looking back, was it too early or too late?

Trying to understand where the sweet spot is between staying lean and accelerating growth.

For the longest time, I thought growth meant building more features.

Every week I'd add something new.

More integrations.
More settings.
More customization.

Then I spent a month doing something different:

• No major feature releases
• Focused only on onboarding
• Fixed bugs
• Improved documentation
• Talked to customers

The result?

Better retention and more upgrades than the previous month.

It made me realize that sometimes improving the experience is more valuable than expanding the product.

Have you ever removed or delayed features and seen better results?

When I launched my SaaS, I assumed paid advertising would be my main acquisition channel.

Turns out I was completely wrong.

The majority of my recent users came from:

• Writing helpful content
• Answering questions in communities
• Sharing lessons learned publicly
• Building relationships instead of campaigns

It's slower than ads, but the users tend to be more engaged and stick around longer.

I'm still experimenting, but organic growth has been much more effective than I expected.

What acquisition channel has worked best for your SaaS?

I've tested dozens of CRM platforms and keep running into the same issues:

• Too many features I never use
• Complex setup processes
• Expensive pricing as teams grow
• Poor integrations

I'm considering building a lightweight CRM focused on simplicity and automation.

Before I go down that rabbit hole, I'd love to hear:

What's the #1 thing you wish your CRM did better?

Trying to validate the idea before writing a single line of code.

A few months ago, I launched a simple SaaS focused on helping small teams manage recurring operational tasks.

No venture funding.
No large audience.
No paid ads.

What worked:

• Talking directly to users
• Posting useful content in niche communities
• Shipping features quickly based on feedback

What didn't work:

• Building features nobody requested
• Trying to target everyone
• Spending too much time on branding early

Still a long way to go, but getting those first paying customers taught me more than months of planning.

Curious to hear how others got their first users.

One of the biggest mistakes I've made while building my SaaS was assuming I knew what users wanted.

I spent nearly 3 months building what I thought would be the product's killer feature.

I was excited about it.

The code was clean.

The UI looked great.

Then I launched it.

Result: almost nobody used it.

After talking to users, I realized they cared much more about solving a simpler problem that I had been ignoring because it didn't seem exciting to build.

That experience changed how I work:

• I validate ideas before building.
• I talk to users every week.
• I prioritize problems over features.
• I ship smaller updates much faster.

For other founders:

What's the most time you've wasted building something users didn't actually want?

I recently got my first 10 paying customers for my SaaS.

What surprised me most wasn't pricing, marketing, or onboarding.

It was that almost none of them used the product the way I originally intended.

People kept finding workflows and use cases I never considered.

A few lessons:

• Users don't care about features; they care about outcomes.
• Most onboarding flows are too complicated.
• Customer conversations are more valuable than analytics.

For founders who already have paying customers:

What's the biggest thing your users taught you that changed your roadmap?