r/SaasDevelopers • • Feb 05 '26

Vibe coded my SaaS in 3 days, but it sat at 0 users for 2 weeks until I fixed distribution

15 Upvotes

Shipped my first vibe-coded SaaS in 72 hours. The flow state was real. Built the core features, designed a clean UI, got authentication working, deployed to production. Everything felt fast and effortless. Launched it and waited for users to show up. Two weeks later I had 3 signups total, all from friends I directly messaged. The vibe coding part worked perfectly but the distribution part was completely broken.

The problem wasn't the product or the build speed. The problem was my domain had zero authority so nobody could discover what I'd built organically. Google wasn't indexing my pages and my landing page wasn't ranking for anything except my exact brand name. Fixed this by adding distribution to my vibe coding workflow. Used directory submission tool to submit the site to 200+ SaaS and startup directories while I kept iterating on features in the flow state. The building speed stayed the same but now I had organic discovery working in parallel.

First two weeks after directory submission looked quiet. A few listings went live but no signup spike. Search Console showed the domain getting crawled more frequently though which meant Google was starting to pay attention to what I'd built. Week three through five is when it clicked. Domain authority went from zero to 18. Landing page started ranking for longtail keywords around the problem my SaaS solves. New feature pages I vibe coded showed up in search results within days instead of being invisible.

Now getting 25 signups weekly with 12% converting to paid users. The vibe coding speed combined with organic distribution means I can ship features fast in flow state and people actually discover them without me manually promoting everywhere. The workflow feels different now. Day one I vibe code the core functionality. Day two I set up SEO foundation to start building authority. Weeks three through eight I stay in flow building features while the organic channel compounds in the background.

The vibe coding SaaS lesson is that shipping speed only matters if people can find what you built. You can go from idea to deployed product in 3 days but if it takes 4 weeks to get discovered organically, you're leaving growth on the table.

If you're vibe coding SaaS projects but struggling with user acquisition, add distribution to your launch checklist. The flow state handles building fast but you need to handle discovery separately or your shipped products stay invisible.


r/SaasDevelopers • • Aug 10 '26

Can we stop insulting people who build "vibe-coded" SaaS?

0 Upvotes

Hey everyone,

I see a lot of judgment and insults in the community directed at founders who build their SaaS using AI tools or "vibe coding" stacks. I want to share a realistic perspective on this.

By trade, I am a backend software engineer. My core background is in heavy engineering like Java, Spring Boot, and DevOps including Docker, Kubernetes, and AWS. I know how to architect enterprise-grade systems from scratch.

But here is the reality: If I built my SaaS MVP using my standard heavy stack, it would be way too expensive.
Between hosting overhead, server costs, and spending months writing complex backend boilerplate, launching an early-stage SaaS that way just isn't smart. Using lightweight stacks combined with AI allows me to ship fast, keep costs low, and validate an idea in the market without burning money.

At the end of the day, we are all here to create products, learn, and grow. We should be helping each other out and sharing knowledge, not gatekeeping or throwing insults just because someone used a faster workflow to reach the same goal.

Let us focus on building and supporting each other.


r/SaasDevelopers • • Apr 25 '26

I went from getting 0 views to over 1K on my Reddit posts in just a week with no audience. Here's exactly what worked.

0 Upvotes

About a week ago, I had almost no Reddit karma, no viewers on my posts, and zero users.

Today I now have 35 karma, 88 contributions, posts hitting the top 5 in their subreddits, and 3 organic signups before I even officially announced. These stats may be small but it's the truth.

Here's exactly what I did and what actually moved the needle.

The format that worked

My best performing post was not "check out my app." It was this:

"Drop your SaaS and I'll give feedback, I'll go first."

That one post hit almost a thousand views and 15 comments on the first day, it's now sitting at almost 2K views with 50 comments. I had made another post asking users to drop their biggest pre-launch fears and that hit 2.5K views and cracked the top 5 in r/SaaSDevelopers.

The pattern: lead with genuine value, make it about the community first, then mention your product second. Every single time.

What I did differently from most founders

Most founders drop a link and disappear. I replied to every single comment within the hour. Not with "thanks!" but with genuine engagement, asking follow-up questions, giving real feedback on their products, as well as sharing specific things I learned from building Trakly.

That reply rate is rare and people notice. Several founders DMed me specifically because of how I engaged in the thread.

The feedback that changed everything

