Demoing to US buyers: why strong Indian products lose the demo
A playbook for demos that name pain, map the room, price risk, and leave a next path US buyers can sell inside.
The short version. Strong Indian products lose the US demo when the call proves the product but fails to prove the deal. Buyers nod, praise the craft, ask smart questions, and disappear after the screen share. Praise fades. A demo has to arm the buyer with pain, risk, money logic, peer proof, and a next path they can sell internally.
Before you start:
- A friendly US demo can still fail if the buyer cannot retell the pain, risk, price, and next path inside their company.
- Lead with the current mess, not the feature tour; strong craft lands only after the buyer sees the wound.
- Treat silent watchers as future blockers with jobs, not as polite audience members.
- End with a written path that names owners, proof, open risks, and the date that makes delay costly.
Step 1: name the buying moment, done when the buyer says the pain in their words
Start before the screen share. US buyers often keep a friendly face while they test whether this is a board-level problem, a team itch, or a founder-led science fair with sharp UI. Ask what broke this quarter, who felt it, who owns the miss, and what happens if the team keeps the same workflow.
Your best feature cannot rescue a vague buying moment. I would rather hear a buyer describe an ugly Tuesday in Salesforce, Slack, AWS, or Excel than watch a perfect tour through every tab; if that story never appears, the demo becomes entertainment. Deal drift starts there.
- Trigger event named
- Current workaround named
- Owner of pain named
- Deadline heard
- Do-nothing cost spoken
Step 2: show the before-state first, done when the spreadsheet has a wound
Open with their mess. A US buyer brings a mental spreadsheet to the demo, even when the call sits in a calendar invite with a casual title and warm chatter. Walk through the old workflow until the bad cell, broken handoff, stale report, or angry customer has a place on the screen.
Many Indian technical founders start with architecture, speed, edge cases, and a clean UI. That proves craft. Buyer needs stakes. A pre-demo script, like the one I lay out in Founder-led sales for technical founders who have never sold, keeps the screen share from becoming a museum tour.
- Old tool on screen
- Manual step exposed
- Bad handoff circled
- Lost hour made visible
Step 3: map the room, done when every watcher has a job
Gartner frames B2B buying as a group sport, and US buyers often bring quiet watchers who later veto the deal from legal, finance, security, data, or an ops seat. Names matter. Treat every silent tile as a future paragraph in an internal note, even if that person says nothing after hello.
Your champion needs words for peers, not only joy from the live call. Give legal the risk story, finance the budget logic, security the data path, and ops the rollout shape. Silence is a role. A founder who asks each person what they need to believe earns more truth than a founder who performs for the loudest fan.
- Champion
- Signer
- Blocker
- Technical reviewer
- Daily owner
Step 4: demo the path to proof, done when the buyer sees their first win
Cut the tour. A strong demo follows the buyer's early product week, from empty workspace to a result their boss would recognize without a founder narrating in the background. Screens exist to prove steps. Each click should earn the next click by showing a small win, a removed risk, a cleaner handoff, or a faster path.
McKinsey has tracked B2B buyers blending digital self-serve, remote sales, field work, and partner touchpoints; that habit carries into demos, where the buyer expects proof they can replay alone. Your live skill matters less than the artifact the buyer can forward after the call. A clip, sandbox record, ROI sheet, security one-pager, or pilot plan lets the deal move when no founder is present.
- Workflow with sample data
- Success screen
- Proof from a live run
- Risk note
- Replay asset
Step 5: price the risk early, done when delay sounds costly
Say the money part early. US buyers may enjoy a gorgeous demo and still park the deal when price, legal, data handling, service effort, or security review arrives after the applause. Late price feels like a trap. Plain ranges, pilot rules, support scope, and go-live effort belong before the buyer starts imagining a cheap win.
Seed founders often hide price until the buyer likes them. That habit creates fake speed, and fake speed poisons the pipeline math you track in The only GTM metrics that matter before Series B. Budget friction belongs in the demo, where tone, context, trade-offs, and scope can still stay human.
- Price range
- Paid pilot rule
- Security bar
- Go-live effort
What goes wrong?
Politeness fools founders. A US buyer can say this is interesting, ask for slides, praise the UI, and vanish after the call without feeling dishonest. Interest is cheap. They were testing whether your product could survive their internal hallway, legal queue, budget owner, and already full week.
Feature depth also fools strong Indian teams. Engineering pride can turn a buyer call into a release-note parade, with every API edge, dashboard filter, admin knob, latency win, and beta feature fighting for air. Buyers buy escape. No one owns the next step after a tour that tried to impress every possible persona.
Once a rep copies that loose demo, the stall becomes a system rather than one bad call, and the handoff problems I describe in Scaling out of founder-led sales without breaking your pipeline start early. Fix the script first. Better pipeline starts with a call that creates evidence and leaves praise as a side effect.
Step 6: end with a written next path, done when silence has an owner
End before the calendar ends. A clean US demo closes with who writes the internal note, who checks security, who sees pricing, who joins the next call, and what date makes the project real. Hope drifts. The buyer should leave knowing exactly what will happen while your tab disappears from their browser.
Send a crisp recap while the call is still fresh. Use the buyer's trigger, the agreed pain, the first proof, the open risks, and the exact next owner; a vague thank-you email teaches the buyer that urgency lives only on your side. Recap carries the deal. I judge a demo by the next email it makes possible.
- Pain in buyer words
- Proof shown
- Risks still open
- Owner for each task
- Date tied to cost
Common questions
Our demos go well but US deals stall afterwards. What are we doing wrong in the demo?
Likely, you are proving the product and leaving the deal unproved. A US buyer needs a story they can retell without you: current pain, business cost, risk plan, price range, and next owner. If the call ends with praise but no internal note, no named signer, no risk owner, and no date tied to cost, the demo created heat and no path.
Should Indian founders change their accent or style for US demos?
No. Buyers need clarity, pace, risk control, proof, and a path their peers can trust. Accent matters far less than structure. Strong Indian founders lose demos when they translate engineering depth into a product tour instead of a buying case, then read polite silence as interest. Calm pace, crisp pauses, plain English, and direct next steps beat borrowed American swagger.
How long should the demo be for a US buyer?
Long enough to prove the buying case and short enough to leave time for risk. The clock matters less than the shape: pain recap, narrow workflow, proof asset, price range, open risks, and owners. If the buyer spends the final stretch asking who else needs to see it, the demo has shifted from product tour to deal work.
Should I run a pilot after every good demo?
No. A pilot belongs only when both sides name the success bar, data needed, owner, price, and date. Free trials after vague praise train the buyer to browse. Paid or tightly scoped pilots work when the demo already proved pain, mapped the room, priced the risk, and exposed the risk that a short proof can remove.