u/Alive-Cake-3045

Twelve months ago I started tracking what happens to vibe coded projects after the initial launch excitement fades. The pattern is consistent enough that I wanted to hear if others are seeing the same thing.

The first three months feel fine. Features ship fast, the client is happy, everyone looks productive. Then something needs to change. Not a new feature, just a modification to something existing. And that is where it gets uncomfortable.

Nobody can explain why a specific decision was made. The code works but the reasoning is gone. There are dependencies that were added because the model suggested them, not because anyone evaluated them. Patterns are inconsistent across files because different prompts produced different styles on different days.

The developer who built it can read the code but cannot confidently change it without breaking something unexpected. The test coverage that exists was also generated and may not actually be testing the right things.

I am not saying this always happens. I have seen vibe coded projects that held up well because the developer reviewed everything carefully and maintained discipline around the output.

But I have also seen projects from 18 months ago that are now quietly being rewritten because the maintenance cost exceeded the original build cost faster than anyone expected.

If you have actually maintained a vibe coded code-base through real production use, what did 12 months in actually look like? Was the code salvageable or did you end up starting over?

Curious how teams are managing inference costs at scale. At what point did token spend become a line item someone actually owns, and what changed when it did?

Most founders only ask about price and timelines when they meet a bespoke software developer for the first time.

Those are the wrong questions to lead with.

Ask how they handle scope changes mid-project. Ask what happens if a key developer leaves their team. Ask whether they have worked with businesses at your stage of growth before, and what went wrong in those engagements.

Ask who owns the IP once the work is done. Ask what their process looks like in the first 30 days. Ask how they communicate when something is behind.

The answers to those questions tell you more than any portfolio ever will.

Getting this decision wrong costs more than money. It costs months.