2
6 Comments

SaaS Growth: Stop Building Features Nobody Wants

SaaS Growth thrives when you stop building features nobody wants. Answer real questions, delight users, and boost your Indie Hacker success.

Stop Building Features Nobody Wants – Start Answering Real Questions
The harsh truth: Your customers don’t care about your shiny new dashboard or the latest feature you built. What they really care about is the problem that keeps them awake at 3 AM.

Why Indie Hackers Fall Into the Feature Trap
As indie hackers, many of us fall into the same cycle:

A customer mentions a problem → We rush to build a feature.

Low engagement → We build another feature.

Still no growth → We polish the UI.

Repeat until motivation and funds run dry.

I witnessed this firsthand. After 18 months of helping founders craft “feature announcement” blog posts, the traffic was nice—but conversions? Terrible.

Then came the accidental breakthrough.

The Breakthrough: Answering Real Questions
One client, a solo founder of a productivity app, ditched polished blogs for honest answers on Hacker News during coffee breaks. Those spontaneous comments got more signups than six months of my “professional” content.

That moment changed everything.

I started lurking where real users hang out:

Hacker News threads about workflow frustrations.

Twitter conversations venting about tools.

Niche Reddit groups.

Discord servers buzzing with conversations.

Comments on competitor blogs.

The pattern? People ask the same core questions repeatedly. Yet, no one gives honest, detailed answers.

The Shift That Actually Works
Old approach: Write about your product.
New approach: Write about their problems.

Instead of:

“Introducing Our New Analytics Dashboard”
Try:

“Why Your App Analytics Are Lying to You (And What to Track Instead)”

Instead of:

“10 Productivity Tips for Remote Workers”
Try:

“I Tracked My Productivity for 90 Days. Here’s What Actually Moved the Needle”

Instead of:

“Our Tool vs. Competitors”
Try:

“When to Use Notion vs. Airtable vs. Custom Solutions (Decision Framework)”

Real Indie Hacker Wins
Productivity app founder: Shared authentic daily workflows instead of generic advice. Monthly signups doubled; churn dropped 40%.

Agency tool builder: Posted honest breakdowns of failed experiments. Attracted more qualified leads who understood real value.

E-commerce SaaS: Publicly analyzed customer support tickets. Competitors’ customers started reaching out directly.

Authenticity and specificity outpace polished marketing every single time.

Content That Converts Indie Hackers
"I Built This Feature. Nobody Used It. Here’s Why"

"Our Worst Month: $247 MRR and What I Learned"

"The Customer Email That Changed Our Roadmap"

"Most Free Trials Fail. Here’s What I Learned"

"The Stupid Onboarding Mistake That Took Me Months to Notice"

"Spent $2k Testing Payment Processors. Here’s What Actually Matters"

Questions That Drive Growth
How to validate ideas without building anything?

What’s the real cost of technical debt for indie hackers?

How do indie hackers handle customer support alone?

What metrics actually matter for early-stage SaaS?

How do you compete with free tools as a solo founder?

My Indie Hacker Research Process
Daily: Scan Hacker News, Indie Hackers, Twitter for repeated complaints.

Weekly: Analyze customer support tickets for content ideas.

Monthly: Interview 2-3 customers about biggest frustrations.

Tools That Help
Hacker News search

Twitter advanced search

Customer.io surveys

Loom for interviews

Notion for organizing themes

Mistakes That Waste Time
Over-optimizing answers to sound like marketing copy.

Copying big company strategies that don’t fit indie scale.

Focusing on SEO rankings over being truly helpful.

Avoiding controversial takes—leading to boring content.

Publishing inconsistently and losing momentum.

What Actually Works for Indie Hackers
Be scrappy: One deep answer beats ten shallow posts.

Be personal: Share your struggles, not just success stories.

Be specific: “Increased signups 40%” beats generic “explosive growth.”

Be consistent: Better to publish weekly than sporadically.

Be helpful first; monetize later.

Let’s Talk
What question do you get asked most by potential customers?

Where do people in your niche go to complain or seek help?

What’s your biggest content creation struggle as a solo founder?

Happy to dive into specifics in the comments. Indie hacking isn’t easy, but sharing what works helps all of us grow.

Edit
To those asking if this is a sales pitch—I’m just sharing what I’ve seen work. We all face the same “content vs. building” hustle as indie hackers. This is my take on wiring that balance for growth.

This article aims to motivate indie hackers to focus on authentic content answering real questions, avoiding wasted effort on unwelcome features, and building genuine relationships that fuel sustainable growth.

posted to Icon for group Saas Makers
Saas Makers
on September 4, 2025
  1. 2

    Really resonates! Early-stage SaaS teams often rush to build features instead of solving real user problems. Even small misalignments between product and user needs can change projected retention and growth dramatically. When you research these patterns, do you see more insights from forum discussions or directly from early user behavior?

    1. 1

      Both matter, but I usually start with forums and communities to spot recurring pain points and questions. Early user behavior then validates which ones actually impact retention and growth. The combination helps avoid building features nobody wants.

  2. 2

    Love this! Especially the “one deep answer beats ten shallow posts” mindset. So much of indie hacking is noise over signal. What I've found works: Every Monday I plan 3 key goals for the week that map directly to my quarter’s objective. It keeps me from getting sucked into distraction or features nobody asked for.

    Really appreciate the reminders here!

    1. 1

      Thanks Ian! Love your 3 key goals approach ..... it’s a perfect way to cut through the noise and stay intentional. That discipline is exactly what keeps indie hackers from falling into the feature trap.

  3. 1

    100% agree with this — I’ve seen so many projects sink time into features that only 1% of users care about. In your experience, what’s the best way to validate which feature requests are actually worth building: surveys, direct user calls, or usage analytics? I usually lean on analytics + 1:1 calls, but curious what you’ve found.

    1. 2

      100% agree, analytics + 1:1 calls is solid. i usually start by spotting repeated pain points in usage data, then hop on quick calls to understand context and desired outcomes. surveys work too, but only after you’ve seen patterns—otherwise feedback can be too broad or vague.

Trending on Indie Hackers
I built a tool that turns CSV exports into shareable dashboards User Avatar 81 comments $0 to $10K MRR in 12 Months: 3 Things That Actually Moved the Needle for My Design Agency User Avatar 67 comments Why Indie Founders Fail: The Uncomfortable Truths Beyond "Build in Public" User Avatar 56 comments The “Open → Do → Close” rule changed how I build tools User Avatar 52 comments I got tired of "opaque" flight pricing →built anonymous group demand →1,000+ users User Avatar 42 comments A tweet about my AI dev tool hit 250K views. I didn't even have a product yet. User Avatar 41 comments