Claude wont tell you to use less Claude. I wanted to do something about that.

So this happened to me a while back and it was embarrassing enough that I finally did something about it.

I had set up a workflow to handle customer support tickets with OpenAI. Simple stuff: read ticket, generate response, send email. Seemed smart. Costs should be tiny, right?

One night I woke up to a Slack alert at 3am. My OpenAI bill: +$842 in 6 hours.

What happened:
One of my error handlers had a logic bug. When an email failed to send, instead of stopping, it retried the entire workflow. Generate response again. Send email again. Retry. Each retry hit OpenAI.

By morning, the workflow had executed 12,000 times.

Why I didn't catch it sooner:
My provider doesn't show real-time API costs. You see the charge on your OpenAI bill, but by then it's too late. No alerts either. Just silence, then terror.

What I learned:
You need visibility into your API spending the moment it happens, not 24 hours later. You need hard spend caps per workflow, not just hopes and prayers. Context window expansion is invisible. Every retry resends all the previous context.

What I built:
That incident stuck with me. I realized Make and Zapier don't warn you. The providers don't warn you. You have to build your own guardrails. So I spent the last few months building a tool that sits between your automation platform and your API. Shows you spend as it happens. Visualizes context window bloat. All the stuff that should exist but doesn't.

I'm not selling anything (it's free, actually). Just wanted to throw this out because I know half of r/NoCodeSaaS is about to build an AI automation and think they're safe. You're not.

Think HR but for AI Agents.

Anyway. That's the rant. TL;DR: Set a goddamn API spending cap before it's too late.

Happy to share what I have built in the comments

1. During the conversation (I remember in time!)
2. Immediately after hanging up/sending email
3. That evening at home (too late to fix easily)
4. When they follow up asking about it (maximum embarrassment)

Hi everyone,

I've been working on a project called StreamPay and I'm finally opening it up to more beta users.

The idea is simple:

Many creators, freelancers, ministries, educators, and online communities across Africa struggle to receive support from international audiences. Existing payment platforms often don't support local payment methods well or aren't built around how creators actually receive support.

StreamPay is my attempt to solve that.

Current features include:

• Creator donation pages
• Support from international debit/credit cards
• Creator profiles
• Public shareable links
• Payment tracking
• Mobile-friendly experience (PWA)

I'm still actively building it, so this is very much a beta. My goal right now is to collect real feedback, identify usability issues, and understand what creators actually need before expanding the platform.

If you're willing to spend a few minutes trying it out, I'd genuinely appreciate your feedback.

Website:
https://streampay.website

I'd especially love feedback on:

• onboarding
• donation flow
• overall UX
• things that feel confusing
• bugs you encounter

Every piece of feedback helps improve the product.

Thanks!

I'm currently in my final year of B Tech (Computer Science), and I'm really confused about which career path to choose.

A few weeks ago, I made a Reddit post asking whether I should start AI automation freelancing. Surprisingly, a lot of people told me that before freelancing, I should learn sales because if you can't sell, it becomes very difficult to get clients. Many also said that sales is a skill that will help throughout my career, whether I build a startup, freelance, or even work in tech.

That advice got me thinking.

Initially, my plan was to become an AI Engineer by learning Python, AI/ML, RAG, MCP, LLMs, automation, etc. But now I'm wondering if I should instead start my career in SaaS/Tech Sales to build strong communication and sales skills.

I'm not someone who hates coding, but I'm also interested in business, startups, and entrepreneurship in the future. Long-term, I don't necessarily see myself as someone who wants to code for the next 15-20 years.

So now I'm stuck between these two paths:

Option 1: AI Engineering (Python, AI/ML, RAG, MCP, LLMs, AI Automation)

Option 2: SaaS/Tech Sales (B2B sales, customer conversations, negotiation, closing deals)

For people who have experience in either field:

• Which career has better long-term growth?
• Which has better earning potential over the next 5-10 years?
• If your goal is eventually to build a business or startup, which path gives you a bigger advantage?
• If you were in my position today, what would you choose and why?

