r/SaaS

▲ 25 r/SaaS+2 crossposts

A launch video gets your product way more attention than screenshots. So I built a tool to easily make them yourself.

Static screenshots get scrolled past. A few seconds of motion makes people actually stop and look at your launch, your landing page, your ads.

Problem is that usually means hiring an agency for 10k or learning After Effects. Built Raylight so you can just do it yourself. Browser based, drop your product shots on a timeline, add cinematic effects, and export. The film above was made 100% in Raylight just animating shapes and images.

u/Horror_Turnover_7859 — 7 hours ago
▲ 3 r/SaaS

I think my AI startup is ready for its next chapter.

A few months ago I started building an AI startup because I believed there was room to make AI feel more useful and enjoyable.

I spent countless late nights building, fixing bugs, redesigning the product, and wondering if anyone would actually use it.

Then something unexpected happened. People started finding it, sharing it, and using it every day. In less than three weeks after launch, it grew to over 1,200+ users, which honestly exceeded my expectations.

Now I'm thinking a lot about what comes next. There are so many directions I could take it keep bootstrapping, grow a team, pursue partnerships, or something else entirely.

I'd love to hear from founders who've reached this stage. What was your next move, and what would you do differently?

reddit.com
u/Careful_Jackfruit_25 — 4 hours ago
▲ 209 r/SaaS+5 crossposts

After 3 Months of GRINDING... I hit 7k in revenue!

Still a bit stunned typing this. Three months ago I was refreshing Stripe hoping for one sale. Now there's a small but growing group of people paying every month to keep their apps from leaking.

CheckVibe is a security scanner for vibecoded apps shipped fast with AI tools. You paste a URL or hook up a GitHub repo and it surfaces what's leaking: secrets in the frontend, open database rules, missing headers. Two of us, fully bootstrapped, no funding. Three months in and we've done about $7k in gross volume, 200+ all time paying customers, 5k signups. Public Stripe link in case anyone's seen too many fake numbers: https://profile.stripe.com/checkvibedev/ZumatA0Y

A few things that actually worked:

TikTok slideshows have carried us. Aesthetic Pinterest-style backgrounds with tool names overlaid, five slides, no branding on the account. One hit a million views and is still quietly sending signups weeks later. 15 minutes to make. As a 2-person team that can't afford to spend hours on content every day, this format is unreasonably good.

Cold outreach worked, but only the version where I scanned the prospect's app first and DMed them what I found. Generic pitches got ignored. Useful findings got replies almost every time.

Paywall design was a 3x lever. The first version blurred all results, which felt clever and barely converted. Switched to one that just shows the count of critical issues with the actual findings locked. Conversion tripled. Curiosity beats obfuscation.

What nearly killed me was mobile activation tanking compared to desktop and not catching it for weeks. Onboarding had too many steps on small screens. Cut two and the gap basically closed overnight.

If you've shipped something with AI tools and haven't really checked what's exposed, checkvibe.dev runs in 30 seconds. Scan for free, only pay if you have issues. Almost every app I've scanned came back with something.

u/funfunfunzig — 10 hours ago
▲ 9 r/SaaS

Launching my first SaaS in 2 days. Any advice?

I’m launching my first SaaS in 2 days, and I’m both excited and nervous.
For those who’ve launched before, what’s the one thing I should definitely do and one mistake I should avoid?
Any tips or lessons learned would be greatly appreciated.

reddit.com
u/codewithashfaque — 7 hours ago
▲ 14 r/SaaS

One Reddit thread brought me 13 paying customers in a week

One thread I posted here last week got me 13 paying customers in about 5 days.

But this thread only got 3 upvotes. Top comments called me a snakeoil seller and said I made up my customers. 39k views, mostly "nice try buddy".

I just kept replying. Stayed calm, answered everyone, even asked the ones roasting me what they'd actually want to see.

And the whole time it was quietly outselling everything else I'd posted.

My guess is the people buying were the quiet ones watching how I dealt with the ones going at me.

One spike though, mostly dead after 48h.

Anyone else pulling real customers out of Reddit, or did I just get lucky once?

u/hlpb — 5 hours ago
▲ 4 r/SaaS+3 crossposts

First 3 sales on the macOS app I've been building solo 🎉

>

u/DutyOnly4308 — 2 hours ago
▲ 407 r/SaaS+9 crossposts

