[{"data":1,"prerenderedAt":109},["ShallowReactive",2],{"writing-\u002Fwriting\u002Fa-demo-has-one-job":3},{"id":4,"title":5,"author":6,"body":7,"date":95,"description":96,"extension":97,"meta":98,"navigation":99,"path":100,"seo":101,"stem":102,"tags":103,"__hash__":108},"writing\u002Fwriting\u002Fa-demo-has-one-job.md","A demo has one job: answer the buyer's real question",null,{"type":8,"value":9,"toc":86},"minimark",[10,14,17,22,25,34,38,46,49,53,61,64,68,76,79,83],[11,12,13],"p",{},"Most technical deals don't stall on features. They stall on one unanswered question - usually some version of \"will this actually work for us?\" - that nobody on the buyer's side can answer from a slide deck. My job is to find that question and answer it with something that runs.",[11,15,16],{},"Here's what that looks like in practice, across a few deals.",[18,19,21],"h2",{"id":20},"find-the-claim-then-build-only-that","Find the claim, then build only that",[11,23,24],{},"When a prospect wanted co-browsing inside Amazon Connect, the claim to prove was one sentence: an agent can start co-browse without leaving the Connect workspace. Not \"Webfuse is a great platform.\" Not a tour of every feature. One claim.",[11,26,27,28,33],{},"So the ",[29,30,32],"a",{"href":31},"\u002Fwork\u002Fwebfuse-amazon-connect-cobrowse","build"," was small on purpose - a few hundred lines, validated end to end in a real Connect instance, at roughly zero running cost. The prospect adopted the approach. A bigger demo would have answered more questions nobody asked, and taken longer to answer the one they did.",[18,35,37],{"id":36},"build-in-the-buyers-stack-for-the-person-wholl-run-it","Build in the buyer's stack, for the person who'll run it",[11,39,40,41,45],{},"A prospect had built their product on ",[29,42,44],{"href":43},"\u002Fwork\u002Fwebfuse-lovable-cobrowse-integration","Lovable"," - a React frontend and a Supabase backend, maintained by people who describe features in a chat box rather than open a terminal. A generic integration guide would have been technically correct and useless to them.",[11,47,48],{},"So the deliverable was shaped by who receives it: a reference app in their exact stack, a backend that fits the one server runtime Lovable already ships with, and a build spec they could paste straight into Lovable's chat. It ran with one command. We won the deal. The buyer didn't have to imagine the integration in their stack; they watched it run there.",[18,50,52],{"id":51},"a-good-demo-outlives-the-deal-it-was-built-for","A good demo outlives the deal it was built for",[11,54,55,56,60],{},"The ",[29,57,59],{"href":58},"\u002Fwork\u002Fwebfuse-voice-form-automation","voice agent that fills intake forms"," started as client work, and the hard part was engineering: cutting tokens per run from 66K to about 3K and fill time from three minutes to one. But the reason it matters commercially is that it now does a second job. Our sales team runs it live with prospects as leverage to close deals.",[11,62,63],{},"That's the test I now apply to anything I build for a prospect: could someone other than me show this next quarter, without me in the room?",[18,65,67],{"id":66},"after-the-deal-a-precise-answer-is-the-product","After the deal, a precise answer is the product",[11,69,70,71,75],{},"Pre-sales doesn't end at signature. A customer running Webfuse inside their own Electron wrapper hit two bugs that never appeared in Chrome. The tempting move was to guess a cause and advise. Instead I built a ",[29,72,74],{"href":73},"\u002Fwork\u002Felectron-webfuse-repro-harness","harness"," that turned every difference between the two environments into a toggle, and refused to name a cause until flipping it both reproduced and removed the symptom.",[11,77,78],{},"Both bugs were root-caused - one turned out to be a Chromium version regression no amount of reading code would have revealed. The customer stayed, and the account grew into an upsell. Trust built in support is pipeline too.",[18,80,82],{"id":81},"the-principle","The principle",[11,84,85],{},"Every one of these came down to the same move: work out the single question standing between the buyer and a yes, then build the smallest working thing that answers it - in their stack, for the person who has to run it. Impressive is optional. Answered is not.",{"title":87,"searchDepth":88,"depth":88,"links":89},"",2,[90,91,92,93,94],{"id":20,"depth":88,"text":21},{"id":36,"depth":88,"text":37},{"id":51,"depth":88,"text":52},{"id":66,"depth":88,"text":67},{"id":81,"depth":88,"text":82},"2026-10-20","What building prospect demos, reference builds and customer fixes taught me about what actually moves a technical deal - and why the smallest working thing usually beats the impressive one.","md",{},true,"\u002Fwriting\u002Fa-demo-has-one-job",{"title":5,"description":96},"writing\u002Fa-demo-has-one-job",[104,105,106,107],"Pre-sales","Solutions Architecture","Demos","Proof of Concept","MSFb6pwrjsHGqQWsJWZjeyy8B0uGpdT7CJ1Y-PbSfMQ",1792511334546]