Outcome-Based Sales Enablement: Why Enablement's New Job Is Closing Gaps

A good friend who’s led enablement for her company for a few years was just acquired by a much larger firm, and now she’s acclimating to a new enablement “culture.”

She gave me a ring the other week:

“Our reps were all Slacking me saying they finished all their new enablement videos, and then were like, so that’s it? What do I do now?”

Their point was that the “big company” enablement felt… pointless. Because it was a lot of knowledge, separate from their actual job-to-be-done, and delivered outside the context of their actual deals.

Then, last week, I was at a CRO dinner in Salt Lake City, where someone asked the question:

“How should I be writing our ops and enablement job descriptions? We’re behind on hiring, but part of it is that I’m not sure we want skill enablement without tech, or tech without skills work. What’s the right structure here?”

And, I will say, the lines between the roles are getting blurrier every month as “revenue enablement” emerges. But I don’t think that’s a bad thing. Because I think it’s a major part of the shift to an outcome-based approach (vs. a knowledge-based approach) to enablement.

That’s focused on building new skills inside the actual work, using GTM data to target a handful of high-value behaviors that decide whether deals convert (or not).

Why doesn't sales training stick?

Now, follow me here:

1. Knowledge isn't an output, let alone an outcome. A rep can pass a certification on MEDDPICC fields, and still never get the EB (economic buyer) to a call. So head knowledge, and executing a specific skill to a specific standard, are quite different.
2. Training that lives outside daily context. Sales kickoffs and onsite workshops are great: I keynote and facilitate these for our customers, multiple times per month. But if there’s no ongoing practice after, or the practice is outside deal context, it’ll never stick.
3. There's no finish line. If you never wrote down a current state and a goal state, you can't tell if the program worked, so it just keeps running (and keeps adding to the pile).

Which is why "more training" has hit a wall, but a different approach can break through it:

What is outcome-based sales enablement?

Outcome-based enablement:

1. Targets a measurable revenue outcome (e.g. stage conversion, ACV, win rate);
2. By finding a highly-specific rep behavior that predicts that outcome;
3. Then closes the gap between how a rep actually executes that behavior today (or doesn’t), vs. how closed-won / converted deals executed it.

To contrast them:

Why think of enablement as a series of “sprints?”

I’ve built products, and enablement programs. Over time, I ended up adopting some paradigms from engineering rhythms that are ideal for enablement. A core primitive here is sprints:

Sprints force measurement: are we improving the one thing we prioritized, yes or no? If yes, can we lock it into the structure our reps operate with, and then move to the next gap, building on the progress over time? Or, if not, let’s stop and change the approach.

Which is more a process of continuous improvement, vs. a check-the-box approach. Because each part of the training is a single, measurable step, and the compounding comes from stacking them together over time.

How do you find the highest-value execution gaps to prioritize?

So, in designing the right enablement “sprints” to run, you're looking for the intersection of two things:

1. High value: a behavior that strongly and objectively separates won deals vs. lost ones, or a stage where most of your pipeline gets stuck.
2. Low execution: a behavior your team runs far less often, compared to a set of your won / converted deals.

Find the biggest gap, the root cause, and then work on that until the measure improves.

Which is similar thinking to how we’ve thought about engineering Loop, from Fluint.

So here's the five-step version of shifting your enablement to this outcome-based approach, using an example Loop workspace to bring the points and data to life.

Step 1: Stack-rank which “predictors” matter.

What are the leading indicators of win rate at your specific company, in a specific segment?

Some "leading indicators" can be semi-universal (champion, multithreading, next steps). Which are fine starting points, but the ranking has to come from your own closed deals, because the order changes WILDLY by segment, deal size, and motion.

For example, maybe you sell to engineers, and Economic Buyer access matters far less early-stage than in another setting, like more traditional HR or enterprise SaaS.

In this example, EB Access tops the default predictors at 0.72, followed by Timeline Confirmed (0.67) and Champion (0.63). But a custom predictor the team defined themselves, cfo_attended, scores even higher at 0.79.

Each score = how well that predictor separates winning deals from losing ones, based on regression testing that dimension against every other variable in a deal.

Step 2: Find where deals drop off, and which predictors drive that stage.

How do predictors show up in our stage-to-stage conversion rates?

