Comprehensive Sales Engineering playbook based on John Care's "Mastering Technical Sales: The Sales Engineer's Handbook" (4th Edition). TRIGGER WHENEVER the user mentions ANY of these contexts — even casually or implicitly: - Sales engineering / presales / solutions consulting / technical sales - Preparing for a customer demo, presentation, whiteboard, or proof-of-concept - Discovery calls, qualification, lead scoring (BANT, MEDDIC, etc.) - Handling objections, answering technical questions, competitive positioning - Building trust with customers, becoming a trusted advisor - RFP / RFI responses — strategy, scoring, go/no-go - Crafting pitches, value propositions, messaging (FAB, RM+3KP, ROI) - Executive engagement, C-level presentations, business value conversations - Partner selling, channel enablement, joint selling - Time management for sales engineers, managing multiple opportunities - SE career development, onboarding, ramping, interview prep - Storytelling in sales, using customer references - Demo strategy, demo GPS, dash-to-demo problems - Negotiation support, post-sales handoff - Cloud / SaaS selling, consumption models, monthly recurring revenue - Competitive tactics, win/loss analysis - Remote presentations and virtual selling - Whiteboarding techniques, visual selling - Personal branding for technical professionals This skill is a comprehensive reference. Use it to give practical, actionable advice drawn from the book's frameworks. Do not just summarize — APPLY the relevant framework to the user's specific situation.

Mastering Technical Sales — Sales Engineer's Playbook

Based on Mastering Technical Sales: The Sales Engineer's Handbook, 4th Edition by John Care (Artech House, 2022).

Why This Skill Exists

The Sales Engineer (SE) is the bridge between business/commercial interests and technical details. Unlike quota-carrying salespeople, the SE's power comes from trust, technical credibility, and the ability to translate between languages (Techie, BizTalk, ExecSpeak). This skill gives you the frameworks to excel in every phase of the technical sale.

The book's core promise: apply these techniques → better win rate, higher customer satisfaction, hitting revenue targets, greater job satisfaction.

1. The Four SE Roles

An SE is a blend of four distinct personas. The best SEs can morph between them fluidly:

Role	What It Means	When to Activate
Technical Engineer	Know enough to sound knowledgeable. Translate tech ↔ business. "A mile wide and an inch deep."	In discovery, demos, technical discussions
Salesperson	You have an obligation to sell. But sell indirectly — be the catalyst, not the closer. "Do no harm."	During qualification, positioning, competitive situations
Trusted Advisor & Consultant	Understand the customer personally and professionally. Establish a "golden future." Use a gravitational close (everything naturally comes together) not a hard close.	Throughout the entire lifecycle
Storyteller / Explainer	Multilingual: switch between Techie, BizTalk, ExecSpeak. Make the customer say "I see what you mean."	Presentations, demos, whiteboarding, all customer interactions

Key insight: You're a fixer and pleaser — you solve problems and make people happy. If neither motivates you, this isn't the right role.

2. The Sales Process (10 Stages)

The SE has different activity levels across stages:

Stage	SE Activity Level	Key SE Task
1. Market Definition	Relax	Provide input if add-on product
2. Marketing Campaigns	Engage where appropriate	Attend events, build partner relationships
3. Lead Qualification	Validate technical environment	BANT/MEDDIC check
4. RFP	Heavy lifting	Answer hundreds of questions
5. Discovery & First Engagement	Heavy activity	This is where deals are won or lost
6. Present, Demonstrate, Propose	Heavy activity	Frame proposal as uniquely qualified
7. POC / Trial	Potentially high	Map success criteria rigorously
8. Negotiation / Close	Relax, do no harm	Maintain relationships
9. Post-Sales Support	Lower activity	Stay connected — there's always another deal
10. Restart	Learn → Input into next cycle	Feed insights back

3. Lead Qualification Frameworks

BANT (Simplest)

Budget — Allocated? How much? Who owns it?
Authority — Does this person have decision power?
Needs — High-level business drivers and technical fit
Timing — Compelling event? Timeframe?

