What's the trigger to launch an enterprise motion separate from mid-market?

Direct Answer

The trigger to launch a dedicated enterprise motion separate from mid-market is not a revenue number — it is a pattern of evidence that your existing motion is structurally incapable of capturing demand you are already generating. The clean go-signal is when four or more of seven trigger signals fire simultaneously: inbound enterprise demand exceeds 15 percent of pipeline but converts at under half your mid-market rate; mid-market reps repeatedly lose six-figure deals to incumbents they cannot out-navigate; you have hit an ACV ceiling; you are losing deals on security questionnaires and SOC 2 or SSO gaps rather than on product value; competitor-displacement opportunities needing nine-month cycles are appearing and dying; the board is pressuring for marquee logos; and the product is genuinely enterprise-ready.

Product readiness is necessary but never sufficient. The cost structure is steep: an enterprise AE runs roughly 160K base plus 160K variable for a 320K OTE carrying a 1.2M to 2M quota, needs a solutions engineer at roughly 1:2, plus deal desk, legal, and a security function — realistically a 1.5M to 3M, 12-to-18-month investment before the team is net-positive.

Hire in the order first enterprise AE, then SE, then enterprise CSM, then enterprise sales leader once you reach four to six reps — never a leader first. The dominant failure mode is launching too early, which starves mid-market of capital and attention. Treat enterprise as a separate company you are incubating inside your company, and only pull the trigger when the evidence is overwhelming and the product can survive a CISO review.

TL;DR

• The trigger is a pattern of evidence, not a revenue milestone — require 4 of 7 signals firing at once before committing capital, and one of those four must be genuine product readiness.
• The seven signals: 15 percent inbound enterprise pipeline, six-figure incumbent losses, an ACV ceiling, security-review losses, competitor-displacement opportunities, board pressure, and product readiness.
• A credible enterprise motion is a 1.5M-3M, 12-18-month block investment — two AEs, an SE, partial deal desk and legal, and a funded security and compliance function. A half-funded motion is worse than none.
• Hire AE first, SE second, CSM third, leader fourth (at 4-6 reps). Promoting your best mid-market rep into the first enterprise seat is the most expensive single mistake.
• Do not launch on board pressure alone, on an unready product, without a funded security posture, without committed capital, or while mid-market still has large untapped runway.
• The deepest pattern: enterprise motions convert demand that already exists inside large logos — they rarely create it. HubSpot, Zoom, Notion, Airtable, and Figma all had organic footprints before they built the motion.

1. The Definition Problem: What "Enterprise" Actually Means

Before a CRO can decide whether to launch an enterprise motion, the leadership team has to agree on what "enterprise" actually means — and most teams discover, the moment they write it down, that they have been using the word to mean three or four incompatible things: "a big logo," "a deal over 100K," "a company we saw at a conference." None of those are operational definitions, and a motion built on a fuzzy definition will hire the wrong people, build the wrong process, and forecast garbage.

1.1 The Five-Attribute Operational Definition

An operational definition of enterprise has five components, and a true enterprise account hits most or all of them.

• Company size: 2,000-plus employees — increasingly the more useful cut is 5,000-plus or the Fortune and Global 2000, because buying behavior changes qualitatively in that band.
• Deal size: 250K-plus ACV as a floor, often 500K to 1M-plus, with multi-year total contract value frequently in the seven figures.
• The buying committee: 8-plus stakeholders, often 12 to 20 — economic buyer, champion, technical evaluators, security, legal, procurement, IT, finance, and the executive sponsor.
• Cycle length: 6 to 12 months from first qualified conversation to signature, sometimes 18 months for category creation.
• The gauntlet: a mandatory procurement process, a legal and MSA negotiation, and a security review — each of which can independently kill the deal regardless of how much the champion loves the product.

1.2 Why Each Attribute Breaks a Mid-Market Assumption

Each of those five attributes breaks a specific assumption baked into a mid-market motion. A mid-market rep is comp'd and coached to run a 30-to-60-day cycle, work two or three contacts, send an order form, and move on. Drop that rep into an eight-month, fourteen-stakeholder, procurement-gated deal and they will either abandon it — their comp plan punishes time spent — or mishandle it, because they have never multi-threaded an org chart or survived a redline negotiation.

The definition determines whether you need a separate motion at all. If your "enterprise" deals are really just 80K mid-market deals with a recognizable logo, you do not need an enterprise motion — you need better logos in your existing motion. You only need a separate motion when the deals genuinely have the five attributes above.

1.3 The Closed-Won and Closed-Lost Audit

A useful discipline: write the five-attribute definition down, then pull your last 24 months of closed-won and closed-lost data and tag every deal against it. You will usually find genuine enterprise is 6 to 12 percent of deals, that those deals close at a lower rate than mid-market, and that the win rate craters at the procurement and security stages.

That data set is the foundation for every decision that follows — the difference between a debate and a reading. The broader segment-strategy question of moving upmarket versus deeper into mid-market is covered separately (q106).

2. The Seven Trigger Signals: The Evidence That Says "Now"

There is no revenue threshold that tells you to launch enterprise. A 20M company with the wrong product should not; a 12M company with screaming enterprise demand and a security-ready product probably should. The trigger is a pattern of evidence — require that four or more of the following seven signals are firing at once before you commit capital.

Any one signal alone is noise; four together is a structural condition.

2.1 Signal 1 — Inbound Enterprise Demand Exceeds 15 Percent of Pipeline

Pull the pipeline, tag it, measure the gap. If genuine enterprise opportunities are consistently 15 percent or more of inbound — and convert at *less than half* your mid-market rate — you have demand you are already paying to generate and structurally failing to capture. That gap is the most expensive thing in your funnel: the marketing cost is sunk and the conversion loss is pure.

2.2 Signal 2 — Mid-Market Reps Repeatedly Lose Six-Figure Deals to Incumbents

Read the closed-lost notes on every deal above 150K. If the pattern is "lost to the incumbent, they had relationships above our champion" or "we never got to the economic buyer," your reps are losing because they cannot navigate an enterprise org. That is a motion problem, not a rep-quality problem, and it does not get better with coaching.

