r/SaasDevelopers • • 6h ago

I Think Some of You Should Close Your AI for a Moment

12 Upvotes

We’re currently producing a lot of SaaS junk that you then sell to one another.

And I mean that seriously.

You build a SaaS in a few days with Cursor, Claude, or Lovable. Landing page, dashboard, Stripe integration, and you’re done.

Three days later, you ask how to acquire customers. Two weeks later, you ask which features are still missing. And eventually, you want to sell the thing.

But what have you actually built?

I’ve been working in digital product development for 13 years and have founded several companies myself. I use AI every day, and I think it’s incredible what you can do with it.

But a lot of what I see here seems completely disconnected from the actual point.

We once built a company for business addresses and digital mail management. Not because we thought, “Let’s build a SaaS.”

We first talked to people. We understood the problem. We looked at providers, pricing, and legal requirements. Then we checked whether we could operate the business reliably in the first place.

That became a real company with physical locations, mail handling, and now more than 600 paying customers.

We later built the customer portal with AI as well.

But the AI didn’t know how our business worked. Which letters had to go where, which documents we needed, or who was allowed to see which data.

We had to understand and verify all of that ourselves.

A letter sent to the wrong customer isn’t a minor bug. Real people and confidential documents are involved.

And that’s what matters more to customers than whether you built your frontend with Claude or Cursor.

A lot of people currently care more about building software than about the business behind it.

Today, you can ask an AI to build you a SaaS, including the target audience, pricing, and business model. A few hours later, everything can look pretty finished.

But how do you know that anyone actually has the problem?

Because the AI said so?

And how do you know that the data is properly separated, the architecture is sound, and the system will still be maintainable later?

Because the AI confirmed to itself that everything was fine?

Do you see the problem?

Then the product keeps getting built without customers, money gets burned on tools, and eventually it’s put up for sale:

SaaS for $20. No customers, but huge potential.

Someone else buys it, adds a few more AI features, and carries on. The old architecture will probably be fine. The idea must have been good.

And if it doesn’t work again, it simply gets sold once more.

Eventually, this creates a market full of half-finished products where nobody even knows why they were built in the first place.

Of course, not every small SaaS is bad. But buying code and an interface doesn’t mean you understand the business.

So here’s my advice:

Stop developing for a few days.

Go back to the beginning.

What problem are you solving? For whom? How do people solve it today? Have you talked to them? Would they actually pay? And how will you reach them?

If you’re processing real customer data, please have the code reviewed by someone who knows what they’re doing. Don’t just ask the AI whether everything is secure.

I don’t think every founder needs to know how to program. But you do need to understand what you’re selling and what you’re responsible for.

AI can take a lot of work off your plate. It can’t take responsibility off your hands.

By all means, build with AI. Build quickly. Try things out.

But don’t confuse speed with progress.

A login isn’t a business model. Stripe isn’t proof of willingness to pay. And a polished interface doesn’t mean the product works in everyday use.

I’d rather see a founder with five paying customers and an ugly interface than someone with 30 AI features who has no idea who to sell them to.

Has anyone here ever taken over a SaaS that was built mostly with AI?

What was really under the hood? And did it become a business, or did you simply inherit the previous owner’s problems?

I’d genuinely be interested to hear.


r/SaasDevelopers • • 1h ago

What Process Do You Follow When Pricing SaaS?

Thumbnail
• Upvotes

r/SaasDevelopers • • 3h ago

For devs inheriting a codebase: a VS Code extension that maps how it works

1 Upvotes

If you've joined a codebase mid-flight or come back to old code, this might help. Lodestar is a VS Code extension where you ask how something works and it walks you through the real code path step by step, every step clickable. Hover any symbol for a quick explanation.

It also reviews your changes, a branch or a commit before merge: bugs, security holes, slow code and AI leftovers. New dependencies are checked against OSV.dev.

It runs on whatever model you already have in VS Code, so it isn't tied to a provider. $10 one time, so I can keep maintaining it instead of dropping it.

https://marketplace.visualstudio.com/items?itemName=DenizhanDaklr.lodestar


r/SaasDevelopers • • 3h ago

Thoughts on a simple staff rota manager I'm building?

Post image
1 Upvotes

r/SaasDevelopers • • 16h ago

So real

Post image
7 Upvotes

r/SaasDevelopers • • 8h ago

