Resources›Operational Walkthrough
Discovery FrameworkAI Variant

Find where AI actually fits
in your prospect's workflow.

Stop demoing AI features nobody asked for.

A 5-phase structured discovery framework for AEs and SEs - built around the buyer's process, not your feature list.

Read time 10 minFor AEs & SEsUse it pre-demo
60min
Ideal duration
5–7
Process steps
3
Pain points
80%+
Prospect talk time
5 phases
1Context Setting2Current State Map3Process Deep Dive4Pain Point Deep Dive5Wrap-up & Next Steps
Phase 1

Context Setting

10 min

Understand who you are talking to, what they own, and which process is worth mapping in detail. You are choosing the right thread to pull - not pulling all of them.

Questions to ask
Walk me through what your team is responsible for - end to end.
What does a typical week look like for someone in your role?
Which process would have the highest impact if it ran faster or more consistently?
How many people are involved in this process? Across which teams?
Where does the process start - what triggers it?
Bring with you
✓Prior discovery notes✓CRM activity log✓Org chart / LinkedIn research✓Any RFP already shared
Phase 2

Current State Map

15 min

Build a shared, accurate picture of how the work flows today - step by step, system by system. This map becomes the foundation for every AI conversation that follows.

Questions to ask
Walk me through exactly what happens from trigger to output.
What does the handoff look like between teams at that point?
What systems or tools are involved at each step?
Where do things slow down - or stop - most often?
Is this the same every time, or does it vary by case?
Bring with you
✓Whiteboarding software - Miro or FigJam✓Blank process template✓Screen share ready to sketch in real time
Phase 3

Process Deep Dive

20 min

Surface the AI signal data hidden inside each process step - volume, consistency, input quality, and decision complexity. What looks like a workflow conversation is actually a readiness assessment.

The conversation
What happens next?
Who else is involved at this step?
How often does this happen - and at what volume?
Where does this information come from? How consistent is it?
Does this step require human judgment, or is it mostly rule-based?
Are there dependencies on other teams?
What would you do if this constraint didn’t exist at all?
What to capture vs. what to ask

Listen for

  • What happens next?
  • Who else is involved at this step?
  • How often does this happen - and at what volume?
  • Where does this information come from? How consistent is it?

Write down

  • Tools and systems used at each step
  • Manual, repetitive steps - high-volume tasks are AI candidates
  • Handoffs between teams - where data changes hands
  • Wait times and delays - especially approval or review bottlenecks
  • Data re-entry and format inconsistency - signals poor AI readiness
  • Frustrations - around speed, scale, or consistency
  • Tasks done the same way every time - strongest AI signal
Bring with you
✓The map built in Phase 2✓AI readiness scoring framework✓Volume / frequency notes template
Phase 4

Pain Point Deep Dive

10 min

Turn a surface-level frustration into a quantified business problem. You need frequency, impact, and stakeholder breadth before you can build a credible business case or a focused demo.

Questions to ask
You mentioned [pain point] - tell me more about that.
How often does this happen? At what volume?
What’s the impact when this goes wrong?
What other approaches have you tried before?
How long does it take today? What would ideal look like?
Who else feels this pain?
Is the input consistent enough to automate, or does it vary too much?
If this step happened instantly and at any scale - what would that unlock?
Who in your organization would need to support a change to how this works?
Bring with you
✓Phase 3 notes with flagged steps✓Value hypothesis template✓Deal qualification scorecard
Phase 5

Wrap-up & Next Steps

5 min

Leave the prospect feeling heard, and leave yourself with a clear brief. A confirmed summary prevents misalignment in the demo stage. A committed next step prevents the deal from going quiet.

Close the loop
01

Summarize

Recap what you learned. Confirm you understood correctly before proposing anything.

02

Validate pain points

So the top challenges are: 1) … 2) … 3) … Did I get that right?

03

Next steps

Schedule follow-up. Ask who else to include. Set expectations on what comes next.

