Built a SaaS all week, hit one tiny bug, grabbed a handful of pie seeds out of frustration, and threw them at my friend while screaming my bs.
Pretty sure this is what founders mean by work life balance.
Anyway, Leadline has been way less painful than debugging:
https://leadline.dev
Feels like there are still a lot of boring painful workflows nobody has solved properly yet.
Usually the best ideas are not futuristic. It is just something people are already hacking together with spreadsheets, docs, and manual work every week.
Interested what problems people here still keep running into.
If your website only offers email signups or magic links, nobody is going to use it. Period.
I learned this the hard way with Lervos. I had 2,000 visits in the first week, yet the only person in the database was me. It felt like a ghost town. I started doubting my own code! Added PostHog and it clicked. Magic links sound cool in theory, but in reality, people just want to click one button and get in.
I spent a little time adding Google OAuth, and within 48 hours, I finally started seeing real signups.
The rate at which people care about your product especially if it is new drops to zero the second they see a "Check your inbox" screen.
If you're building for general users, go with Google.
If you're building for developers, add GitHub.
If it's for gamers, use Discord.
Just don't make them type a password or wait for an email that's probably sitting in their spam folder.
Friction kills conversion. Fix your auth.
Disclaimer: I am the founder of lervos and this is not intended as an ad but respecting the rules here.
Hey everyone,
I currently have 6 micro-SaaS live, bringing in a bit over $20k in MRR.
The crazy part? I barely wrote a single line of code. I used AI to generate everything, from the database to the UI.
It wasn’t magic on day one. I spent hours stuck on broken code before I finally cracked the system:
Lately, I see too many non-tech people give up at the first AI bug. It sucks because the technical barrier is basically gone.
So, I’m starting a Skool community.
Full transparency: I will probably charge for the full course down the line. It makes sense given the exact workflows and copy-paste prompts I’ll be sharing.
But the main goal right now is to build together. Building alone is the fastest way to quit.
If you want to join and build your own AI SaaS with us: drop a comment or shoot me a DM, and I’ll send you the invite!
It's so crazy just a little while ago I was celebrating my first few hundred signups, and now I've hit the unreal number of 10,000 users with over 50,000 prompts generated on the platform! I can't thank everyone enough. So many people offered feedback, ideas, and support along the way. I really mean it.
Of course I'm not stopping here. I'm already working on the next big update that will benefit the whole community. More is coming soon.
I've built Prompt Builder, a platform where anyone working with AI can generate, test, optimize, and organize prompts for ChatGPT, Claude, Gemini and other models — all in one place. I grew it mostly by sharing what I was learning and posting here on Reddit. It didn't explode overnight, but I managed to get slow and steady growth.
For those of you who never heard about Prompt Builder, here's how it works:
The whole point is to stop wasting tokens on failed attempts and stop rewriting the same prompt for every model. Chrome extensions on a way!
Currently: 10,000+ users, 50,000+ prompts generated, and growing every day.
You can try it here (free tier available): Link
Follow me on X: https://x.com/nicklaunches
I'm glad for any feedback/suggestions/roasts in the comments.
If you’re building a dev tool, your best early users are already telling you who they are. They’ve starred a repo adjacent to yours. They care about the problem. They’re not a cold list, they’re a warm one , you just have to do a tiny bit of work to reach them.
The catch is that GitHub hides emails on profiles. But most developers leak theirs anyway, through commits in their own public repos. The author.email field is right there in every commit. That's the seam.
The idea is dumb-simple. Pick a repo whose stargazers are your target audience, pull the stargazer list from the GitHub API, walk each person’s recent repos, read the commit metadata, grab author.email, filter out the noreply@github.com ones, dedupe. No scraping, no sketchy tooling, just the public API and public commit data.
I wrote a bash script that does the whole thing. You need gh (authenticated via gh auth login) and jq. That's it. You run it, paste a repo, set a cap, and a few minutes later you've got a CSV with names, emails, logins, and which repo of theirs you got it from.
./scrape_stargazer_emails.sh
GitHub repo URL or owner/repo: vercel/next.js
Max stargazers to scan [200]: 100
Five minutes later there’s a CSV waiting for you with a hundred real emails of real developers who star projects in your space. The script and the walkthrough are here: https://npad.run/p/how-to-find-emails-of-github-repo-stargazers-hytfnmtgph.
Now the part that actually matters.
This works way better than a Show HN. A launch post gets you two hours of attention from people scrolling past fifty other launches that day. Half of them never even click. But a personal email, written like a human, that mentions something specific from their GitHub, that gets read. Sometimes it gets a reply. Occasionally it gets a user who sticks around and tells their friends.
A few things I’ve learned the slightly harder way. Don’t go wider than 200 stargazers, the returns get noisy fast, more bots, more dead accounts, more noreply emails that slipped through. Don't bulk-send the same template to everyone, because the moment you do that you've turned a warm list into spam, and the recipients can tell. Spend twenty seconds looking at each person's profile and mention their actual repo in the first line. It quadruples replies. Send from a real address with your real name on it, not hello@yourstartup.com. And space the sends out, four or five seconds between each, because Gmail flags bursts and you do not want to land in spam jail on day one.
If you’re shipping a dev tool, this is probably the highest-ROI hour you’ll spend on go-to-market this week. The script is free, the API is free, and the audience is pre-filtered for you. The only hard part is writing the actual email, and you should be writing those one at a time anyway.
Easy way: https://npad.run/p/how-to-find-emails-of-github-repo-stargazers-hytfnmtgph (put this to your claude code, u will get the full working script in one shot, thank me later)
I run a bootstrapped B2B SaaS company in India.
Like many early-stage companies, our internal processes were stitched together manually.
For invoicing, my cofounder would manually export data, generate invoices, send emails to each client one by one, and then compile a separate sheet for our CA for GST filing. This would take 8-10 hours every single month.
As we scaled, this manual system started to crack - errors crept in, clients said they didn't receive invoices, our CA kept asking for corrections, etc. It was a mess.
So instead of hiring ops people, I built an internal automation stack using Google Sheets + Apps Script + APIs.
Now with one click, it:
(I’ve attached a short demo video in the post showing how it works end-to-end.)
What used to take 8–10 hours now takes ~10 minutes, with near-zero errors.
We’ve used it internally for 3+ months and it’s been rock solid.
I built it for ourselves, but my accountant pointed out that many SMEs have painful manual workflows around billing / reconciliation / reporting / finance ops. He's already referring a few of his clients to me - which is why I'm posting this.
I'm taking on a few clients to help them set up such automation for their business. Initial setup takes about a week depending on complexity. You own it fully after that.
One-time fee. No subscriptions. 30 days of support included.
If your billing process still involves manual work, copy-pasting, or your CA chasing you for clean data — DM me or drop a comment. Happy to understand your workflow and tell you honestly if this can help.
(We're a bootstrapped SaaS ourselves — this isn't a product pitch, it's a founder who solved his own problem offering to solve yours.)
19 year old dev here, trying to build something people actually want instead of guessing in the dark
I'm not pitching anything. I genuinely just want to know what part of running your business makes u go "why is this still so manual in 2026"
could be something small and tedious, could be something that takes hours every week, could be something u've tried 5 tools for and none of them actually solved it
drop it in the comments. the more specific the better. like not just "invoicing" but "i have to manually copy line items from my email into my invoicing tool every single time and it takes 30 mins per client"
that kind of thing
I'll read every single reply and if enough people share the same pain I'm gonna build something for it and give early access to everyone who commented
what's the thing that's quietly killing ur time every week?