2.3 Signal 3 — You Have Hit an ACV Ceiling

Chart the distribution of your deal sizes. If your top decile clusters tightly — everything bunches at 60K to 90K and almost nothing breaks 120K — you have a structural ceiling, because the packaging, pricing, buyer, and rep all top out together. Breaking it requires a different motion, not a stretch goal.

2.4 Signal 4 — Repeated Security-Questionnaire and Compliance Losses

Losing at the security stage is a two-in-one signal. If you are losing deals at the security review stage — failing on SOC 2, SSO and SAML, data residency, penetration-testing evidence — and the champion says "we love it but security blocked us," it is also a *prerequisite* signal: enterprise demand is real and you are not yet ready to serve it.

The full security-review playbook is covered separately (q93).

2.5 Signal 5 — Competitor-Displacement Opportunities Appearing

When the market starts handing you nine-month deals. When prospects come to you mid-contract with an incumbent — "we are unhappy, our renewal is in nine months, can you displace them" — those are enterprise-shaped deals: long cycles, heavy proof-of-concept, executive sponsorship, procurement.

A mid-market rep will not run a nine-month displacement; their comp plan will not let them. If these opportunities show up and die on the vine, that is signal.

2.6 Signal 6 — Board Pressure for Logos

Real, legitimate, and dangerous. Boards and investors push for marquee logos because logos drive the next round's narrative and the eventual multiple. Board pressure is a legitimate *input* — but never the *deciding* signal on its own. Board pressure plus three evidentiary signals is a go; board pressure alone is how companies launch enterprise motions 18 months too early.

2.7 Signal 7 — Product Readiness for Enterprise

Necessary but never sufficient. The product genuinely supports SSO, SAML, and SCIM, audit logs, RBAC, the security certifications, API rate limits for large deployments, and a contractual uptime SLA. A ready product with no demand is not a reason to launch; an unready product with screaming demand is a reason to *wait and build*, not to launch and lose.

The decision rule: count the signals — fewer than four, keep optimizing mid-market; four or more with one being product readiness, you have a real trigger.

3. The "Accidental Enterprise Deal" Pattern

Long before a company formally debates launching an enterprise motion, it has already run a dozen unintentional experiments — and lost almost all of them. The pattern is consistent enough to deserve a name: the Accidental Enterprise Deal.

3.1 How the Pattern Unfolds

A mid-market rep gets an inbound from someone at a 9,000-person company — a whale. They run their normal playbook: demo, proposal, follow-up, order form. For three weeks it feels great.

Then the deal hits the wall. The champion says, "Great, now I need to get this through security review and procurement." The rep has never seen a 300-line-item security questionnaire, has never been redlined on an MSA, does not know what a DPA is, and has no idea procurement will demand a competitive bid and a 15 percent discount as policy.

The champion goes quiet for six weeks navigating internal politics the rep cannot see, and the rep — whose comp plan rewards velocity — mentally writes the deal off.

3.2 The Two Bad Endings

One of two things then happens.

• The deal dies: the champion loses momentum without air cover and the initiative stalls — six months of effort and a 250K-potential account evaporate.
• The deal closes badly: the rep, desperate to salvage it before quarter-end, caves to procurement's discount demand and signs a 250K-potential account at 70K on a one-year term with no expansion path. The company books a "win" that is actually a loss — a reference-grade logo paying mid-market money for an enterprise cost-to-serve.

3.3 Why This Pattern Is Itself Trigger Evidence

This pattern is one of the most important pieces of trigger evidence, for three reasons.

• It proves the demand is real: enterprises are finding you organically without an enterprise motion.
• It proves the existing motion cannot capture it: not because the reps are bad, but because the motion is structurally wrong for the deal.
• It quantifies the cost of inaction: every accidental enterprise deal that dies or under-prices is measurable lost ACV, and over 18 months the number is usually large enough to fund the motion.

A disciplined CRO treats these not as anomalies but as a data set — totaling the lost ACV and putting that number into the business case. How to run a procurement-gated deal without losing momentum is a deep dive of its own (q105), as is how sales-motion design shifts under structural disruption (q1899).

4. Enterprise Motion Cost Structure

"Just hire an enterprise rep and see what happens" is bad advice because the enterprise motion is not a rep — it is a *system* with a cost structure that has to be funded as a whole or it does not function.

4.1 The Enterprise AE

Compensation runs roughly 160K base plus 160K variable, a 320K OTE, sometimes higher in competitive markets, carrying an annual quota of 1.2M to 2M. The variable is structured 50/50 — versus the 60/40 or 70/30 of transactional roles — because enterprise cycles are long and lumpy and you cannot ask someone to live on commission with an eight-month cycle.

4.2 The Solutions Engineer

Enterprise deals are technical, and the AE cannot run them alone. You need an SE at roughly a 1:2 ratio early on, sometimes 1:1 in highly technical categories; an enterprise SE costs roughly 160K to 220K OTE. Skipping the SE does not save money — it just lowers your win rate until the AE quits.

Building the solutions engineering function is its own deep dive (q92).

4.3 Deal Desk and Legal

Enterprise pricing is bespoke — multi-year terms, ramped deals, custom usage tiers, volume discounts — so someone must own quote construction, approval workflows, and pricing discipline; early on a fractional RevOps or finance responsibility. Enterprise deals also come with MSA negotiations, redlines, DPAs, and security addenda; you will need either dedicated commercial counsel or a reliable outside-counsel relationship with fast turnaround, because legal latency directly extends your cycle.

A deal that sits in redlines for five weeks gives the incumbent five weeks to counter.

4.4 Security and Compliance

This is its own function — covered in depth in section 7 — and at minimum it is a security lead, the certification investments, and questionnaire-response capability.

4.5 The Total

The realistic first-year cost of a credible enterprise motion — two AEs, an SE, partial deal desk and legal, and the security function — is 1.5M to 3M, and the team will not be net contribution-positive for 12 to 18 months. A half-funded motion is worse than none: it consumes capital and reference equity and produces neither pipeline nor proof.

