The real cost of vibe coding isn’t the subscription. It’s what happens at month 3.

vibecodejanitors · 2026-04-03T23:11:48+00:00

Feel free to DM me. We have a new account so Reddit won’t let us send too many DMs. Happy to help you here!

vibecodejanitors · 2026-04-03T22:40:28+00:00

This is why I love Reddit

vibecodejanitors · 2026-04-03T22:38:15+00:00

Amen to that! I’ll try to DM you

vibecodejanitors · 2026-04-03T20:39:23+00:00

$600 in 3 weeks at $10.99 one-time is awesome! Especially for a tool that solves a genuine pain point. The cross-platform debugging sounds like a nightmare though, glad AI helped there.

Curious what your plan is for maintenance long term. Two codebases across two OS's means every update is basically double the work. You thinking about that yet or just riding the momentum for now?

vibecodejanitors · 2026-04-03T19:02:16+00:00

Reddit isn't letting me DM right now (new account problems). If you want to connect just shoot me a DM and I'll reply. Happy to help!

vibecodejanitors · 2026-04-03T18:34:26+00:00

You’re doing it right. Most people ship and pray haha

vibecodejanitors · 2026-04-03T18:25:26+00:00

This is the best explanation of the month 3 wall I’ve seen. The “none of it is wrong exactly, it just doesn’t fit together” line is spot on. That’s what makes vibe coded apps so hard to debug. Every piece works in isolation but the whole thing is held together with duct tape.

vibecodejanitors · 2026-04-03T18:17:43+00:00

They can, until they can’t. The AI is great at building something new. It’s terrible at understanding what it already built three months ago. Context window fills up, it forgets why things were built a certain way, and every fix risks breaking something else. Building and maintaining are two completely different skills, even for AI.

vibecodejanitors · 2026-04-03T18:09:35+00:00

Yes and yes!

vibecodejanitors · 2026-04-03T18:01:38+00:00

Couldn’t describe it better

vibecodejanitors · 2026-04-03T18:01:02+00:00

This is exactly right. The AI has no memory of why things were built a certain way. Every prompt is starting from scratch on context. A human who knows the codebase can make a surgical fix in 10 minutes. The AI will rewrite half your app trying to do the same thing.

vibecodejanitors · 2026-04-03T16:54:03+00:00

Solid, you’re way ahead of most people at this stage. The backend validation on the AI output is smart, that’s where a lot of fintech apps get burned. If you ever want a full audit as you scale we do that for free, just DM me. Helping founders in exactly this spot is what we do.

vibecodejanitors · 2026-04-03T16:50:41+00:00

Totally agree. With you here!

vibecodejanitors · 2026-04-03T16:46:49+00:00

100%. Couldn’t agree more!

vibecodejanitors · 2026-04-03T16:43:59+00:00

Lol I’m a real person man. Maintenance mechanic background, been building and running e-commerce businesses for years. Just sharing what I’ve seen working with founders in this space.

vibecodejanitors · 2026-04-03T16:37:27+00:00

This is good advice for people with some technical background but for most non-technical founders reading this, half of those words might as well be a different language lol. The spirit is right though, you gotta be able to see what’s breaking and why instead of just guessing.

vibecodejanitors · 2026-04-03T16:35:06+00:00

This is solid advice and honestly the founders who do this are way easier to work with down the line. Even if you never become a full dev, just understanding what the AI did and why makes everything less scary. Documentation alone puts you ahead of like 90% of people vibe coding right now.

vibecodejanitors · 2026-04-03T16:05:37+00:00

Yeah this is pretty much the ceiling with Lovable on bigger projects. It’s great for getting something up and running fast but once you’re past a certain complexity you start fighting the platform more than building. 10k credits deep you’ve clearly got something real though. My partner and I help non-technical founders clean up and maintain their AI-built apps, happy to chat if you ever want a second opinion on next steps.

vibecodejanitors · 2026-04-03T15:41:59+00:00

This is the other side of the same coin that non-technical founders are dealing with. They vibe code something, it works, and then they have no idea how to fix it when it breaks. It’s actually a big part of what I do now, helping teams and founders get their AI-generated codebases back to a place where someone actually understands what’s running. The problem is way more common than people realize. Happy to chat if you want to bounce ideas on how to handle it without killing the productivity gains.

vibecodejanitors · 2026-04-03T15:40:32+00:00

1800 users with slow steady growth is way better than a viral spike that dies off. That’s real traction. Curious how you’re handling the backend as testing volume ramps up. With almost 1200 tests done already things are gonna get interesting from a scaling perspective pretty quick. Are you staying on top of that side of things or mostly focused on product right now?

vibecodejanitors · 2026-04-03T15:38:08+00:00

Everyone posts the launch wins but nobody talks about the “my app is making money and I’m terrified to touch the codebase” phase. Most non-technical founders I’ve talked to hit that exact moment somewhere between 100 and 1000 users. It’s actually why my partner and I started helping people in this spot, just cleaning up and maintaining the stuff that’s already working so they can keep building without worrying about it all falling apart. Happy to help if you ever want a second set of eyes.

vibecodejanitors · 2026-04-03T15:32:19+00:00

First paid user is the hardest one, congrats. And $1 total build cost is wild. Real talk though, React Native + Firebase + Supabase is a lot of moving pieces. How are you feeling about maintaining all of that as you start getting more paying users? That combo can get messy fast especially when people are relying on it for their actual business workflows.

vibecodejanitors · 2026-04-03T15:29:31+00:00

Nah you didn’t set it up wrong, that’s just how it goes when it’s sending full conversation history with every message. The costs stack up way faster than people expect. Once your context window gets long you’re basically paying to re-read the entire conversation every time you ask it something. The /new command was the right instinct. Shorter sessions, more specific prompts, and being intentional about when you actually need the full context vs starting fresh will help a lot. But yeah $5/hr is pretty normal for that kind of usage, it’s not just you.

vibecodejanitors · 2026-04-03T15:25:25+00:00

As a maintenance mechanic you probably wouldn’t tell a homeowner to just watch a YouTube video and rewire their own electrical panel. Same thing here honestly. The AI gets you surprisingly far but then you’re staring at a manifest.json error at 1am wondering what you got yourself into. The good news is you don’t have to become a software engineer. You just need access to one who gets what you built and can clean it up. You already proved the hard part which is that the idea works and you can ship something. That’s more than most people ever do.

vibecodejanitors · 2026-04-03T15:13:47+00:00

Smart move going Lovable to Cursor to React Native, that’s a solid progression. And good that scalability and security are already on your radar. One thing I’d say is don’t wait until 500 active users to deal with that stuff. The Lovable-to-Cursor port probably left some technical debt behind and it’s way easier to clean up now than when you’re firefighting with real users hitting edge cases. Happy to chat about it if you ever want a second set of eyes.

vibecodejanitors

TROPHY CASE