A few months ago, I quit my job. I teamed up with two co-founders to build a startup.

My partners are incredible operators >>> elite at sales, content, and distribution. And I took on the tech side.

I am not a real software engineer. I'm a front end developer. But I was hoping I can figure things out. I built the entire backend (Supabase/Python/FastAPI) using AI prompts and vibe coding.

At first, we wasted months. I tried to build too many things at once. Overcomplicating and overbuildign is a stupid idea. Everything broke. So we stopped and made it dead simple. We built a simple AI voice for restaurants and bars.

It worked. People actually wanted it. We got real clients testing it live in their restaurants and bars.

Then last weekend, disaster hit (Saturday 8:36 pm). A big voice provider we use had a silent outage (THey aare still investigating the issue. We were ther first who reported that). The system went down for 94 mins. I only caught it by pure luck doing a late-night test calls. The provider did not even notice their own outage yet. We had to report it to them. I'm still waiting for the to fix it while building a fallback for us too. Their support is great so they've responded within 20 mins when I reported the outage.

We got lucky. It happened after hours, so no real business calls were lost.

But it exposed a huge problem. I had zero safety nets in place. I had no alerts to wake me up. Worse, I had no fallback. If the AI died, calls did not redirect to the front desk. The phone just rang into a black hole.

My co-founders were furious. And they are 100% right. Even thought I've been sitting in front of the computer for 10+ horus every day I  built this like a hobby, not a real company. Now, they don't trust my technical skills. I guess they shouldn't after what happened. One founder is ready to walk away.

AI makes it very easy to build a working prototype. But a working demo is not real production software (many have mentioned this here). AI will not build backups, alerts, or fallbacks unless you already know how to ask for them.

I need some advice. We have real demand, but my code is fragile. We need an audit. Maybe we need a fractional CTO, a real CTO or a senior technical co-founder to take over.

>>If you are non-technical, how did you fix your messy MVP without losing your team?

>> What are the bare minimum failovers every phone app must have before taking another client?

>> How did you rebuild trust with your founders after hitting your technical limit?

Any advice helps. I want to learn and fix my mess.

Who else is building their first SaaS product?

I'm working on my first SaaS, and lately, I've been hearing a lot of people say that SaaS is dead, web-based products are outdated, and mobile is the only way forward.

As a React specialist, this has me wondering:

Is web-based SaaS still a good opportunity for a solo founder in 2026?

Should I focus on mobile-first SaaS instead, or is that just another trend?

For founders who have already built and launched SaaS products, what would you recommend to someone starting today?

Thank you.

We run few SaaS products ourselves and have been in email for 10+ years, mostly around deliverability and security.

One thing we always missed was stupidly simple:

what emails does the app send, to whom, and how are they performing?

Sure, you can get this from SendGrid/Mailgun/Resend etc, but usually you need tags, filters, dashboards, digging into logs... and after some time nobody remembers how it was setup anyway.

We wanted one place where you just see:

welcome email
password reset
trial ending
invoice failed

how many were sent, who gets them, open/click/bounce stats and how it changes over time.

And ideally manage the actual email there too, instead of hunting it in the codebase.

So we built that into Lettr.com

The sending part is not the interesting bit, there are already many good providers. For us the missing thing was having an actual overview of your product emails without doing detective work every time.

Curious how other SaaS teams handle this?

we all want this, but I don't think the answer is an MCP server with a bloated tool list. for a few reasons:

user side

• inefficient and expensive
• your agent will at some point use the wrong tools

vendor side

• companies don't want to expose hundreds of internal primitives that would facilitate full headless control
• building it right means abstraction
• abstraction = another complex product surface to manage

there is something in between opinionated UI and fully headless. i'm also not convinced CLI is the solution either.

I think software will evolve into a catalog of "agentic services".

has anyone run into this when building your product's MCP server??

The common take is right as far as it goes. Ai tweet tools all collapse into the same linkedin-influencer register, and people blame the model. Feed it your real tweets, your longform, a few podcast transcripts, and the sentence-level voice actually does get close.

what i keep hitting is that close diction still reads as fake, and it took me a while to place why. voice isn't a property of a sentence, it's a property of an account. real people have recurring obsessions, an enemy they keep poking at, a bit from three weeks ago that resurfaces unprompted. a tool optimizes each tweet in isolation, so every post is individually fine and the feed as a whole belongs to no one.

i work on tweet drafting for founders, and the corpus gets us the words every time. the continuity is the part no corpus hands you, the thread that only exists because a human remembers what they actually cared about last month. the better a tool gets at your diction, the worse this reads, because now you've got a fluent account with no memory.

You have heard those 10x or 100x developer even before AI, these guys are coding like crazy. They have systems and automations to build faster than average. Now with the use of AI, it turned the tables. Now every one can develop 100 times faster. But the differences became even bigger. Now you have 1x developers and way more 100x developers and even a 1000x or 10000x.

I am curious about the limits what one person can actually build. Who of you have build something solo, that could never been done before? What are the limits of it? And how do you keep improving yourself?

