Practice recovering when a technical evaluator disengages mid-demo. Consultative selling vs. feature dumps — with modern discovery discipline.
Lead Integration Engineer
Hidden agenda: Burned by last vendor’s ‘REST API’ that needed professional services for every field
Style: Goes quiet when skeptical; won’t interrupt politely
Ops Director
Style: Wants to keep demo moving; unaware of Taylor’s concern
You play Alex Rivera. Read their lines aloud or have a partner play the buyer.
Second meeting — demo for IT and ops. Discovery identified reporting pain; technical lead (Taylor) was enthusiastic in call one.
Stakes: Taylor’s recommendation drives shortlist. Silent disengagement usually means hidden blocker or misaligned demo.
Company: Retail ops buyer (~400 stores). Custom ERP, brittle integrations, small IT team.
Re-engage the technical buyer, clarify integration requirements, and avoid a premature ‘send documentation’ ending.
Read through each act, then work the decision points below. Coaching notes appear after annotated lines.
Alex Rivera
Here’s our open API — pre-built connectors for major ERPs, webhooks for custom flows…
Typing on second monitor, camera off briefly
Taylor Brooks · Lead Integration Engineer
Mm-hmm.
Jamie Wu · Ops Director
Can we jump to the district rollup view? That’s what I need for Q4.
Alex Rivera
Taylor — I’m going to pause the screen share. What’s going through your mind on the integration piece?
Taylor Brooks · Lead Integration Engineer
…Honestly? Every vendor shows an API slide. Last one needed three PS sprints per field. I’m not doing that again.
Jamie Wu · Ops Director
I didn’t know that was still an issue.
Alex Rivera
So maintainability and on-call load matter more than connector count. What broke on-call last time — failure rate, alert noise, or change windows?
Taylor Brooks · Lead Integration Engineer
Alert noise and no sandbox parity. We found out in production.
Alex Rivera
If we mapped your ERP sandbox with our SE for 45 minutes — no slide deck — would that be worth more than a PDF tonight?
Taylor Brooks · Lead Integration Engineer
If your SE actually knows retail ERP, yes. Thursday.
Jamie Wu · Ops Director
I’ll join for the rollup use case after your first 30 minutes.
Choose a path before reading the debrief. In pair practice, pause and discuss which option you would take.
Decision 1 of 2
Continue demo for Jamie — Taylor can read docs later
RiskyWhy: Loses technical win; Taylor becomes silent blocker.
Pause and ask what they’re thinking about integration
RecommendedWhy: Surfaces hidden objection; consultative recovery.
Defend API maturity with customer logos for five minutes
RiskyWhy: Feature dump without addressing maintainability fear.
Decision 2 of 2
Send API PDF tonight
RiskyWhy: Passive; doesn’t prove sandbox parity claim.
Book technical working session on their sandbox
RecommendedWhy: Buyer enablement with proof; engages Taylor as co-builder.
Offer professional services credits
AcceptableWhy: May help but doesn’t solve trust — use after technical validation, not before.
Continue practicing related situations.
Your champion booked a demo for six people. Three minutes in, Security says no API access — and the economic buyer goes quiet.
Jordan Chen has twelve minutes, a failed vendor rollout last year, and zero patience for slides. Can you earn a second conversation without pitching too early?
Frameworks and research cited in this scenario.
Understanding modern discovery call framework helps sellers align with how buyers actually think, feel, and decide — not how slide decks assume they do.
Both approaches reject product-pushing, yet they differ in how problems are diagnosed, value is framed, and deals are won in complex B2B environments.
SPIN Selling revolutionized consultative sales by proving that the questions you ask matter more than the pitch you deliver.
Understanding buyer enablement selling helps sellers align with how buyers actually think, feel, and decide — not how slide decks assume they do.