It's been a little over six months since I launched and it has been quite a journey. No exponential growth or huge user spikes but rather slow and steady growth. But in my opinion that is the best for building something actually valuable because you can react to user feedback along the way and constantly keep improving the app.

It's so crazy, just two weeks ago I was celebrating 2,000 users here and now I have hit another unreal milestone of 2,400! I can't thank everyone enough. I really mean it, so many people were offering their help along the way.

Of course I will not stop here and I am already working on the next big update for the platform which will benefit all the community. More is coming soon.

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 2402 users, 1969 tests done and 587 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.

u/luis_411 — 13 hours ago
▲ 37 r/SaaS

I am tired of seeing ai slop shitty self promotions

Wtf is going in this sub man ? Again everyone has started promoting their saas? Bruh I don't wanna see your vibecoded project . Mods pls do something 🙏

reddit.com
u/Pratiksinha007 — 9 hours ago
▲ 32 r/SaaS

Does a starter kit even matter anymore in the age of AI coding?

Hi r/Saas

Genuine question;

now that tools like Bolt, Lovable, Cursor, and Claude can literally spit out a functional app from a single prompt, are starter kits and boilerplates even relevant anymore?

Or are they completely obsolete?

Personally, I feel like they actually matter more now.

AI is insane at churning out code fast, but it doesn't intuitively know how you want your auth, payments, or database structured unless you feed it instructions every single time.

Without a solid base, the AI just throws slightly different, inconsistent design patterns at you every time you open a new prompt window.

I actually ended up building my own boilerplate (Indie Kit) for exactly this reason.

I just got so tired of re-explaining my architecture to Claude on every single project.

Once you give the AI a rigid foundation to work on top of, it stops guessing from scratch and its output gets 10x better.

What’s been your experience?

Have AI tools made boilerplates useless for you, or have they made them even more essential?

reddit.com
u/charanjit-singh — 7 hours ago
▲ 1 r/SaaS

Running a video editing / YouTube automation agency in Pakistan, now learning to code need honest input on scope, remote jobs, and realistic timelines

hay everyone. Quick background: I’m 19, based in Faisalabad, Pakistan. I run a video editing / YouTube automation agency have 2-3 international clients right now. It covers my bills, but it’s not scaling the way I want, and I don’t see it as a long-term ceiling I’m happy with.
So I’ve started learning to code. Right now I’m building an app (a habit tracker where users stake real money on their check-ins) using React Native/Expo, learning JavaScript fundamentals alongside it, and leaning on AI tools (Claude Code, Cursor) cuz its the meta ig. while I actually understand what’s happening under the hood not just copy-pasting.
A few things I’d love honest opinions on, no sugarcoating: 1. Scope and future of programming/dev work with AI tools getting this capable, is learning to code from scratch in 2026 still worth it for someone starting where I am? Or is the value shifting somewhere else (e.g., knowing how to direct AI tools well vs. deep manual coding skill)? 2. Remote jobs from Pakistan realistically, how hard is it to land a remote dev job (even junior/entry-level) living in Pakistan? Is there a meaningful disadvantage from location alone, separate from skill level? Given Ik good english and meet with clients regularly 3. The “vibe coding” wave I’ve seen a ton of people on Instagram shipping websites/apps built almost entirely with AI (“vibe coding”). I’m curious how real that path is as a business model vs. hype, and whether it’s a legit way to build something on the side while I keep learning fundamentals properly.
Marketing as the bottleneck I’ve read that most indie devs/founders (the number I’ve seen floated is something like 90%+ of small projects, not literally “400 developers”) don’t fail because the product is bad, they fail because they can’t market it. I’ve got 2 years of video editing experience and I already run an agency so content, hooks, and short-form marketing are things I can actually do. Does having that skill set make the “build small apps and sell them” path more realistic for someone like me? 5. Realistic timeline if my target is something modest to start say a $1,000–$1,500/month remote job (junior/entry-level, not senior Fahh money) what would you actually prioritize learning, and how long is that realistically going to take someone starting from near-zero coding but with real business/client-facing experience already?

Not looking for hype or “just grind brothaand you’ll make it” I want the blunt, real answer, including if you think this is a bad plan. I herd to tiktok cluely founder said any one can land a job just do 300 lee code questions and some mid level personal projects idk what lee code is.