Bring with you
✓Summary email template✓Demo brief template
A demo built before a walkthrough is a best guess.
A demo built after a walkthrough is a response to a problem
the prospect has already told you matters.
The point of view
I used to walk in with a generic AI demo. After three deals with this framework, demo prep dropped in half and our close rate on AI-led deals doubled. Phase 3 catches the deals that aren’t really ready - before we burn a month on them.
Sarah ChenSenior Account Executive, Northwind Logistics
What to look for

AI Readiness signals & risks

Sort what you hear into two columns as you go. By the end of the call, you should know which signal each step belongs to - and whether this is a deal that's ready for a demo.

+Strong signalGreen-light a demo

Strong AI candidate

High volume, consistent inputs, rule-based steps, clear output. The process runs the same way every time.

Transformation opportunity

Something they can’t do at all today - scale, speed, or language coverage - not just doing the same thing faster.

!Risk signalPause before demoing

Weak AI candidate

Low frequency, high variability, heavy editorial judgment, or data that is inconsistent and unstructured.

Data readiness risk

Inconsistent taxonomy, unstructured content, or data spread across disconnected systems. AI will not fix a messy foundation.

Change readiness risk

Strong process ownership by one person, previous failed automation attempts, or no executive sponsor for change.

Integration risk

Key data lives in systems outside the buyer’s control - procurement, legal, or IT approval likely required.

In-room habits

Good practices

The walkthrough is a buyer-centric conversation. These habits keep you on that side of the table - and out of demo-mode reflexes.

01

Don’t pitch AI

Resist the urge to map every pain point to an AI feature. Some processes aren’t ready. Say so.

02

Use their language

They won’t say “automate.” Listen for “faster,” “consistent,” “scale,” “always manual.” That’s where AI fits.

03

Watch for gaps

Note what they don’t mention. A team not talking about scale often hasn’t imagined what’s possible.

04

Ask “What if”

“What would you do if this step happened instantly at any scale?” surfaces transformation, not just efficiency.

05

Read emotional cues

Sighs and pauses around repetitive tasks signal AI opportunity. Hesitation around change signals adoption risk.

06

Qualify the use-case

Volume + consistency + clear output = strong AI fit. One of those missing = a conversation before a demo.

The walkthrough changed how my engineering team prepares for technical demos. We’re not demoing features anymore - we’re showing prospects their own process with AI doing the parts they told us were broken.
Marcus RiveraPrincipal Sales Engineer, Helios Health
Overheard in discovery

Red flags worth pausing for.

If you hear any of these, slow down. Each one warrants a conversation before you build a single demo slide.

We usually just use Excel for this
Lots of copy-paste between systems
I have to check with [person] first
This part takes forever
The data is never quite consistent
Every case is a bit different
We’d need IT to sign off on any changes
We tried automating this before…
After the call

Post-interview actions

The walkthrough is only valuable if you translate it. Four moves between the call and the demo.

01Within 2 hours

Document the flow

Capture the process map and flag each step as strong, weak, or unclear AI candidate.

02Within 24 hours

Send the summary

Thank you note with your initial read on where AI fits - and, importantly, where it doesn’t.

03Same day

Tag in CRM

Log AI readiness signals: volume, data quality, integration constraints, change readiness.

04Before the demo

Build the demo brief

Map the 2–3 strongest AI use-cases to specific capabilities. That’s your demo. Nothing else.

Phase 4 is where I close every deal now. Once you’ve quantified the pain and got the prospect to commit to who else needs to be in the room, the demo writes itself.
Priya PatelEnterprise AE, Meridian Software

Want to run this with your team?

Book a diagnostic conversation.

60 minutes. We'll walk through one live deal and find the AI fit - or the reason a demo would be premature.

What you'll leave with

  • A scored process map of one live deal
  • 2–3 AI use-cases worth demoing - and the ones that aren't
  • A demo brief your team can build to
  • A list of the readiness risks to flag in CRM
Loading booking calendar...