Part 1 · Orientation
Why discovery comes first
This lesson is for new and developing Sales Engineers who lead technical discovery with large, global enterprises — where stakeholder complexity, regional differences, and hybrid environments make the first conversation hard.
Learning objective
Scope a broad customer request, uncover the relevant workflow and stakeholders, and agree on an appropriate next technical action.
The customer’s opening
“We need better visibility into security risks across the company. We have too many tools and too many findings, but no consistent way to determine what needs immediate action.”
— Priya Raman, Global CISO (fictional)
Your task
Across the next five parts you will learn a discovery method, plan your approach, run the customer meeting, and receive a performance scorecard with targeted practice.
Coach’s note
Under pressure, the instinct is to reach for a product answer early. This lesson builds the opposite habit: understand first, so you can tell what a good solution must accomplish.
Part 2 · The Sales Engineer’s role
Know what you own
Discovery works best when you know which parts of the deal are yours to lead.
The SE leads
- Technical discovery and technical fit
- Architecture discussion
- Tailored demonstrations
- Technical validation
- Proof-of-value success criteria
The SE does not primarily own
- Pricing
- Contract negotiation
- Legal approval
- Post-sale implementation
Knowledge check
Choose the best answer, then check it.
Part 3 · The SCOPE framework
Five moves of good discovery
A simple order of operations. Expand each move to see what to listen for, then match a question to the move it serves.
Match the question to its SCOPE move
Pick the letter each question is really doing the work of, then submit.
Part 4 · Plan your discovery
Build your approach
The account
Apex Manufacturing Global — a fictional company with 45,000 employees across 24 countries. A recent audit found inconsistent asset ownership and uneven remediation tracking across regions. The CISO has a board risk update in four months.
“We have too many security tools and too many findings, but we cannot consistently determine what needs immediate action.”
Coach’s prompt
Before you pick questions, name what you think might really be going on.
Part 5 · The customer meeting
Run the conversation
You are the Sales Engineer. Ask one question per turn. The room responds to what you actually ask. Aim to cover the full SCOPE picture within six turns.
Part 6 · Performance & next steps
Your discovery scorecard
Targeted retry
Write how you would ask this in your own words, in the flow of a real meeting.
Lesson complete
- Discovery is a sequence: understand the spark, context, workflow, pain, and evidence before proposing anything.
- The SE’s credibility comes from restraint — earning the demo by understanding the problem first.
- A strong meeting ends on an agreed next technical action and a shared definition of success.