Concepts
Enterprise Sales
Enterprise sales is the pursuit of large, complex contracts sold to organizations with sizable buying committees, multi-stage procurement, and 6-to-18-month sales cycles, distinguished from SMB or mid-market sales by deal size, stakeholder count, and cycle length rather than any fixed revenue threshold.
Enterprise sales is what happens when a $40,000 software deal turns into a nine-month negotiation involving a CISO, a procurement officer, two VPs, outside counsel, and a security questionnaire nobody on the vendor side has ever fully answered. The label gets applied loosely — companies call anything "enterprise" once the logo has more than 1,000 employees — but the real marker isn't headcount, it's the buying committee. Gartner puts the average B2B buying group at 6 to 10 stakeholders; enterprise deals sit at the high end of that range, often with a legal and security review layered on top of the commercial one.
How Enterprise Sales Is Identified
There's no regulatory definition, so orgs pick their own gates. The three most common: ACV above a threshold (commonly $50,000-$100,000+), target account employee count (often 1,000+ or 5,000+), and sales cycle length (routinely 6-12 months versus 30-90 days for inside sales). Most RevOps teams use a combination — a $60,000 deal that closes in three weeks with one signer isn't enterprise no matter how big the logo is, and a $30,000 deal that needs eight signatures and a security review usually is.
Enterprise vs. SMB vs. Mid-Market
| Segment | Typical ACV | Cycle Length | Avg. Stakeholders | Primary Rep Type |
|---|---|---|---|---|
| SMB | $2k-$15k | 14-30 days | 1-2 | Inside sales / transactional AE |
| Mid-Market | $15k-$50k | 60-120 days | 3-5 | Commercial AE |
| Enterprise | $50k-$500k+ | 180-540 days | 6-15+ | Enterprise AE |
Worked Example
An AE closes a 30-seat deal at $45,000 ACV with a school district: single decision-maker, signed in 11 days. Same AE closes a $52,000 ACV deal with a regional bank: five stakeholders (IT, security, procurement, compliance, the VP sponsor), a 9-month cycle, a security questionnaire, and a legal redline round. Same ballpark ACV, completely different motion — the bank deal is enterprise, the school district deal isn't, and treating them identically in a comp plan or forecast model breaks both.
When Sales Teams Use the Enterprise Label
VPs of Sales use the segment to build pods — enterprise AEs carry different quotas, different OTE, and often a named-account list instead of an open territory. RevOps uses it to route leads and set sales cycle length benchmarks per segment rather than blending everything into one company-wide average, which otherwise makes forecast models useless. Recruiters use "enterprise experience" as a proxy for a candidate's ability to navigate procurement and multi-stakeholder negotiation — a real skill gap between someone who's only closed transactional SMB deals and someone who's run a six-month security review to close.
Common Enterprise Sales Gaming Patterns
The segment label is a lever, and reps and managers both pull it. A rep with a slipping quarter reclassifies a mid-market deal as "enterprise" to justify a longer runway before it counts against attainment — nobody audits the segment tag, so it sticks. Managers do the reverse: label a rep "enterprise" to justify a lower quota-to-OTE ratio, because enterprise cycles are longer and harder to model, then never revisit the classification once the rep's actual deal mix drifts back toward mid-market. The deeper problem is that "enterprise" tells you almost nothing about win probability — a single-threaded enterprise deal with one champion and no economic buyer signed off is weaker than a fully-vetted mid-market deal, but the segment label alone makes it look more substantial in a pipeline review. Segment should describe the buying process, not launder the quality of the deal.
Related terms
Ready to see your numbers?
Get your verified Alpha Score. Read-only CRM, score within minutes.
Get my Alpha Score