There s a point where products stop being fully understandable.

Too many features
Too many dependencies
Too much history

And decisions start getting made with partial context.

For us, it started from something frustrating: creating content felt very annoying and time-consuming. We tried the classic way: scripting, memorizing, filming, editing. But none of it felt authentic. And honestly, it was eating time we needed to focus on other things.

At the same time, we kept reading the same advice everywhere:
"founders should build in public and create content consistently". Easy to say but harder to do in reality. So instead of forcing ourselves to create content from scratch, we tried something simple: recording our own calls and using those moments as content.

AI is incredibly good, I d even say almost perfect.

And for many people, that uniformity of perfect templates is starting to feel annoying.

We thought we were ready.

Bigger deals. Fewer customers. Better margins. That was the dream.

So we built enterprise features. SSO. Advanced permissions. Audit logs. A whole new pricing tier starting at $2,000/month.

We spent 6 months. Three engineers. One dedicated product manager. Endless meetings about "enterprise readiness."

Let me start from the creator s perspective:
I personally don t have a product (apart from hiring people for creative work or offering personal consultations).

But as a creator, I constantly share content, insights, and information, value that helps me build trust (for free). Based on that perceived expertise, people eventually decide to work with me (a paid service).

I keep seeing the same pattern across early-stage teams:

the MVP works until it really doesn t.

For many founders, the hardest part isn t getting something online
it s everything that comes after:
infra that cracks under real users
code that no dev wants to touch
rewriting the whole stack
AI-built projects no one can maintain
the moment you realize your prototype isn t a product

I keep seeing the same pattern across early-stage teams:

the MVP works until it really doesn t.

For many founders, the hardest part isn t getting something online
it s everything that comes after:
infra that cracks under real users
code that no dev wants to touch
rewriting the whole stack
AI-built projects no one can maintain
the moment you realize your prototype isn t a product

Hello everyone, Sumit here from the Himalayas. I hope everyone is having a relaxed weekend. My workflow with vibe coding has settled pretty well as I get more and more time out of desk while Claude Code builds the software.
I wanted to offer any assistance to fellow founders. I have been vibe coding full-time for a little over 4 weeks. Wrote about it here. Please share your tools, or workflow and in particular what is not working for you. What is frustrating you in building software with vibe coding?