5. The Enterprise AE Profile

The single most expensive mistake in launching enterprise is promoting your best mid-market rep into the first enterprise seat. Top mid-market reps are excellent at velocity, volume, and a tight transactional process — and almost none of those skills transfer. Enterprise selling is a different job.

5.1 The Four Pillars of the Profile

• 10-plus years of selling experience: a track record specifically of closing six- and seven-figure deals, not a long tenure of closing many small ones.
• Fluency in a structured qualification methodology: MEDDPICC or MEDDICC — a discipline they run on every deal, not a buzzword. Operationalizing MEDDPICC is a deep dive of its own (q94).
• Multi-threading experience: building relationships across an entire buying committee simultaneously, mapping an org chart, developing a champion while cultivating the economic buyer and neutralizing detractors.
• Executive presence: the credibility to sit across from a CIO or CISO as a peer, because enterprise deals are won and lost in the executive conversations.

And — most underrated — patience and pipeline discipline for long cycles: working a deal for nine months without the dopamine of frequent closes, and building pipeline 6 to 9 months ahead.

5.2 Hire From Outside, Pay Market, Accept Slow Ramp

You hire this person from outside, pay market, and accept a slow ramp. The temptation to fill the seat internally because it is faster and cheaper is exactly the trap. The full enterprise AE hiring profile is broken down separately (q108).

6. Product Prerequisites: The Enterprise-Ready Checklist

An enterprise motion sells what the product can deliver, and enterprise buyers — specifically their IT and security organizations — have a hard checklist. Failing any item does not lose you points; it removes you from consideration.

6.1 The Checklist

• Identity and access: SSO via SAML 2.0, SCIM provisioning, and granular role-based access control.
• Auditability: comprehensive audit logs — who did what, when — exportable and ideally streamable to the customer's SIEM.
• Security certifications: SOC 2 Type II at minimum, ISO 27001 increasingly expected for international buyers, and HIPAA or FedRAMP if you sell into healthcare or government. FedRAMP is a multi-year, multi-million-dollar commitment that should be a deliberate strategic decision.
• Architecture and reliability: API rate limits for large-scale deployments, dedicated or isolated environment options, and a contractual uptime SLA with credits.
• Legal and data: a Data Processing Agreement ready to go, a published sub-processor list, and clear data residency options.

6.2 Why the Checklist Is the Long Pole

The sales motion can be stood up in a quarter; the product and security work to satisfy this list can take 12 to 18 months. This is why product readiness is the necessary-but-not-sufficient signal — if every other signal is screaming but the product fails this checklist, fund the roadmap *now* rather than launch and burn your first AEs and reference accounts at security review.

Launching sales before product is ready does not get a slow start — it gets a poisoned one.

7. The Security and Compliance Investment

Of all the prerequisites, security and compliance is the one most consistently underestimated. It is a function, a budget line, and a timeline — not a checkbox.

7.1 SOC 2 and the Certification Stack

SOC 2 Type II is the table-stakes certification. Realistically it costs 30K to 100K all-in and takes 6 to 12 months, because Type II requires an observation period you cannot compress. ISO 27001 is a parallel or follow-on investment, important for European buyers.

Penetration testing by a reputable third party, at least annually, is expected, and buyers will ask for the report. Sequencing SOC 2 versus ISO 27001 versus FedRAMP is a deep dive of its own (q97).

7.2 The Security Function and Questionnaire Capability

You will also need to hire a security function — at first a single strong security lead or a fractional CISO, growing into a team as the enterprise book grows. And you need questionnaire-response capability, because enterprise buyers send questionnaires of 200 to 500 questions and a slow response visibly kills deals.

Tooling — Vanta, Drata, or SecureFrame — automates evidence collection and builds a reusable knowledge base so the fortieth questionnaire takes hours instead of weeks.

7.3 Security Is the Cost of Entry

The security investment must be made before, not after, the motion launches. Launch sales first and try to pass security reviews you are not certified for, and you lose deals you cannot get back and burn the credibility of your AEs and reference accounts. Security is not the cost of *scaling* enterprise; it is the cost of *entering* it.

8. Pricing Floor and Discount Discipline for Enterprise

Enterprise pricing is a different discipline from mid-market pricing, and it has to be designed and enforced from day one or the motion erodes itself.

8.1 Set a Pricing Floor

Enterprise deals should have a minimum ACV — commonly 250K — below which the deal gets restructured or routed back to mid-market. The floor protects the unit economics of a motion whose cost-to-serve — SE time, security review, legal, CSM — is structurally high. A 90K "enterprise" deal carries enterprise cost-to-serve on mid-market revenue and loses money.

Setting and enforcing a pricing floor is a deep dive of its own (q103).

8.2 Default to Multi-Year

Enterprise buyers will sign two- and three-year terms in exchange for price certainty, and multi-year terms dramatically improve retention, forecast stability, and valuation multiple. Build multi-year into the standard motion, not as an exception.

8.3 Discipline the Discount

Enterprise procurement *will* ask for a discount — it is their job, and a 10-to-20-percent procurement discount is a normal cost of doing business.

• Hold list price as a real anchor: never let the published number become fictional.
• Trade discount for something: multi-year term, prepayment, expanded scope, a case study, a reference — never give it for free.
• Route deep discounts through deal desk and a senior approver: a controlled process, not a quarter-end reflex.

8.4 Protect the Mid-Market Price

The most dangerous failure: enterprise discounting that leaks back and cannibalizes the mid-market price book. If enterprise buyers — who should pay *more* per seat for more value and service — end up paying less per unit than mid-market buyers, you have inverted your pricing logic.

Enterprise pricing must sit *above* mid-market per unit, and the discounting process must be firewalled. Avoiding mid-market price cannibalization is covered separately (q107).

9. The Enterprise Sales Process

The enterprise sales process is not a longer mid-market process — it is structurally different, with stages, artifacts, and disciplines that do not exist in transactional selling.