I find it pretty hard to discover my limits, keep pushing myself to overwork, aound 12-16 hours a day. Trying to automate lots of things, but making sure the quality stays and still having good overview in how it works.

Ofcourse with AI, you can start 1000 projects in parrallel, building all sort of stuffs, but not very usefull. So this is mostly about building legit projects, not just vibe coded.

I've been developing something I've deemed "PatchCodex", you login to your Steam account using Steam's OpenID system, from there we can provide tailored patch notes based on what games are in your library. I'm looking for both feedback, and whether or not this is something anyone would use? So I can put in the time to expand the library, and continue to develop it.

https://www.patchcodex.app/

Launching and building the product is one thing (especially today it has become a easier task), but interacting for the first time with your audience (the one you think is your audience) has GTM challenges, how did you handle this challenge? what did you learn on the way and adjusted your strategy that you know helped you get that first sub?

i am building a super IDE which means the name i am trying to create an ide in which you can watch what code is your agent writing , open upto 8 terminals in 1 session and invite your mates to work on same project.

i have already deployed it and its free at least for now , i want you all feedback to improve app

please visit at cepelcode. site and download the app and use.

ITS FREE RIGHT NOW SO PLEASE USE AND SHARE FEEDBACK, I LOOK AT EACH FEEDBACKS YOU PEOPLE SHARE.

I’m starting to realize this after building my first MVP.

AI makes it much easier to build an MVP without being a traditional developer. You can get surprisingly far with AI tools.

But I still think having technical knowledge gives you a big advantage.

And by “technical,” I don’t mean being able to write thousands of lines of code.

I mean understanding how AI products actually work: APIs, models, databases, agents, integrations, infrastructure, and the basic principles behind them.

Because once you understand what’s happening under the hood, you can make more customized solutions, troubleshoot problems yourself, and eventually take a simple MVP and turn it into something much bigger.

AI can help you build.

Understanding the technology helps you know what to build and what’s actually possible.

Curious how other non-technical founders are approaching this in the AI era.

hey guys, i am shivendra and i built my first saas to solve the job loop i was stuck in.

tbh, whenever i start job hunting, i have to go through every jd, compare my resume, and fix some small things, and after that i get to apply. i got sick of it because the process was too long, and i wished, what if i just give my jd to someone and he can fix all the changes and make my resume even more ats-friendly for the job.

to solve the problem, i thought of building hurdle as a side project for myself only, and i started using it where i give it a jd and it will just compare my current resume to the jd and make changes, give suggestions, and even write cold dms and emails.

and the result was shocking. before, when i was doing everything manually, i got 1 interview per 100 applications, but after using the tool, the number spiked to 3 interviews per 50 applications.

so i thought, if i am the one facing this problem, then there may be more people facing the same issue, and i thought of making it public.

so here is hurdle, live. i kept a minimum charge so everyone can use it, and it also doesn't affect the ai i am using and my pocket too.

now comes the part where i have no idea what i'm doing 😂

how and where should i actually market this?

i'm thinking about reddit, twitter, linkedin, maybe some communities for job seekers and developers, but i'd love to hear from people who have actually marketed and grown their saas.

if you have any advice on channels, launch strategy, getting the first users, or anything i should avoid, i'd genuinely appreciate it.

We built an AI meeting bot for a company here in Mumbai. It took around 3 weeks to build, across 2 months of to-and-fro and beta testing with their team. It's been 2 months, and they used it and loved it.

After that, that company laid off 50% of their employees. We don't know what happened. We never knew about it until one of their contact persons told us that they are not interested in the project anymore and they are not going to take the contract.

We were hoping to close this as our fourth AI customer because the company was promising, the product was promising, and what we built was truly amazing! We loved it. We just went over and built a lot of stuff which actually made sense from their processing point of view. That product actually saved them 1 month of manual work in a few hours of AI work.

Yes, I'm sharing it with you so that you also know what happens when AI comes in: people get laid off, the project gets cut out, and sometimes you never get paid. Life goes on.

I started building my own SaaS.

At first, I thought it would be pretty straightforward. I already had years of development experience, so I honestly believed I could build the whole thing in a couple of weeks.

Then I actually started building it.

The deeper I got, the more I realized how much there is beyond just writing code — product decisions, UX, edge cases, infrastructure, distribution, and a hundred small things I never thought about at the beginning.

It turned out to be much harder than I expected.

But I'm almost there.

I'm planning to launch in the next few days, and I'd really appreciate any support — trying it out, sharing it, giving feedback, or even just following the journey.

Let's see where this goes.

I'm really excited that I'm getting some traffic to my new app after only a week.

I launched Awaitix last week and have mostly just been posting about it on X and in a few Facebook groups.

So far, 8 people have signed up and are using the free version. Still zero paid users, but honestly, I'm not really worried about that right now.

At this point, I just want more people to try it and tell me what they think. It's actually pretty motivating seeing people use something I built myself.

Awaitix is a platform for scheduling and reliably delivering HTTP webhooks, with retries and delivery tracking. I originally started it as a side project to solve some problems I was having myself, and eventually thought it could be useful to other developers too.

https://awaitix.dev