One commenter looked at my landing page and said: "You're jumping straight to step 6 of the conversion funnel. The visitor hasn't answered 'what is this?' or 'is it for me?' yet."

I shipped a full demo mode the same day. allowing visitors the opportunity to explore Trakly with pre-populated sample data before creating an account.

That single piece of feedback probably doubled my conversion rate, and I honestly would have never figured that out by myself.

Another commenter said: "Your first screen asks me to do work before showing me anything works. Three zeros across the top, three Pro locks visible, a form to fill out."

Same day I rebuilt the entire landing page around a single CTA, "Try the demo, no account needed." One action per phase of the funnel. Nothing competing for attention.

What subreddits actually worked

r/SideProject — best for "show me what you're building" posts. Builders helping builders energy

r/SaaSDevelopers — great for technical and business model discussions

r/NoCodeProject — slower with less members but higher quality engagement from my experience

What didn't work: places like r/personalfinance for self-promotion. Strict rules, will more than likely get removed. Better to just answer questions genuinely there and let people find your profile.

The karma wall is real but falls faster than you think

this subreddit requires comment karma to post. I hit the threshold finally today by just genuinely commenting on other people's posts. Not by spamming, or self-promoting, just by being a real person amultiple communities.

The trick is replying to posts within the first hour they go live. Early comments on active threads accumulate upvotes over days as more people find the post.

None of that happens if I just drop a link and leave.

The actual numbers

Day 1: First post, 286 views, 0 comments, 0 karma

Day 2: Second post, 382 views, 3 upvotes, 4 comments

Day 3: Third post, 1.9K views, 11 upvotes, 50 comments

Day 4: Fourth post, 2.5K views, 6 upvotes, 18 comments

All time total: 35 karma, 88 contributions, active in 18 subreddits, 3 organic signups

What I'd do differently

Start engaging on Reddit before you even have a product. The karma and community relationships you build are an asset that takes time to compound. I started too late and hit karma walls that slowed me down.

I had to comment on other subreddits for days before meeting the karma threshold for this subreddit. So my best advice I can give would be to either already have karma on your account or be like me and start from the bottom up and show up everyday with posts or genuine comments on other peoples posts.

The one thing that made everything else work

Shipping features based on feedback same day. When the demo mode suggestion came in I built it. When the landing page critique came in I rebuilt it. When someone pointed out the conversion funnel was broken I fixed it.

That reputation, "this founder actually listens and ships fast", spreads in these communities pretty quickly. People remember and will keep note of that.

My question to you:

What was your Reddit strategy at this stage? Curious to hear what's working for others.


r/SaasDevelopers • • Dec 13 '25

I have 3 dead SaaS projects. Here's what each one taught me.

4 Upvotes

Not a flex. Just reality. Most side projects die. Here's my graveyard and the lessons:

1. Lesson: Building a to-do app in a world with Notion is suicide.

2. Lesson: Fitness apps have insane churn. People quit in 2 weeks.

3. Lesson: B2B sales cycles are brutal for solo founders with no network.

4. Lesson: Viral ≠ Monetizable. 50K users, zero willingness to pay.

5. Lesson: Developer tools can work, but you need a massive audience.

6. Lesson: Competing with Buffer/Hootsuite is a losing game.

7. Lesson: Don't build for bubbles.

