r/SaasDevelopers • u/BoroBokachoda • Feb 23 '26
r/SaasDevelopers • u/WildScreen6662 • Mar 21 '26
Useful Claude Code Cheatsheet I found
Came across this in another subreddit and figured it’s worth sharing here too.
Pretty handy if you’re working with Claude.
r/SaasDevelopers • u/luis_411 • Mar 13 '26
Guys my app just passed 1,300 users!
Hey guys, you might have seen my previous posts where I was celebrating previous milestones! Since then, I've implemented some huge updates because I currently have more time to work on the platform. You should really check it out again :)
I've built IndieAppCircle, a platform where small app developers can upload their apps and other people can give them feedback in exchange for credits. I grew it by posting about it here on Reddit. It didn't explode or something but I managed to get some slow but steady growth.
For those of you who never heard about IndieAppCircle, it works like this:
You can earn credits by testing indie apps (fun + you help other makers)
You can use credits to get your own app tested by real people
No fake accounts -> all testers are real users
Test more apps -> earn more credits -> your app will rank higher -> you get more visibility and more testers/users
Since many people suggested it to me in the comments, I have also created a community for IndieAppCircle: r/IndieAppCircle (you can ask questions or just post relevant stuff there).
Currently, there are 1302 users, 805 tests done and 228 apps uploaded!
You can check it out here (it's totally free): https://www.indieappcircle.com/
I'm glad for any feedback/suggestions/roasts in the comments.
r/SaasDevelopers
•
u/Unusual-Big-6467
•
Feb 15 '26
I made a free list of 80+ websites and directories to submit your saas
Edit:- Starups-atlas added
Edit:- now offering Submission from https://mywpbro.com
r/SaasDevelopers • u/Low-Construction1898 • Jul 29 '26
What do you guys think of my ui?
Trying to tackle a pain point I have of having to manage a million difference calendars and systems
r/SaasDevelopers
•
u/Leather_Silver3335
•
Mar 10 '26
I built a System Design Simulator – drag, simulate, and break your own architectures in minutes
Hey folks,
I’ve been hacking on a side project: a web-based “System Design Simulator.” It’s like a whiteboard, but you can actually press play and watch your architecture behave (or fail).
What you can do:
Drag-and-drop common pieces: load balancer, API gateway, caches, DBs, queues, even some AI bits.
Hit “Start Simulation” to see latency, error rate, throughput, cache hit rate in real time.
Flip chaos switches: traffic spikes, cache-miss storms, network partitions, component crashes.
Share & remix: every design gets a short link; anyone can fork it and improve.
Built-in hints: it tells you if you forgot an entry point or storage.
Why I made it:
Diagrams don’t fail; systems do. I wanted a fast way to feel trade-offs without spinning up infra.
For interviews and design reviews, it’s nice to ask “what if the cache dies?” and just click a button.
Try it here: "https://paperdraw.dev/"
Quick start: drop Load Balancer → App Server → Cache → DB, press play, then trigger a cache-miss storm.
Would love feedback:
What metrics or failure modes would you add?
Is the start/stop flow obvious enough?
Any presets you want (payments, chat, ingestion)?
Should I add “export GIF of the run” for sharing?
Thanks for taking a look—happy to fix bugs or add features if you ping me.
r/SaasDevelopers • u/Errorbuddy • Feb 12 '26
Launched my Saas yesterday. Woke up to 5 Paying Users 🥹
Ohhh this is a MOMENT 🥺 And I just stared at the screen for 5 minutes. Not because it's a lot of money.
But because someone, somewhere, took out their card... for something I built.
For weeks it was just:
late nights tweaking UI rewriting landing copy questioning if anyone even needs this
You keep building in silence. No applause. No traction. Just hope.
And then yesterday I hit launch.
Didn't expect much.
This morning: 5 payments.
No big influencer shoutout. No ads. Just people who genuinely wanted it.
For context - I'm building Retainer Al, a tool that helps creators understand why their content works (or flops) and gives strategy-backed suggestions instead of generic Al captions. You can even connect your instagram professional account for exact data-driven analysis (it's in testing).
It's still early. It's still imperfect. But it's real.
And today it feels real. $53 won't change my life. But it changed my belief. Someone believes this is useful. That's enough to keep building. If you're building something quietly: Keep going.
That first notification hits different. Now the real work begins.
r/SaasDevelopers • u/bryce2uj • Feb 12 '26
I launched my app 4 minutes ago and already got 10,000 users! Spoiler
This never happened, and I'm very tired of seeing these kinds of posts.
r/SaasDevelopers • u/Single_Complaint3829 • Aug 31 '26
I’m a 34-year-old developer who needs to figure out how to provide for my family. What would you do?
I’m 34, a software developer, and I recently lost my job.
I’m already looking for another job, and I’m not putting all my hopes on a side project. But I also need to find a way to generate income. I have a one-year-old baby, and I just found out that my wife is pregnant with our second.
So, honestly, I can’t afford to just “build in public” for two years and hope something works.
I’m a decent programmer. I know how to build software. I know how to use social media and content tools, but I’ve never actually used them to launch or grow a product.
Recently, I built a 100% local/private note-taking app. It runs locally, and I’m trying to figure out if it could become a real business.
But I don't want to come to Reddit and spam my product.
I know self-promotion is often banned or frowned upon in these communities, and honestly, I don't think that's what I need anyway.
What I’m looking for is advice from people who have actually built side projects, indie businesses, or products from scratch.
If you were in my position, what would you focus on?
Would you document the journey through YouTube/videos?
Write about it on Reddit/X/blogs?
Build an audience first or just focus on getting paying customers?
How would you try to get the first 10 customers without an existing audience?
Would you freelance/consult on the side while building?
Is “building in public” actually worth it, or is it mostly survivorship bias?
I’m completely new to this part of building.
I’m not looking for someone to tell me “just work harder.” I’m trying to understand what has actually worked for people who started with no audience, no community, and limited time.
I’m also considering documenting the whole process—not as a marketing campaign, but as an honest record of what happens when you’re trying to build something while simultaneously trying to provide for a family.
If you’ve been through something similar, what would you do if you had to start from zero today?
I’d genuinely appreciate any advice, even if it’s “don’t build the product and go get a job.”
r/SaasDevelopers
•
u/EfficientHomework350
•
Mar 03 '26
How I hit $20k last month just by asking for feedback (and why building for free was the secret sauce)
I see a lot of people struggling to get their first users or sales. Last month, I hit $20k in revenue, and I did it without a single "Sales" pitch. I did it by being annoying about asking for feedback.
I also built the core of this for free, which I realize is a massive advantage for gathering data. Here’s exactly what worked and what you should avoid if you’re trying to grow a MicroSaaS on Reddit or X.
-----------> Something that worked (The Dos)
Stop saying "Try my tool." It sounds like work. Instead, I asked: "I built this to solve [Problem X], but I’m worried the onboarding is confusing. Could someone tell me where I’m losing you?" People love being the expert, and they’ll click just to see if they can find a flaw.
Pivot fast! This is a superpower. When someone gave a valid critique, I fixed it and replied to their comment the next day: "Hey, I actually implemented your suggestion!" This turns a random critic into a "founder-level" supporter who feels a sense of ownership over your success.
Finding Pain Threads since I didn’t just post my own threads. I looked for people complaining about my competitors and commented: "I'm building a free alternative to fix exactly what you're hating, would you mind checking if I missed anything?" It’s a 100% conversion rate because you’re solving a fresh wound.
Leading with a free tool removed the "What's the catch?" barrier. It allowed me to build a massive user base quickly. Eventually, those users were the ones who started asking for paid premium features.
-------------> Something to avoid (The Don’ts)
Do not drop a link and disappear. If you don't reply to the first 5 comments within 20 minutes, the algorithm and the community will bury you. You have to be present.
Value all kind of feedback! If someone calls your UI ugly or your idea "useless," don't argue. Say: "That’s a fair point. How would you make it useful for your workflow?" This kills the toxicity and gives you free product research.
Avoid "Let me know what you think!" It’s too broad and lazy. Ask about a specific button, a specific price point, or a specific feature. Specific questions get specific (and useful) answers.
If you build it for free and focus 100% on the feedback loop, the revenue eventually starts chasing you instead of you chasing it.
Happy to answer any questions about the tactics and tools.
r/SaasDevelopers • u/No_Dragonfruit3391 • Jun 29 '26
Dear vibe coders: your “SaaS” is a demo with a database
Every week, same thing: “Built a SaaS in 3 days with Cursor 🚀”, pretty dashboard, 400 upvotes. Then you start charging for it and find out the entire hard part is still missing.
A few things that are absent from basically every one of these projects. Honest question: how are you handling this?
Auth. Someone increments the user ID in your API and sees other people’s data. Does your backend actually check that or are you hoping the AI wired up “something with auth”?
Secrets. Stripe key or DB credentials sitting in the frontend bundle or a public repo. You wouldn’t even know.
Migrations. Live DB, 200 real users, you need to change one field. Now what?
Compliance. Real users means real data laws where it’s stored, who you share it with, deleting it on request. For EU users that’s GDPR and it’s not optional. “I’ll deal with it later” is a fine with a date on it.
Cost. Every click fires a GPT-4 call, no rate limit. Someone writes a 10-line script and you wake up to a four-figure bill. Who’s paying that?
Backups. “I have backups.” Have you ever tested a restore? No? Then you don’t have a backup, you have a feeling.
When the AI can’t fix the bug. It loops, changes random lines, makes it worse. You can’t read the code because you never read it. Who debugs that? hope?
This isn’t gatekeeping. It’s the bare minimum between “prototype” and “something you can actually charge money for.” And it’s exactly the part no tool does for you, because it’s the part where you have to understand what you’re doing.
So, genuinely: how do you deal with this stuff? Or is the plan “I’ll fix it when it breaks”?
(And before someone says “works fine for me” yeah. Everything works fine at 5 users.)
r/SaasDevelopers • u/RunnerZee • Sep 16 '26
I vibe coded an AI startup to real clients. Then it crashed. Now my team wants to quit
A few months ago, I quit my job. I teamed up with two co-founders to build a startup.
My partners are incredible operators >>> elite at sales, content, and distribution. And I took on the tech side.
I am not a real software engineer. I'm a front end developer. But I was hoping I can figure things out. I built the entire backend (Supabase/Python/FastAPI) using AI prompts and vibe coding.
At first, we wasted months. I tried to build too many things at once. Overcomplicating and overbuildign is a stupid idea. Everything broke. So we stopped and made it dead simple. We built a simple AI voice for restaurants and bars.
It worked. People actually wanted it. We got real clients testing it live in their restaurants and bars.
Then last weekend, disaster hit (Saturday 8:36 pm). A big voice provider we use had a silent outage (THey aare still investigating the issue. We were ther first who reported that). The system went down for 94 mins. I only caught it by pure luck doing a late-night test calls. The provider did not even notice their own outage yet. We had to report it to them. I'm still waiting for the to fix it while building a fallback for us too. Their support is great so they've responded within 20 mins when I reported the outage.
We got lucky. It happened after hours, so no real business calls were lost.
But it exposed a huge problem. I had zero safety nets in place. I had no alerts to wake me up. Worse, I had no fallback. If the AI died, calls did not redirect to the front desk. The phone just rang into a black hole.
My co-founders were furious. And they are 100% right. Even thought I've been sitting in front of the computer for 10+ horus every day I built this like a hobby, not a real company. Now, they don't trust my technical skills. I guess they shouldn't after what happened. One founder is ready to walk away.
AI makes it very easy to build a working prototype. But a working demo is not real production software (many have mentioned this here). AI will not build backups, alerts, or fallbacks unless you already know how to ask for them.
I need some advice. We have real demand, but my code is fragile. We need an audit. Maybe we need a fractional CTO, a real CTO or a senior technical co-founder to take over.
>>If you are non-technical, how did you fix your messy MVP without losing your team?
>> What are the bare minimum failovers every phone app must have before taking another client?
>> How did you rebuild trust with your founders after hitting your technical limit?
Any advice helps. I want to learn and fix my mess.
r/SaasDevelopers • u/Free_Tennis7754 • 15d ago
Instead of killing my 20+ vibe-coded side projects, I built one HQ platform so AI can run the business side
I think, like many of us, I got plagued with vibe coding. I ended up building so many little tools that are mostly for personal use that I never actively advertise. Maybe I make a post or something about them, but I never go out and promote them or run ads.
After building dozens of apps, tools, Chrome extensions, services, and stores, I had to make a decision: either kill them all and focus on a few things, or delegate them to AI and let it take over most of the business. I chose the latter, and for the past few months I've been building a headquarters platform that aggregates all of my shit in one place.
In this post I wanted to share some ideas that I'm using:
First rule: everything stays "snippable"
Every app still keeps its own database, its own Stripe account, and its own separate email list.
Apps talk to HQ through tiny copy-in kits. If I remove the API key, the app falls back to local defaults and keeps working.
Why: if an app takes off later, I can snip it out and sell it as a standalone business. If an app dies, I unplug and kill it in 5 minutes without breaking anything else.