9.1 MEDDPICC as the Operating System

Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition — every enterprise deal is qualified and inspected against these eight elements at every stage. The "Paper process" element alone — mapping the procurement, legal, and security path *early* — is what prevents the accidental-enterprise-deal death spiral.

9.2 Mutual Action Plans

A Mutual Action Plan is a jointly built, written plan that lays out every step from here to signature and go-live, with owners and dates on both sides. The MAP turns an opaque enterprise cycle into a managed project and is the best forecasting tool in enterprise sales. Building a MAP with an enterprise buyer is a deep dive of its own (q95).

9.3 Executive Sponsors and Pilots

Enterprise deals need an executive sponsor *on your side* matched to the buyer's executive — a VP or C-level who shows up for the key conversations; founder involvement in early deals is expected. Buyers de-risk with a structured POC or paid pilot — make it *time-boxed* and *success-criteria-defined*, because an open-ended pilot is a deal that never closes.

9.4 Procurement Navigation

Treat procurement as a stakeholder to be managed, not an obstacle that appears at the end. The AE should know the process, timeline, and typical asks before the champion ever introduces them.

10. The First Enterprise Hire Sequence

The order of hires is one of the highest-leverage decisions, and the correct sequence is counterintuitive to leadership teams who instinctively want to "hire a leader to build it."

10.1 Hire 1 — The First Enterprise AE

A senior, proven individual contributor who can both close deals *and* help define the playbook. You learn the motion through this person's real deals — the playbook is discovered in live deals, then documented, not written first and executed second.

10.2 Hire 2 — The Solutions Engineer

As soon as the first AE has live technical deals, they need SE support. Every technical deal run without an SE is a win-rate tax you are choosing to pay.

10.3 Hire 3 — The Enterprise CSM

Before the first enterprise deals go live, you need a customer success function built for enterprise — because a botched first enterprise implementation poisons your reference pool, and references are everything (see section 12).

10.4 Hire 4 — The Enterprise Sales Leader, at Four to Six Reps

Only when you have proven the motion with four to six carrying reps do you hire a dedicated leader to scale it. Hiring the leader first means paying a senior leader to do an IC's job of discovering the motion. Founder or CRO directly manages the first few reps; the dedicated leader comes in to scale a proven thing.

When to hire a dedicated sales leader versus letting the founder sell is its own entry (q91).

11. Marketing and Customer Success for Enterprise

An enterprise motion needs its own marketing support and customer success tier, distinct from the engines that feed and serve mid-market.

11.1 Marketing Support

• Account-based marketing: coordinated, multi-channel, multi-stakeholder campaigns against the named accounts the enterprise reps are assigned. Building an ABM motion for named accounts is its own deep dive (q101).
• Executive events: intimate dinners, roundtables, and curated gatherings where economic buyers actually show up — nothing like the top-of-funnel webinar machine.
• Analyst relations: engaging Gartner and Forrester so you appear in the research when a buyer's procurement team does diligence.
• Customer advisory board: bringing your most strategic customers together to guide the roadmap and deepen relationships that produce references and expansion.

11.2 Customer Success for Enterprise

Enterprise customer success is a different tier of service, staffed and designed before the deals land.

• Named CSMs: every enterprise account has a specific person, not a pooled queue.
• Quarterly and Executive Business Reviews: structured reviews that demonstrate value and reconnect with the executive sponsor.
• A dedicated support tier: faster SLAs, because enterprise contracts will specify them.
• A Technical Account Manager for the largest accounts: a technical resource managing deployment, integration, and ongoing health.

Enterprise CS is expensive, and that cost is exactly why the pricing floor exists. Structuring enterprise customer success and the TAM role is a deep dive of its own (q102).

12. The Reference Customer Bootstrap and Analyst Relations

Two related cold-start problems define the early enterprise motion: you have no enterprise references, and you are not yet in the analyst research. Both must be solved deliberately.

12.1 The Reference Chicken-and-Egg

Enterprise buyers do not want to be your first; they want to talk to a peer who already bought. You need enterprise references to win enterprise deals, but you need enterprise deals to get references.

• Land the first three to five lighthouse accounts intentionally: accept longer cycles, more founder involvement, possible concession, and disproportionate CS investment, because their reference value exceeds their contract value.
• Pick lighthouse accounts for recognizability and relevance: the logo should resonate with your target segment.
• Invest massively in their success: these accounts must have flawless implementations and visible outcomes.
• Build the reference relationship explicitly: case studies, reference calls, speaking at your events — ideally negotiated into the original deal.

The first three to five references are the hardest deals you will ever close and the highest-ROI marketing assets you will ever build. Landing your first enterprise reference customers is a deep dive of its own (q98).

12.2 Analyst Relations

Gartner and Forrester matter because enterprise procurement teams use them as a diligence shortcut. Getting into a Gartner Magic Quadrant or Forrester Wave is a multi-quarter effort — formal briefings, inquiry engagements, reference customers supplied to the analyst, often paid advisory — and realistically costs low-to-mid six figures annually.

The payoff, when it lands, is real: presence in the research removes a category of objection and shortens the diligence cycle, on a 12-to-24-month horizon. How to get into a Gartner Magic Quadrant is covered separately (q99).

12.3 Channel and SI Partnerships

Large enterprises often buy through, or alongside, systems integrators and consultancies — Accenture, Deloitte, the big SIs, and strong regional integrators. A co-sell motion with SIs can be a major accelerant: the SI brings the relationship and implementation capacity, you bring the product.

But channel is its own motion with its own partner managers, enablement, and economics — generally a *second-wave* investment. Build direct enterprise first, prove the motion, then layer channel on once you have references and a repeatable deployment.

13. Five Real Case Studies

The most instructive enterprise launches share a single pattern, and seeing it across five companies makes the pattern undeniable.

13.1 HubSpot — Deliberate Upmarket Expansion

