We just hit 1,000 members 🎉
To celebrate, we’re opening a SaaS Showcase Thread where founders can share what they’re building.
👉 Drop your SaaS below:
⚡ Rules:
Let’s use this thread to discover new tools and support builders in the community 🚀
Hey, I’ve been working on https://scriptonia.dev
I kept running into the same problem you have a decent product idea, maybe a messy Slack thread or some notes, but turning that into a proper PRD that engineers can actually use takes way too long.
So I built something to make that easier.
You can drop in a rough idea or discussion, and it gives you a structured PRD, along with things like system flow, APIs, schema, and even tickets to get started.
Still early, but it’s been useful for me while building, so thought I’d share it here.
Could be for productivity, coding, editing, or anything useful.
Looking to discover some underrated tools 👀
We talk to hundreds of businesses every month and everyone is always looking for honest software recommendations from real people.
So here is what we are doing.
Drop the tools you use daily in the comments and tell us in one line why you love or hate them. We will pick the most interesting ones and feature them right here on the page so the whole community can see them.
To get featured tell us:
What tool you use
What you use it for
One honest thing you think about it
I’m building Trenith AI, and I decided to start with one narrow problem: helping SaaS founders understand weekly Stripe revenue changes.
I noticed that early founders usually know something changed in revenue, but not always why it changed. Was it churn? Failed payments? Downgrades? Fewer new subscriptions? Expansion slowing down?
So the first version is a weekly brief that explains what moved in Stripe and what to look at next.
I’m keeping the beta small because I want to learn before adding too many features.
For other indie hackers: when you review revenue, what do you check first — MRR, churn, failed payments, upgrades, downgrades, or something else?
Not looking for “best tools” lists, just real examples.
What software did you start using for one thing, but it ended up improving your workflow way more than expected?
Drop the tool and what it changed.
Not looking for the obvious answers. Everyone's using ChatGPT for something.
I mean the specific combination of tools you've actually built into your marketing workflow — and what job each one is doing.
For example is it content, ads, email, SEO, social, outreach? And which AI tool handles that for you specifically? What does your stack looks like?
Every sales team I talk to has the same setup:
CRM
spreadsheets
cold email tool
LinkedIn tool
notes app
Slack reminders
random Zapier automations
another dashboard nobody checks
…and somehow leads STILL fall through the cracks.
A rep books a call.
Nobody follows up.
Warm lead disappears.
Another one gets hit 14 days later with “just checking in.”
It feels insane that in 2026 outbound still looks like this.
I honestly think the problem isn’t “lead generation.”
It’s that the entire workflow is fragmented.
You have:
one tool for data
one tool for outreach
one tool for tracking
one tool for pipeline
one tool for follow-ups
And nobody actually has a SYSTEM.
So I started building something for this internally.
Basically:
lead tracking
outreach
follow-up logic
deal movement
pipeline visibility
team accountability
reminders that don’t suck
AI assistance built directly into workflow
Not another bloated CRM.
More like an outbound operating system.
The goal is:
You should NEVER lose a warm lead because your stack is disconnected.
Would anyone actually use something like this?
Or am I the only one losing my mind over how broken outbound still is?
I did a quick audit of my tools last month.
$30 here. $49 there. $99 for something I used twice.
Added up to way more than I expected, and half of it was tools I signed up for during a "productive" week and never really committed to.
But here's the thing, some of those tools genuinely save me hours every week and the math actually works out. Others are just digital hoarding.
Curious if anyone has actually done this exercise, went through every subscription and been honest about what's earning its cost vs what's just sitting there.
What did you cut? And what survived the audit?
We’re doing a stack audit and realized our team is drowning in pings. Slack is our hub, but the huddles and thread notifications are constant. Some of our devs are pushing for a move back to a more "Discord-style" setup, while management wants us to go full MS Teams for the integration.
In your experience, which one is actually the "quietest"? I’m looking for the tool that lets people actually do deep work without needing a PhD in notification settings to stay sane. Or is the problem the culture, not the tool?
I'm currently working on some complex projects, but love building prototypes in the mean time. If Anybody has any simple requests, you're welcome to ask.
I’m looking for a few small teams to test a very lightweight internal helpdesk I’ve been building.
The idea is simple:
tickets that feel like conversations instead of enterprise software.
Main focus:
* extremely fast setup
* simple enough for non-technical teams
* searchable history
* saved solutions
* less chaos than WhatsApp/email
I’m not really looking for “startup feedback”.
I’m more interested in understanding:
* what feels natural
* what feels annoying
* what people ignore completely
* whether teams actually keep using it after day 1
Free access obviously.
In exchange, I’d love honest day-to-day feedback.
Especially interested in small businesses currently managing requests through chats, calls or scattered messages.
If you're evaluating or struggling with a tool, drop:
I’ll suggest:
Also, if you’ve already solved a software problem, jump in and share what worked (and what didn’t).
Let’s build a thread that’s actually worth bookmarking.
Most small teams already use conversations as a ticket system.
The problem is that after a few days everything disappears into:
* WhatsApp chats
* Slack messages
* emails
* calls
* random screenshots
So the same problems get solved over and over again because nobody remembers the original solution.
That’s why I started building TaskDesk
The idea is simple:
conversational tickets.
Tickets that feel natural like a chat, but stay organized, searchable and saved over time.
The video shows a small example of how comments and saved solutions work inside a ticket.
Main goals:
* fast setup
* lightweight
* searchable history
* saved solutions
* simple enough for non-technical teams
I’m currently looking for a few small teams willing to beta test it in real-world usage.
Especially interested in teams currently managing internal requests through chats, emails or scattered messages.
Would genuinely love honest feedback on:
* what feels natural
* what feels confusing
* what people ignore completely
* whether teams actually keep using it after the first few days
Nobody talks about the embarrassing stuff.
The manual DMs at midnight. Submitting to 30 directories by hand. Replying to strangers venting on Reddit just to start a conversation.
I've been speaking to a lot of small product owners lately and the honest answer is almost never "we ran ads" or "we went viral." It's usually something scrappy, repetitive, and a little desperate, that somehow worked.
So what was yours? The thing you'd never put in a case study but actually moved the needle.
Not talking about building the product. That part everyone figures out.
I mean after, when it's live and nobody's showing up.
A lot of small product owners I've spoken to say the hardest part isn't the product, it's getting in front of the right people without a big budget or a marketing team.
So I'm curious, what actually moved the needle for you? Could be a tool, a platform, a channel, anything.
And if you're still figuring that part out, drop where you're stuck. Maybe someone here has been through it.
Been 13 years in performance marketing and different lead gen niches, nowadays i have my GTM startup that enabling distribution at low costs.
Made the classic mistake tho by focusing on several acquisition channels at once when started marketing.
Only once i laser focused on one channel i made progress- Conversee which is the tool ive made helps you focus on intent demand and get REAL traction at fair costs.
What were your mistakes when started your biz distribution and marketing?
These three come up constantly whenever someone asks about note-taking or knowledge management and everyone has a strong opinion.
Notion people swear by the flexibility. Coda people say it's more powerful for actual workflows. Obsidian people never shut up about it (respectfully).
But what I actually want to know is which one you started with, which one you're on now, and what made you switch, or stay.
Real experiences only. Not feature lists.
Definitely sourcing is one tough part but given today's social world with Linkedin, Naukri X, reddit, simple job post will get 1000 applicants.
Equally tough part is having minimal pipeline to manage applicants and find best hire from them.
Broken pipeline like accepting applicants via Google forms, HR emails, spreadsheets, slack threads might seem faster in the initial stages, but suffer in later stages
- Downloading and managing offline resumes,
- outreaching applicants
- Sharing profiles across client's team
- Moving across stages
These are very crucial user flow actions but broken pipeline will slow down process drastically, might leading to overlooking quality ones or even making bad hire.
Building an ATS for startups VS SMBs would be totally different game in terms of features and cost-value proposition.
We have built HuntYourTribe, lightweight ATS to make life easy for HR professionals.
Curious to know what the community thinks!
Genuinely curious where people draw the line.
Because I’ve seen teams:
What’s your personal “okay, we should’ve just bought this” moment?