What I do differently now: Before I write a single line of code, I run my idea through a "stress test". I look for:

  • Existing competitors (and why I'm different)

  • Red flags in the business model

  • Whether I'd pay for it myself

I built a tool (Torrn) that automates this because I got tired of doing it manually for every new idea.

Your turn: What's in YOUR project graveyard? What did it teach you?


r/SaasDevelopers • • Dec 13 '25

I can't code. So I yelled at AI for 12 hours and now I have a Chrome Extension in review. Here's exactly how.

5 Upvotes

So I work in Sales. Not a dev. Never been one.

Yesterday morning I was annoyed. You know when someone drops a naked URL in Slack and it just... sits there? No context, no preview, nothing. Nobody clicks it. It's basically digital homework nobody asked for.

I wanted something that fixes this. Grabs context, formats it nicely, boom – done.

24 hours later, my Chrome Extension "LumaClip" is in review. I didn't write a single line of code manually.

Here's the actual breakdown – including where I wasted 3 hours on a dumb idea.

The Bad Idea

I originally wanted to build some kind of game overlay to bridge loading times in AI tools. Like a little minigame while you wait for GPT to think.

Spent way too long on this before realizing: that's not productivity, that's procrastination with extra steps.

Scrapped it. Back to the Slack thing.

The Stack (aka "I just talked at my laptop")

  • IDE: Antigravity (Google's agent-first IDE) + Gemini 3 Pro + Wispr Flow

  • Landing Page: Gemini 3 Pro – told it I wanted "Obsidian Glass aesthetic" and it just... did it.

  • Waitlist: Tally.so   → Notion pipeline.

  • Input method: 90% voice dictation. I was literally pacing around my apartment explaining features out loud like a crazy person.

I acted as the PM. The AI acted as the Senior Dev who somehow tolerates my vague requirements.

The part where I almost gave up

Standard Chrome popup UI is ugly. Like, genuinely depressing.

I kept prompting "make it look modern" and getting garbage. Finally, I said "copy the Apple Vision Pro aesthetic" and suddenly we had frosted glass, subtle animations, the whole thing.

Sometimes the prompt isn't "do this better" – it's "steal from someone who already figured it out."

How it actually works

  1. User hits Alt+C

  2. Extension grabs tab title, URL, and page content

  3. Sends it to Gemini with a "helpful colleague" persona prompt

  4. Returns formatted text: headline, TL;DR, bullet points, source link

  5. Click "Copy for Slack" → paste → actually looks good

There's a little visual flash when you capture (we call it "shutter effect") which felt unnecessary but honestly makes it 10x more satisfying to use.

Where I'm at now

  • Extension submitted to Chrome Web Store (Pending Review).

  • License keys via Gumroad API integrated.

  • Settings stored locally.

  • Landing page is live (hosted on Cloud Run for now).

Honest takeaway

This didn't feel like coding. It felt like being a very impatient creative director who keeps saying "no, not like that" until the AI figures it out. The skill wasn't syntax. It was knowing what to ask for and recognizing when the output was wrong.

Happy to answer questions about the prompt engineering or the Antigravity workflow.


r/SaasDevelopers • • Feb 13 '26

Building SaaS in the era of weekly AI launches

0 Upvotes

I’ll be honest.

Every time something like OpenClaw drops, I feel a small punch in the gut.

New features.
Slick landing page.
People tweeting “this changes everything.”

And I’m here… still building my SaaS. Fixing edge cases. Pushing small updates nobody sees.

For a few hours, it genuinely feels like I’m late.
Like the train already left and I’m still tying my shoes.

But then something shifts.

The same tools that make me feel behind
are the ones helping me ship faster than I ever could 2 years ago.

Better APIs.
Better infra.
Better AI wrappers.

The barrier isn’t building anymore. It’s clarity.

So yeah — some days I feel behind.
Other days I realize the playing field just got leveled.

Both feelings are real.

And I’m still shipping. Hoping for a great 2026 in terms of doing good at running SaaS.


r/SaasDevelopers • • Jul 13 '26

Frustrated with developer

0 Upvotes

I repeatedly asked my developer for access to the business onwer and employee log in. After 6 weeks he gave it to me... and y'all IT IS A MESS!!! I was supposed to present this THIS COMING THURSDAY at 8AM to a room full of almost 2,500 professianly and it is NOWHERE near complete.

I am on the verge of sending him a 7 page google doc. Should I send it if it's that long or not? Should I post what i'm about to send him in here or will any of you actually read it all. I am beyond done at this point. I've been working 80 hour weeks for the past two months. I haven't seen my own child in 2 months and he lives with me full time.


r/SaasDevelopers • • Feb 25 '26

SaaS Is Dead. I Buried It in 15 Days. Here's the Proof.

0 Upvotes

Last month I looked at the invoice from Intercom and something inside me said "enough."

$132/seat/month. Plus $0.99 for every AI response. We have tens of thousands of students. You do the math.

Pipedrive was no better. Starts as "affordable," climbs to $79/user/month once you add the extras. Combined annual bill for both: somewhere between $60K and $100K.

But the real pain wasn't the money.

The real pain was this: none of these tools knew our students. They didn't know our most common problems, our education consultants' procedures, which student drops off after which lesson. They couldn't measure teacher-student compatibility. They couldn't use the behavioral data flowing from our Insider CDP.

We were paying nearly $100K a year. In return, we got generic tools that didn't know us, built the same way for every company, speaking nobody's language in particular.

It's like living in a rental apartment. Same floor plan, same furniture, same wall color. Want to customize? Upgrade to the Enterprise plan. Hire a consultant. Sign an annual contract.

One night I sat down and thought: "What if I built my own house?"

And I built it. In 15 days.

What Can You Possibly Build in 15 Days?

Now you're probably thinking exactly that. I would have thought the same thing before I started. Honestly, if someone had told me six months ago that we were building our own CRM, I would have smirked and told them to focus on their core business.

But building software in 2026 is nothing like 2020. Andrej Karpathy called it "vibe coding," you might remember. His February 2025 tweet got 4.5 million views. A year later, he updated the term himself: he now calls it "agentic engineering." You give tasks to AI agents, they write the code, you supervise.

That's exactly what I did.

What I built is not a prototype. It's a production system currently serving thousands of students and teachers:

Omnichannel inbox - WhatsApp, Instagram DM, Gmail, webchat, phone... all on a single screen. Our support reps no longer toggle between 5 different tabs.

AI agent system - A 9-step orchestration. It detects customer segments, classifies intent across 17 categories, scores leads using 20+ signals, assesses churn risk across 9 dimensions. Three different Claude models work together: one classifies, one generates content, one makes complex decisions. On top of that, the system takes initiative on its own and uses our MCP tools. It's not just an AI that "responds" - it's an AI that "solves problems."

Autonomous churn prevention - When a student quietly starts drifting away, the system notices. It sends personalized WhatsApp messages. Hour 0, hour 24, hour 48, hour 72. No human intervention.

Self-improving pattern learning - At 2:00 AM every night, a pattern learning process runs. It analyzes the last 7 days of results. It learns what worked. It forgets what didn't.

Over 100 automations. 15 trigger events times 20 action types (and we'll keep expanding).

This is not Intercom. This is not Pipedrive. This is something neither of them could do together. Because this system knows our DNA.

This Is Bigger Than One CTO's Story

So is this just a "look what I built" post?

No. This is part of something much bigger.

In the first week of February 2026, an earthquake hit Wall Street. $285 billion evaporated in 48 hours. Salesforce shares dropped 38% since the start of the year. The media called it the "SaaSpocalypse." In February alone, an estimated $1 trillion in market value was wiped from the software sector.

Where did this panic come from?

From companies starting to realize something. That they can build their own software now.

Klarna eliminated 1,200 SaaS tools. Replaced Salesforce and Workday. Their AI chatbot took over two-thirds of customer service. $40M in annual savings. Revenue per employee jumped from $400K to $700K.

Blinkist replaced $60K/year in SaaS spending with apps built using Lovable and Replit. And the people who built them weren't engineers. Over 20 non-technical employees built their own internal tools.

According to Retool's 2026 report, 35% of builders have already replaced at least one SaaS tool with a custom build. 78% plan to do more this year.

And now Flalingo is part of this story.

This isn't a trend. It's a wave. And the wave hasn't even hit the shore yet.

An Economist Described This 80 Years Ago

Joseph Schumpeter introduced "creative destruction" in 1942. That unstoppable process that continuously transforms the economic structure from within, tearing down the old and creating the new.

SaaS itself was a product of this process. In the 2000s, it destroyed on-premise software. Server rooms shut down, CDs went in the trash, everyone moved to the cloud. SaaS companies were the disruptors of that era.

But disruptors get disrupted too.

Clayton Christensen called it the "Innovator's Dilemma." Large companies become so dependent on their existing customers' demands that they can't see the change coming from below. Salesforce can't abandon per-seat pricing because their entire revenue structure depends on it. Intercom keeps charging $0.99 per AI response because their margins require it.

Both know they need to change. Neither can.

Satya Nadella said it plainly in December 2024. "Business applications are essentially CRUD databases with business logic. In the agent era, this logic will migrate to AI agents."

When Microsoft's CEO says this, it's worth listening. :)

Sam Altman added in July 2025: they've been cutting inference costs by 10x every year for the past five years. He predicted that by the end of 2026, software that used to take a team a year to develop could be produced for just $100-$1,000 in inference costs.

I proved that prediction right this month. In 15 days.

The Jevons Paradox, 1865

William Stanley Jevons discovered that making steam engines more efficient wouldn't reduce coal consumption. The opposite happened: as efficiency increased, the range of applications expanded, and total consumption grew.

The same thing is happening with software. When AI makes software development 10x cheaper, we won't produce the same amount of software. We'll produce 100x more. Software custom-built for every company, every problem, even single-use software.

Kevin Roose of the New York Times called it "software for one." Software written for a single person.

This is SaaS's worst nightmare. Because the competitor is no longer another SaaS company. The competitor is the customer themselves.

The Numbers Don't Lie

Cursor AI became the fastest company in history to go from $1M to $500M in revenue. $1B+ annual revenue. $29.3 billion valuation. OpenAI, Shopify, and Nvidia use it.

Lovable reached $200M annual revenue in 8 months. 8 million users. 100,000 new apps generated every day. $6.6 billion valuation with just 45 employees.

Bolt went from zero to $40M annual revenue in 5 months. The second fastest-growing product in history after ChatGPT.

In Y Combinator's latest batch, a quarter of applications had codebases that were 95% AI-generated.

GitHub Copilot has 20 million users, and nearly half the code its users write is generated by AI.

Jensen Huang said it back in 2023: "Everyone is a programmer now. You just have to say something to the computer."

That day it sounded like an early prophecy. Today it's reality.

The Honest Part

This isn't easy. Not everyone can do it. At least not yet.

A METR study found something interesting: experienced open-source developers were actually 19% slower with AI tools. But they thought they were 20% faster. A serious gap between perception and reality.

According to Veracode, 45% of AI-generated code contains security vulnerabilities. The maintenance burden is real. The "last 20%" problem is real.

Someone on Hacker News rightly wrote: "Once you finish building that SaaS replacement, you're also signing up to operate, maintain, and secure it for as long as you run it."

True. But that objection applies to amateurs.

A CTO building contextual bandit pattern learning and multi-model AI orchestration isn't doing "vibe coding." They're doing what Andrej Karpathy defined in February 2026: "agentic engineering." No vibes. Engineering discipline.

And the real question is this: are the risks of a system I built myself greater? Or is the greater risk paying $100K+ per year for a generic tool that doesn't know its students by name?

I Backed My Thesis With My Wallet

This isn't just an engineering story. I made the same move in my own investment portfolio. I exited SaaS stocks. Moved from the application layer to the infrastructure layer. Companies like DigitalOcean and Cloudflare.

The logic is simple: if every company is going to build its own software, demand for the infrastructure that software runs on will multiply. In the 1849 California Gold Rush, the biggest winners weren't the people digging for gold - they were the ones selling shovels and tents.

Same story, different century.

This is not investment advice. But it is an indicator of how deeply someone believes in their own thesis.

SbY: Software by You

I'm proposing a term: SbY. Software by You.

SaaS sold you a rental apartment. SbY is building your own house. AI is the power tools placed in your hands.

Foundation Capital calls this "Service as Software" and frames it as a $4.6 trillion opportunity. Bessemer says "Vertical AI is the new SaaS." DHH is bringing back the "pay once, own forever" model with his ONCE brand.

I'll put it more simply: software will now be built by the person who knows their business best, for their own needs, with AI's help.

And that person will most likely be you.

Where Are We on the Map?

Economist Carlota Perez has an elegant model. Every technological revolution passes through five stages: irruption, frenzy, turning point, deployment, maturity.

SaaS was the deployment phase of the internet revolution. It had matured. Growth was slowing. Prices were rising.

With AI, we've entered a new frenzy. Cursor is valued at $29 billion, Lovable at $6.6 billion. Speculative capital is flooding in. SaaS stocks are collapsing while AI stocks climb.

This frenzy will calm down someday. And in the deployment phase that follows, what's dismissed today as "vibe coding" will become standard business practice.

Just like the people who said "you're going to put data in the cloud? Are you crazy?" in 2005 now run everything on AWS.

The Wind Doesn't Ask Permission

I built a CRM and customer support platform in 15 days.

But the important thing isn't 15 days.

The important thing is that the paradigm shift that made this possible isn't going back.

Every year inference costs drop by 10x. Every year AI tools become more capable. Every year the "buy or build" equation shifts a little more toward "build."

The average company spends nearly $5,000 per employee per year on SaaS. It wastes $21 million annually on unused licenses. Some of that money can now go toward AI tool subscriptions and a few weeks of development time.

The SaaS era taught us a lot. But like every era, it's ending too.

And Schumpeter's wind of creative destruction doesn't ask permission. You know, that "unstoppable process that continuously transforms the economic structure from within, tearing down the old and creating the new."


r/SaasDevelopers • • Jul 01 '26

If you're a software engineer, please help me.

6 Upvotes

Right now, I have about 8 months, God willing, to learn how to build a SaaS, specifically a mobile application.

My programming knowledge is literally zero. I asked AI what I should learn, and it suggested that I start with React Native using TypeScript. But when I watch programmers on YouTube, they keep saying that I need to build a solid foundation first and that I shouldn't start directly with JavaScript or TypeScript.

So what should I do? Should I spend, for example, 4 months building my fundamentals with a language like C, or should I jump straight into JavaScript? Or should I just learn Flutter instead? What's the best approach?

For context, my goal is to build the MVP with AI acting as a coding assistant. I don't want AI to write everything while I blindly copy and paste the code. I want to actually understand what it's doing so I can build things properly.

And, God willing, when I'm successful and the product grows, I want to be able to scale it instead of rebuilding the entire application from scratch.

So what's your opinion? What do you think I should learn?

One more thing that's making this decision harder is that I also want to become a software engineer as a career in the future. So I'm trying to balance two goals: building my SaaS within these 8 months, and also learning in a way that sets me up for a long-term career. After those 8 months, I probably won't have much time to keep learning from scratch.


r/SaasDevelopers • • Sep 27 '26

Looking for a technical cofounder to build a SaaS together

2 Upvotes

I'm a programmer in my late twenties from the Netherlands, working mostly with TypeScript/JavaScript and Rust. I'm looking for someone with a similar background and, ideally, someone who's been programming professionally/seriously for a few years.

I'm not looking to build a huge startup. The idea is to build a small SaaS product, with a target of going from idea → working product in weeks rather than months. The idea mostly involves some form of data collection/scraping, and the approach is pretty straightforward:

Find potential customers first → validate that they actually want it → build the smallest thing that solves the problem.

So rather than spending 6 months building something and then trying to find users, I'd rather find someone who needs it and build around that.

I'm looking for someone who:

  • Is in their twenties or older

  • Is an experienced programmer

  • Can commit a couple of hours on a couple of days per week

  • Likes moving quickly and shipping

I'm deliberately not sharing the idea publicly, but I'm happy to share more details on a call.

I used AI to polish my message.


r/SaasDevelopers • • Jan 04 '26

Bottom line, no fluff.

1 Upvotes

Everyone “building with AI” is either 1. duct-taping APIs and calling it a revolution, or 2. one Medium post away from pivoting to a newsletter.

AI didn’t make you a founder. It gave you a loud keyboard and confidence you didn’t earn.

95% of “AI startups” are just ChatGPT in a trench coat charging $29/month and praying no one clicks “view source.”

The real flex isn’t using AI. It’s shipping something that still works when the model rate-limits, hallucinations hit, and Twitter finds your landing page.

AI is the new crypto: Everyone’s early, nobody’s profitable, and somehow everyone’s a thought leader.

Edit: This is what ChatGPT said when I asked “What do you think about all this ai slop coming out each day. Tell me no fluff.” lol.


r/SaasDevelopers • • May 25 '26

AI won't kill Devs, I can see why (Rant)

1 Upvotes

It is clear that vibecoding will make websites and apps more expensive. That increases the market value of a person who knows how to code.

Every single fkin founder is an AI expert, lecturing everyone on everything. I created this app to satisfy my partner in 30s or less. Yeah bro half of your code is written in Php and the other half in expressjs.

But all these plays that we are seeing on the internet are short-term plays, and you can understand that by looking at it. The code these guys are generating is not maintainable, for most businesses, dumping an existing solution and cloning the same one from scratch is NOT viable, because the opportunity cost will be extremely high.

Even for Mncs who Automated 99.9% of their workflow and fired their entire workforce ran into a problem. Problem named, slop maxxing. So to solve this problem, they invented human employees, again.

You might argue with me that it's great for POCs yeah but you need a problem for that. And on that note I have a great idea, write a rate limiting piece of code that won't let you post on Facebook and LinkedIn more than 3 times a week. And pitch this to the United Nations. The pitch being this will help in ozone layer regeneration, reduce global warming, and increase the oxygen content of the Earth.


r/SaasDevelopers • • Feb 17 '26

I stopped “building features” and did this instead. Went from 0 → 37 paying users in 21 days.

2 Upvotes

Everyone says “ship fast.” I did that for weeks. Got nothing.

So I switched to a boring plan that actually works when you have zero audience.

What I did (with numbers)

1) Picked a painfully specific ICP
Not “founders” or “creators.” One job title, one workflow.

2) Built a lead list of 312 people
Mostly LinkedIn + company sites → dumped into a Google Sheet.