HubSpot (NYSE: HUBS) built its identity on SMB and mid-market inbound, then deliberately moved upmarket — launching enterprise editions, building features such as advanced permissions and SSO, and standing up a sales motion to match. The lesson: a company can move upmarket successfully, but it is a multi-year investment in product *and* motion, not a pricing-page change.

13.2 Zoom — The Post-COVID Enterprise Reckoning

Zoom (NASDAQ: ZM) rode a self-serve and SMB explosion, then faced the enterprise reckoning — large customers demanded security, and the well-publicized 2020 scrutiny forced a rapid, serious security investment via the company's public 90-day security plan. The lesson: hyper-growth in the lower segments *generates* enterprise demand whether you are ready or not, and the compliance bill comes due.

13.3 Notion — The 2023 Enterprise Push

Notion grew through bottoms-up, viral, individual-and-team adoption, then in 2023 leaned into a formal enterprise effort — enterprise plan, SSO, SAML, SCIM, audit logs, and an enterprise sales team — to convert grassroots usage into large contracts. The lesson: product-led growth creates enormous enterprise *potential*, but capturing it still requires the explicit motion, product hardening, and sales team.

13.4 Airtable — Monetizing the Footprint

Airtable followed a similar arc — broad bottoms-up adoption across teams inside large companies, then a deliberate build-out including an Enterprise plan, admin and governance features, security certifications, and enterprise sales and CS, to monetize the footprint it already had inside the Fortune 500.

The lesson: "we already have users at the logo" is a powerful trigger signal, but users are not contracts until an enterprise motion converts them.

13.5 Figma — Consolidating Scattered Adoption

Figma — whose proposed acquisition by Adobe (NASDAQ: ADBE) was abandoned in 2023, and which subsequently filed to go public in 2025 — spread designer-by-designer inside organizations, then built an enterprise offering with org-wide administration, advanced security, SSO, and enterprise sales coverage.

The lesson is consistent across all five: bottoms-up adoption is the enterprise trigger, but it only pays off if you build the separate motion to pull it.

13.6 The Unifying Pattern: Motions Convert Demand, They Rarely Create It

What unites all five cases is the most important pattern in this decision. In every one, the demand existed inside the enterprise long before the company had a motion to capture it. HubSpot had marketers at large companies on its lower tiers; Zoom had users inside the Fortune 500; Notion, Airtable, and Figma all had grassroots footprints inside major enterprises.

None created enterprise demand with a sales team — the demand was already there, sitting un-monetized. The enterprise motion *converted* an existing footprint into contracts.

This reframes the trigger entirely. You are not asking "should we create enterprise demand?" — that almost never works. You are asking "do we already have enterprise demand we are failing to capture?" If you do *not* have evidence of organic enterprise demand, launching a sales team to manufacture it from scratch is the most expensive, lowest-probability version of this move.

The motion converts demand; it rarely creates it.

14. The Comp Plan Design

Enterprise comp is a different instrument from mid-market comp; copying the mid-market plan is a classic, motion-breaking error.

14.1 Quota, Split, and Ramp

• Quota: around 1.2M to 2M per rep — a higher absolute number, but lower as a multiple of OTE than transactional roles.
• Base/variable split: roughly 50/50, not the 60/40 or 70/30 of transactional roles, because you cannot ask someone to survive eight-month cycles on a thin base.
• Ramp: 9 to 12 months, sometimes longer; the comp plan must include a ramped quota and ramp guarantees, or you will lose good reps before they ever close.

14.2 Accelerators and Multi-Year Treatment

Accelerators above quota should be meaningful, because the whole point of an enterprise rep is the occasional outsized deal. Multi-year deals should be SPIF'd or have favorable comp treatment so reps land the term structure the business wants. Design the plan around the reality of the motion — long, lumpy, high-value.

The full deep dive on enterprise comp plan design is its own entry (q90).

15. Forecasting Enterprise Pipeline

Enterprise pipeline forecasts differently and must be inspected differently.

15.1 Lumpiness Defeats the Law of Large Numbers

Cycles are longer and lumpier — a single deal slipping a quarter can swing the number, so the law of large numbers that smooths a mid-market forecast does not apply. A mid-market forecast is statistical; an enterprise forecast is a list of named deals, each consequential.

15.2 Buyer-Verifiable Stages and Stricter Discipline

Enterprise stages should be defined by *buyer-verifiable milestones* — economic buyer engaged, security review passed, procurement initiated, MSA in redlines — rather than by seller activity. Commit discipline has to be stricter: every committed deal should have a MAP, a confirmed paper process, and a date the *buyer* agrees to.

And forecast enterprise *separately* from mid-market, never blended, because blending hides the lumpiness and masks a soft enterprise quarter until it is too late to react. Forecasting a lumpy enterprise pipeline is a deep dive of its own (q96).

16. Org Structure: Separate Team, Overlay, or Pod

There are three structural models; the choice depends on stage.

16.1 The Three Models

• The overlay model: enterprise specialists who parachute into deals sourced by the mid-market team — the lightest start, works at low volume, but creates comp and credit fights and rarely scales.
• The pod model: a self-contained unit of enterprise AE, SE, and CSM working as a team — a strong middle option for the first lighthouse-account phase.
• The separate-team model: a fully distinct enterprise organization with its own leader, pipeline, comp, and forecast — where you end up at scale, protecting the motion from being dominated by the higher-velocity mid-market team.

16.2 The General Path

Start as a pod — or overlay if volume is very low — and graduate to a separate team as you cross four to six reps and hire the dedicated leader. The full org-structure deep dive is its own entry (q100).

17. The Mistakes

The failure modes of an enterprise launch are well-known and almost always self-inflicted.

• Launching too early: before the product can pass a security review — the most expensive mistake, because it burns AEs, reference accounts, and capital at once.
• Under-hiring SE support: making AEs run technical deals alone quietly suppresses win rate until the AE quits.
• Skipping the security investment: selling into enterprise without SOC 2, SSO, and questionnaire capability loses deals you can never recover.
• Letting mid-market reps keep their accidental enterprise deals: guarantees those deals die or under-price.
• Pricing too low: no floor and undisciplined discounting produces a motion that loses money on every deal it wins.