reddit.com
u/Flikz6309 — 4 hours ago
▲ 2 r/SaaS+1 crossposts

I hated digging through PostHog data and I don’t trust AI to touch production. So we built a CRO agent that auto-reverts if the bounce rate spikes.

Hey everyone,

Like most SaaS founders here, we know we should constantly optimize our landing pages and onboarding funnels. But honestly? Digging through PostHog clickmaps, funnels, and bounce rates every single week is tedious and time consuming.

At the same time, we’re terrified of generic AI tools that blindly tweak copy or components and end up breaking production or hurting conversions.

So we built Velyr.

It’s an agent designed specifically for React/Next.js/Vite sites and Shopify stores.

Here is the exact workflow we built to keep total control:

  1. Velyr reads your frontend analytics (traffic, scroll depth, ...) via PostHog.

  2. It identifies the biggest conversion bottlenecks and actually writes the code fix.

  3. It opens a clean GitHub Pull Request (or drafts a Shopify theme change) and alerts you via Telegram.

  4. You simply reply YES/NO to the Telegram message to deploy it live.

Because we are paranoid about AI making things worse, Velyr monitors the site for 48 hours post-deployment.

If things get worse, it automatically rolls back the changes. No harm done.

We just launched and would love your brutal feedback.

Would you trust an AI agent with your SaaS funnel if it had a built-in safety net like this?

reddit.com
u/Difficult_Celery3458 — 4 hours ago
▲ 31 r/SaaS+1 crossposts

Built my first SaaS and got my first $3 in revenue

Link : https://easeassign.com/

I launched EaseAssign about a week ago after noticing that many students and freshers struggle to find small freelance work without competing against experienced freelancers.

The idea is simple:

People post small tasks.

Others complete them and earn money.

Today I got my first paid requests on the platform and saw users actually completing tasks.

Revenue is only around $3, but seeing strangers use something I built feels like a much bigger milestone.

Built it with GPT + Antigravity and finally bought a proper domain.

I'd love feedback from people who've built SaaS before.

u/Responsible_Way_9875 — 11 hours ago
▲ 3 r/SaaS

100 registered users in 1 month, 55 Uploaded Reels - Here are the things what I learned

A few weeks ago, I started building Lifto, a video-first product discovery platform where founders showcase their products through short demo reels instead of static screenshots.

Today we reached our first milestone:

  • 🎉 100 registered founders
  • 🎥 55 demo reels uploaded
  • ❤️ Hundreds of interactions across the platform

It might not sound like much compared to huge startups, but getting the first 100 users taught me a lot.

A few things that surprised me:

1. Building was easier than distribution.

I spent weeks coding the platform.

I've spent even more time trying to get people to actually use it.

2. People love giving feedback.

I've received everything from bug reports to design critiques.

Sometimes it stings, but almost every piece of feedback has made the product better.

3. Community is harder than software.

Getting someone to upload their own product is one challenge.

Getting them to also watch, like, and comment on other founders' demos is a completely different problem.

That's probably the biggest challenge I'm working on now.

4. Demo videos explain products far better than screenshots.

This was the original hypothesis behind Lifto, and it's been reinforced over and over.

People understand what a product does in 20–30 seconds of video much faster than by reading a long description.

I'm still very early in this journey, but I'm excited to keep improving the platform and learning along the way.

If you've built a marketplace or community product before, I'd love to hear:

What's the hardest part of getting users to contribute instead of just consume?

u/Rydbkhsh — 5 hours ago
▲ 136 r/SaaS

The 18 rules for building SaaS in 2026

  1. Provide Google login: The majority of people wouldn't create an account otherwise.
  2. Charge immediately: Stay away from free trials. Paid users = serious users.
  3. Launching is the start not the end: Post-launch is 4/5 marketing, 1/5 product.
  4. Promote shamelessly: Plug in your product everywhere, not just where it's "safe".
  5. Value the unsubscribers: They're giving you the most valuable input.
  6. Use your own product as much as you can: You'll find bugs your users haven't reported yet.
  7. Retention > acquisition: The most valuable revenue comes from existing users.
  8. Cut your MVP in half: Then cut it again. Ship the core, nothing else.
  9. Think bigger: $10k/month feels great until you realize $100k requires the same effort.
  10. Pay attention to market: If it's not converting after real attempts, the market is telling you something. Listen.
  11. Distribution before features: A product nobody discovers is a product nobody uses.
  12. People buy outcomes, not software: Sell the result, not the feature.
  13. Measure behavior, not compliments: Revenue and retention matter more than praise
  14. Make the first win happen fast: Users should experience value within minutes
  15. Don't build for everyone: The narrower your audience, the stronger your message.
  16. Your landing page has 5 seconds: Clean, fast, obvious value prop or they're gone.
  17. Talk to your users: Email your users. DM them. Get on calls.
  18. Price based on value, not competition.

