r/Startup_Ideas

For months, I saw other founders talking about Reddit as this goldmine for early traction, but every time I tried, it felt like walking through a minefield. I'd spend hours scrolling, trying to find relevant threads, carefully crafting replies, only to either get ignored or, worse, instantly flagged for self-promo. It was frustrating, inefficient, and honestly, a bit intimidating. The fear of getting banned from a valuable community was always lurking.

I realized the problem wasn't Reddit itself, but my approach. Most of us just dive in thinking "I need to market my SaaS here," when really, Reddit is about communities, solving problems, and being genuinely helpful. You can't just pitch; you have to earn the right to even hint at a solution.

So, I shifted my mindset. Instead of pushing my product, I focused on:

• Deep Listening: Really understanding the pain points people voiced, not just keywords.
• Community Rules: Treating each subreddit like a unique country with its own laws.
• Authentic Engagement: Participating in discussions where I could genuinely add value, even if it wasn't directly related to my SaaS.

This started to work. I built karma, made connections, and found a few legitimate opportunities to share my insights. But here's the kicker: it was still incredibly manual and time-consuming. Identifying threads with real buying intent among thousands, then drafting a reply that was both helpful and compliant with obscure subreddit rules? That was the biggest bottleneck.

That's why I started using a tool called Karmo. It basically turns Reddit from a time sink into a predictable lead-gen channel. What I love about it is how it watches my chosen subreddits, scores posts by buying intent, and surfaces only the high-value threads. Then, for each, it generates an on-brand reply in the subreddit’s native tone, while checking rules so I don’t get banned. It compresses discovery, drafting, and compliance into one pass, making Reddit actually usable as a growth channel. It even helps generate ban-proof posts for different goals, whether it’s sharing ideas, optimizing for SEO, or making a gentle pitch.

It’s been a game-changer for consistently finding and engaging with potential users without the constant fear of the ban hammer. If you're struggling to make Reddit work for your SaaS, I highly recommend adopting a community-first approach, and tools like Karmo can seriously streamline the most challenging parts.

What strategies have you found most effective for engaging with Reddit communities without crossing the line?

Share your work/SaaS/app.

I'm working on: https://www.weekhack.com/

Weekly launch platform. Launch your side project. Get a high-DR backlink

Looking for honest feedback on whether this solves a real enough pain point or if it’s just “nice to have.”

I built Dunningly.app — a tool that automates overdue invoice follow-ups for freelancers, consultants, and small agencies.

The problem I was trying to solve:

Most people don’t forget to follow up on unpaid invoices…
they avoid it because it’s awkward and mentally draining.

So the product handles:

• automatic overdue reminders
• escalating tone over time
• CSV/PDF invoice import
• reminder tracking
• pause/resume reminders per invoice

Basically “set and forget” invoice chasing without sounding aggressive or damaging client relationships.

One thing I’m especially trying to figure out:
is the real value the automation itself, or the psychological relief of not having to manually chase clients?

Curious what people think.
Would you use something like this?
If not, why?

Every company does training. Almost nobody thinks it works.

Slides, videos, a quiz at the end. Done. Two weeks later nobody remembers anything and everyone knows it, but the box is checked so we move on.

The thing that actually works is practice. Doing the thing, not watching someone explain the thing. The problem is practice is expensive - it requires time, a trainer, and someone willing to play the other side of an uncomfortable conversation.

So we made the AI do it.

You write the scenario. Your team talks to the AI. It can be a difficult client, a sales call, an internal procedure, an onboarding situation - whatever your team actually needs to get better at.

We call it Socratize.io. MVP is live.

Does this resonate with anyone here, or is corporate training just something people complain about but never actually fix?

Hey everyone — PasteCheck just launched on Product Hunt today, and I'd love your support!

It's a free, mobile-friendly code linter that runs entirely in your browser. Paste your JavaScript, TypeScript, Python, or HTML and get instant error highlights with plain-English explanations. No install. No account. Just paste and check.

Built this entirely from my Android phone as a solo dev, It would mean a lot if you checked it out on Product Hunt today.