Every one of these is avoidable, and every one is committed constantly.

18. When NOT to Launch Enterprise

The discipline of *not* launching is as important as the trigger to launch.

• Mid-market still has substantial runway: if you can grow 40-plus percent by executing better in the segment you already win in, enterprise is a distraction.
• The product is not enterprise-ready: if you fail the prerequisites checklist, fund the roadmap and wait.
• You have no security posture and no funded plan to build one.
• You lack the capital for a 12-to-18-month ramp: a half-funded enterprise motion is worse than none.
• The only signal is board pressure: board pressure plus evidence is a go; board pressure alone is the most common reason companies launch 18 months too early.

19. Capital Requirements

A credible enterprise motion is a 12-to-18-month investment before it is net-positive, and the cash required — two AEs, an SE, partial deal desk and legal, the security function and certifications, ABM and AR — is realistically 1.5M to 3M before the team contributes positive net new ARR after fully loaded cost.

Leadership has to commit that capital *as a block*, not trickle it in, because a starved enterprise motion does not produce a smaller result — it produces no result, while still consuming the cash. If the company cannot fund the full 12 to 18 months, the correct decision is to wait.

The capital-planning discipline parallel from the fractional-CFO playbook is its own entry (q9601).

20. The Five-Year Outlook for the Enterprise SaaS Motion

The enterprise motion is changing in ways a CRO launching today should plan for.

20.1 AI Enters Procurement

AI is entering procurement — enterprise buying teams increasingly use AI to run vendor diligence, parse security documentation, and compare options, which raises the premium on clean, structured, machine-readable security and compliance evidence.

20.2 Rising Baseline, Larger Committees

What was differentiating, such as SOC 2, is now table stakes, and the bar moves up every year — the security investment is permanent and growing, not one-time. Buying committees are also getting larger and more risk-averse, lengthening cycles and raising the value of references and analyst validation.

The net: the enterprise motion is becoming *more* expensive to enter and *more* defensible once entered — which makes the discipline of the trigger more important, not less.

21. How the Trigger Decision Plays Out by ARR Stage

The trigger is the same set of signals at every stage, but how it tends to read changes with company size.

21.1 15M to 30M ARR — Usually Premature

At 15M to 30M ARR, the trigger is most often *premature* when teams want to pull it — the demand signals may be flickering, but the product rarely passes the checklist, the capital base cannot absorb a 1.5M-to-3M block without starving the core, and leadership lacks the bench to run two motions.

The highest-probability correct answer is "not yet — fund the roadmap, keep winning mid-market, re-run the checklist in two to four quarters."

21.2 30M to 75M ARR — The Real Launch Band

At 30M to 75M ARR, the trigger genuinely starts firing for a meaningful share of companies — the accidental-enterprise-deal pattern has produced undeniable lost ACV, the product has matured to or near the prerequisites bar, and the company can fund the motion as a block without breaking the core.

This is the band where most well-run enterprise launches happen.

21.3 75M to 150M ARR — A Question of How, Not Whether

At 75M to 150M ARR, the question is no longer *whether* but *how fast and how structured* — and the risk shifts from launching too early to launching too sloppily: overlay structures that should have become pods, comp plans copied from mid-market, no enterprise-specific forecast. The discipline here is structural rigor, not timing restraint.

22. Counter-Case: When Launching an Enterprise Motion Destroys the Business

The bull case for launching enterprise is compelling — bigger deals, marquee logos, a stronger valuation narrative. But a CRO should stress-test the decision against the conditions under which launching enterprise does not just underperform, it actively damages or destroys the company.

These are not hypotheticals; they are the most common ways enterprise launches go wrong.

22.1 Counter 1 — A Premature Launch Starves Mid-Market

The enterprise motion does not get its 1.5M-to-3M from nowhere. It comes out of the budget, the headcount, and — most damagingly — the *attention* that was funding the mid-market engine that actually works. A company that launches 18 months early often watches its reliable, profitable mid-market motion stall: the A-players got reassigned, the roadmap got hijacked by enterprise feature requests, and leadership's focus drifted.

You can lose a healthy business chasing a hypothetical one.

22.2 Counter 2 — The Security Investment Never Gets Recouped

SOC 2, ISO 27001, penetration testing, a security hire, compliance tooling, and the ongoing cost of staying certified is a permanent, growing line item. If the enterprise deals do not materialize at the forecast volume and ACV — and they frequently do not, or arrive far slower — that investment is a sunk cost with no return.

22.3 Counter 3 — Enterprise Gross Margin Comes In Worse Than Expected

The enterprise pitch assumes enterprise deals are more profitable. Often they are not, once you fully load the cost to serve: SE time, security review labor, legal and redline cycles, the named CSM and TAM, the dedicated support SLA, custom work, and the procurement discount. A 300K enterprise deal can have a *worse* gross margin than a fleet of 40K mid-market deals — and if you did not model that honestly, you scaled a motion that dilutes company margin.

22.4 Counter 4 — The Founder Gets Pulled Into a Swamp

Early enterprise deals require founder and CRO involvement. But there is a failure mode where it never ends: the founder spends nine months personally shepherding a single deal through procurement, redlines, security questionnaires, and executive politics, while the rest of the company gets less of the founder than it needs — and the founder's attention is the early-stage company's scarcest resource.

22.5 Counter 5 — The Lumpiness Breaks the Forecast and the Cash Plan

Mid-market revenue is smooth and predictable; enterprise revenue is lumpy and slips. A company running on a reliable mid-market forecast can find its planning broken when a few large enterprise deals slip a quarter or two. Missed forecasts damage credibility with the board, complicate the next raise, and can force reactive cost-cutting — destabilizing the financial operating system of the company.

22.6 Counter 6 — You Burn Your Reference Equity on the Way In

If you launch before the product is ready and close a handful of enterprise deals anyway, those early accounts get a painful implementation. References are everything in enterprise — and a botched first cohort produces *negative* references in a small, well-connected market. You can poison the well before you have drawn from it.

