Why
Demos get promised too early
Most demos are delivered too early, with minimal knowledge of the prospect's current state. The result is a long demo through everything the vendor finds cool to show, or thinks the prospect should see. That's not what buyers want. They know the pain points in their processes, but struggle to pin them down in a project brief.
The Operational Walkthrough is a discovery technique rooted in the prospect's current state. It surfaces what needs fixing, both for the prospect and the vendor.
What
A visual whiteboarding technique with real downstream value
A visual whiteboarding technique that produces a clear list of problems, priorities, and focus areas for the demo. No more guessing what a prospect needs to see.
The AE and SE may still choose to show process improvements beyond what was surfaced, but never just because Product shipped something new.
Done well, an Operational Walkthrough delivers 3 things:
- Surfaces the magnitude of the problem, for both the buyer and the vendor, and gives both a starting point to quantify pains and gains
- Identifies the parts of the demo that matter most, so prospects stop yawning through irrelevant features
- Opens up natural paths to multi-thread across the buying group
How
The Five-Phase Framework
Follow these five phases in sequence. Each one builds on the last — from preparation and observation through to pain point validation and next steps.
📋 Phase 1: Pre-Interview Prep
✓ Research
Company background, industry, prior discovery (SDR/AE/SE notes)
✓ Schedule
Book 60–90 min · Send clear agenda · Get right stakeholders
✓ Tech Setup
Recording tools ready · Note-taking system · Screen share confirmed
💬 Phase 2: Opening & Context
Opening Script
"Today, I'd love for you to show me how your team(s) work. Could you walk me through a typical [process] from start to finish?"
Set expectations
Get permission to record
Have them share their screen
YOU observe, THEY drive
👁 Phase 3: The Walkthrough
Key Questions to Ask
What to Capture
"What happens next?"
🔧 Tools & systems used
"Who else is involved at this step?"
✋ Manual steps
"How do you know when this is done?"
🔄 Handoffs between teams
"Where does this information come from?"
⏱ Wait times & delays
"What do you do if X goes wrong?"
📋 Data re-entry
"Are there dependencies on other teams?"
😤 Frustrations (verbal & body language)
⚠️ Phase 4: Pain Point Deep Dive
"You mentioned [pain point] – tell me more about that"
"How often does this happen?"
"What's the impact when this goes wrong?"
"What other ways have you tried before?"
"How long does it take today? What would 'ideal' look like?"
"Who else feels this pain?"
✅ Phase 5: Wrap-up & Next Steps
Summarize
Recap what you learned. Confirm you understood correctly.
Validate Pain Points
"So the top challenges are: 1) ... 2) ... 3) ... Did I get that right?"
Next Steps
Schedule follow-up · Ask who else to include · Set expectations
💡 Good Practices
Don't Pitch
Resist the urge to jump in with solutions. This is pure discovery.
Use Their Language
Take notes on exact terms they use. Mirror this in proposals.
Watch for Gaps
Note what they DON'T mention – often reveals blind spots.
Ask "Why"
Understand the reasoning behind their current approach.
Emotional Cues
Sighs, pauses, frustration – these signal real pain points.
Take Screenshots
Capture their actual screens (with permission) for reference.
🚩 Red Flags to Watch For
"We usually just use Excel for this"
Lots of copy-paste between systems
"I have to check with [person]"
"This part takes forever"
Using screenshots/email as handoff
No single source of truth
Multiple versions of same doc
"We built a workaround..."
📝 Post-Interview Actions
Within 2 hours
Document process flow while fresh
Within 24 hours
Send summary + thank you to prospect
Tag in CRM
Log key insights, tools, pain points, stakeholders
Identify
Top 3–5 pain points & map to your solution
↗ Success Metrics
60–90
minutes ideal duration
5–7
process steps documented
3–5
pain points identified
