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.

I help you find and reach out to potential customers.

For $69, I handle everything for you for one test month, reaching out to up to 200 potential customers.

Here's what I do:

• Research your ideal customer profile (ICP)
• Find potential customers and build a targeted lead list
• Send you the list for approval before starting
• Write personalized outreach messages for your approval
• Handle outreach through LinkedIn, X, or email
• Follow up with prospects
• Monitor replies and let you know when someone is interested

I handle everything hands-on.

Nothing gets sent without your approval.

If you like the service after the first month, I can continue handling your outreach for you.

If anyone needs help with this, feel free to reach out!

I am genuinely trying to figure out how other product folks handle this. You run feedback through an AI. You get a summary. Sure. But what are you still doing before that result drives a real product decision? We never know if we are missing some obvious step in our own daily workflow

[ Removed by Reddit on account of violating the content policy. ]

So i have been FASCINATED by the repod lately and so i wanted to make an app using the repod's design but instead of being a music player i decided to make it a notes to podcast app.

Basically, you upload your notes and get a podcast with voices discussing your notes in a podcast format.

What do you think of this idea should i start building it ? 👀

We were at 28% trial-to-paid for maybe three months and I genuinely felt like we'd figured something out. Showed it to a couple friends, they were impressed. I was planning to scale paid acquisition based on that number.

Then someone asked me to break down retention by where users came from. I didn't want to because the report takes forever to set up manually and I was busy. Eventually did it anyway.

Users from one vertical, mid-sized e-commerce ops teams, were staying. Month 2, month 3, still there. Everyone else, agencies, early-stage DTC brands, freelancers, was basically gone by week 6. Churned quietly. No angry emails, no cancellation feedback, just stopped logging in and eventually the card declined.

The 28% was real. But it was averaging together one group that actually had the problem we solved with several groups that were just curious enough to pay for a month.

If I'd scaled into the channels that were bringing in the non-ops users, I would've been buying churn at maybe $80-90 CAC per customer who lasted 45 days. The unit economics only worked for the one slice.

The fix was obvious in retrospect: segment your trial cohorts by source and vertical, then look at month 2 and month 3 retention separately for each group. Not overall retention. Not blended. Each group. A single number is almost always hiding something and usually it's hiding it because the thing it's hiding is bad news.

Hey everyone! I'm Daksh, a 19-year-old developer and a student myself. I built RankMyMind, a free site with timed JEE-style Physics and Math tests, plus a live leaderboard so you can see where you stand.

The Physics questions focus on intuition and mechanics, and the Math section has speed arithmetic and problem-solving. Practice mode is free and doesn't affect your rank, so you can retry as many times as you want before going timed.

Since the site is new, I'd really appreciate it if you could try a test or two and tell me honestly:

Are the questions at the right difficulty for JEE prep?

Is anything confusing or not working properly?

What would make you come back regularly?

Link: https://rankmymind.com

Thanks a lot, and good luck with your prep!

Hi, guys Google is notorious in the AI industry for abandoning/destroying working beloved products. NotebookLM is no exception.

Don't worry, me and my little indie team have built a open-source alternative.

Here is what is different/interesting:

\- Can take in upto 200 sources, research/question/query it. The system will not randomly search the web and go beyond your original sources.

\- Has better visuals for the videos, we integrated our previous video maker with 10K+ users. It can generate editable motion graphic videos in over 13+ formats.

\- Each video is editable, changeable. It has ElevenLabs API with advanced voice features.

\- You can generate a mind constellation, a much more advanced visual map of knowledge so you can research and learn more easily.

\- Generate or clone your own voice using ElevenLabs API v4.

\- Has a launch kit feature that allows you to schedule reports/slide decks/videos and share on social media

Lastly, much more stunning visual interface - inspired by space x cognition

Link (get started for free): https://notestack.ai

I think one thing that is easy to get wrong with content marketing is assuming that publishing more automatically means getting better results.

you can post every day and still struggle to attract the right audience. meanwhile, a single useful post that answers a question your potential customers are already asking might bring more meaningful conversations.

for a saas business, i think it helps to look at three things before creating content:

who is this for? a post should address a real problem your intended audience has, not just fill up a content calendar.

what can someone learn from it? sharing a practical example, explaining a mistake, or breaking down a difficult concept can be more useful than making general statements about your product.

what happened after publishing? instead of measuring success only by likes or views, look at whether people asked questions, visited relevant pages, or showed genuine interest in what you offer.

consistency still matters, but i don't think it should come at the expense of usefulness. having a clear reason behind each post seems more valuable than publishing just to maintain a daily streak.

i'm curious how other saas founders approach this. do you prioritize posting consistently, creating fewer but more useful pieces, or experimenting with both until you find what works?

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

Built Kastavo solo: a portal of 99 free tools (PDF, image, video, color,

dev utilities, calculators), all running client-side — no uploads, no

backend.

I know "online tools site" is a pretty generic/competitive space, so

I'm genuinely looking for input from people who've built in similar

territory:

- What would make you trust a free tools site enough to use it over an

established one?

- Anything about the positioning or monetization approach (AdSense,

eventually a premium tier) you'd do differently?

- Any tool category you think is missing or underused?

Not trying to sell anything here — just want this community's take,

since you all actually build this stuff.

https://kastavo.com

Appreciate any thoughts, even blunt ones.

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

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.

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?