3) Sent 180 cold emails (3 lines, no fluff)
Results:

  • 180 sent

  • 41 replies

  • 19 calls

  • 11 trials

4) Did 1:1 onboarding for every trial
Loom setup + follow-ups + “tell me what sucks” calls.

Results after 21 days

  • 37 paying users

  • $1,480 MRR

  • $0 ads

What mattered

The product wasn’t “viral.”
Distribution was.

Also, batching content + landing pages helped a lot — I used tools like Runable / Canva to ship decent visuals fast instead of wasting hours tweaking design.

Biggest lesson: if you can’t find 100 real people to message this week, it’s probably not a SaaS problem… it’s a targeting problem.

What worked for your first 10–50 paying users?


r/SaasDevelopers • • Sep 27 '26

[No f*cking AI post] - wanna get into sass hustle, 4th attempt

0 Upvotes

Like every developer I've tried launching a few projects without any market testing before I started building them. I love programming and I thought building a good product with clean well-maintained code was enough. But reality showed me that nobody cares about your code or your project if nobody knows it exists.

After three big failures I didn't give up. I analyzed my past mistakes instead.

Marketing is the new skill I want to invest in because I still have tons of ideas for things I want to build for people.

So I'm looking for people who are also interested in this. It would be great to work together, learn this skill, analyze product-market fit and so on


