Seeking founders whose vibe-coded product they can't touch

He had 200 paying users. Solid retention. Real revenue.

I asked him how his authentication worked.

He said he wasn't sure.

Not "I'll need to check the docs." Not "my co-founder handles that." He genuinely didn't know, because he had never written a line of it. Cursor had. He accepted whatever it gave him and moved on to the next feature.

The product worked. Until it didn't.

A user with enterprise data hit an edge case in session handling. The founder spent 3 days trying to fix output he couldn't read, in a codebase with no memory of why it was built the way it was.

This is the part nobody talks about with vibe coding.

It's not that the tools are bad. It's that they produce working software with no owner. The founder is a user of the product, not the builder of it.

That risk stays invisible until something external forces the question. An investor. A security incident. A new hire who asks why something works the way it does.

At that point the answer is almost always the same: I don't know.

This is exactly the situation we work with. If you're sitting on a vibe-coded product that users love but you can't confidently touch, send me one line about what you're building: hi.hamza.dev@gmail.com

I'll read it personally and let you know if a call makes sense.

Has anyone else hit this — either as the founder in that position, or watching it happen to someone building next to you?