Getting Leadership Buy-In for a New Enablement Initiative

Enablement leaders pitch good ideas to revenue leadership all the time, and a surprising number of good ideas get rejected — not because the idea is wrong, but because the pitch is built around the wrong currency. Revenue leadership is measured on pipeline, quota attainment, and forecast accuracy. When an enablement proposal leads with training hours delivered or certification completion rates, it's making a case in a currency the room doesn't spend. The idea might be exactly right, and it will still get shelved, because it was never translated into terms the person approving the budget is actually accountable for.

Activity metrics don't get budget approved

It's an easy trap to fall into, because activity metrics are the easiest thing for enablement to measure and report on directly. Hours of training delivered, number of reps certified, completion rate on a course — these are real signals of effort, but they say nothing about whether reps are actually winning more, ramping faster, or retaining more revenue. A VP of Sales looking at a proposal built around those numbers has no way to connect it to their own scorecard, and a proposal that can't be connected to the scorecard gets deprioritized, however good the underlying idea is.

Anchor to a problem leadership already sees

The fix starts before the proposal is even written: find the specific, already-visible business problem that leadership is already worried about. That might be a new-hire ramp time that's noticeably longer than the target, a win rate that varies wildly by rep or by region with no clear explanation, or a churn spike that account teams have quietly flagged as tied to weak renewal conversations. These are numbers leadership is already tracking and already uncomfortable with — which means the enablement initiative doesn't need to create urgency, it just needs to attach itself to urgency that already exists.

Framed this way, the pitch changes shape entirely. Instead of “we should invest in a coaching platform,” it becomes “ramp time for new reps has grown from ten weeks to sixteen over the last two quarters, and here's a specific, low-cost way to test whether structured practice closes that gap.” The first version asks leadership to trust a new initiative on faith. The second version asks them to help solve a problem they already know they have.

Ask for a pilot, not a rollout

Even a well-framed pitch is a harder sell if the first ask is a full-org rollout budget. Leadership is being asked to commit real spend to something with no internal proof point yet, and that's a much bigger risk than they need to take on your say-so. A far more approvable ask is a small, time-boxed pilot: one team, one quarter, one clearly defined metric to track. This lowers the cost of saying yes dramatically, and it gives the initiative something a full rollout ask never has — real internal data, generated inside your own org, that leadership trusts more than any outside case study.

A useful structure for the pilot ask:

• Name the exact metric being targeted (ramp time, win rate, renewal rate) and the current baseline.
• Name the exact team and time window for the pilot — small and specific, not org-wide.
• Name the comparison you'll bring back: pilot group vs. a control group, or pilot group vs. its own prior baseline.
• Name the decision the pilot will inform — what happens if the metric moves, and what happens if it doesn't.

What to bring back after the pilot

The case for scaling is made almost entirely by the data you bring back, so it needs to be the same metric you promised at the start — not a different, more flattering one. If the pilot was framed around ramp time, come back with a before/after ramp-time comparison, ideally against a control group that didn't go through the pilot. Resist the temptation to pad the case with satisfaction scores or completion rates; leadership already told you, implicitly, what currency they spend in when they approved the pilot around a specific metric. Give them more of that same currency, and the ask to scale becomes a much shorter conversation.

Why this pitch works better as a practiced conversation than a written memo

A pitch this specific rarely survives being delivered exactly as written — leadership will push back, ask for a smaller scope, or question the metric choice in real time, and an enablement leader who's only ever written the pitch, never said it out loud under pushback, tends to concede ground they didn't need to. This is the practice gap showing up in a boardroom instead of a sales call: knowing the argument isn't the same as being able to hold it under real-time questioning.

Before bringing this pitch to leadership, it's worth rehearsing the hardest version of the conversation — the CFO who questions the ROI math, the VP who wants to skip straight to a smaller ask, the stakeholder who brings up a failed initiative from two years ago. Frontline Coach's roleplay scenarios can be built around exactly this kind of internal stakeholder conversation, not just customer-facing calls, so the pitch is practiced before it's live. For the measurement side of this argument, see the companion guide on measuring sales readiness, and once the pilot succeeds, use the methodology rollout guide to plan the scale-up itself.