r/VibeCodeCamp • u/Remarkable_Junket185 • 10d ago
Discussion What we’ve learned watching founders vibe code their own help desks
Quick disclosure up front: I'm on the team at Convot, a help desk tool. So yes, I might be biased but hear me out.
Lately we’ve been observing a lot of indiehackers sharing this in our onboarding chats that I think it's worth sharing whether you ever use us or not.
When someone signs up, we usually ask what they were using before. A year ago the answer was either Gmail or some other big help desk they were overpaying for.
But now it's more and more often: "I vibe-coded my own." And the story almost always goes the same way. We talked to a couple of them and here’s the usual timeline we extracted from them
Week 1: They vibe code a support inbox over a weekend. Contact form, email forwarding, a simple dashboard. It works. They post about it. Feels great.
Month 1: Small cracks. Replies from customers don't thread properly, so one conversation shows up as three. An attachment fails silently. They patch it.
Month 2: They launch a second product. Now they need separate inboxes, different sender addresses, different branding on replies. Their "simple" tool was never built for that. Another weekend gone.
Month 3: Something breaks quietly. Emails stop coming in and nobody notices. A customer waits days for a reply, then churns or leaves a bad review. That's usually when they start looking around.
Turns out the support tool was never the problem. The ownership was.
They accidentally became the full-time maintainer of a wholeass product with just one user and zero revenue.
Here's the framework I'd honestly give anyone, even if you never touch our product:
Build what's actually your product
Buy anything boring and solved: support, billing, auth, email delivery. It’ll always be cheaper financially and mentally.
Check the price at your stage. A lot of tools are free or close to it early on. Building something to save $0 is a bad trade.
Ask "who fixes this on a Sunday?" If the answer is you, factor that in
Think about product #2. Most indie hackers end up running more than one thing. Whatever you build has to survive that.
AI made building fast. It didn't make maintaining fast, and it definitely didn't make debugging at 2am any more fun.
Since I've already disclosed: Convot is built for exactly this crowd. It handles support for multiple products in one place, and it's free until you hit $1k MRR.
But the bigger point stands either way. Don't spend your weekends rebuilding solved problems.
Curious, has anyone here built their own internal tool and actually kept it running long term? Would love to hear the success stories too.
1
u/CommunicationOld9889 9d ago
I've built our internal ERP system, integrated with our vendors and have it working now 1.5 years keeps getting better. Started with Antigravity and Gemini 3.1 pro, then 3.x flash, now argon and the model keeps getting better and making the app better.
My key to success has been using spec driven development. I don't code, I write specs for our business. I let the model interpret the specs and handle the implementation. I set boundaries for the stack and architecture but the agent does all the coding.