r/SaasDevelopers • • 20d ago

SaaS ideas for a beginner

0 Upvotes

Hi guys,

I am a software engineer with knowledge and experience in Fullstack AI development

I am new to the world of SaaS and I have no clue where to start. Even if I knew where to start, I am not sure if it's worth doing that.

I am in search of new SaaS ideas. I'm not here to build a startup at least for now. However, learning to make SaaS products - maybe which could fetch passive income.

Can you help me with finding worthy ideas? Or anyone can let me know if you are looking for anything specific to your business or smth. I am ready to explore a multitude of options.

This is an attempt to learn more and contribute to the real world problem solving.

Thanks.


r/SaasDevelopers • • Aug 11 '26

Has anyone vibe coded a profitable SaaS or even a mobile app?

0 Upvotes

Vibe coding seems to have become a huge trend. The thing is when I see someone who has a profitable app, they seem to always have a technical background. Is there anyone on this subreddit that can't code but they used AI tools to make a profitable app?


r/SaasDevelopers • • May 20 '26

Bro SaaS is sooo dead in 2026

4 Upvotes

bro SaaS is straight up dead, was chatting with my homie yesterday and we were saying how crazy easy it is now to build a SaaS. Just spam a few prompts and you got an app. But everybody doing the exact same sh!t makes it mad hard to stand out.

