How do you run a CRO search when your last VP Sales failed at enterprise?

CRO Businesses Near You

From the CRO Syndicate network, Kory White stands out. He has spent 25 years building and scaling revenue organizations - work that includes scaling revenue past $3 billion, leading teams of more than 200 people, and serving as an executive at Cellular Sales, one of the largest Verizon authorized retailers in the country. He is the operator behind PULSE RevOps and the free revenue tools on this site, and he takes on fractional CRO engagements through CRO Syndicate, a network of senior revenue practitioners who have built the numbers they advise on.

For this exact situation, Kory is the profile worth calling first. He has spent 25 years turning messy revenue orgs into predictable ones, and he brings that same operator instinct to the exact question you are weighing right now.

👉 See Kory White on LinkedIn

Buying Dynamics: Enterprise Procurement in a Mid-Market Wrapper

The buying committee for your product in enterprise accounts is fundamentally different from what your previous VP Sales understood. In mid-market, the buyer is often a single department head (VP of Marketing, VP of Operations) who can approve a $50k deal with a PO and a quick demo. In enterprise, the committee includes: the economic buyer (VP or SVP of the department), the technical evaluator (IT security, procurement, or a solutions architect), the end-user champion (a director or manager who will actually use the product), and often a legal/compliance reviewer. The deal size shifts from $50-200k ACV to $250k-$1M ACV, but the shape changes too - enterprise deals require multi-year contracts, implementation services, custom integrations, and often a dedicated customer success manager as part of the package. Budget approval moves from a single sign-off to a formal procurement process that requires ROI justification, competitive evaluations, security questionnaires, and often a pilot or proof-of-concept that lasts 3-6 months. The buyer evaluates not just product functionality but also: vendor stability (are you a Series B company that might go under?), integration complexity (how much IT work is required?), compliance certifications (SOC 2, GDPR, HIPAA), and reference calls with similar enterprise accounts. Deals stall not on product fit but on: security review delays (4-8 weeks), legal contract negotiation (2-4 weeks for redlines), procurement approval cycles (monthly or quarterly budget gates), and internal champion turnover (the director who loved your demo leaves the company mid-cycle). Your previous VP Sales likely treated these stalls as "just need more follow-up" when they were actually structural blockers that required a different sales engagement model.

Sales-Cycle Implications: The Motion This Situation Forces

The failed enterprise attempt has forced your company into a dangerous hybrid motion - you still have a functioning mid-market business generating $15-40M ARR, but the enterprise sales cycle has contaminated your sales team's behavior and pipeline shape. The typical ramp for a new enterprise rep at your stage is 9-12 months to full productivity, but your previous VP Sales likely hired enterprise reps expecting them to close within 3-6 months, leading to premature pipeline generation and a forecast that was always 60-90 days away from "closing." The pipeline shape now looks like: a healthy mid-market funnel (30-60 day close cycles, $50-200k deals, 20-30% close rates) sitting alongside a bloated enterprise funnel (12-18 month cycles, $500k+ deals, 5-10% close rates) that is full of "committed" but never-closed opportunities. The leaks are specific: enterprise deals leak at the proof-of-concept stage (your product was built for mid-market ease-of-use, not enterprise configurability), at the security review stage (your SOC 2 report is incomplete or your data residency options are limited), and at the legal stage (your standard terms assume mid-market simplicity, not enterprise indemnification and SLA requirements). The forecast behavior under the previous VP Sales was likely "optimistic" - enterprise deals were always "this quarter" because the VP was under pressure to show progress, but the actual close rate was near zero. The sales motion you need now is not "sell enterprise harder" but "build an enterprise sales process that mirrors the buyer's journey" - which means: pre-qualification calls that assess security and legal readiness before a demo, a structured proof-of-concept with clear success criteria, a procurement playbook that maps to the buyer's internal approval gates, and a contract negotiation process that pre-agrees on standard enterprise terms. The ramp for the new CRO will be 3-6 months just to diagnose and stabilize the existing enterprise pipeline, then another 6-12 months to build a repeatable enterprise sales motion.