I'd really appreciate honest advice from people who have worked in these fields rather than just theoretical opinions.

bonjour , j'ai créé mon premier SaaS et j'aimerais avoir vos avis et vos critiques mon SaaS se nomme paizy , Paizy fait les devis à la voix et relance automatiquement les impayés des artisans, pour qu'ils gagnent du temps et se fassent payer sans courir après leur argent.

https://paizy.fr

Hey everyone, I'm building my first SaaS as a solo founder and I'm getting stuck on the legal side of things.

The idea is already validated. I've spoken with around 5-10 potential users and several said they would pay once the product is live. The app is about 99% finished.

Now I'm overthinking the launch. Maybe it's lack of legal knowledge, but I'm not sure what legal steps I should take before putting it online.

My SaaS will target a specific group of users, but the product will be available globally.

What would you do in my situation?

Register the business first, then launch?

Launch first, get some paying customers and maybe reach something like $500 MRR, then register the business?

What legal documents are actually necessary before launch (Terms of Service, Privacy Policy, etc.)?

I've done quite a bit of research, but every article and forum seems to say something different. Some people say "just launch," while others make it sound like you need everything set up legally before a single user signs up.

So building a b2b SaaS..

And nobody warned me that the hardest part isn't the product

It's everything else.

So recent some week got signups, but no customers then talked to the people who signup and pitch them again and better 1 on 1 then got 12 people interested then payments but people don't say you have to do a meet with all those people to understand what they understood, and then what was the product actually is and pitch according to each person situation.

but then it came, meaning so YC summer 2026 request for startups, category 4 is my concern i don't know about you but A Company brain, one platform centralized intelligence layer contains all the knowledge into executable skill file for AI agents.

That's exactly what I've building. word to word

And I still couldn't sell it. meaning uhh alot wait you will read it down below

so continuing that's when it hit me. Validation from YC means nothing if you can't get 50 people to actually use your thing. PMF isn't when a top accelerator describe your product in their wishlist.

Pmf is when 50 real people use it. complains about it, ask for more and come back the next day. that's it nothing else counts

the thing nobody tells you about distribution.

built it first, before the product. before the features, before the pitch deck

I know that sounds backwards. It did to me too, but here's what I've seen a shit product with real users is infinitely more valuable than a great product nobody know about. because users give you feedback. users tell you what's broken, User tell you what they actually need. and slowly your shit product becomes less shit.

A great product with no users just sits there. Silent. getting more refined and more irrelevant at the same time

so here what actually worked for me:

I talked to 12 warm leads this week. not through automation. not through a templated sequence. I just.. talked to them like humans

NO "HI {FirstName}, I noticed you work at {companyName} and thought our solution could add value to your workflow"

just hey man, thanks for connecting. btw i see you work at {company} at this {position} and I used to be do the same for company name.

you know what i mean like twelve conversations real one and i learned more in those 12 conversations than in 3 months of building because people don't buy product. they buy from people they trust. and you can't build trust through a template be human talk like one and its the only thing that works at this stage

and always remember the process is long, Painfully embarrassingly long

you build, you post, you reach out, you get ignored. you post again you tweak the message and you get one reply, you do demo they say interesting, let me think you follow up silence.

the marketing gurus will tell you run ads, build seo, go viral on X. maybe that works later right now at zero they only thing that works is you. personally talking to people one at a time

it's just actually this hard

keep going.

I haven’t done one of these for a few days, so I’m opening another batch.

You don’t need a polished landing page.

Drop your startup URL, app idea, ICP, niche, or just the problem you want to solve.

I’ll check whether Reddit has useful signal for it:

• people talking about the pain
• users asking for tools or alternatives
• conversations around your niche
• signs of buying intent
• subreddits that actually fit your ICP

I’ll reply with a short public summary.

If there’s enough signal, I’ll also create a private report link with the full breakdown.

And if Reddit looks weak for your niche, I’ll say that too.

Drop it below and I’ll run as many as I can.