Real question is that, is SaaS actually cooked or are people just building stupid stuff with no demand?

Me personally, building something just cuz you can prompt it with zero market research is dumb af.

What y’all think? SaaS still has hope in 2026 or nah?


r/SaasDevelopers • • Mar 26 '26

Unpopular opinion: most SaaS fail because of this

0 Upvotes

Curious what you think:

What’s one unpopular opinion about SaaS that you believe is true?


r/SaasDevelopers • • Sep 12 '26

Saas build opportunity

4 Upvotes

Yo guys, I'm lookin for a SAAS builder, I owned different saas and I'm able to make profits with them, I need a guy who want to build the site, I will do all the traffic system and he will earn a part of each sell on the saas website

If you guys are interested, message me


r/SaasDevelopers • • 10d ago

Drop your homepage and I’ll tell you what I’d change first

0 Upvotes

I’m a designer and I’ve got some free time this weekend. Drop your homepage and I’ll go through it.

I’ll mostly look at:

  • Whether it’s clear what you do within a few seconds

  • Whether it feels trustworthy

  • Whether it looks like you or like every other startup

I’ll reply to as many as I can.


r/SaasDevelopers • • Oct 16 '26

Do you really need a technical cofounder?

0 Upvotes

Your technical cofounder might be the most expensive hire you never needed. I know this is probably an unpopular take in startup circles, but not every non-technical founder needs to give away 30–50% of their company just to get a product built. Sometimes you need a technical cofounder, sometimes you need one solid engineer for two months, and sometimes you just need a small team to get the MVP out, test whether anyone actually wants it, and figure out what comes next. I think founders often confuse needing someone to build their product with needing someone to own half the company. Genuinely curious, how many founders here gave up equity because they needed a cofounder, and how many did it because they just needed someone to build the damn thing?