Most SaaS founders fail because they give up too early

Stay in the game...

reddit.com
u/warrioraashuu — 14 hours ago
▲ 4 r/SaaS

€3,158 in 7 months from a habit tracker.

When you say "habit tracker" here, everyone lands on the same stuff. Saturated niche, vibe coded, slop, "not another one." The list is long. The main idea is always the same. Don't build another one.

Well, I built one anyway. It was something I wanted for myself. The idea was to replace Notion with something that looks better and has habits built in. It ended up mostly a habit tracker with a bunch of extra features.

From December to now (July) I made €3,158 total. It's a mix of MRR and lifetime deals, so not all of it is recurring.

Some context. Started building in November, launched the web app in December, got my first paying users that same month. Since then I've done marketing every single day. Almost all of it is Threads, posting there basically daily. I've had maybe a handful of days off in 7 months. This was never a quick money thing. It's slow and kind of boring work.

The app does way more than habits, even if that's how I sell it. It's Loggd. Habits, tasks, goals, a Pomodoro timer you can link to a task, a leaderboard, animated characters, a small community. More of an all-in-one, really. I just market the habit side because that's what gets people in the door. Most only find out what it does after they sign up.

It was dead slow at the start. Picked up recently once the iOS app went into prelaunch, and I just kept showing up. The thing that actually worked was building in public. Posting every number, every user, every euro. People trust that way more than a clean pitch.

So can you make money in a saturated niche? Yeah. Just not fast and not from some trick. Some friends of mine build habit trackers, too. One just hit €1,000 total. It's not a dying niche. It's just work. Show up, talk to people, repeat.

What's next is connecting my app to Claude and ChatGPT through MCP. I live inside Claude all day anyway, so I want to just ask it what's on my list today, throw in a few tasks, check off habits, sort my goals, and have the app update itself in the background. Building that now.

That's it. €3,158 in 7 months, one of the most crowded niches out there, a lot of showing up. Happy to answer anything.

u/Fuzzy_Act5528 — 8 hours ago
▲ 3 r/SaaS+2 crossposts

I cut my AI dictionary app’s first streamed result from 13.3s to 3.0s by making it stop overthinking the word “apple”

I’m building UrLingo, a personal dictionary/wordbook app for that very specific human ritual where you search “[word] meaning,” understand it for 14 seconds, and then your brain quietly throws it into the ocean.

The core flow is simple:

User searches a word → backend checks auth/quota/preferences → OpenAI generates a structured dictionary entry → frontend streams (will come to the streaming part in a bit) the response.

Simple. Beautiful. Innocent.

Except my app was taking 13 seconds before showing the first useful streamed output.

Initial numbers were rough:

OpenAI TTFT: 8296ms

First frontend OpenAI chunk: 13274ms

Hidden reasoning tokens: 1088

Yes. 1088 hidden reasoning tokens.

For a dictionary response.

Apparently the model needed to assemble the Seven Kingdoms before explaining what a word means.

After profiling and fixing the path, the latest batch looks like this:

OpenAI TTFT p50/p95: 1247ms / 3514ms

First frontend OpenAI chunk p50/p95: 3038ms / 4873ms

Hidden reasoning tokens: 0

Priority tier: true on all runs

So roughly:

OpenAI TTFT p50: 6.7x faster

First frontend chunk p50: 4.4x faster

First frontend chunk p95: 2.7x faster

Reasoning overhead: eliminated

What actually helped:

- Removed reasoning overhead for simple dictionary lookups. No need for Socrates to define “serendipity.”

- Verified `service_tier: priority` was actually being used, because apparently checking that the thing you paid for is turned on remains a valid engineering strategy.

- Added detailed timing logs on both server and client.

- Split metrics into same-clock measurements so I stopped chasing fake delays like a Victorian ghost hunter with a Datadog account.

