5 Things Every Funnel Builder Needs to Know When a Client App Breaks

Everybody is building apps right now.

People are vibe-coding their funnels. Your clients are vibe-coding apps. And somewhere in that mix, you became the "tech person".. the one they call when something breaks.

The problem is nobody taught you what to actually do when it does.

So when the call comes in.. the app is down, the client is waiting, you're the expert.. something happens in your body before your brain even catches up. A shot of fear. The kind that floods your chest and makes your hands move faster than your thinking. You open a new tab. You start Googling. You ask your LLM. And the responses come back in a language that doesn't quite connect to anything you already know.. so you keep going, deeper into pathways that don't resolve, until eventually you pass it off or quietly decide it's not your problem to solve.

Except it is. They come to you to handle this stuff.. and they're going to keep coming. The time to get good at this is now.

Here's what I've found after years inside enterprise software and months watching funnel builders navigate this exact situation: you don't need to become a developer. You need five areas of fluency.. enough to understand what's happening and have a productive conversation with your LLM about it.

Identity & Access. Authentication and authorization. Who can log in. What they can do once they're in. When an app breaks in a confusing way after a user does something.. this is usually the first place to look.

Secrets & Environment. API keys, credentials, sensitive data. These never belong in client-side code. Ever. A lot of vibe-coded apps get this wrong by default. Knowing this one thing can tell you immediately whether an app has a structural problem worth flagging.

Structure & Patterns. MVC. Separation of concerns. The difference between an app that holds under load and one that buckles when success hits. You don't need to memorize this.. you need enough of a mental model to ask your LLM the right question.

Source Control. Git. The safety net. How you read what someone else built, trace the history, and make a fix without accidentally destroying everything else. Clients show up with apps they didn't build and can't explain.. Git is how you start to understand what you actually have.

Observability & Error Handling. Knowing when something breaks before the client does. Logs, error states, monitoring. This is the area that turns you from reactive to ahead of it.

Armed with these five areas, an LLM, and some persistence.. you can figure out pretty much anything a client drops in your lap.

The next time that call comes in, you won't freeze. You'll know which area to check first. You'll know what question to bring to your LLM. You'll move through the problem instead of around it.. and the fear that used to flood your chest when a client said "something's broken" starts to shrink, because you've been in there before and you found your way out.

🚀

- James

9 comments