1. The shared foundation (boring stuff I stopped rebuilding 20 times)
One JSON spec per app defines its URLs, pricing plans, sender domain, health checks, backups, and cross-promos.
Copy-in kits for billing UI, lead pages, feedback widgets, feature flags/kill-switches, and a "more tools I built" footer ring.
Self-hosted analytics, error tracking, uptime checks, and encrypted backups that run weekly restore drills (spins up a throwaway container, restores the DB dump, verifies rows).
One-click deploy, restart, and rollback from HQ.

2. The collective ledger (how the money works)
Separate Stripe accounts + Gumroad + Google Play all flow into one central append-only Ledger.
Individual apps don't write Stripe webhook math anymore. Ledger verifies the payment and pushes a signed "grant pro" or "revoke" entitlement to the app.
Handles self-serve refund windows, dispute alerts, and an optional cross-app All-Access pass (fans out normal signed grants via email hash — still zero shared user DB).

3. Identity & how we talk to customers
No forced umbrella login wall. Users sign up inside each app normally.
One central email engine (SES primary + Resend fallback) handles receipts, onboarding, and promos across all domains, with bot-proof two-step double opt-in.
Lists stay separate per project, but the mail engine enforces a 1-marketing-email-per-day cap per person across everything so nobody gets spammed if they use 3 of my apps.
Every app's bug/support/feature-request widget lands in one unified HQ inbox.