- Improved the stream path so useful chunks reached the UI earlier, not just backend tokens flapping around in the void.

- Measured backend prep separately: auth, quota, preferences, OpenAI startup, all the tiny goblins hiding before the model call.

The biggest lesson: streaming alone does not make an AI app feel fast.

Users do not care that your backend received a token if the UI is still sitting there like Clippy after a head injury. The only thing that matters is when the first useful thing reaches the screen.

Also, check hidden reasoning tokens. Mine quietly ate the latency budget, stole my lunch, and left 1088 little footprints in the logs.

Still more to clean up, but getting UrLingo’s first streamed output from 13.3s to about 3.0s made the whole product feel different. It went from “is this broken?” to “oh, this thing is alive! (In Phoebe's high pitched voice)”

Small win, but a huge leap forward! Hope you all find this helpful too!

Website: https://urlingo.app/

App Store: https://apps.apple.com/us/app/urlingo/id6762142203

u/Cute-Ad-363 — 4 hours ago
▲ 4 r/SaaS

Lessons from a $50k ARR micro SaaS that I acquired for $97k

I've built a 6-figure portfolio of micro SaaS through acquisitions. I'm very transparent with my numbers and recently recorded a 30 min deep dive into the economics of my most successful acquisition.

The video covers a lot and there are many lessons that can be learnt, especially for developers building "nice to have" micro SaaS that they hope to sell one day.

Since the video is longer than Reddit's 15 min limit, I couldn't upload it directly.

View the deep dive here: https://www.saasdecoded.com/p/lessons-from-a-50k-arr-micro-saas

If you have any questions on anything I share in the video, please write them in a comment below, I'll be more than happy to help.

u/hawkeye77787 — 9 hours ago
▲ 3 r/SaaS

How do you optimise AI token spend?

Hey guys, I wanted to know how you optimise your AI token spend because recently I've been spending soo much!! on AI credits, and I think it's getting a little bit overboard. I wanted to understand how you guys are managing your own situations with the apps that you're building.

reddit.com
u/Big-Win-3895 — 8 hours ago
▲ 3 r/SaaS+1 crossposts

Does anyone have a good QA protocol for vibe-coded software to cut down on production bugs? 100% Codex-built mobile and desktop software with 80 features with an extreme amounts of production bugs

I built my software 100% vibe-coded, and now I need to tighten up QA.

I’ve already set up around 200 automated Playwright tests for the software. I created the test cases using screenshots from both the mobile app and desktop version. I’m also using Checkly now to test workflows like invoicing, since that’s one of the features inside the app.
I’m curious what other vibe coders, or people working with mostly AI-generated codebases, are doing to reduce bugs and errors. Right now I have a staging environment with a new version of the software that I’m also unit testing each feature on using Codex as that is my primary AI coding tool. I’ve used Claude code, but I really prefer Codex and I have some technical background. I completed a degree in computer science southern private school so I’m not clueless when it comes to the software development life cycle but for vibecoding specifically I’m curious what protocols people have used to cut down on production bugs. To me it seems like with AI you can build much faster, but the testing process needs to be much more thorough than it needed to be before. I catch them by looking at post hog, and sometimes the users tell me directly, but the ones who onboard itself self serve without me talking to them thought the software was broken. Partly because to do the invoicing feature you needed to connect your Stripe account or Square account and I was doing that part of the onboarding on the phone and I’ve now moved up doing this step in the onboarding process but steal, I think that just goes to show that I really need to cut down on bugs. I get regression with sign in as well so I’ll fix a bug with sign in and then two days later. People can’t login with Google again. It’s extremely aggravating.

Right now, I dogfood the product, do manual testing, and run automated Playwright tests every morning around 4 AM. Sometimes the tests give me useful insight, and sometimes I question their reliability, but overall I know I need much stronger QA to reduce production bugs.
The hard part is that the software is already pretty extensive. I have around 70–100 features, so there are a lot of edge cases. Even with dogfooding and manual testing, users still report bugs I didn’t catch.

Marketing is working pretty well through Meta ads, and people are ready to use the software. The problem is that a lot of trials don’t convert because users hit bugs. The UI is also confusing, but I’m not focused on fixing that yet. The bigger issue right now is literal software bugs breaking the experience.

reddit.com
u/RichTrust2321 — 9 hours ago