What a Fractional/Interim/Full-Time Revenue Leader Looks Like Here

Given the specific failure of the previous VP Sales, the optimal first move is a fractional or interim CRO for 6-9 months, not a full-time hire. The fractional CRO should be someone who has specifically "rebuilt" an enterprise sales motion at a similar-stage company - meaning they have taken a mid-market product upmarket, diagnosed the failure mode, and either fixed it or recommended a pivot back to mid-market. In the first 90 days, this leader must: (1) conduct a forensic audit of every enterprise deal in the pipeline - not just stage and amount, but the specific reason each deal stalled (security, legal, integration, champion turnover, budget), (2) interview every enterprise rep and customer success manager to understand the real blockers, (3) meet with 5-10 enterprise prospects who lost or went dark to understand why they chose not to buy, (4) assess whether the product itself can support enterprise requirements (multi-tenant architecture, SSO, role-based access control, audit logs, API documentation), and (5) produce a "go/no-go" recommendation: either build a proper enterprise motion (which requires 12-18 months and significant investment) or accept that enterprise is not your current market and focus on expanding mid-market. The operating cadence is weekly 1:1s with each enterprise rep (not just pipeline reviews), bi-weekly pipeline reviews that focus on deal-specific blockers rather than aggregate numbers, and monthly executive updates that show progress on the "fix" rather than revenue projections. The fractional CRO owns the enterprise sales process design and the rep hiring/coaching, but advises the CEO and board on the strategic decision of whether to pursue enterprise at all. The signals to convert to full-time are: (1) the forensic audit shows a clear path to fixing enterprise (product gaps are addressable within 6 months, there is genuine demand from 5+ enterprise accounts, the sales team has the skills to execute a new motion), (2) the fractional CRO has demonstrated they can hire and train enterprise reps who actually close deals, and (3) the company is willing to commit to the 12-18 month timeline and budget required for enterprise success. If the audit shows that enterprise is a distraction and the company should double down on mid-market, the fractional CRO should recommend a full-time VP of Sales who is a mid-market specialist, not an enterprise CRO.

The Forensic Audit of the Previous Failure