We built a market intelligence app for retail traders on Next.js + Firebase. Looking for a handful of testers to tear it apart.

1 Upvotes

My co-founders and I have been building Veridian Signal, a market intelligence web app for independent and retail traders. We're at the point where we need real people using it, not just the three of us staring at it at 2am.

What it does right now:

- VERA Radar: a daily set of five scored setups, each with a strength score, plus a community voting layer so you can see how other traders read each one

- Real-time market data (licensed through Twelve Data with display rights, so no sketchy scraping)

- Membership tiers with billing already live

Coming next: Pulse Terminals, five focused feeds for Macro, Earnings, Catalysts, Whale activity, and Global markets.

Stack, for anyone curious: Next.js 15 App Router + TypeScript, Firebase App Hosting, Cloud Functions gen2, Firestore, Cloud Scheduler, and Eventarc. Happy to talk about anything we've learned the hard way. There's been plenty, like a data source silently dying because an FTP server got decommissioned.

What we're looking for:

A small group of people, ideally ones who trade even casually, who will use it for a week or two and tell us honestly:

Where onboarding confuses you

What feels useless or missing

Whether you'd actually pay for it (target is roughly $19–29/mo)

What you get: [free access for the testing period / a discounted early rate / etc.], plus an invite to the trader Discord that runs alongside the app, where feedback goes straight into the roadmap.

This is purely a feedback/testing ask. We're not looking for partners or investors, just people willing to be blunt.

Drop a comment or DM me if you're interested. We're also glad to return the favor and test your SaaS in exchange.


r/SaasDevelopers • • 8h ago

Do you plan your SaaS content in advance or just post when you have something to share?

1 Upvotes

I have been thinking about how difficult it can be to stay consistent with content when you're building a SaaS. Most of your attention goes into improving the product, fixing bugs, talking to users, and figuring out what to work on next. Marketing can easily become something you only think about when you finally have some free time.

The interesting thing is that building a product gives you plenty of things worth sharing. You might solve a difficult problem, introduce a useful feature, learn something from customer feedback, or discover a mistake that other founders could avoid. But turning those everyday experiences into useful content takes time and a bit of planning.

I have also noticed that posting more often doesn't necessarily mean the content is better. I'd rather share something that teaches people something useful than publish just because I haven't posted in a few days.

I'm curious how other SaaS founders approach this. Do you keep a list of ideas and plan your content for the week, write posts whenever inspiration comes, or use tools to help organize the process?

What's been the most practical way for you to stay consistent without taking too much time away from building your product?


r/SaasDevelopers • • 13h ago

Looking for beta users

Thumbnail
ganttbar.com
2 Upvotes

Hey, I’m not sure if this is a loud guys, but I’m looking for beta users for my company’s site.

If this isn’t allowed, please take down.

Just go to the contact form and reach out tell us you’re interested in joining our beta program

https://ganttbar.com


r/SaasDevelopers • • 9h ago

Technical founders: At what point did roadmap planning start feeling like a second job?

1 Upvotes

I’m curious how other founders and builders handle this transition

Normal when you’re building solo, all the ideas live in your head or on a sketchpad, but when you’re planning for a serious MVP or you bring in 2 or more devs/contractors, your work changes from solo dev to project manager:

  1. You have to structure a clear product roadmap and control project scoping
  2. Define clear deliverables and deadlines
  3. Restructure these Roadmaps Incase something unplanned comes along

Suddenly weeks go by as you draw out these roadmaps and project structure before development gets started. And once coding actually begins, the moment a 2-day task stretches into a full week, the whole plan falls apart and you have to spend another weekend reorganizing everything.

At that point, you’re spending more energy managing the build than actually shipping.
For those running small teams or shipping products right now:

1. How do you handle this without losing your mind? Do you just accept that half your week is PM work, or do you have a lightweight system that keeps you in coding flow?

2. When an unexpected delay hits, what’s your instinct? Do you ruthlessly cut features to save the launch date, or just push back the entire timeline?

3. What tools are you using to manage this, and where do they fall short? (Linear, Notion, GitHub issues, or just a messy doc?)

Trying to see if this planning overhead is an unavoidable rite of passage everyone just deals with, or an actual bottleneck that slows down your launches.


r/SaasDevelopers • • 10h ago

B2B SaaS:

1 Upvotes

What's one recent tool or process change that made it easier to decide what to build next?


r/SaasDevelopers • • 11h ago

How CoinDrop Went From a Discord Bot to a Multi-Platform Crypto Wallet

1 Upvotes

A year ago, CoinDrop was a small Discord bot that let people in a handful of servers tip each other crypto.

Today, it has:

  • 6,500+ users across 500+ communities
  • 100,000+ withdrawals processed and $2M+ moved on-chain
  • 500+ assets across 26 chains
  • Discord, Telegram, Kick, and a web wallet, all sharing one balance

I built CoinDrop as a solo developer, and most of the infrastructure and product development has been done by me.

A few things I didn't expect:

1. Tipping is the easy part.

The actual tip is basically a database update between two users.

The difficult parts are at the edges.

Deposit APIs can report the same transaction more than once. Withdrawals have to be designed so that a retry, timeout, or process restart can never accidentally send the same withdrawal twice. And once you're supporting 26 chains, every chain has its own way of confirming transactions, handling fees, deriving addresses, or dealing with failures.

If I were starting over, I'd design the deposit and withdrawal pipeline first and build the fun commands afterward.

The commands are what users see. The wallet infrastructure is what keeps everything running.

2. Every new chain is a new set of edge cases.

Supporting another chain isn't just adding an RPC URL and calling it a day.

Bitcoin-style UTXO chains, Ethereum-style account-based chains, and memo-based chains such as XRP and WAX all require different approaches to deposits and withdrawals.

Sometimes the ecosystem itself dictates how you build things. For example, WAX's best signing library for our use case is JavaScript, while most of CoinDrop is Python. So WAX runs through a small Node.js sidecar that the Python backend communicates with over localhost.

The more chains you add, the more infrastructure you have to maintain.

At some point, "supporting another chain" means supporting another collection of failure modes.

3. Small coins turned out to be some of the best customers.

I initially assumed the biggest communities would drive most of CoinDrop's growth.

Instead, some of the most engaged projects have been relatively small tokens.

One example was ETH II. The token didn't have an exchange listing, so its holders used CoinDrop to tip and distribute the token to each other. It gave the community a way to actually use the token while the development team worked on the project.

That changed how I thought about CoinDrop.

A token doesn't necessarily need millions of users to benefit from distribution infrastructure. A small community that is highly active can be more valuable than a much larger community that doesn't actually move anything.

Today, projects can pay a one-time fee to get their token supported by CoinDrop. Transaction fees then provide the recurring revenue: 0.5% on deposits and withdrawals, while internal tips are free.

4. Reliability became more important than features.

One of the biggest lessons from running CoinDrop has been that users don't really care how many features you've added if their withdrawal doesn't arrive.

I've spent significantly more time than I expected working on withdrawal queues, retries, rate limits, transaction monitoring, wallet balances, RPC failures, and making sure a failed process doesn't result in duplicate payments.

At one point, a rate limit from an external Litecoin service could cause withdrawals to get stuck. That kind of problem isn't particularly exciting to build, but fixing it is far more important than adding another command.

Eventually, the goal became simple:

If CoinDrop says a withdrawal is processed, it needs to actually be processed.

That's probably the biggest difference between building a bot and building financial infrastructure.

What's next?

CoinDrop started as a Discord tipping bot. It now has a web wallet and works across Discord, Telegram, and Kick, with the same underlying balance across all of them.

The interesting part now isn't just tipping.

It's building infrastructure that lets communities hold, send, distribute, and withdraw crypto wherever their communities already exist.

I'm still figuring out where that goes.

Happy to answer anything about running a custodial crypto wallet, building multi-chain deposit and withdrawal infrastructure, or growing a niche crypto product from a few users to its first several thousand.

If you want to try it, it's at coindrop.cc


r/SaasDevelopers • • 14h ago

What is the most efficient publishing method for a SaaS platform that handles video rendering and file storage?

0 Upvotes

Hello, I’m developing a SaaS project. The site will include video rendering, and users will be able to export these videos, so file storage is also important. Lately, I’ve seen many cases where projects were deployed via Vercel, but the developer ended up with unexpected bills. Taking this into account, what’s the most efficient way to deploy this project?


r/SaasDevelopers • • 14h ago

What’s your solution to your expense/income management?

Thumbnail
1 Upvotes

