Table of Contents >> Show >> Hide
- Why $5m–$10m ARR is the “messy middle” inflection point
- Sign #1: The org still runs on vibes instead of dashboards
- Sign #2: They can’t hire (or develop) great managers under them
- Sign #3: They only hire people who look, talk, and sell like them
- Sign #4: They’re scared of big numbers (and act like the targets are unfair)
- Sign #5: They threaten to quit if you discuss adding a CRO or a layer above them
- Sign #6: Results have flattened for 2+ quartersand the explanations keep repeating
- A fast diagnostic: 10 questions a scalable VP can answer without sweating
- What to do if you spot 2+ of these signs
- Experiences from the $5m–$10m ARR trenches (the “this feels familiar” section)
- Conclusion
There’s a weird, awkward, very real truth in SaaS: a VP of Sales can be absolutely perfect for getting you to the first
few million in ARR… and still be the wrong leader for the next chapter. Not because they’re “bad.” Not because they
didn’t work hard. But because scaling from $5m–$10m ARR is less about heroic selling and more about
building a revenue machine that works without heroics.
Think of it like this: early-stage sales is jazz. The next stage is an orchestra. Same music. Totally different job.
And if your VP still wants to improvise every quarter, you’ll keep getting… improvisational results.
Why $5m–$10m ARR is the “messy middle” inflection point
Around this range, the company usually hits a few pressure changes at once:
- More reps, more deals, more noise: your CRM stops being “a place we log stuff” and becomes “the business.”
- Forecasting becomes existential: because hiring, runway, and board confidence now depend on predictable numbers.
- Enablement and onboarding become expensive: a slow ramp can quietly burn a shocking amount of cash.
- Founders can’t be the glue anymore: they can’t join every call, patch every deal, and personally hire every rep.
In other words: you can’t “grit” your way through this phase. You need systemscapacity planning, pipeline discipline,
coaching rhythms, hiring consistency, and cross-functional alignmentto make growth repeatable.
Sign #1: The org still runs on vibes instead of dashboards
What it looks like
- Pipeline reviews are storytelling sessions: “This one feels good.” “I think they love us.”
- Deal stages don’t mean anything (everything is “90%” for three months).
- CRM hygiene is optional, forecasting is “best guess,” and nobody trusts the numbers.
- There’s no clear view of conversion rates by stage, cycle length by segment, or rep-level performance drivers.
Why it caps you at $5m–$10m ARR
When you have a small team, a VP can keep it all in their head. Past a certain size, that becomes a bottleneckand a risk.
If the business can’t answer basic questions (“How much pipeline coverage do we need?” “Where are deals dying?” “Which
segment is slowing?”), growth becomes a coin flip.
Specific example
A founder asks, “Why did we miss?” The VP answers, “Two big deals slipped.” That’s not a diagnosisit’s a recap.
A scalable leader can say: “We under-created pipeline in Mid-Market by 18% in September, our stage-2-to-stage-3 conversion
dropped after we changed discovery, and ramped reps are only at 62% of modeled productivity.”
How to test it
- Ask for a one-page weekly dashboard: pipeline created, pipeline coverage, win rate, cycle length, stage conversion, and forecast by segment.
- If it takes weeks, looks hand-built every time, or sparks a debate about “what counts,” you’re seeing the ceiling.
Sign #2: They can’t hire (or develop) great managers under them
What it looks like
- They hire “mini-me” reps and promote the loudest top performer into management with no coaching plan.
- They complain about manager performance but keep hiring the same profile again.
- They avoid experienced leaders because they’re “too expensive” or “won’t fit our culture.”
- The org structure is flat: too many direct reports, too many ad-hoc escalations, too little coaching time.
Why it caps you
Scaling sales is fundamentally a management multiplication problem. At $5m–$10m ARR, you need leaders who can coach, run
forecasts, enforce process, recruit, and build a bench. If your VP can’t attract or grow strong directors/managers, they
become the single point of failureevery hire, every deal, every miss, every fire goes to them.
Specific example
The VP says, “I’m in every deal because we’re still early.” That might be true at $1m ARR. At $8m ARR, it’s a red flag.
If every rep needs the VP to close, you don’t have a sales teamyou have a VP with supporting actors.
How to test it
- Ask: “Who could run the team for 30 days if you were gone?”
- If the honest answer is “no one,” you’re not building an engineyou’re building dependence.
Sign #3: They only hire people who look, talk, and sell like them
What it looks like
- Hiring is mostly from their network, their last company, their preferred “type.”
- Diversity of selling styles is low (everyone sells the same way, to the same buyer persona, with the same playbook).
- They dismiss candidates with different strengths: “Not a culture fit,” “Too enterprise,” “Too structured,” “Too scrappy.”
Why it caps you
As you scale, your go-to-market inevitably broadens: new segments, new geographies, new deal sizes, new competitive landscapes.
That requires different strengthspipeline creation, discovery mastery, expansion selling, partner selling, enterprise procurement
navigation. If the VP keeps cloning themselves, the org becomes fragile. One motion works… until it doesn’t.
Specific example
A company starts in SMB with fast cycles and founder energy. Then the ACV rises. Now deals have security reviews, CFO scrutiny,
and multi-threading requirements. A “move fast and charm them” motion stops working. If the VP won’t bring in enterprise-experienced
leadership (or refuses to learn from it), growth stalls.
How to test it
- Review the last 10 hires: do they all share the same background and selling motion?
- Ask for a hiring scorecard that includes competencies (not just “I liked them”).
Sign #4: They’re scared of big numbers (and act like the targets are unfair)
What it looks like
- They talk more about why goals are unrealistic than how to hit them.
- They resist capacity planning (“We’ll just hire good people and it’ll work out”).
- They treat forecasting like a quarterly event, not a weekly operating system.
- They don’t translate revenue targets into inputs: headcount, ramp, pipeline creation, and conversion.
Why it caps you
At $5m–$10m ARR, the math gets louder. If you need a record quarter, you don’t get it by hoping harderyou get it by planning:
how many reps at full productivity, what quota attainment assumptions, what ramp timeline, what pipeline required, what win rates
by segment. Leaders who fear the math tend to avoid it, and avoidance is expensive.
Specific example
The company needs to go from $8m to $12m ARR. The VP says, “That’s a huge jump.” A scalable VP says, “Yes. Here’s the model:
we need X net-new ARR this year; with a Y win rate and Z average deal size, we need A qualified pipeline; given our cycle length,
we must create B pipeline per month; that requires C fully ramped reps plus D hires accounting for ramp and attrition.”
How to test it
- Ask to see the sales capacity model (even a simple one) and how it links to hiring and pipeline targets.
- If the answer is “we don’t really do that,” you’ve found the scaling gap.
Sign #5: They threaten to quit if you discuss adding a CRO or a layer above them
What it looks like
- Any mention of a CRO/SVP triggers defensiveness or ultimatums.
- They frame organizational change as betrayal instead of evolution.
- They resist collaboration with Marketing, Product, and Customer Success unless they “own” the narrative.
Why it caps you
Scaling companies layer leadership. It’s normal. The best VPs understand stage-fit and welcome supportespecially if it helps
the company win. The ones who can’t handle a boss often can’t handle the next stage, because the next stage requires
cross-functional alignment, tighter planning, and shared accountability.
Specific example
A founder wants a CRO to unify Sales, Marketing, and CS around one revenue strategy. The VP reacts like the founder suggested
replacing their dog with a Roomba. That’s not “passion.” That’s insecurity controlling the org design.
How to test it
- Ask: “If we hired a CRO, what would you want your role to be in 18 months?”
- A scalable answer focuses on impact (“I’ll own new logo sales and build managers”). A non-scalable answer focuses on title and territory.
Sign #6: Results have flattened for 2+ quartersand the explanations keep repeating
What it looks like
- Bookings plateau for multiple quarters, and the “why” sounds the same each time.
- Pipeline is consistently thin or inflated, with late-stage surprises.
- Rep churn rises (“We just can’t find good reps”), and ramp stays slow.
- There’s no clear experimentation loop: messaging, segmentation, enablement, pricing packaging, or channel tests.
Why it caps you
Every team has a rough quarter. But two or more quarters of flat performance suggests a structural issue: the motion is not
scaling, the team is not improving, or the leader is out of new ideas. At this stage, you need a VP who can diagnose, adjust,
and rebuildnot just rally the team with “We’ll get ’em next time.”
Specific example
If inbound leads drop, a scalable org adjusts: better outbound motion, tighter ICP focus, improved conversion, partner channels,
or pricing packaging changes. If the org just waits for inbound to “come back,” it’s not scalingit’s weather-dependent.
How to test it
- Ask for the last two quarters’ retrospective: what was tried, what changed, what worked, what didn’t, and what’s different now.
- If it’s mostly excuses and not experiments, you’ve got the plateau pattern.
A fast diagnostic: 10 questions a scalable VP can answer without sweating
- What’s our ICP todayand what’s the “nope” ICP we avoid?
- What are win rates and cycle lengths by segment?
- What’s our required pipeline coverage to hit plan (by segment) and why?
- What are stage conversion rates, and where are we leaking?
- What does “qualified” mean here (exit criteria), and is it enforced?
- How long is ramp, and what changes would reduce it?
- What % of reps are hitting quotaand what’s the distribution?
- What’s our hiring plan tied to capacity, ramp, and attrition assumptions?
- How do we coachwhat’s the weekly cadence and what behaviors are we changing?
- What are the top 3 reasons we loseand what did we change because of them?
If you’re getting blank stares (or a nervous monologue about “intangibles”), it’s not that the VP lacks effort. It’s that the
operating system isn’t there yet.
What to do if you spot 2+ of these signs
This is where founders often panic and swing the axe. You don’t always need to. A stage-mismatch can be solved with the right
structureespecially if the VP is coachable and ego-light.
Option A: Add RevOps and enablement before you replace leadership
Sometimes the VP isn’t “unscalable.” They’re unsupported. Adding strong Revenue Operations (and basic enablement) can
professionalize forecasting, pipeline management, onboarding, and reportingfast.
Option B: Layer a CRO/SVP above them (with a clear charter)
If the VP is strong at team motivation, early selling, and customer empathybut weak at systems and scalingbring in a CRO
who can build the machine. The key is role clarity: who owns the number, who owns process, who owns hiring, who owns cross-functional alignment.
Option C: Redesign the VP’s scope to match their superpower
Some leaders thrive in a narrower lane: SMB, commercial, outbound, or a specific region. If you can preserve the value they
bring while adding experienced scaling leadership, you get continuity without capping the company.
Option D: If you must change leaders, do it with respect and speed
A prolonged limbo damages the team. If it’s truly not working, make the change cleanly, communicate clearly, and protect customer
experience and rep confidence. Dragging it out is how you lose both the VP and the org.
Experiences from the $5m–$10m ARR trenches (the “this feels familiar” section)
Below are common experiences revenue teams report when a VP of Sales is hitting their scaling ceiling. These are not
rare edge casesthey’re the recurring patterns that show up in retrospectives, board decks, and those “quick sync?” Slack messages
that are never actually quick.
1) The Forecast Whiplash Experience: Monday’s forecast says you’re on track. Two weeks later, half the “commit”
deals slip because procurement “suddenly got involved.” The team starts treating the forecast like a mood ring. Finance stops
believing Sales. Sales feels micromanaged. Nobody wins.
2) The Hero-Dependent Close Experience: Reps book meetings, run decent demos, and then… everything stalls until
the VP joins. The VP becomes the closer, the negotiator, the discount gatekeeper, and the relationship saver. It feels productive
because deals close. But it’s secretly a scaling trap: reps don’t learn, managers don’t coach, and the org can’t grow without
multiplying the VP (which, last time anyone checked, is not a supported feature in humans).
3) The “We Just Need Better Reps” Experience: Every miss gets blamed on talent. Reps are “weak.” SDRs “aren’t hungry.”
The market is “tough.” But the hiring profile never changes, onboarding is still tribal knowledge, and coaching is inconsistent.
Over time, the company develops a churn treadmill: hire, hope, miss, replace. The VP stays busy, but the system never improves.
4) The Meeting Explosion Experience: As headcount grows, the calendar fills with pipeline reviews, forecast calls,
deal desk debates, and “alignment” meetings. Yet outcomes don’t improve. People leave meetings with more tasks but less clarity.
This is usually what happens when process is added without definition: lots of activity, not enough operational truth.
5) The Copy-Paste Hiring Experience: The org keeps hiring the same background because it worked once. But now the company
is selling to a different buyer, in a different segment, with a different competitive set. The team feels like a band playing the
same hit single in every city… even when the audience changed genres. Eventually, pipeline creation slows and win rates soften, and
everyone is surprised except the data.
6) The “Marketing Isn’t Helping” Experience: Sales says lead quality is bad. Marketing says Sales doesn’t follow up.
Customer Success says handoffs are messy. Product says feedback is inconsistent. If leadership doesn’t create shared definitions
(ICP, qualification, pipeline stages, attribution, handoff rules), teams will fight over opinions instead of improving the funnel.
This is often where a CRO-level operator can unify the revenue systemif the VP can collaborate.
If you recognized your week in any of those, you’re not aloneand you’re not doomed. The fix is rarely “try harder.”
The fix is usually “build the operating system, then coach people inside it.”
Conclusion
The jump from $5m to $10m ARR isn’t just “more sales.” It’s a different job: hiring and developing managers,
building forecasting discipline, separating pipeline management from forecasting, reducing ramp time through enablement,
and creating repeatability across segments.
If your VP of Sales shows multiple signs above, treat it as a stage-fit signalnot a character judgment. Sometimes the best move
is adding RevOps or layering a CRO. Sometimes it’s reshaping scope. And sometimes, yes, it’s upgrading leadership. Whatever you choose,
make it decisive, respectful, and tied to building a scalable revenue enginenot chasing the next quarter with duct tape.