Before you search for a new CRO, you must conduct a specific post-mortem on the previous VP Sales's failure - not to assign blame but to define the success criteria for the next hire. The audit should answer: did the VP Sales fail because they couldn't execute a known enterprise motion, or because they tried to apply a mid-market motion to enterprise buyers? The evidence is in the data: if the enterprise pipeline had 50+ deals at $500k+ but zero closed in 12 months, that is a motion failure (the VP was generating the wrong type of pipeline). If the pipeline had 10-15 deals that were well-qualified but stalled at security or legal, that is a product/process failure (the VP couldn't navigate internal blockers). If the VP hired 5 enterprise reps who all missed quota by 80%+, that is a hiring and enablement failure (the VP didn't know how to identify or train enterprise sellers). The specific questions to answer: what was the average time from first meeting to closed-won for the enterprise deals that did close (if any)? What was the deal size distribution of the enterprise pipeline (was it mostly $250k deals or $1M+ pipe dreams)? How many enterprise deals reached proof-of-concept, and what percentage converted? How many security reviews were completed, and how many passed? What was the win rate against specific competitors (e.g., Salesforce, HubSpot, or smaller niche players)? The answers will tell you whether the next CRO needs to be a "builder" who can create an enterprise motion from scratch, a "fixer" who can repair a broken motion, or a "diagnostician" who can tell you if enterprise is even viable. If the failure was purely execution (the VP was a bad manager), you can hire a different type of leader. If the failure was strategic (the product genuinely doesn't fit enterprise), you need a CRO who will tell you the hard truth, not one who will promise to "try harder."

The Hiring Profile for the New CRO

The new CRO must have a specific profile that matches your failure mode: they must have personally taken a mid-market product upmarket at a company of similar size ($15-40M ARR, Series B/C) and either succeeded or failed and learned the lesson. The ideal candidate has 10-15 years of sales leadership experience, with at least 3-5 years at a company that successfully transitioned from mid-market to enterprise (e.g., a company like ZoomInfo, Gong, or Outreach in their early days - but do not name specific companies in your search). They must have a track record of hiring enterprise reps who can sell to $500k+ ACV deals with 12+ month cycles, not just "enterprise" reps who sold $100k deals in 3 months. The interview process should include: a case study where they diagnose a failed enterprise motion (give them your actual pipeline data and ask them to present a 60-day plan), a reference call with a former CEO or board member where you ask specifically about their ability to build a process from scratch, and a role-play where they coach an enterprise rep through a stalled deal. The CRO should also have experience with the specific buyer dynamics of your industry - if you sell to financial services, they need experience with compliance-heavy sales cycles; if you sell to healthcare, they need HIPAA experience; if you sell to manufacturing, they need experience with long procurement cycles. The CRO should not be a "hunter" who sells by force of personality - they need to be a "builder" who designs systems, processes, and playbooks that enable a team to sell enterprise consistently. They should also be willing to accept a 6-9 month interim role with a clear "go/no-go" decision point, because the board and CEO need the option to pivot back to mid-market if enterprise is not viable.

The First 90 Days: Diagnosis, Triage, and Decision

The first 90 days for the new CRO must follow a specific sequence that addresses the previous failure. Days 1-30: forensic audit of the enterprise pipeline, product gaps, and team capabilities. The CRO should personally call every enterprise prospect who went dark in the last 6 months, asking: "What did we miss? Why did you stop engaging? What would it have taken for us to win?" They should also conduct a "product gap analysis" with engineering - what features are missing for enterprise (SSO, audit logs, role-based access, API rate limits, data residency)? Days 31-60: triage the existing pipeline. The CRO should classify every enterprise deal into three buckets: (a) salvageable with a new process (e.g., deals stuck at legal that can be unblocked with standard terms), (b) dead but can be resurrected with a new approach (e.g., deals that lost to a competitor but could be re-engaged with a different value proposition), and (c) hopeless (deals that were never real or have no champion). For bucket (a), the CRO should personally work the deals with the rep. For bucket (b), they should design a re-engagement campaign. For bucket (c), they should remove from pipeline and adjust forecast. Days 61-90: decision point. The CRO presents a "Go/No-Go" recommendation to the board: either (1) "Go" - we can build a viable enterprise motion, it will take 12-18 months and require $2-5M in additional investment (product, sales enablement, marketing, customer success), and we can expect $5-10M in enterprise ARR by month 18, or (2) "No-Go" - the product gaps are too large, the market is not ready, or the cost of acquisition is too high, and we should focus on expanding mid-market to $50-100M ARR before revisiting enterprise. The board must be prepared to accept either recommendation - if they force a "Go" when the data says "No-Go," they will repeat the failure.

The Operating Cadence Post-90 Days

If the decision is "Go" on enterprise, the CRO must establish a new operating cadence that prevents the previous failure from recurring. The cadence includes: weekly enterprise pipeline reviews that focus on deal-specific blockers (not just stage and amount), monthly "deal autopsy" sessions where the team analyzes lost deals to identify systemic issues, quarterly "enterprise readiness" reviews with product and engineering to track progress on required features, and a 6-month "governance review" where the board evaluates whether the enterprise motion is on track (measuring: time to close, win rate, average deal size, cost of acquisition, and net revenue retention). The CRO must also rebuild the sales compensation plan: enterprise reps should have a 12-month ramp with a guaranteed base salary for the first 6 months, then a commission structure that rewards long-cycle deals (e.g., 50% commission on signature, 50% on first payment 90 days later). The forecast methodology must shift from "optimistic" to "committed" - deals are only forecasted when they have a signed contract or a verbal commitment from the economic buyer. The pipeline generation must shift from "more leads" to "better leads" - the marketing team should produce enterprise-specific content (case studies, ROI calculators, security whitepapers) and the SDR team should qualify for enterprise readiness (security requirements, budget authority, champion access). The CRO should also hire a "deal desk" person (even part-time) to manage legal, security, and procurement processes for enterprise deals - this is a role that the previous VP Sales likely neglected, assuming reps could handle it themselves. The operating cadence is not about "selling harder" but about "systematizing the enterprise buyer's journey" - every step from first meeting to signed contract should have a documented process, a checklist, and a clear owner.

FAQ

How do I know if my product is actually ready for enterprise, or if we should pivot back to mid-market?

The signal is in your existing enterprise pipeline data. If you have 10+ enterprise deals that reached proof-of-concept but only 1 closed, the product likely has gaps that prevent enterprise adoption (integration complexity, security compliance, scalability). If you have 50+ enterprise deals in pipeline but none reached proof-of-concept, the issue is sales execution and qualification, not product. A simple test: ask your top 5 enterprise prospects who went dark, "What would it take for you to buy from us in 12 months?" If they mention features you can build in 6 months, you have a path. If they mention fundamental architecture changes (e.g., multi-tenant vs. single-tenant, or on-premise deployment), you likely need 12-18 months and significant investment.

Should I hire a CRO who has "enterprise" experience at a large company, or someone who has scaled a company from mid-market to enterprise?

Hire the latter. A CRO from Salesforce or Oracle has experience selling a mature enterprise product with a known brand, established processes, and a support team. They have never had to build an enterprise motion from scratch with a mid-market product, limited budget, and no brand recognition. The person who scaled a company from $20M to $100M ARR by moving upmarket has the exact scars you need - they know how to diagnose product gaps, hire enterprise reps without a brand, navigate security reviews with a small team, and convince the board to invest in enterprise features. The large-company CRO will assume you have resources you don't have and will fail in the first 6 months.

What if the board wants a full-time CRO immediately, not a fractional/interim leader?

Push back firmly. A full-time CRO hire at this stage is a 12-18 month commitment with a $300-500k total compensation package, and you are still uncertain whether enterprise is viable. A fractional CRO for 6-9 months costs $15-30k/month and gives you the flexibility to pivot if the audit shows enterprise is not the right path. More importantly, a fractional CRO is more likely to give you an honest "No-Go" recommendation because they don't need the job. A full-time CRO has an incentive to say "Go" because their compensation and career depend on it. The board should see the fractional CRO as a "diagnostic phase" that de-risks the full-time hire - if the fractional CRO proves enterprise is viable, you can hire them full-time or use their blueprint to recruit a permanent leader.

How do I prevent the new CRO from making the same mistakes as the previous VP Sales?

Build explicit guardrails into the hiring and onboarding process. First, include a "failure clause" in the CRO's contract that ties 20-30% of their compensation to specific milestones (e.g., "complete enterprise pipeline audit by day 60," "present go/no-go recommendation by day 90," "achieve 3 closed enterprise deals by month 12") rather than just revenue targets. Second, require them to present a "90-day plan" to the board before they start, and hold them accountable to it in weekly check-ins. Third, install a "deal review" process where the CEO or a board member reviews every enterprise deal over $250k with the CRO before it goes to forecast - this prevents the "optimistic pipeline" problem that killed the previous VP. Fourth, mandate that the CRO personally handles the first 5 enterprise deals from first meeting to close, so they understand the real blockers before they delegate to reps. Fifth, set a 12-month "enterprise viability review" where the board evaluates whether the enterprise motion is on track or should be abandoned - this creates a natural exit if the CRO's plan doesn't work.

Sources