Intermediate – Builder · Module A
Building POCs & Demos Under Time Pressure
What to cut, what to fake, and what must actually work in a 48-hour demo.
What this session covers
- Scope to the one workflow the customer actually cares about — a POC that does one thing convincingly beats one that half-does five things.
- It's fine to hardcode or mock data that isn't the point of the demo; it's not fine to fake the specific thing you're being evaluated on.
- Always have a fallback recording or screenshots — live demos fail in front of customers more often than anyone admits.
- Tell the customer explicitly what's real vs. simulated in the POC, before they assume the wrong thing and it costs you credibility later.
Worked example
A bank wants to see fraud alerts reach their Slack within 10 s. In two days you build exactly that path end to end, mock the transaction source with a script, and say up front: 'The alert pipeline is real; transactions are simulated from your sample file.' You also record a backup video in case the live demo fails.
Exercises
- Pick a product idea and write a one-page POC scope: the one workflow you'll prove, what's real, what's mocked, and what success looks like.
- Build a 2-hour POC that sends a message to a Slack or Discord channel when a webhook arrives (use webhook.site or a free incoming webhook).