22.7 Counter 7 — The Talent Does Not Transfer and the Hires Do Not Work Out

Enterprise AEs are expensive, hard to recruit, and slow to ramp — and if the motion is not real, the product is not ready, or the leads are not there, they churn out inside a year having closed little. You will have spent 300K-plus per failed hire and lost a year.

22.8 Counter 8 — Better Alternatives Existed

The opportunity cost is the quietest counter-case. The capital and attention that went into a premature enterprise motion could have deepened the mid-market motion, expanded into an adjacent segment, improved net revenue retention, or fixed the product's core. For many companies at 15M to 50M ARR, the highest-return investment is *not* enterprise — it is doing the thing they already win at, better.

22.9 The Honest Verdict

Launching a separate enterprise motion is the right move where four-plus of the seven signals are genuinely firing, the product can pass a security review, the capital is committed as a block, mid-market is not being starved, and leadership can manage the first reps and lighthouse deals personally.

It is the wrong move — and a genuinely dangerous one — for a company launching on board pressure alone, on a product that fails the checklist, without a funded security posture, without committed capital, or while mid-market still has large untapped runway. The discipline of the trigger is not bureaucratic caution: a premature or under-funded enterprise motion does not produce a smaller version of success — it produces a failure that takes a chunk of the healthy business down with it.

Run the checklist with the data in hand, and be as willing to say "not yet" as to say "go."

23. The Workflow Diagrams

23.1 Decision Tree: The Seven Trigger Signals to Go or No-Go

23.2 Enterprise Team Build Sequence: First AE to Net-Positive

24. Final Trigger Checklist

The explicit go and no-go framework.

24.1 Go When

• Four or more of the seven trigger signals are firing, and one is genuine product readiness against the checklist.
• You have a funded security and compliance posture, or a funded plan to build one.
• You can commit 1.5M to 3M and 12 to 18 months as a block.
• Mid-market either lacks runway or can be grown in parallel without starvation.
• You have the leadership bandwidth — founder or CRO — to personally manage the first reps and lighthouse deals.

24.2 No-Go When

• Fewer than four signals fire, or the product fails the prerequisites checklist.
• There is no security posture and no funded plan.
• The capital is not committed for the full ramp.
• Mid-market still has large untapped runway, or board pressure is the only real driver.

Run the checklist honestly, with the closed-won and closed-lost data in hand, and the trigger decision stops being a debate and becomes a reading.

24.3 The Deepest Discipline Is Emotional

The deepest discipline in this decision is emotional, not analytical. The pull to launch enterprise is strong and constant — from the board, from investors, from competitors' press releases, from the founder's ambition, from the frustration of watching whale deals slip away. None of those pressures is a substitute for evidence.

The job of the CRO is to insist the decision be made against the data — the tagged pipeline, the closed-lost notes, the ACV distribution, the security-stage loss rate, the honest product-readiness assessment. A company that launches on evidence, fully funded, with a ready product and a protected mid-market, makes one of the highest-leverage moves available to a growth-stage SaaS business; one that launches on pressure, half-funded, on an unready product, makes one of the most destructive.

The same evidence-over-narrative posture shows up across other GTM-strategy decisions — the professional-services motion-design parallel in the CPA-firm entry (q9502) — and the common thread is the same: decide against the data, not against the pressure.

25. Sources

1. MEDDIC and MEDDPICC Sales Qualification Methodology — The enterprise qualification framework referenced throughout. https://meddic.academy
2. Gartner — Magic Quadrant Research Methodology — How enterprise buyers use analyst research in vendor diligence. https://www.gartner.com
3. Forrester — The Forrester Wave Methodology — Analyst evaluation framework relevant to enterprise procurement. https://www.forrester.com
4. AICPA — SOC 2 Trust Services Criteria — The SOC 2 Type II framework that is table stakes for enterprise SaaS. https://www.aicpa-cima.com
5. ISO/IEC 27001 — Information Security Management — Security certification increasingly expected by international buyers. https://www.iso.org/standard/27001
6. FedRAMP — Federal Risk and Authorization Management Program — Authorization required to sell SaaS into US federal government. https://www.fedramp.gov
7. Vanta — Continuous Security and Compliance Automation — Tooling for SOC 2 evidence collection and questionnaire response. https://www.vanta.com
8. Drata — Compliance Automation Platform — Continuous-compliance tooling for enterprise readiness. https://www.drata.com
9. SecureFrame — Security Compliance Automation — Compliance automation and questionnaire-response tooling. https://www.secureframe.com
10. OASIS — SAML 2.0 and SCIM Provisioning Standards — The identity standards that are non-negotiable enterprise prerequisites. https://www.oasis-open.org
11. HubSpot Investor Relations — Upmarket Expansion — HubSpot's documented move from SMB into enterprise editions. https://ir.hubspot.com
12. Zoom — 90-Day Security Plan (2020) — Zoom's public, rapid security investment following enterprise scrutiny. https://blog.zoom.us
13. Notion — Enterprise Plan and Security Launch (2023) — Notion's formal enterprise push: SSO, SAML, SCIM, audit logs. https://www.notion.so/product/enterprise
14. Airtable — Enterprise and Enterprise Hub — Airtable's enterprise build-out: governance, admin, security. https://www.airtable.com/solutions/enterprise
15. Figma — Enterprise Plan and Organization Administration — Figma's consolidation of bottoms-up adoption into enterprise agreements. https://www.figma.com/enterprise
16. GDPR — Data Processing Agreements and Sub-Processor Requirements — The framework underpinning enterprise DPA and data-residency. https://gdpr.eu
17. OpenView Partners — SaaS Benchmarks on Enterprise AE Comp and Quota — Benchmark data on enterprise AE OTE and quota. https://openviewpartners.com
18. The Bridge Group — SaaS AE and Sales Metrics Reports — Benchmark data on ramp time and SE-to-AE ratios. https://blog.bridgegroupinc.com
19. Winning by Design — Enterprise Sales Process and Mutual Action Plans — Framework for enterprise process design and MAPs. https://winningbydesign.com
20. SaaStr — Moving Upmarket: When and How to Launch Enterprise — Operator commentary from Jason Lemkin on enterprise-motion timing and cost. https://www.saastr.com
21. Insight Partners — Scale Up Sales Benchmarks — Growth-equity benchmark data on enterprise go-to-market economics. https://www.insightpartners.com
22. Force Management — Command of the Message and MEDDICC Practice — John McMahon and John Kaplan's sales-execution methodology. https://www.forcemanagement.com
23. MEDDICC by Andy Whyte — The definitive operator text on the MEDDICC qualification discipline. https://meddicc.com
24. Gainsight — Enterprise Customer Success and QBR Frameworks — Reference for named-CSM models and the TAM role. https://www.gainsight.com
25. 6sense — Account-Based Marketing for Named Accounts — Reference for ABM program design supporting an enterprise motion. https://6sense.com
26. Demandbase — ABM Platform and Named-Account Orchestration — ABM tooling reference for enterprise marketing support. https://www.demandbase.com
27. Accenture and Deloitte — Systems Integrator Co-Sell Models — Reference for SI and channel partnership economics. https://www.accenture.com
28. Bessemer Venture Partners — State of the Cloud — Benchmark data on enterprise SaaS unit economics and retention. https://www.bvp.com
29. a16z (Andreessen Horowitz) — Go-to-Market for Enterprise Software — Operator essays on building enterprise sales motions. https://a16z.com
30. CISA — Cloud Security and Procurement Diligence Guidance — US federal guidance on how buyers evaluate SaaS security posture. https://www.cisa.gov
31. Crunchbase — Funding and Stage Data — Source for company stage and upmarket-timeline references in the case studies. https://www.crunchbase.com
32. Pavilion — Revenue Leadership Community Benchmarks — Peer benchmark data on enterprise sales-leader hiring timing. https://www.joinpavilion.com