4. Funnels & fixing the "I never promote anything" problem
Readiness grid: scores every product across 16 launch checks (health, legal pages, backups, pricing, lead magnet, emails, creative) so I see on one grid what's actually ready to push.
Rotating cart calendar: I can't market 20 things at once, so HQ rotates one active launch window at a time. When a window closes, checkout fails closed and the pricing page auto-flips to a waitlist.
8-step funnel + A/B tests: tracks
ad click -> squeeze page -> lead -> email open -> click -> cart -> activation -> paidwith built-in split testing.Event sequences: 8-step launch emails trigger off calendar events (cart open, 24h left, cart closed) and stop pitching the second someone buys.

5. How AI runs most of it (with a 1-click approve queue)
Rule is simple: AI does 95% of the prep, HQ gives me a 1-click Approve/Reject queue before anything public fires.
Launch packs & video: reads the app's real specs/pricing (so it doesn't hallucinate features) and drafts landing copy, ad hooks, social posts, OG cards, plus a 30s promo MP4 rendered headlessly.
Nightly funnel check: flags the worst funnel drop-off, checks A/B test significance, and recommends what to change next launch.
Inbox triage: tags bug severity, clusters duplicate feature requests across users, and drafts replies for 1-click send.
Updates & ops: turns deploy hooks into "what's new" feeds + monthly digest drafts, and runs weekly security probes on every live app.
Now whenever I vibe-code a new tool, it snaps into the same money, email, funnel, and ops spine in about an hour instead of rotting on GitHub.
Happy to share how any piece of this is wired if anyone else is dealing with too-many-projects syndrome.
r/SaasDevelopers • u/No-Career1273 • Oct 09 '26
1,400 active users this week, and I am building it solo
Checked my analytics this morning. Around 1,400 active users since Sunday.
A few months ago, I was working on a file sharing tool. Now people are actually using it.
I know this might be a small number for some founders. But when you handle the code, support emails and marketing yourself, it means a lot.
The idea is simple. Upload a file or a collection of files and share everything through one link.
Getting it built was one part. Getting people to try it has been much harder for me.
I have spent a lot of time posting on Reddit, answering comments, asking for feedback and improving things people found confusing.
Some conversations gave me useful ideas. Others showed me that something I thought was clear really wasn’t.
That has probably been the most useful part of sharing the journey publicly.
There’s still plenty to improve. These numbers don’t tell me everything, but seeing people use something I built gives me energy to keep going.
Sharing this small win with other people building on their own 🙂
What was the first milestone that made your project feel real to you?
r/SaasDevelopers • u/Substantial_Army_754 • Mar 24 '26
Time to promote YOUR SaaS 👇 (share what you’re building)
Thought it’d be cool to give everyone here a place to share what they’re working on.
Drop your SaaS / project below and include:
• What it does (short description)
• Link (if live)
• How long you’ve been working on it
• Why you started it
• Revenue (if any)
Always interesting to see what people are building and how it’s going.
I’ll check out as many as I can 👀
r/SaasDevelopers • u/luis_411 • May 28 '26
After 7 months of GRINDING... I finally hit 1k in earnings!
This is just so incredible... I honestly never thought this was possible for me. But I did the thing...
I JUST STARTED!
I put together a working MVP. Just the bare minimum functionality. Bought a domain and put it out there. I posted about it here on Reddit and got in contact with the people who commented and started using it.
I followed a simple concept that just came to me naturally:
put out what you have
post about it
listen to feedback in the comments
implement the feedback and adapt quickly
start the loop over again
And after some time your product becomes so good that it no longer sounds absurd to charge money for some features.
Anyways... I'm super grateful that this is working out so well and I really think I've built a community that is actually useful to many people.
About the product:
I've built IndieAppCircle, a platform where small app developers can upload their apps and other people can give them feedback in exchange for credits. I grew it by posting about it here on Reddit. It didn't explode or something but I managed to get some slow but steady growth.
For those of you who never heard about IndieAppCircle, it works like this:
You can earn credits by testing indie apps (fun + you help other makers)
You can use credits to get your own app tested by real people
No fake accounts -> all testers are real users
Test more apps -> earn more credits -> your app will rank higher -> you get more visibility and more testers/users
Since many people suggested it to me in the comments, I have also created a community for IndieAppCircle: r/IndieAppCircle (you can ask questions or just post relevant stuff there).
Currently, there are 2841 users, 2497 tests done and 629 apps uploaded!
You can check it out here (it's totally free): https://www.indieappcircle.com/
I'm glad for any feedback/suggestions/roasts in the comments.
r/SaasDevelopers • u/optigreat • Sep 20 '26
My Android app got the first paying user :)
I've been running a web app for a year now with relative success.
I published the Android app a bit more than one month ago, got ~80 installs, and yesterday the first paying user.
I was almost giving up the mobile platform, now my energy is renewed :)
r/SaasDevelopers • u/Internal_Meringue738 • Dec 17 '25
Do AI agents for IT actually work or are they just hype?
Been in IT for 10 years and I can't believe the amount of hype around "AI agents for IT." Seems like there's an insane amount of VC $ going into them... The biggest one I've heard of is Console. Does anyone actually use these tools or is it just VC hype?
r/SaasDevelopers • u/Royal-Artist4477 • Apr 22 '26
Anyone here figured out how to get their first SaaS users?
Hey everyone,
I’ve been building a small SaaS for a while now and I finally have something usable, but I’ve kind of hit a wall when it comes to getting actual people to try it.
I thought this part would be easier once the product was ready, but it’s been the opposite. I’ve shared it in a few places and tried reaching out to people directly, but the response has been pretty quiet so far.
At this point I’m not even thinking about scaling or anything like that, I just want a handful of real users who actually care enough to try it and tell me what’s wrong with it.
If you’ve been through this stage already, what actually worked for you? I feel like I might be overthinking it or maybe focusing on the wrong things.
Would really appreciate hearing how others approached this early phase.
r/SaasDevelopers • u/DustinJacksonEN • Jul 30 '26
How do you create real value when anyone can build the same app?
I've been thinking a lot about how easy it has become to build software. With AI tools and no-code platforms, almost anyone can ship an app in a few weeks. Every category already has dozens of similar products.
So I'm curious: what actually puts a product ahead of the competition for more than a few months these days? Is it still possible to create real product differentiation, or has distribution and marketing become the only lasting advantage?
Would love to hear your experiences. What has worked for you when the tech itself is no longer unique?
r/SaasDevelopers • u/AgencyVader • Aug 07 '26
The vibe‑coding hype feels weird when you’re the one who has to clean it up
Every time I open LinkedIn lately it’s some “I built a full SaaS in a weekend with AI” flex.
Everyone claps, drops fire emojis, calls it the future.
Meanwhile in the back of my head I’m just thinking:
“Cool, where did you put the real data? And who’s on the hook when it blows up?”
I run a tiny dev shop. We’ve been building boring SaaS for a long time.
The stuff that actually pays our rent is… dull. Auth, audit trails, weird edge cases, compliance checklists, backup plans.
None of it is vibe‑friendly.
So when I see “non‑technical founder shipped their MVP in 3 days with Cursor,” tbh I don’t feel inspired.
I feel tired in advance.
Because I know how this usually goes:
weekend build becomes “internal tool”
internal tool quietly becomes “how we really run this process now”
then six months later someone realises money / health / HR data has been flowing through a thing nobody understands
Nobody posts the “3 months of unsexy refactors so this thing doesn’t leak data” thread.
Now, I get the thrill of shipping fast. I use AI to write code, I’m not pretending I’m above it.
But the way people talk about vibe coding right now, it’s like security, maintenance, ownership just… don’t exist.
Feels a bit like watching people brag about drifting a rented car while you’re the mechanic who has to fix the engine on Monday.
Idk. Maybe I’m just the grumpy old dev in the corner.
But this whole “anyone can build a SaaS in a weekend” narrative feels incredibly disconnected from what it actually takes to own software once it’s in the wild.
r/SaasDevelopers • u/xerrs_ • Apr 03 '26
What are you building? Drop the website and I will give honest feedback.
Feedback is very rare nowadays, especially quality feedback. Feel free to post below your website, and 5 questions I should answer (eg. "What is good with the UI/UX", "What is confusing?", "Which features are missing?").
I will be taking a detailed look, and giving my honest, and brutal feedback on all of them.