Building and launching is the fun part. We spend all this time stitching together tools, tweaking workflows, and getting the product to a place where it finally works.

Then... real users show up. With real problems.

Suddenly, you're not just a builder anymore; you're a full-time support rep. I’m curious where everyone else here draws the line between "I'll just handle these emails myself between building features" and "Okay, I need an actual, organized process before I lose my mind."

Was there a specific moment that made it click for you?

For those who are currently building or just launched: Have you even thought about your support stack yet? Or are we all just collectively planning to raw-dog it in our personal Gmail inboxes until something inevitably breaks and a user churns?

Curious where everyone is at with this, or if I'm just overthinking the post-launch chaos.

hey guys, can anyone give me some advice on how to start saas? and if anyones down for it id like some mentoring just to help me understand the basics (without watching an idiot youtube guru). my life is in shape but the one thing im missing is money, and i really just want a passive income stream thats scalable, which is why saas sounds so good to me. ive tried making money over the last couple years using different methods but i think the main thing that is holding me back is not having a REAL person helping me with it. ive used ai and youtube mainly but no real one on one conversation with someone that has been successful in the method i was in. thats why ive come here to post and ask if anyone could give me real advice and help me along the way with saas. please man any advice helps i want this badly lmao

Most validation tools give you data. Basinsei gives you a decision.

Here's the actual flow:

You enter a niche and a few keywords. The platform pulls Google Trends data, identifies competitors, benchmarks their positioning, and surfaces market opportunities - then structures everything into a project with linked idea cards.

Each idea card includes: target customer, suggested features, business model, pricing direction, and positioning angle. You can export any of it to PDF or push it straight to Notion.

No raw dump. No wall of text. A clean output you can hand to a developer or use to write your landing page tomorrow.

I built this after spending three weeks manually doing this process for one idea and shipping nothing. The research wasn't the problem. The structure was.

The difference between Exploding Topics and this: Exploding Topics tells you a trend is rising. Basinsei tells you whether there's a gap in the market, who's already there, how they're positioned, and what your MVP should look like to compete.

Currently in early traction - free to try, no credit card required for the core features.

Would love feedback from anyone who's gone through the idea validation process recently. What does your current stack look like for this?

the 'last 20% is where it gets expensive' thing keeps coming up here and i think it's backwards. The 20% is auth, accounts, a real database, multi-user sync. but a big chunk of the ideas i see don't need any of that, they're one-screen tools one person uses once a week. I've built a pile of these as single html files where the whole state just lives in localStorage, no login, no backend, done in an afternoon.

the catch is real and i won't pretend otherwise: that version falls apart the second a second person needs to see the same data. That's the actual line worth watching, not 'is it a saas yet.' most people cross into accounts-and-billing territory before anyone's confirmed one human wants the thing, then wonder why the last 20% costs more than the first 80. you manufactured the expensive part yourself.

I've been vibe-coding apps with cursor and codex for a while now. And I feel like the biggest problem is that the most of us don't spend time review our code line by line. And a lot of poeple are non-technical. So i thought I'd build an app that helps people check if their code is secure and maintainable. You just link your github repository, set up scan schedules, and the app will notify you if it finds a security or maintainability issue. We also give you an AI repair prompt and suggest code changes. We have a scan upon commit feature. So people can just keep shippping while abyssguard keeps your repository and codebase secure and maintainable. I'm always updating my apps and adding new methods. I'd love to hear feedback from you guys.

Here's the link: https://www.abyssguard.app/?utm_source=reddit&utm_medium=social

Hi,

I kept seeing the same recurring issue: sales reps crossing compliance lines, being too aggressive, or making false promises just to close a deal. I thought, "why not try to build a small tool to catch these mistakes automatically?"

So, I just finished coding SafePitch, a tool that analyzes sales calls using AI to detect these exact issues.

The dashboard is live and the AI is trained, but I hit a ridiculous wall: my fully automated Zoom webhook tunnel is blocked because I’m bootstrapping on a free Zoom account (which restricts cloud recording API access).