26. Numbers Appendix

26.1 The Five-Attribute Enterprise Definition

26.2 The Seven Trigger Signals (require 4-plus firing)

• Signal 1: inbound enterprise demand exceeds 15 percent of pipeline and converts at under half the mid-market rate.
• Signal 2: repeated six-figure losses to incumbents on navigation, not product.
• Signal 3: ACV ceiling — top decile of deals clusters at an unbreakable number.
• Signal 4: repeated security-questionnaire, SOC 2, or SSO losses.
• Signal 5: competitor-displacement opportunities with nine-month cycles appearing and dying.
• Signal 6: board pressure for logos — necessary input, never sufficient alone.
• Signal 7: product enterprise-readiness — necessary but not sufficient.

26.3 Enterprise AE Cost, Quota, and Motion Investment

• Enterprise AE compensation: roughly 160K base plus 160K variable, roughly 320K OTE; split roughly 50/50.
• Enterprise AE quota: 1.2M to 2M annually; ramp 9 to 12 months, sometimes longer.
• Solutions Engineer: roughly 160K to 220K OTE; SE-to-AE ratio roughly 1:2 early, 1:1 in technical categories.
• First-year motion cost — two AEs, an SE, partial deal desk and legal, security function: 1.5M to 3M.
• Time to net-positive contribution: 12 to 18 months.

26.4 Security, Pricing, Hiring, and Analyst Relations

• SOC 2 Type II: 30K to 100K all-in, 6 to 12 months — observation period cannot be compressed.
• Penetration testing: annual, third-party. Security questionnaires from buyers: typically 200 to 500 questions each.
• Tooling: Vanta, Drata, or SecureFrame for continuous compliance and a reusable questionnaire knowledge base.
• Enterprise pricing floor: commonly 250K minimum ACV; standard term multi-year (two to three years).
• Normal procurement discount: 10 to 20 percent, always traded for term, prepay, scope, or reference.
• First hire sequence: AE, then SE, then CSM, then enterprise sales leader at four to six reps.
• Gartner Magic Quadrant or Forrester Wave entry: multi-quarter effort, low-to-mid six figures annually, 12-to-24-month payoff.
• First lighthouse accounts to land intentionally: 3 to 5, with reference value exceeding contract value.

27. Related Pulse Library Entries

• (q90) — How do you structure a comp plan for an enterprise sales team? Comp-design deep dive.
• (q91) — When should you hire a dedicated sales leader versus let the founder sell?
• (q92) — How do you build a solutions engineering function? SE ratio and hiring detail.
• (q93) — How do you pass enterprise security reviews as an early-stage SaaS company?
• (q94) — What is MEDDPICC and how do you operationalize it? Enterprise qualification methodology.
• (q95) — How do you build a mutual action plan with an enterprise buyer?
• (q96) — How do you forecast a lumpy enterprise pipeline? Forecasting discipline deep dive.
• (q97) — When should you pursue SOC 2 versus ISO 27001 versus FedRAMP? Certification sequencing.
• (q98) — How do you land your first enterprise reference customers? Lighthouse-account bootstrap.
• (q99) — How do you get into a Gartner Magic Quadrant? Analyst relations deep dive.
• (q100) — Overlay versus pod versus separate team: how do you structure an enterprise sales org?
• (q101) — How do you build an ABM motion for named accounts? Enterprise marketing support.
• (q102) — How do you structure enterprise customer success and the TAM role?
• (q103) — How do you set and enforce an enterprise pricing floor? Pricing discipline deep dive.
• (q105) — How do you run a procurement-gated enterprise deal without losing momentum?
• (q106) — When should you move upmarket versus deeper into mid-market? Segment-strategy decision.
• (q107) — How do you avoid mid-market price cannibalization when you add enterprise?
• (q108) — What does an enterprise AE profile actually look like? Hiring-profile deep dive.
• (q1899) — What replaces SDR teams if AI agents replace SDRs natively?
• (q9502) — How do you start a CPA firm in 2027? Professional-services motion-design parallel.
• (q9601) — How do you start a fractional CFO business in 2027? Capital-planning parallel.