MEDDIC (More rigorous — use for enterprise deals)

Metrics — Quantified business impact
Economic buyer — Who controls the budget?
Decision criteria — How will they choose?
Decision process — Steps and timeline
Implement — identify Pain (what's broken)
Champion — Who advocates for you internally?

SE rule: Never work an unqualified lead. If in doubt, tighten the technical qualification questions early.

4. Technical Discovery

The Three Behavioral Crimes of Discovery

Tell — You start talking before you understand. The most common crime.
Accept — You accept every customer statement at face value without probing.
Guess — You guess at the answer instead of asking.

The Basic Discovery Methodology

Inputs → Process (Questions + Listening) → Outputs

Inputs to gather: Current environment, team structure, technical stack, business drivers, timeline, budget context.

Outputs to produce: Prioritized pain list, success criteria, technical requirements map, relationship map, competitive landscape.

The (Optional) Magic Wand

Ask the customer: "If you had a magic wand and could fix three things about [area], what would they be?" — reveals latent needs they didn't articulate.

5. Business Value Discovery: Pains & Gains

Three Types of Pain

Pain Type	Definition	Example Statement
Latent Pain	Customer knows something is wrong but hasn't acted	"Our reporting takes too long but that's just how it is"
Current Pain	Active problem they're trying to solve	"We need to reduce breach detection time"
Vision Pain	They want to achieve something new	"We want to offer self-service analytics to our customers"

How to Identify Pain (4-Step Process)

Gather a complete list — Ask open-ended questions about challenges
Verify completeness — "Is there anything else?"
Ask permission to add your own — "Based on what I've seen at other companies, may I suggest..."
Prioritize the list — Rank by business impact

6. Business Value Discovery: Time, Money & People

BVD Quadrants — Four questions per pain point:

	Current State	Future State
How do you KNOW it's a problem?	Evidence something is wrong	How will you know when it's fixed?
What is the SIZE of the problem?	Impact today	Impact of the problem going away?

Question Types

Closed-ended: "Do you use AWS?" — for confirmation
Open-ended: "Tell me about your current infrastructure" — for discovery
Nonquestion question: "Interesting, tell me more about that" — the most powerful tool

3WM+M Approach

Who is involved?
What is the problem/impact?
Where does it show up?
Why does it matter NOW?
→ How Much (Money)?

Time, Money & People Framework

Time: Hours wasted, delays, missed deadlines, time-to-value
Money: Direct costs, opportunity costs, revenue loss
People: Headcount, morale, turnover, skills gaps

Preliminary Financial Checkpoint

After discovery, ask yourself: "Is the cost of this problem greater than the cost of our solution?" If yes, you have a viable deal. If no, you need to find deeper pain.

7. FAB: Features → Advantages → Benefits

The most common SE mistake: listing features. The FAB framework converts features into customer-relevant value.

Level	Definition	Example (from the book)
Feature	What the product does	"4 GHz processor, 64GB RAM"
Advantage	What that means generically	"Faster processing of large datasets"
Benefit	What it means for THIS customer	"Your analysts will finish their daily reports by 10 AM instead of 3 PM."

Rule: A Benefit must tie to a specific pain or gain the customer identified. If you haven't done discovery, you cannot deliver FAB — you can only do FA (Features → Advantages), which is weak.

Back to Being FABulous: After explaining the FAB, always check and re-anchor: "Does that address the [specific pain] we discussed?"

8. Pitch Structure: RM+3KP

The Attention Curve

Audience attention peaks in the first 60-90 seconds and at the very end. Structure accordingly.

RM+3KP Framework

Relevance Message
  → Key Point 1 (with proof point)
  → Key Point 2 (with proof point)
  → Key Point 3 (with proof point)

Relevance Message — Single sentence: "Here's why this matters to YOU specifically"
3 Key Points — Maximum three. Each with a proof point (customer story, data point, demo moment)
Delivery — Transfer each key point to your slides/demo/whiteboard, NOT the other way around

Pitch Structure Sequence

Start with structure: Success = RM + 3KP
Drill down on solution and proof points
Organize the ideas (logical flow, not chronological)
Focus the key points (cut everything that doesn't support the RM)
Transfer to your delivery mechanism

9. Pitch Delivery

Nonverbal (55% of impact)

Element	Do	Don't
Appearance	Dress one level above the customer (or match)	Out-dress them
Posture	Stand straight, open stance	Slouch, cross arms
Eye contact	3-5 seconds per person in small groups	Stare at slides
Gestures	Purposeful, above the waist	Fidget, hands in pockets
Movement	Move between "zones" during transitions	Pace nervously
Facial	Smile, show engagement	Deadpan, frown

Verbal (38% of impact)

Element	Guideline
Pace	Vary speed. Slow for emphasis, faster for energy
Pitch	Drop pitch at end of statements (authority). Raise at questions (engagement)
Tone	Warm and conversational, not monotone or sing-song
Volume	Project to the back of the room. Soften for confidential moments
Articulation	Clear. No jargon, no filler words ("um", "like", "you know")

Structure for Every Presentation

Bright and beautiful beginning: Hook them in the first 60 seconds
Make a fantastic finish: End with a clear call to action or memorable summary
Use nervous energy: Channel it into purposeful movement and vocal energy

10. The Dash to Demo (And How to Stop It)

The most dangerous moment in the sales cycle: when a customer asks for a demo before you've done discovery.

Why It Happens

Customer wants to see before they believe
Salesperson wants to show off
SE wants to please

Three Questions to Ask Before Any Demo

What do we know about this customer? (Have we done discovery?)
What is the agenda? (Who's attending? What are their roles?)
What does success look like? (How will we know it worked?)

Checkpoint Charlie — The Pre-Demo Gate

Before every demo, stop and verify:

Do we know the customer's pain? (At least one specific pain point)
Do we know who will be in the room? (Roles, technical level)
Do we know what "good" looks like to them?
Have we set mutual expectations for the demo's outcome?

If you can't answer all four → you are about to dash to demo. Push back. Do a mini-discovery call first.

11. Building the Demo — Demo GPS Roadmap

A structured approach to building customer-specific demos.

The Demo GPS Roadmap

Destination (What's the outcome?) → Route (What's the flow?) → Checkpoints (How do we know we're on track?)

Building It

List the pain points identified in discovery
Map each pain to a demo moment — a 2-3 minute segment that shows the solution
Sequence the demo moments into a narrative flow (problem → exploration → resolution)
Define transition points — how you move between segments
Define success checkpoints — "If they nod at this point, proceed. If confused, pause."

The Pain of the Demo (Customer Perspective)

Customers hate:

Death by slides
"And then" demos (feature after feature with no narrative)
Irrelevant content
Technical problems during the demo

Rules for Great Demos

Never show a feature you haven't discussed in discovery
Use the customer's data/examples when possible
Pause and check every 5-7 minutes
Have a backup plan for tech failures

12. Remote Demonstrations

Advantages

Recordable, shareable
Lower travel cost, faster scheduling
Screen sharing allows precise focus

Disadvantages

Harder to read body language
Easier for attendees to multitask
Tech issues compound

Remote Demo Best Practices

Know your customer: Ask about their remote setup. Camera on/off? Platform preference?
Know your technology: Test audio, video, screen sharing, backup connection. Have a second device ready.
Know your product AND your demo: Know what you'll show and in what order. Know the keyboard shortcuts. Have a "clean" demo environment.
Engage actively: Ask questions every 5 minutes. Use polls, chat, reactions. Call people by name.
Handle multitasking: If you sense distraction, ask a direct question to re-engage.

13. Whiteboarding & Visual Selling

Power of Whiteboarding

Collaborative (customer participates)
Flexible (adapt in real-time)
Memorable (visuals stick)
Positions you as an expert

Getting Started (The Chunking Method)

Start with a statement: "Let me show you how I see this working"
Draw the context: The current situation (boxes and arrows)
Introduce the problem: Where it breaks
Show the solution: How your approach fixes it
Capture the outcome: What the future looks like

Whiteboarding Mechanics

Stance: Don't block the board. Stand to the side.
Timing and chunk: Draw for 30-60 seconds, then turn and explain. Repeat.
Speed: Deliberate and clear, not fast.
Color: Use deliberately:
- Black/blue: neutral info
- Red: problems, competition, alerts
- Green: solutions, positive outcomes
Icons: Use simple, repeatable icons. Cloud, database, user, money — establish a visual vocabulary.

Whiteboarding as a Closing Tool

A well-done whiteboard at the end of the sales cycle can serve as the "final picture" of the solution. Use it to confirm mutual understanding before close.

14. Storytelling

Why Stories Work in Sales

Stories make you memorable, interesting, and compelling
They create emotional connection (which data cannot)
They make abstract concepts concrete

Story Structure (Good)

Context (who, what, where) → Conflict (the problem) → Resolution (how we helped) → Result (measurable outcome)

The Conversational Customer Reference Story (Best for sales)

Keep it short and natural:

"Actually, that reminds me of <customer name>. They had a similar challenge with <specific problem>. We helped them by <approach>, and within <timeframe> they achieved <measurable result>."

Storytelling Grammar

Use specific numbers ("reduced downtime by 73%") not vague claims ("significantly reduced downtime")
Use customer names (with permission)
Use before/after contrasts
Keep it under 90 seconds

15. Evaluation Strategies & Proof of Concept

Creating the POC Success Criteria

Key question: "How do you define success for this evaluation?"

The 7-Phase POC Process

Phase	Activity	Key Question
1. Document success criteria	Write it down, get sign-off	"What specifically must work?"
2. Mini-discovery	Understand their environment	"What are the technical constraints?"
3. Development	Build/test the solution	"Are we on track?"
4. Test	SE validates internally	"Does it meet the criteria?"
5. Deployment	Install in customer environment	"Is the environment ready?"
6. Demonstration & validation	Show the working solution	"Does this satisfy the criteria?"
7. Presentation of results	Formal readout	"Here's what we proved."

Intellectually Closing the Deal

Before the POC ends, start the close: "If we meet all the success criteria, is there any reason we wouldn't move forward?" — Address objections before they block the deal.

Don't Forget

Training & documentation: Handoff materials for the customer team
The competition: They're probably running a parallel POC. Know what they can/can't do.
The people: Build relationships with everyone involved, not just the champion.

16. Answering Questions — The LACE Strategy

When a customer asks a question, DO NOT answer immediately. Use LACE:

Step	Action	What to Say
Listen	Hear the full question without interrupting. Pause 2 seconds.	(Silence + nod)
Accept	Acknowledge the question positively	"Great question." / "That's a really good point."
Clarify	Ensure you understand what they truly want	"To make sure I understand, are you asking about X or Y?" / "Can you help me understand what's behind that question?"
Execute	Answer directly and concisely. Confirm satisfaction.	Deliver the answer, then: "Does that address your concern?"

Question Types and How to Handle Them

Type	Characteristics	Strategy
Standard	Genuine information request	Answer directly with LACE
Coach	Easy question from your internal champion	Answer well, thank them. Don't reveal the relationship.
Competitive	"How are you better than X?"	LACE. Clarify: "What specifically is important to you about X's approach?" Then answer that.
Consultant	Expert probing from an outside advisor	Deep technical answer. Be precise. They'll verify.
Seymour	"What's your biggest weakness?" (named after the Sinéad O'Connor song "Nothing Compares 2 U")	Acknowledge honestly, then pivot to your roadmap or mitigation
Hostile	Loaded or aggressive	Stay calm. Accept the emotion: "I hear your frustration. Let me address that directly."

17. The Trusted Advisor SE

The Trust Equation (Modified for SEs)

Trust = (Credibility + Reliability + Intimacy) / Self-Orientation + Positivity

C = Credibility: Do they believe what you say?
R = Reliability: Do you do what you say you'll do?
I = Intimacy: Do they feel safe sharing sensitive information with you?
S = Self-Orientation: Are you focused on them or on making your quota?
P = Positivity: Do you bring energy and optimism?

The SE's Automatic Trust Advantage

SEs start with higher trust than salespeople because:

You're seen as the "technical conscience" — less biased than a quota-carrier
You solve problems rather than push products
You speak the customer's technical language

Building Trust Intentionally

Show up prepared — Do your research before every meeting
Admit what you don't know — "I don't know, but I'll find out" builds MORE trust than bluffing
Over-communicate — Send follow-ups, share timelines, keep promises
Be vulnerable — Share a personal story, a past mistake, a lesson learned

18. The Executive Connection

What Executives Want From You

Brevity — They have limited time. Get to the point.
Business outcomes — Revenue, cost, risk, competitive advantage
Proof, not promises — Case studies, data, references
Your expertise — Don't bring a salesperson to handle the business side. YOU handle it.

Planning the Executive Meeting

Set the stage: Who's attending? What's their agenda? What's their relationship to the problem?
Follow the money: What financial outcome matters to this executive?
Set the goals: What ONE outcome makes this meeting a success?
You are the expert: You were invited for your knowledge. Own it.

Presentation Ideas for Executives

The 3-slide deck: Problem → Solution → Business Case
Analogy first: Compare your solution to something they already understand
Peer reference: "Your competitor X is doing Y and seeing Z results"
The "so what" test: Every slide/statement must pass: "So what?" If it doesn't, cut it.

Follow-Up After the Meeting

Same-day follow-up email with 3 key points
Action items with owners and dates
Link back to the business outcome discussed

19. Proving Business Value / ROI

How Customers Assess Value

Cost savings (TCO reduction)
Revenue generation (faster time-to-market, new capabilities)
Risk mitigation (security, compliance, downtime)
Strategic advantage (competitive differentiation, innovation)

Value Assessment Methods

TCO Analysis: Compare total cost of current vs. proposed solution (include hardware, software, labor, training, downtime, migration)
ROI Calculation: (Gain from Investment - Cost of Investment) / Cost of Investment
Payback Period: How long to recover the investment
Time to Value: How quickly will they see results? (This matters more than total ROI for many buyers)

The Emotional Return on Investment

Sometimes the real decision driver isn't financial — it's:

Peace of mind: "I won't get fired if this goes wrong"
Professional pride: "My team will be leading edge"
Career advancement: "This project will make me look good"
Personal relationship: "I trust this team"

Don't dismiss emotional drivers. They're often more powerful than financial ones.

Value Engineering and FinOps (Cloud-Specific)

Cloud shifts capex to opex — the value conversation changes from "buy less hardware" to "optimize consumption"
FinOps is the practice of managing cloud costs through visibility, allocation, and optimization
For cloud/SaaS: focus on consumption efficiency, waste reduction, resource rightsizing

20. Competitive Tactics

Your Number One Competitor

Usually not the other vendor. It's the status quo — the customer doing nothing. Always address this first.

Five Competitive Strategies

Strategy	When to Use	How It Works
Frontal	You're clearly better	Head-to-head comparison. Show your superiority directly.
Flanking	You're different, not better	Attack where the competitor is weak or absent. Change the evaluation criteria.
Fragment	You have options	Split the deal. Take part of the business now, expand later.
Defend	You're the incumbent	Reinforce relationships. Highlight switching costs and risks.
Develop	New market / greenfield	Educate the market. Create the category. Set the evaluation criteria.

Know Thine Enemy

Build a competitive intelligence file:

What are their strengths? (Don't attack these)
What are their weaknesses? (Where to attack)
What is their typical pricing and packaging?
What do customers say about them? (Gartner, G2, Peer reviews)
Who are their reference accounts?

Reversing the Dirt

When a competitor attacks your weakness, reframe it as a benefit:

Competitor: "Their solution is too complex." You: "Our solution has the depth and configurability that enterprises need. Let me show you how our architecture handles scenarios their simpler solution cannot."

21. New SE: Getting Started (30/90/180-Day Plan)

Phase 1: First 30 Days — Absorb

Find a mentor (formal or informal)
Read the manual / product documentation
Watch "the movies" (recorded demos, sales calls)
Join internal communities (Slack, Teams distribution lists)
Learn the product: install it, use it, break it

Phase 2: 30-90 Days — Practice

Master the product (deep dive into key features)
Work in the "factory" (shadow experienced SEs on calls)
Practice your demo (record yourself, get feedback)
Know your customer stories (3-5 reference stories)
Use your product in your daily life (dogfooding)

Phase 3: 90-180 Days — Perform

Lead your first discovery call (with support)
Run your first demo (with shadow support)
Get feedback from everyone (manager, peers, sales partner, customers)
Build your personal brand (internal and external)

22. Personal Brand

Defining Your Brand

Your personal brand is what people say about you when you're not in the room. For an SE, this is about three things:

What you're known for (technical domain, industry expertise, specific skill)
How you make people feel (trustworthy, responsive, insightful)
What you deliver (closed deals, happy customers, team value)

Building the Brand Statement

Format: "I help [specific audience] achieve [specific outcome] by [specific method]."

Examples:

"I help financial services firms reduce compliance risk through automated security monitoring."
"I help enterprises migrate to the cloud faster with zero downtime during the transition."

Living Your Brand

Internal: Be the go-to person for your domain. Share knowledge. Help teammates.
External: Speak at events, write LinkedIn posts, contribute to community forums, build a network.
Honesty and ethics: Never misrepresent capabilities. Your reputation is your most valuable asset.

23. Partner Selling

Types of Partners

Partner Type	Role	SE Engagement
SI (Systems Integrator)	Build and integrate solutions	Joint discovery, architecture
VAR (Value-Added Reseller)	Resell with their own services	Enablement, deal support
Distributor	Logistics and aggregation	Training, broad enablement
Technology Alliance	Complementary products	Joint value proposition, co-demo

Rules of Engagement

Define account ownership — Who leads? Who supports?
Establish communication protocols — Direct or through the partner?
Clarify deal registration — Who gets credit?
Provide enablement — Train the partner's SEs, don't just sell through them

The Partner Engineer's Special Role

Partner engineers need to:

Be product-agnostic (they represent multiple vendors)
Focus on the partner's solution, not just your product
Build relationships with partner sales and SE teams
Understand the partner's business model and margin structure

24. Time Management: The DOG Framework

DOG: Distractions, Objectives, Gains

Element	Definition	SE Application
Distractions	Things that pull you away from important work	Reactive emails, low-value meetings, internal politics
Objectives	What you need to accomplish	Deals to close, demos to prepare, POCs to run
Gains	Activities that build long-term value	Learning, relationships, certification, personal brand

The 80/20 Rule for SEs

80% of your results come from 20% of your deals
Identify which 20% and protect time for them ruthlessly
Delegate, defer, or decline the rest

Daily Time System

Time	Activity
Start of day (15 min)	Review calendar. Identify top 3 priorities. Prepare for any customer meetings today.
During the day	Batch low-value tasks (email, admin) into blocks. Protect demo prep and strategic work.
End of day (10 min)	Update CRM. Note follow-ups. Review tomorrow's calendar. Clear inbox to zero or folder.

Metrics-Driven Self-Management

Track yourself on:

Learning & Growth: Certifications, skills acquired, books read
Process: Demo quality scores, POC success rate, response time
Customer: NPS, satisfaction, referenceability
Finance: Quota attainment, average deal size, win rate

25. CRM Usage

Why CRM Is Your Best Friend

It's your memory — you can't remember details across 20+ active deals
It's your visibility — managers, peers, and successors rely on your CRM data
It's your proof — at annual review time, CRM data justifies your compensation
It's your repeatability engine — capture what works and replicate it

CRM Best Practices for SEs

Update immediately after customer interactions (not at end of week)
Log technical requirements, competitive mentions, and key relationships
Link POC success criteria to opportunity records
Tag customer references and success stories for reuse

26. The Hiring and Interview Process

For Hiring Managers

Write the job description — focus on attitude and adaptability over specific technical skills
Look in unusual places — English lit, philosophy, history majors often make great SEs
Interview for these traits:
- Curiosity (do they ask good questions?)
- Adaptability (can they handle curveballs?)
- Communication (can they explain something complex simply?)
- Attitude (are they a fixer and pleaser?)

For Candidates

The screening call — Be prepared to explain why SE. Have a 60-second "cocktail party answer."
The hiring manager — Expect a technical discussion AND a role-play scenario
SE leadership — Expect strategic questions: "How would you build an SE team?"
The salespeople — Expect a "sell me this pen" variant. Show you can partner.
Closing the deal — Move from recruit to attract. Show enthusiasm. Ask about career paths.

27. Compensation (For Understanding, Not Negotiating)

Typical SE Compensation Components

Base salary (fixed) — typically 70-80% of total for junior, 60-70% for senior
Variable pay — tied to team/company quota, individual MBOs, or both
MBOs (Management By Objectives) — bonuses for non-revenue activities (training, enablement, certifications)
Stock/equity — RSUs or options, typically at senior levels

Key Terms

OTE (On-Target Earnings): Base + Variable if you hit 100% of quota
Accelerators: Higher commission rates above 100% quota attainment
Clawbacks: Repayment of commission if the deal is cancelled
Ramp: Reduced quota (and protected comp) for the first 6-12 months

28. Career Progression Paths

Typical SE Career Ladder

Associate/Junior SE → SE → Senior SE → Principal SE → SE Manager → Director of SE → VP of SE

Alternate Paths

Subject Matter Expert (SME): Deep specialization in one product/domain
Solutions Architect: More strategic/architectural, less hands-on
Product Management: Leverage customer insight to influence product direction
Sales: Many SEs transition to quota-carrying roles successfully
Professional Services: Implementation and post-sales delivery
SE Enablement: Train and develop other SEs

Behavioral Competencies for Promotion

Strategic thinking: Seeing beyond the current deal to account/territory strategy
Executive presence: Comfortable in C-level conversations
Mentorship: Developing other SEs
Thought leadership: Contributing to company/industry knowledge

Response Efficiency

This skill contains 28 chapters of detailed frameworks. Be smart about output length:

For simple, single-topic questions (e.g. "how do I handle a competitive question?") → Give the framework name, the core 3-4 steps, and one concrete example. Then ask: "Want me to go deeper on any part of this?"
For complex, multi-topic scenarios (e.g. "I have an executive presentation, a demo, and a POC to plan") → Go comprehensive. The user needs the full playbook.
When in doubt, give the TL;DR first. Name the relevant framework, apply it to their situation, offer to expand.

Skill Reference: When to Use Which Framework

Situation	Framework	Chapter Reference
First meeting with prospect	Three Behavioral Crimes + BANT	Ch. 3, 5
Need to understand customer pain	Pain Types (Latent/Current/Vision) + BVD Quadrants	Ch. 6, 7
Building a presentation from scratch	RM+3KP + Attention Curve	Ch. 10
Pressure to demo without discovery	Checkpoint Charlie	Ch. 12
Planning a demo	Demo GPS Roadmap	Ch. 13
Customer asks a hard question	LACE Strategy	Ch. 18
Need to build trust	Trust Equation	Ch. 19
Presenting to executives	3-slide format + Follow the Money	Ch. 20
Proving ROI	TCO/ROI/Payback/Emotional ROI	Ch. 21
Facing a competitor	Five Competitive Strategies	Ch. 25
Running a POC	7-Phase POC Process	Ch. 17
Feature-focused pitch not landing	FAB (Features→Advantages→Benefits)	Ch. 8
Customer says "tell me about yourself"	Cocktail Party Answer (Four Roles)	Ch. 1
Feeling overwhelmed	DOG Framework (Distractions, Objectives, Gains)	Ch. 32
New to the role	30/90/180-Day Plan	Ch. 22

name

mastering-technical-sales

description