(https://www.producthunt.com/products/pastecheck)

Happy to answer any questions!

Tibo (the founder behind tools like Revid.ai, Outrank.so, SuperX, Post Syncer, and Feather) broke down exactly how he repeatedly takes micro‑SaaS products to $100K+ MRR.

Here’s a structured breakdown of how he does it, framed as a repeatable playbook rather than just a success story.

Who is Tibo and what did he build? 

• Founder profile: Indie builder from France who has launched dozens of products over the last few years.
• Current portfolio:
  • Revid.ai – AI video creation SaaS, ~$400K MRR and still growing.
  • Outrank – AI + SEO SaaS, recently crossed $200K MRR.
  • SuperX – Audience growth tool for X (Twitter), >$10K MRR.
  • Post Syncer – Cross‑posting social scheduler, currently early stage but profitable.
  • Feather – Notion → blog publishing tool, acquired for $250K and grown to ~$10K MRR.
• Portfolio outcome: Combined portfolio at ~$700K MRR, growing ~20% month‑over‑month with ~50K paying customers.

How he actually builds winning SaaS products (step‑by‑step) 

1. Build the MVP in days or weeks, not months 

• Take shortcuts: No‑code (e.g., Bubble), boilerplates (Best one in town - AnotherWrapper), skipping non‑critical engineering polish.
• Reasoning: He assumes a ~90% failure rate for new ideas; the only way to win is to run many attempts quickly.
• Goal: Ship a new project fast enough that failure only cost weeks, not years.

2. Talk only to relevant users, not friends or family 

• Find 5–10 “perfect fit” users for the initial version.
• Acquisition channels: X (Twitter), subreddits, email, small DMs.
• Key idea: Feedback from non‑target users is noise; it doesn’t help with product‑market fit.
• Find Validated Painkiller Ideas - Sonar

3. Build real relationships with early users 

• Deep discovery, not shallow surveys: Understand their workflow, daily life, and the real pain behind their request.
• Outcome: This context guides which problems to solve and which features to completely ignore.

4. Talk to users every single day 

• Objective: Understand why they do or don’t come back to the product.
• Tactic:
  • Until a product hits $10K MRR, the support link points directly to his Twitter DMs.
  • He replies quickly, fixes issues in minutes or hours, and turns users into evangelists.
• Effect: Faster iteration, higher retention, and extremely “human” support for early customers.

5. Understand the user’s ultimate goal 

• Think beyond the feature: He focuses on what users ultimately want (e.g., more traffic, revenue, audience), not just the immediate function of the tool.
• Why it matters: When the product directly moves the ultimate metric that matters to the user, perceived value (and willingness to pay) increases 10–100x.

6. Build features that solve their problems, not the founder’s 

• He is a heavy user of his own tools, but still prioritizes real users’ pains over his own preferences.
• Execution style:
  • Fix small UX issues immediately.
  • Ship requested features in 1–2 hours when possible.
• Result: Users feel “heard” and start advocating for the product publicly.

7. Iterate in public and stay close to your users 

• Use social media as a feedback + relationship loop:
  • Share progress, ship logs, and updates.
  • Watch what users ask for in replies and DMs.
• Benefit: Continuous demand‑driven roadmap, instead of guessing in isolation.

8. Don’t scale acquisition until people can’t live without it 

• Focus on retention first:
  • If new users churn instantly, acquisition is a leaky bucket.
  • Complaints are treated as a strong signal of commitment (only invested users bother to complain).
• Checkpoint: Only when users are “stuck” to the product does he start pushing growth hard.

How he approaches distribution and scaling 

9. Go broad on acquisition channels (then measure) 

• Early growth tactics:
  • Product Hunt launches.
  • Building in public on X.
  • General social promotion.
• Goal: Find which channels actually move the needle for that specific product.
• Typical pattern: These free/organic efforts are often enough to reach the first $1–10K MRR.

10. Turn the company into a media engine 

• Content is non‑optional:
  • Social content, SEO content, email, or cold outreach – pick one strength and lean in.
  • Publish case studies, testimonials, and practical content around the problem space.
• Reason: A repeatable content pipeline keeps fueling all other acquisition channels.

11. Double down on scalable channels: SEO, ads, affiliates 

• He focuses on three main scalable levers:
  • SEO (long‑term, compounding).
  • Paid ads (scalable budget if unit economics work).
  • Affiliate programs (partners drive customers in exchange for revenue share).
• Example: Outrank went from $0 → $20K MRR by building in public, then $20K → $200K MRR after adding SEO, ads, and an optimized affiliate program.

12. Ruthlessly scale what works and kill what doesn’t 

• For each product, only 1–2 growth channels truly matter.
• Once those are identified:
  • Scale them hard (more content, more ad spend, more campaigns).
  • Drop or minimize everything else that doesn’t show clear ROI.
• Mindset: Growth is about deep focus on a few effective channels, not doing everything.

Why he runs a portfolio instead of just one SaaS 

• Risk management: Multiple products = resilience against platform and AI shocks.
• Real example: When Elon changed X’s policies, it almost killed Tweet Hunter at ~$200K MRR.
• Today: If one product gets disrupted by a new AI feature or platform change, the rest of the portfolio keeps the company and his family financially safe.

Main takeaway for builders 

Tibo’s core message is simple: the “secret” isn’t a niche hack or a magic tech stack. It’s:

• Building fast and expecting many projects to fail.
• Talking to users daily and letting their real pains drive the roadmap.
• Delaying “growth hacking” until retention and stickiness are obvious.
• Then going very deep on 1–2 acquisition channels that clearly work.

For anyone building SaaS or micro‑SaaS right now, his process is a concrete, repeatable how‑to rather than just a motivational story.

https://apps.apple.com/us/app/humanize-ai-text-rewriter/id6738139751 only on App Store

I’m going to personally review it after I use it. Used once so far so good!

Hello, I created a website for my product called QuickProof, but I’m not really satisfied with how it looks right now. The layout feels a bit plain and not very engaging, and I’m struggling to figure out how to improve the design and overall structure.

Here’s the link: https://www.quickproof.ai/

I would also like to make the page more clear in terms of what the product actually does and add better sections for things like workflow explanation and early access signup. Can someone guide me on what I should improve or change? Any feedback would really help.