If you’re a founder conflicted about what’s happening inside your sales org—forecasts swinging 30% in either direction, pipeline numbers that look healthy but never materialize, a VP of Sales who seems occupied but not truly leading—you’re not misreading the signals. You’re staring at one of the most predictable breaking points in a scaling company. The phase between founder-led sales and a real go-to-market engine is where most teams stall, burn out, or make expensive hiring mistakes.
The default reaction is almost always the same: jump back into deals, micromanage your VP, or quietly start thinking about replacing them. The truth? None of those is the right first move. What you’re seeing isn’t a VP problem—it’s a system problem. And this is exactly where a strong COO changes the trajectory of the entire company.
The COO is the one person who can turn strategy into operating rhythm, noise into clarity, and individual performance into a repeatable system. When done right, coaching the VP of Sales isn’t a motivational exercise—it’s an operational intervention. And it lifts the entire revenue organization, not just the executive in the seat.
This is a practical, operator-level playbook for diagnosing a misaligned sales organization, coaching a VP of Sales, and installing the operating cadence required to scale with consistency—not heroics.
The Problem You’re Seeing (Even If You Haven’t Named It Yet)
Most founders feel the symptoms long before they can articulate the root cause. Here’s what typically shows up:
- Forecast swings of +/- 30% or worse; leadership hedges, sandbags, or overcommits.
- Pipeline shows 3–5x coverage, but 40–60% of deals are stuck in stages far beyond normal cycle times.
- Quarterly attainment is lumpy: 1–2 top reps carry the number while the long tail misses by 40%+.
- Stage definitions differ by rep; methodology and qualification are optional.
- ICP drift: deals accepted “because they have a budget,” not because they’re winnable.
- SDR → AE handoff is inconsistent; accepted opportunities get disqualified downstream.
- Territories are either overloaded or under-allocated; quota capacity doesn’t match demand generation.
- Enablement is last-minute; onboarding is tribal and unpredictable.
- Compensation fights strategy—paying equally for low-quality upsell and high-priority net-new.
- VP is firefighting late-stage deals rather than building the system.
None of these are isolated VP failures. These are system failures. And systems don’t fix themselves. They require operational intervention.
Why Founders Struggle to Coach a VP of Sales
Founders instinctively try to help, but the environment makes it nearly impossible for them to coach effectively. Four structural issues always get in the way:
1. Context Collision
Founders operate in big bets, product vision, and strategic leaps. VPs of Sales operate in process, qualification, rigor, inspection, and repeatability. Coaching without shared context leads to frustration on both sides.
2. Role Confusion
Founders drift between visionary and sales manager. They jump into deals, contradict the process in front of the team, or intervene inconsistently. This erodes the VP’s authority overnight.
3. Incentive Misalignment
Founders prioritize rapid growth. Good VPs prioritize focus and qualify out aggressively. Without a buffer, this difference becomes friction instead of strategy.
4. No Coaching Framework
This is the big one. Coaching a VP isn’t an elevated pipeline review. It’s capability building across strategy, structure, process, talent, enablement, and governance. Most founders haven’t been trained to operate at that depth.
This is where a COO steps in—not to “fix the VP,” but to architect the system the VP can run.
Where the COO Actually Adds Leverage
A COO’s role in a misaligned sales org is simple: architect the revenue system, install the operating cadence, and coach the VP in the context of that system. The focus isn’t personality—it’s structure.
The COO translates strategy into:
- Clear ICP and segment definitions
- Territory design tied to capacity and demand
- Role clarity across SDR, AE, SE, AM, and CSM
- Documented sales process with strict stage exit criteria
- A qualification framework used consistently (e.g., MEDDICC)
- Weekly operating mechanisms (deal/pipeline/forecast reviews)
- A real RevOps function that enforces data hygiene and reporting standards
- A coaching scorecard for the VP built around specific behaviors
Once this structure exists, coaching becomes objective. Performance becomes visible. And the VP’s real capabilities come into focus.
The Six-Lever Diagnostic for Revenue Misalignment
This diagnostic cuts through noise. Each lever includes questions and validation metrics. Use all six before making decisions about coaching or replacing a VP.
1. Strategy (Where to Play)
Questions: Is the ICP clear, documented, and actually used to qualify the pipeline? Do we know which segments win and why? Are motions (inbound, outbound, partner, PLG) defined?
Metrics: Win rate by segment; cycle length by segment; discounting patterns; ACV trends.
2. Structure (Org Design)
Questions: Are roles defined? Are handoffs tight? Are territories matched to TAM? Is quota capacity realistic?
Metrics: Attainment distribution; quota capacity ratio; ramp time; coverage equity.
3. People (Hiring + Performance)
Questions: Do we have a hiring profile? Is coaching standardized? Are PIPs structured or emotional?
Metrics: Ramp productivity; attrition patterns; interview-to-offer ratios.
4. Process (Stages + Methodology)
Questions: Is there one sales process or seven versions? Are exit criteria enforced? Are pipeline, deal, and forecast reviews distinct?
Metrics: Stage conversion rates; deal slippage; stuck pipeline percentage.
5. Enablement (Content + Training)
Questions: Is onboarding structured? Do reps know the three core problems you solve? Is there a playbook?
Metrics: Time-to-first-meeting; certification rates; content usage.
6. Governance & Data (RevOps + Dashboards)
Questions: Is CRM the source of truth? Are dashboards standardized? Is there a consistent QBR rhythm?
Metrics: Forecast accuracy; data completeness; hygiene across opportunities.
Coachable vs. Structural Problems
Coachable:
- Messy hygiene
- Weak discovery
- Inconsistent methodology
- Shallow 1:1s
- Low-quality QBRs
Structural:
- Broken ICP
- Misaligned incentives
- Territory imbalance
- No RevOps foundation
- Capacity mismatches
You coach the former. You redesign the latter.
The 90-Day COO Coaching Plan
This plan stabilizes the system, lifts VP capabilities, and drives predictable early wins.
Phase 1 (Weeks 1–2): Align and Understand
- Run the six-lever diagnostic
- Clarify growth targets and segment focus
- Map current stage definitions and find friction
- Form a temporary Forecast Council for alignment
Deliverables: Revenue Architecture Canvas, operating cadence v1, VP coaching baseline.
Phase 2 (Weeks 3–6): Stabilize the System
- Install stage exit criteria and enforce via CRM
- Stand up distinct deal, pipeline, and forecast reviews
- Launch weekly call coaching with structured rubrics
- Fix territories and coverage inequities
- Align comp with strategy
- Stand up RevOps to enforce hygiene
Deliverables: Sales playbook v1, forecast categories, exec dashboards.
Phase 3 (Weeks 7–12): Build for Scale
- Install QBR rhythm
- Redesign onboarding with certification gates
- Create a real capacity model
- Align with Marketing on pipeline by segment
- Run win-loss interviews
Deliverables: Capacity model, enablement calendar, QBR framework.
The VP of Sales Coaching Scorecard
Use this to coach objectively and track progress over time.
1. Strategic Clarity
Can articulate ICP, say no to off-ICP deals, and prioritize based on signal—not hope.
2. GTM Architecture
Can align roles, coverage, and quotas with plan; works across functions to improve positioning.
3. Operating Cadence
Runs rigorous reviews; enforces definitions; improves forecast accuracy.
4. Talent
Hires to profile; ramps reps with structure; addresses underperformance quickly.
5. Pipeline & Forecast
Achieves real pipeline coverage; improves conversion rates; forecasts within ~10–15% variance.
6. Deal Execution
Enforces methodology; improves discovery; drives multi-threading; raises ACV or shortens cycle time.
7. Cross-Functional Leadership
Partners with Marketing, CS, and Product with consistency; communicates insights with clarity.
The Weekly 1:1 Between COO and VP of Sales
- Scorecard check-in
- Forecast inspection with evidence
- Pipeline health by segment
- Enablement priorities and call review feedback
- Talent and ramp updates
- Cross-functional alignment needs
- Decisions needed from COO/founder
- Commitments and follow-ups
Deal, Pipeline, and Forecast Reviews — Three Different Meetings
Deal Reviews
Deep dives into strategic deals; mutual action plans; timeline risks; stakeholder maps.
Pipeline Reviews
Hygiene, coverage, pruning, and prospecting commitments.
Forecast Reviews
Roll-up from managers; explain deltas; evidence-based adjustments.
Your Sales Operating Cadence
Daily
- Manager stand-up
- SDR–AE sync
Weekly
- Pipeline review
- Deal review
- Forecast review
- Enablement session
Bi-Weekly
- Forecast Council
Monthly
- Segment performance review
Quarterly
- QBR with commitments
Enablement and Onboarding: Build, Don’t Improvise
- Document the sales playbook
- Use structured call coaching
- Install 30/60/90 certification gates
- Shadowing program for new reps
Capacity, Territories, and Compensation
All three must align with strategy—not historical accident.
- Build a forward-looking capacity model tied to ARR goals
- Territories balanced by TAM and propensity, not random reallocations
- Compensation aligned to strategic outcomes (net-new, margin, ICP focus)
Governance: RevOps as the Backbone
RevOps is not a reporting layer. It’s the system owner.
- Owns definitions, data hygiene, dashboards, and the operating calendar
- Maintains CRM as the source of truth
- Runs signals-based alerts for hygiene violations
When to Coach vs. Replace Your VP of Sales
Coach if:
- They accept inspection and feedback
- They improve hygiene and cadence within 6–8 weeks
- They show learning velocity
Replace if:
- They resist transparency and inspection
- They cannot articulate a strategy
- Forecast accuracy remains chaotic after cadence is installed
- They consistently hire poorly and avoid accountability
Composite Case Story: From Chaos to Cadence in Two Quarters
A 45-employee SaaS org at $6M ARR struggled with erratic forecasts and pipeline stuckness. A COO-led intervention reframed ICP, enforced process, rebuilt territories, aligned compensation, installed RevOps, and coached the VP within a structured cadence.
Within two quarters:
- Forecast accuracy tightened to within 12%
- Stuck pipeline dropped from 50% to 22%
- Win rates improved in ICP segments
- Onboarding improved by 20–30%
- VP credibility increased; founder regained bandwidth
This wasn’t inspiration. It was operational discipline.
High-Impact Coaching Questions
- Which segments should we stop selling into, and why?
- What changed in Commit since last week? Evidence?
- Which deals should we prune today?
- Who is the economic buyer, and how do we know?
- Which reps are coachable vs. miscast?
- What did we learn from lost deals this month?
What Good Looks Like After 90 Days
- Forecast accuracy: +/- 10–15%
- Pipeline quality: 75% meeting exit criteria
- Attainment distribution: 70%+ of reps at 80%+
- Playbook actively used; onboarding structured
- RevOps-led dashboards and governance
- Coaching culture normalized
Common Pitfalls to Avoid
- Overengineering the process
- Confusing activity with productivity
- Mismatched incentives
- Skipping RevOps
- The founder bypasses the VP
The Bottom Line
Coaching your VP of Sales isn’t a pep talk. It’s the installation of a revenue operating system. Founders fail here because the job shifts from improvisation to governance. COOs succeed because they translate strategy into cadence, discipline, and capability-building.
If your sales org is misaligned, don’t churn leadership blindly. Diagnose the system. Install the cadence. Coach the VP through a structured scorecard. Within 90 days, the results will tell you whether the VP can run the system—or whether the system needs a different operator.
About The Author
