The Board Just Moved the Goalposts. Here’s What 25 Years Taught Me About That Call.

I’ve been in the room when a board walks in with a new number. It’s not a sales problem—it’s a revenue architecture problem with a ticking clock. And I’ve seen too many founders waste the next two quarters trying to stretch the old plan like it’ll somehow fit.

Let me tell you what I’ve learned: when your board adds a revenue target mid-year, you have two or three quarters to close a gap that wasn’t in your original math. Your capacity was sized for the old number—headcount, ramp schedules, territory coverage, all built for a target that no longer exists.

Your pipeline coverage, which looked healthy at 3x the old quota, is now mathematically thin. And your comp plan is still pointing your team at last quarter’s behavior, not the incremental revenue you need today.

I’ve seen this play out a dozen times. The original plan, the comp design, the hiring schedule—they all go stale the moment the number moves. Stretching the old plan over the new target rarely works.

You can’t hire and ramp your way there in time if you start in month seven. And nobody recalculated coverage against the new number, so your team is working a funnel that’s too small.

*“You are not facing a sales problem—you are facing a revenue architecture problem on a deadline.”*

That’s why a fractional CRO fits this moment like a key in a lock. A mid-year target change is a temporary spike in leadership demand, not a permanent one. You need a senior operator now, fast, to re-engineer the engine and prove the new number is reachable.

You do not need to add a full-time executive to payroll forever to answer a question that lives inside the next nine months.

The alternative is a full-time CRO: a three-to-six-month search, $300,000 to $500,000 commitment, and equity and severance risk—none of which helps you with a number due this year. A VP of Sales? They manage and motivate reps, but most don’t re-architect the plan, the coverage math, and the comp design under a new target on a deadline.

If your team is fine but the plan is now wrong, a VP alone won’t close the gap.

A fractional CRO gives you that same senior, system-level leadership starting in days, on a fixed retainer of roughly $5,000 to $15,000 a month—a fraction of the $25,000-plus a month a full-time CRO costs all-in once you add salary, bonus, benefits, and equity. You’re buying the expensive part of a CRO—the judgment and the system—without paying for forty hours a week you don’t need yet.

For a business in the $1M to $15M revenue range working through a moment like this one, that’s one of the highest-return dollars in the budget, because the cost of getting the next two quarters wrong is far larger than the retainer.

What does a strong fractional CRO do first? They don’t start by pushing the team to “sell more.” They re-baseline against the real number: required bookings, the coverage ratio needed to support it, and exactly where the incremental dollars have to come from—by segment, product, and rep.

Then they find the fast revenue: expansion and upsell in the installed base, stalled deals worth reviving, pricing and packaging changes that lift average deal size, and your highest-gross-profit lines that reps may be neglecting. They install a tight weekly cadence focused only on the gap to the new target, so slippage shows up in days instead of at the end of the quarter when it’s too late.

The levers that actually close a mid-year gap are the ones that move fast: installed-base expansion (fastest, highest-margin, almost always under-worked), pipeline acceleration (tightening the sales process, removing stalls, improving win rates on deals already in the funnel), pricing and packaging (one of the few levers that works immediately across every open deal), comp re-pointing (a targeted spiff or accelerator aimed at the exact behavior the new number needs), and capacity triage (reassigning your best closers to the highest-value opportunities).

Here’s what the first 90 days look like. In the first 30 days, the focus is the re-baseline: a deep read of the new target against current capacity, pipeline coverage, comp, and per-rep and per-product gross profit, plus a clear-eyed map of where the incremental dollars will come from.

By day 60, the fast-revenue levers are live—expansion plays, pipeline acceleration, a pricing or packaging move, and a targeted comp adjustment—and the weekly cadence is tracking the gap. By day 90, the rhythm is running, your managers are trained to own it, and the board call is a status update against a credible plan instead of an anxiety attack.

From there, the engagement can settle into a steady retainer or wind down once the new number is on track.

I’ve 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. I’m the operator behind PULSE RevOps and the free revenue tools on this site, and I take on fractional CRO engagements through CRO Syndicate, a network of senior revenue practitioners who have built the numbers they advise on.

What that looks like in practice: a real diagnosis of your pipeline and comp plan in the first weeks, a clear revenue operating system your team can run without me, and senior leadership on call when your strategic partner, your market, or your product changes overnight. You get a 25-year operator in the room a few days a month—not a junior consultant reading from a playbook, and not another full-time salary on your books.

The board just moved the goalposts. Don’t waste the year trying to make the old plan fit—re-architect the engine instead.

*If this moment feels familiar, I’ve built the playbook. Check out PULSE RevOps for free tools, or reach out through CRO Syndicate—we’ll know in the first weeks whether the new number is reachable, and we’ll tell you straight.*

*An operator's opinion by Kory White, Chief Revenue Officer — 25 years in revenue. More at PULSE · CRO Syndicate*