What is the SCOTSMAN framework?
SCOTSMAN is a sales qualification framework used to evaluate whether a B2B deal is worth pursuing. It qualifies opportunities across eight dimensions:
- S — Solution: does our product fit the customer's specific problem?
- C — Competition: who else are they evaluating, and how do we stack up?
- O — Originality: what makes our solution different or better?
- T — Timescale: when does the customer need to decide and go live?
- S — Size: is the deal big enough to justify the sales effort?
- M — Money: does the customer have budget, or a path to budget?
- A — Authority: who signs, who influences, who blocks?
- N — Need: how urgent is the pain, and what happens if they do nothing?
The framework is designed for reps and sales managers who need a shared vocabulary for deal review. It works especially well in enterprise sales where a single dimension (like "budget approved") doesn't capture whether a deal is real.
Where SCOTSMAN came from
SCOTSMAN emerged in the UK B2B sales community in the 1990s as an evolution of BANT (Budget, Authority, Need, Timing). BANT works well for transactional deals but breaks down in complex enterprise sales where competitive dynamics, solution fit, and differentiation matter as much as budget. SCOTSMAN adds those dimensions.
It's less famous in North America than BANT or MEDDIC but has been widely adopted in European enterprise sales orgs and technology consultancies.
The 8 dimensions explained
S — Solution
The question: Does our product actually solve the specific problem the customer is trying to solve?
Most losses in enterprise sales aren't lost on price — they're lost because the customer decides mid-cycle that the solution doesn't fit. Solution fit is checked early through discovery, then re-checked after the demo, and again after the technical evaluation.
What good looks like: You can articulate the customer's specific problem in their words, and the sales engineer has walked them through exactly how the product solves it.
What bad looks like: You're pitching a generic solution and the customer is nodding politely but hasn't confirmed the fit.
C — Competition
The question: Who else is the customer evaluating, and how do we compare?
If you don't know who you're competing against, you're not in a deal — you're in a demo cycle. The customer is almost always evaluating something, even if it's just "do nothing."
What good looks like: You know the shortlist, you know how the customer thinks about each competitor, and you have a differentiated angle for each one.
What bad looks like: The customer says "we're just looking at you" and you believe them.
O — Originality
The question: What can we do that competitors can't?
Originality is your differentiation — the two or three things that only you can credibly claim. It's different from "features" — most feature comparisons come out roughly even. Originality is the strategic angle.
What good looks like: You have three concise proof points that no competitor can match — customer case studies, unique technology, unique data set, unique network effect.
What bad looks like: Your "differentiation" is a longer feature checklist.
T — Timescale
The question: When does the customer need to decide, and when do they need to go live?
Timescale is what turns a "someday" deal into a real deal. If there's no compelling event forcing a decision, the deal will slip indefinitely.
What good looks like: A specific date tied to a business event — contract renewal, board mandate, regulatory deadline, product launch, competitive threat.
What bad looks like: "Sometime this quarter." That's not a timescale.
S — Size
The question: Is the deal big enough to justify the sales effort?
Size isn't only about the initial deal — it includes expansion potential. A $30K starter contract into a Fortune 500 that becomes a $300K contract in year 2 is a different animal than a $30K contract that will always be $30K.
What good looks like: You have a defensible number for year 1 ARR, year 2 expansion, and total account potential.
What bad looks like: You're pitching an enterprise motion into a deal that will always be SMB-sized.
M — Money
The question: Does the customer have budget, or a clear path to getting budget?
Money is the classic BANT dimension. In modern enterprise sales, "budget approved" is rare early in the cycle. What you need is a credible path — the champion knows how to unlock budget, the sponsor exists, the fiscal-year timing works.
What good looks like: You know the budget owner, the budget cycle, and the customer has told you approximately what they can spend.
What bad looks like: The champion says "we'll figure out budget later" — which usually means never.
A — Authority
The question: Who signs, who influences, who blocks?
Modern enterprise deals average 10-11 stakeholders (Gartner). Authority isn't a single person — it's a buying committee with distinct roles: economic buyer, technical buyer, users, procurement, legal, and often the informal "influencer" who can kill a deal without being on any org chart.
What good looks like: You've mapped the buying committee, you've engaged 4+ stakeholders, and you know who signs.
What bad looks like: You have one champion, no exec engagement, no procurement contact. This deal will die in month 3.
N — Need
The question: How urgent is the pain, and what happens if they do nothing?
Need is the strategic question underneath everything else. If the customer can credibly do nothing, they will. Your job is to make "do nothing" feel more expensive than doing the deal.
What good looks like: The customer can articulate what happens if they don't solve this problem in the next 6-12 months — and it's bad enough to justify action.
What bad looks like: The customer says "we should probably do this eventually" — which is the same as no.
SCOTSMAN vs BANT vs MEDDIC vs SPIN
Sales qualification frameworks aren't interchangeable — each was built for a different kind of deal. Here's how the four most-used frameworks compare:
| Framework | Best for | Key strength | Weakness |
|---|---|---|---|
| BANT | Transactional / mid-market | Simple, fast to run | No competitive dimension, no solution fit |
| SCOTSMAN | Enterprise deals with competitive evaluations | Explicit competition + originality dimensions | Longer to run, requires disciplined reps |
| MEDDIC / MEDDPICC | Complex enterprise with formal procurement | Deep on decision process + paper process | Weaker on solution fit and originality |
| SPIN | Consultative discovery-heavy sales | Question-driven, discovers pain deeply | Not a qualification framework — a discovery framework |
The right choice depends on your motion:
- Sub-$50K ACV, single decision-maker: BANT is enough.
- $50K-$500K ACV, competitive shortlist: SCOTSMAN wins on competitive dimension.
- $500K+ ACV, formal RFP + procurement: MEDDIC/MEDDPICC handles the paper process.
- Any deal size with heavy consultative discovery: SPIN complements any qualification framework.
Many enterprise orgs run SCOTSMAN + SPIN in combination — SCOTSMAN for weekly deal review, SPIN for discovery calls.
When SCOTSMAN is the right tool
SCOTSMAN works when:
- You sell into competitive shortlists where differentiation matters
- Your deals involve multiple stakeholders across 3+ months
- Your team needs a shared qualification vocabulary for pipeline review
- You're losing deals to competitors and can't articulate why
- Solution fit is genuinely variable across customer types
When SCOTSMAN is the wrong tool
SCOTSMAN is overkill or underpowered when:
- You sell SMB / transactional deals. BANT is faster and enough.
- Your deals are dominated by procurement mechanics. MEDDPICC's decision-criteria + paper-process dimensions matter more than SCOTSMAN's competitive framing.
- You have no clear differentiation. SCOTSMAN forces you to answer the Originality question. If your answer is "our team is nicer," SCOTSMAN will make that obvious — which is either a wake-up call or a reason to pick a simpler framework.
SCOTSMAN in the AI era
Modern AI-assisted sales tools automate parts of SCOTSMAN qualification:
- Solution fit: LLMs can read call transcripts and score how well the demo mapped to stated pain
- Competition: Sales intelligence tools surface which competitors the account is currently evaluating (G2, Gong)
- Authority: Buying-committee mapping tools identify stakeholders you haven't yet engaged
- Need: Trigger-based intelligence surfaces new pain (funding, hiring, tech-stack changes) that increases urgency
The framework itself hasn't changed. What's changed is that the inputs are increasingly automated — which means the rep spends less time gathering data and more time acting on it.
Example: SCOTSMAN applied to a real deal
Deal: SaaS company, $200K ACV, evaluating three vendors including yours.
- S (Solution): Customer's stated problem is "our sales reps can't find warm intros into target accounts." Our product surfaces warm paths through customer/board/partner networks — clean fit. Score: 9/10.
- C (Competition): Evaluating us + one legacy player + one newer competitor. We win on graph coverage; legacy player wins on brand; newer competitor is cheaper. Score: 6/10.
- O (Originality): Two credible differentiators — richest graph in category, real-time job change detection with named path source. Score: 8/10.
- T (Timescale): Contract renewal on existing tool in 90 days — hard deadline. Score: 9/10.
- S (Size): $200K year 1, $500K expansion path if we land the enterprise CRM sync. Score: 8/10.
- M (Money): Budget approved for the category, allocated to Q3. Score: 9/10.
- A (Authority): Champion in RevOps, VP Sales engaged, CRO on the buyer committee. Procurement identified. Score: 8/10.
- N (Need): Pipeline missed last quarter; VP Sales has commit to Board on Q4 recovery. Score: 9/10.
Total: 66/80 = strong deal. Weak spot is Competition — worth investing SE time in a head-to-head bake-off.
How SCOTSMAN connects to pipeline generation
SCOTSMAN qualifies deals in your pipeline. It doesn't help you generate the pipeline in the first place. The upstream question — where does the pipeline come from — is answered by understanding your best warm paths into target accounts.
The teams that combine SCOTSMAN (for qualification) with relationship intelligence (for pipeline creation) tend to have the healthiest funnels — because they're both creating better pipeline and qualifying more rigorously. Boomerang instruments the pipeline-creation side by mapping your team's collective networks and detecting when a warm path opens into an SCOTSMAN-qualified target account.
Frequently asked questions about SCOTSMAN
What does SCOTSMAN stand for?
Solution, Competition, Originality, Timescale, Size, Money, Authority, Need. Eight dimensions used to qualify B2B sales opportunities.
Who created the SCOTSMAN framework?
SCOTSMAN emerged in UK B2B sales training in the 1990s as an evolution of BANT. There's no single credited author — it's been refined across multiple sales enablement companies over the decades.
How is SCOTSMAN different from BANT?
BANT covers Budget, Authority, Need, Timing (four dimensions). SCOTSMAN adds Solution fit, Competition, Originality, and Size. It's designed for enterprise deals where competitive dynamics and differentiation matter as much as budget.
How is SCOTSMAN different from MEDDIC?
SCOTSMAN emphasizes competitive positioning and solution fit. MEDDIC/MEDDPICC emphasizes decision criteria, decision process, and formal paper process. Both are enterprise frameworks — MEDDIC is stronger for RFP-heavy deals; SCOTSMAN is stronger for competitive shortlists.
How is SCOTSMAN different from SPIN?
SCOTSMAN is a qualification framework — it evaluates deal health. SPIN is a discovery framework — it uncovers pain through Situation, Problem, Implication, and Need-payoff questions. Many enterprise teams use SPIN for discovery calls and SCOTSMAN for weekly pipeline review.
When should I use SCOTSMAN?
Use SCOTSMAN when you sell into competitive enterprise shortlists with multiple stakeholders and 3-6 month cycles. It's less useful for transactional deals (use BANT) or RFP-heavy procurement deals (use MEDDPICC).
Can I combine SCOTSMAN with other frameworks?
Yes. Common combinations: SCOTSMAN + SPIN (qualification + discovery), or SCOTSMAN + MEDDPICC (SCOTSMAN for weekly review, MEDDPICC for late-stage paper process).
How do I score SCOTSMAN in practice?
Most teams score each of the 8 dimensions 1-10 during weekly deal review. Total scores under 40/80 usually flag deals that should be de-prioritized. Scores above 60/80 are strong candidates for exec engagement and forecast commit.
Does SCOTSMAN work for SaaS sales?
Yes — it was built for enterprise B2B, and modern SaaS sales fits that profile. It's particularly useful for SaaS deals where you're often up against a legacy incumbent + a scrappier competitor.
Is SCOTSMAN still relevant in the AI era?
Yes. The dimensions haven't changed — competition, solution fit, and differentiation still matter in every enterprise deal. What's changed is that AI tools now automate parts of the data gathering, so reps spend less time filling out qualification templates and more time acting on the insights.
The bottom line
SCOTSMAN is the right qualification framework when you're selling enterprise deals with real competitive evaluations. It forces reps to have honest answers about differentiation and solution fit — two dimensions that BANT ignores and MEDDIC underweights. Combine it with SPIN for discovery and relationship intelligence for pipeline creation, and you have a full enterprise sales operating system.
