Building in Front of the Customer
In customer-facing prototyping, every stuck moment, every wrong guess, happens in front of the person you are trying to convince. That changes how you work — smaller visible steps, more narration, and a plan for what to show even if the main thing breaks.
What holds up under that pressure
- Narrate what you are doing and why, in plain words, as you do it.
- Work in small visible steps so a stuck point is a pause, not a dead end.
- Always have a fallback — a cached result or an earlier working version — ready to show.
Why narration matters more than speedA customer watching silent typing cannot tell a brief pause from a serious problem. Narrating turns a stuck moment into a visible part of the process instead of a moment of doubt about whether the whole thing is broken.
Do this in 60 secondsRecord yourself (audio is enough) building something small for 15 minutes, narrating out loud the whole time as if someone non-technical were watching. Listen back afterward and mark every silent stretch longer than ten seconds — that is exactly where a real customer would start to worry.
Today’s AI angleShowing an AI agent live is riskier than showing regular code, because a model can answer confidently and wrong in front of the customer — so the fallback plan here matters even more than usual.
Interview prepSomething breaks while you are live-coding in front of a customer. What do you do in that moment? I say plainly what broke, in one sentence, without panic, and switch to the fallback I prepared before the session — a cached result or an earlier working version. The mistake most engineers make is going silent to debug live; narrating the pivot keeps the customer's trust even when the specific thing fails.