A predictor that matters at Discovery might not matter at all by Negotiation.

So you look at them, stage by stage:

Here, Evaluation converts at 62% with $2.4M in open pipe. Three main predictors drive that stage, and all three are short of the score that deals need to convert:

• cfo_attended: 0.60 today vs. a 0.70 target
• Economic Buyer Access: 0.58 vs. 0.68
• Multi-Threaded: 0.56 vs. 0.66

So, the next question is: what play moves that predictor?

Step 3: Focus on a specific behavior that moves the predictor.

You can't coach a predictor, but you can coach to a “play.” The play = the output that a specific behavior creates, ideally with a set of golden examples from your own reps, which = the standard.

"Send an exec brief" means a 1-page, risk-focused brief addressed to the EB, with their team’s own data added, sent the week before a next conversation.

Which, in this example, moves two predictors at once: cfo_attended (+0.16) and Economic Buyer Access (+0.08). Run with the other plays at this stage, both predictors clear their targets.

And there's already one rep doing it well, producing the example of the standard: Jared V. sends a 1-page brief to the CFO the week of a demo, covering cost of inaction, risk, etc. in one clear next step.

Step 4: Compare the team to your won-deal benchmark.

How do you measure sales enablement’s impact?

Against the difference in your current vs. target outcome measure. Which isn’t… new. But the point is that it’s so rarely done in enablement that it’s difficult to know if enablement’s contributed to not just knowledge, but revenue.

For example: only 34% of reps run the exec brief play, while 78% of won deals included it.

That's a 44-point gap, worth a projected +3.1 points of win rate if that gap closes, and it's part of what would move Evaluation from 62% to 71% conversion. (It also tells you exactly who to work with: two reps are running it far below the benchmark.)

That's your execution gap: high value, low execution, and a specific set of reps.

Step 5: Act (and there are a lot of ways to act).

Once you know the gap, the question becomes: which intervention closes this gap fastest?

Loop can build an agent that drafts the brief for reps, but that's just one option out of many. The point of backing all the above with a single context layer, engineered with your data, is that every team intervention gets sharper if it's targeted at a specific predictor and play, with a standard.

Notice where the practice happens: on live deals, with tooling your reps already use.

What does an enablement sprint look like?

Here's the Evaluation example as a one-page sprint card:

How long should an enablement sprint be?

Good question: long enough for the play to show up on real deals. For most teams that's roughly 4 to 6 weeks, depending on how fast deals move through the stage.

When do you stop a sprint?

When the gap closes, or when the data says the play isn't moving the predictor. Either way, you re-rank and pick the next gap, and that's where the idea behind “continuous improvement” comes from.

"But what about onboarding and product knowledge?"

Fair question. New hires still need to learn the product, the market, and your process.

Outcome-based enablement doesn't delete that, it just stops treating it as the main focus of enablement: knowledge becomes an input to a sprint, delivered when that play needs it, instead of the focus of the program itself.

"What if we don't have the data?"

You can start “by hand.”

Go pull your last 20 won deals and 20 lost deals at one stage, list what happened in each, and then look for the behaviors that show up most in your wins vs. losses. It'll be slower and noisier, but it's the same principle.

(Loop does this continuously from your CRM, calls, email, and calendar, with a series of ML models to objectively weight them with your outcomes. Which is the difference between a one-time analysis and a living scorecard.)

Pro tips for your first sprint

• One gap at a time. The temptation is to run three sprints at once. Don't.
• Measure outputs vs. attendance. Did the brief get sent, on which deals, to what standard?
• Pull a golden example from your own team. A peer's example > templates, every time.
• Let managers own reinforcement. Enablement designs the sprint, and first-line managers make it stick in 1:1s and deal reviews.
• Socialize the before vs. after. A sprint that moved stage conversion 4 points is the best budget defense enablement will ever have baby.

So, is enablement part of the revenue org in the future?

Back to that CRO dinner.

I think the answer is undeniably yes, but only for the enablement teams that operate with a more direct tie to revenue, not just “learning stuff.” When enablement shows up to the pipeline review with a sprint card, a baseline, a target, and a result, this really isn’t a question people are interested in or feel the need to ask in the first place.

If you want to see your own predictors, stage gaps, and won-deal benchmarks, see how Loop builds your Context Graph →