r/SaasDevelopers • • Sep 10 '26

I’ll try your app and write honest review

0 Upvotes

Hey guys

Just to build some product tastes and get some posting materials for my X account.

I’ll try your app, spend some time testing it (maybe a couple of hours), and write honest reviews.

I have an iPhone, an Android phone, and a Mac.

Just DM me.

Plus, I ship MewGuard. It’s an app that has plant toxicity info for cats. You can log your cat’s info on it too. It’s on AppStore.

Would appreciate for some feedback.


r/SaasDevelopers • • Feb 21 '26

How many apps/SaaS products have you shipped so far?

0 Upvotes

I’m trying to get a feel for what normal looks like for builders.

I’ll start: 5 shipped in the last 3 months.
Here’s my portfolio: https://myfoundrly.com/erick


r/SaasDevelopers • • Mar 23 '26

Looking for a deeply dedicated technical cofounder for my startup Omega Solutions Inc!

0 Upvotes

I have a startup of my own called Omega Solutions, where I am the Founder/CEO.

  • I have a BA from the University of Waterloo in Economics and English. And I have worked in marketing for many years for large companies, from Grant Thornton to Branch.io. I bring extensive product, strategy, and go-to-market experience to the table.

  • I am the CMO, the Founder, and the CEO—so I will be holding 66% equity in Omega Solutions, and you will be given a 33% equity stake that doesn’t vest until results are met/a certain number of years have been completed in building the product alongside me.

  • Looking for a technical co-founder. I already have an API I have half-built using Claude myself for you to get started working on completely building, users who want to test it in the pipeline, potentially, and a real problem worth solving.

  • You should know tech cold. Backend, infra, APIs, I literally mean everything. You don't need hand-holding, and you don't wait to be told what to build next.

  • The problem I am solving is helping people tell when some text document, audio clip, downloaded file, image, media coverage clip, or video is being deceptive in any way or not.

  • I am building a DIE "Deception Intelligence Engine” called FORESEE, which can read and analyze body language, WhatsApp conversations, audio clips, documents, text, and media coverage clips for deception of any kind and tell you with 90-100% probability models to what degree a certain individual, situation, text document, or behavior (culturally Indian for now, but to be going global as soon as possible) is honest or hints at deception of any kind. The DIE (Deception Intelligence Engine) can be used in many industries (legal, professional services, medical, military intelligence, the list is potentially endless), but also for interpersonal communications (particularly WhatsApp) for sure.

  • In the long run, FORESEE would do more than just tell users how deceptive an individual or situation is likely to be. It would be able to build APIs like Claude (do everything that Claude can do already), do everything that ChatGPT can already do, and be better than Claude, ChatGPT, and Gemini COMBINED. So no one uses anything other than FORESEE for Every. Single. One. Of. Their. Needs. Online. And Offline.

  • This is so that FORESEE can then power GOAT Glasses to be able to help the world see eye to eye, live in more harmony and peace, and learn to love each other a little harder (so racism in the entire world is made completely obsolete by 2040). And so are other devices we use right now, like smartphones, laptops, desktops, etc. Nothing OTHER than GOAT AR glasses should exist by 2040, which is what I am working towards.

  • That is the vision I have for FORESEE and GOAT GLASSES that keeps driving me to work day after day and late into the night right now. Every single day. Including holidays and Sundays (I am a hardcore Christian—coming from a religion that preaches and practices LOVE). Just FYI.

About me:

I live in Bangalore, India, right now.

Moreover, I am a bipolar patient living with bipolar and needing to take medication for it, so my sleep is non-negotiable at this point. If you are a technical co-founder based on a different continent with extreme time zone differences, where your day is my night, this potentially might not work, because my sleep is a major non-negotiable at this point.

If there is any way you can see us working together regardless, and taking my non-negotiable into account, I would LOVE to hear from you!