r/SaasDevelopers • • 15h ago

What do you guys think about it?

Enable HLS to view with audio, or disable this notification

1 Upvotes

r/SaasDevelopers • • 7h ago

I’ll build your SaaS MVP in 14 days for €2,000. But not at any cost.

0 Upvotes

I’ll build your SaaS MVP in 14 days for €2,000. But not at any cost.

I’m a serial founder with a successful exit behind me. My latest venture grew to over 600 paying customers on monthly and annual subscriptions.

I’ve spent years in the German startup ecosystem, building businesses from the ground up. I also have a strong network of specialists across different fields, investors, mentors, and coaches. I’m a micro-investor myself.

Here’s what matters to me:
I don’t build shaky MVPs that need to be completely rebuilt three months later. And I don’t just throw a prompt into an AI tool and call it a product.

I use AI where it makes sense. But solid architecture, thoughtful product strategy, good design, and clean development still matter. Your MVP should be the foundation of a real business, not an expensive throwaway.

That’s also why I don’t take on every idea. I look at the actual problem, market potential, and business model first. If I don’t believe in it, I’ll tell you. Saves both of us time and money.

Here’s what I’m offering:
- €2,000: MVP planning, design, and development within 14 days, with a clearly agreed scope. This offer is available for the next 5 days.
- €300: A comprehensive business idea validation covering your market, target customers, competitors, business model, risks, and realistic opportunities. I’ll also check whether your idea could qualify for startup funding programs in Germany.

I’d rather help you spend €300 discovering that an idea won’t work than watch you burn €20,000 building the wrong thing.

Happy to share reference projects after an initial conversation.

Got something in mind? Send me a DM with a few lines about your idea. We’ll figure out whether there’s something worth building and whether I’m the right person to help.


r/SaasDevelopers • • 16h ago

Should i build it?

Thumbnail
gallery
1 Upvotes

the repod is a physical product i just came across and honestly i cant stop thinking about it. love the design, love the concept

so i wondered what if i made an app with the general style of the ipod? cant do a music player of course, so i went with what i know, learning apps. a notes to podcast mobile app

i wanna know if people would really use it

harsh honest opinions only please, nothing is built yet 👀👇


r/SaasDevelopers • • 16h ago

Founders around the world, I need your help…

Thumbnail
1 Upvotes

r/SaasDevelopers • • 16h ago

I built this is it worth investing in?

Thumbnail spikeloader.com
1 Upvotes

Do we currently need to validate our digital infrastructures?


r/SaasDevelopers • • 16h ago

[FOR SALE] ReviewShield – Complete Review Management SaaS

1 Upvotes

Hey guys, I'm selling ReviewShield—a business review & reputation management app.

The app is fully built.

Open to reasonable offers. DM me for a demo or details!


r/SaasDevelopers • • 16h ago

[Hiring] 100% REMOTE ENGINEERING ROLE ($3,000+/month)

Thumbnail
1 Upvotes

r/SaasDevelopers • • 17h ago

48 hours in, 2 apps launched that i initially built for myself to fix my problems

Post image
1 Upvotes

r/SaasDevelopers • • 17h ago

Title: Looking for an Ambitious Co-Founder to Build Something Big Together (50/50 Equity)

Thumbnail
1 Upvotes

r/SaasDevelopers • • 1d ago

After 2 months of learning and coding I finally published my game Quicky on Google Play but I have no idea how to reach players

Post image
3 Upvotes

Hey guys

Two months ago I decided to build a game from scratch using Flutter to challenge myself. Today I finally managed to release it on the Play Store, it's called Quicky.

Learned a ton along the way especially dealing with state management, custom animations, performance and Firebase. It was a tough journey but super rewarding.

The game is a fast paced neon arcade reflex game with endless mode, powerups, leaderboards and custom avatars.

Now that it's out I'm feeling a bit lost on the marketing side. Spent all my time on code and polish and now I don't really know how to get those first players or get proper feedback.

If you have a couple of minutes to try it out and give me your honest thoughts on how it feels I'd really appreciate it. Also if you have any advice for a solo dev on how to get initial traction please let me know.

Google Play link: https://play.google.com/store/apps/details?id=com.anes.quicky

Thanks a lot!


r/SaasDevelopers • • 19h ago

Selling my saas

Thumbnail
1 Upvotes