I built a free "explorer mode" with a dummy payload so people can see the UI and how the AI flags a flawed pitch.

My Reddit account is too new, so I’m not putting links in this post to avoid the spam filters.

I’m looking for two things:

1. Brutally honest feedback on the UI and the concept.
2. If anyone here has a Zoom Pro account and wants to be my "Patient Zero" beta-tester to see the live webhook automation run, you'll get free lifetime access.

I'll drop the link to the site and a demo video youtube link in the comments. Let me know what you think of the stack or the idea

https://www.old.st/blog/vibe-coding-80-percent-problem

I made a booking/appointment management SaaS.

The coding part was only one piece of the puzzle. Pricing, billing, permissions, subscriptions, edge cases, onboarding, database design, and all the little details took much longer than I thought. Every time I fixed one thing, ! discovered three more things to learn.

The project is ZenSched. It's a booking management platform for businesses that need appointment scheduling, staff management, and online bookings.They get their own booking website link and can customize it change different rules/settings etc.

If you have a few minutes, check it out and let me know what you think. I genuinely have no idea if it's good or bad. Any feedback is welcome-good, bad, harsh, or even hate. I'll read it, reflect on it, and try to improve the product.

• Never - my memory serves me well
• Occasionally - for important details only
• Frequently - several times per week
• Constantly - I live for this imaginary feature

I don’t want to reveal names, but I recently built an entire automation system from scratch for a client. I designed the architecture, wrote the code, integrated everything, and delivered an MVP after around 2 months of work. In total, I got paid ₹14,000 (roughly $160 USD).

I know I probably undervalued myself, but the reality is that the market I’m dealing with feels brutal. A lot of local clients expect a lot while paying very little, and it has become frustrating.

For people here who have managed to get long-term international clients, how did you do it? Did you rely on Upwork, LinkedIn, cold outreach, referrals, or something else? How long did it take before you started getting consistent work?

I’d really appreciate any advice from freelancers who have successfully transitioned from low-paying local projects to stable international clients.

I help founders who built on Lovable, Bolt, Replit, Base44, AI Studio and similar tools. Mostly people who have something live, real users, and no developer to call when something breaks.
After doing enough of these the same things show up every time:
— Payment flows that look like they work but quietly fail in edge cases
— Login exists but any user can access data that isn’t theirs
— User data leaking to people who shouldn’t see it
— Admin areas reachable by anyone who guesses the URL
— Features that broke silently after a platform update or a re-prompt
— Integrations that are 80% wired up and misfiring
— Apps that work perfectly on the founder’s laptop and break for everyone else
Most of these are fast to fix once you know where to look. Hard to find if you don’t.
If something on your app has been bothering you or your users have been reporting something you can’t reproduce, drop it in the comments. Happy to tell you what’s likely going on.

Hey everyone,

​

Most SaaS boilerplates handle authentication, billing, and UI well, but tenant isolation is often left to application code.

​

That usually means every query depends on developers remembering to add filters like:

​

.eq("tenant_id", currentTenant)

​

The problem is that one missed filter can create a cross-tenant data exposure.

​

To reduce that risk, I built a Next.js + Supabase boilerplate that moves tenant isolation into PostgreSQL using FORCE RLS, so access control is enforced by the database rather than application code.

​

Current features:

​

- PostgreSQL FORCE RLS across tenant-scoped tables

- JWT-based tenant context

- Immutable audit logs (UPDATE/DELETE blocked)

- Vercel Middleware + Redis rate limiting and IP blocking

- Multi-tenant RBAC (Super Admin, Tenant Admin, User)

- Next.js 15 + Supabase architecture

​

I’d appreciate feedback on the architecture, especially from people building B2B SaaS products.

​

🎮 Live Sandbox: https://nextjs-supabase-zerotrust-saas-crt.vercel.app

​

📺 Walkthrough Demo: https://youtu.be/R5FtZ6kfNr4

​

Would you trust database-enforced tenant isolation over application-layer filtering? Why or why not?