👋 Welcome to another issue of The Enablement Edge newsletter!

Sit back, relax, and get ready for:

• 💡 Key Concept – When forecasts tell different stories
• ✨ What’s New in Enablement – The tech stack disappears into AI
• ⚠️ Key Mistake – Using a marketing case study as buyer enablement
• 🎥 This Week’s Video – How enablement can actually change behaviour
• 🛠️ Piece of Tech – Where does your coaching break?

Redesign Revenue Work for the AI Agent Era

Learn how leading GTM teams are rethinking roles, workflows, and execution as humans and AI agents increasingly work side by side.

💡 Key Concept

Monday morning forecast review.

The CRO is expecting $8.2m.

RevOps has the quarter at $7.4m.

The sales managers, after speaking with their teams, are calling $8.9m.

Same business. Same quarter. Three different forecasts.

So, who got it wrong?

At this point, you cannot really tell.

The disagreement may simply come from the fact that each forecast is looking at the future through a different lens.

A judgement-based forecast leans heavily on what sellers, managers, or executives know about the deals and market.

A historical or conversion-based forecast asks what usually happens based on previous performance.

A pipeline or opportunity-based forecast looks at the deals currently in play – their value, stage, probability, age, expected close date, and other signals.

And a statistical or probabilistic forecast uses larger datasets and formal models to estimate relationships, probabilities, or ranges of possible outcomes.

Each method trusts different evidence, and that is exactly where the disagreement becomes interesting.

If manager judgement is significantly more optimistic than both your historical and pipeline views, there is something worth investigating.

Perhaps sellers know about recent buyer commitments that have not yet made their way into the data.

Perhaps the quarter contains a few genuinely unusual opportunities.

Or perhaps unfounded optimism has crept into the forecast.

Likewise, if your historical model is consistently predicting much more revenue than the current pipeline supports, the question becomes whether something fundamental has changed: pipeline creation, conversion, sales capacity, market conditions, or the sales motion itself.

The goal is not necessarily to make all of these forecasts produce the same number.

It is to understand what is causing the gap, work out which assumptions need challenging or updating, and get closer to a forecast the business can rely on.

In practice, that means doing three things.

1. First, diagnose the disagreement. Which assumption or piece of evidence is causing one forecast to move away from the others?
2. Then, reconcile what you know. New information from sellers may justify changing the pipeline view. Equally, historical conversion rates may need revisiting if the market or sales motion has changed.
3. Finally, learn from what actually happens. Once the quarter closes, compare each forecast with the outcome. If manager judgement consistently overestimates revenue, or a historical model repeatedly misses changes in the business, that should influence how much weight you give that view next time.

Over time, you are trying to improve two things: forecast accuracy and the organisation’s shared understanding of what sits behind the number.

This is why the gap between forecasts can be useful information in its own right.

I spent six weeks researching the different ways B2B teams forecast sales, covering everything from executive judgement and sales-force composite forecasting to weighted pipeline, time-series models, regression, multivariable approaches, and Monte Carlo simulation.

​The full guide that I put together in partnership with Airspeed breaks down how each approach works, what evidence it relies on, where it performs well, and how different methods can be combined and calibrated over time to build a more reliable forecasting process.

✨ What’s New in Enablement

One of the more interesting shifts I’ve been watching over the past couple of weeks is how quickly AI is moving from being another set of features inside the sales tech stack to becoming the interface sellers use to access the systems underneath it.

Salesforce is bringing CRM workflows directly into Claude, while Enverus is already using Highspot’s Model Context Protocol connection to surface governed enablement content inside ChatGPT and Claude.

For enablement, this could change what in the flow of work really means.

The platform may still hold the content, methodology, permissions, and knowledge, but the seller might never need to visit it directly. That puts much more pressure on whether the underlying information is structured, governed, and clear enough for an AI system to use reliably.

There are some smaller signals worth paying attention to as well.

Current enablement roles at organisations such as Hootsuite and insightsoftware are being described more explicitly around pipeline, win rates, adoption, retention, and other field outcomes. Practitioner discussions are also continuing to focus on measurement and repeatability rather than programme completion alone.

A few job descriptions and LinkedIn conversations don’t establish a market-wide trend. But taken alongside the technology changes, they reinforce a broader direction I think is worth watching:

​→ Read the full revenue & enablement news edition​

⚠️ Key Mistake

Your 1,500-word customer case study may be great for Google, yet your buyer probably doesn’t want to read it.

There is nothing inherently wrong with a detailed case study. Marketing may want the full customer story, plenty of context, quotes, product detail, and enough substance to perform well in search or when someone is researching your website.

The problem starts when we assume the same asset will work equally well inside a live deal.

Just put yourself in your champion’s shoes.

They have an internal meeting tomorrow and need to convince a sceptical CFO that your solution is worth pursuing.

They don’t need the customer’s origin story, three strategic pivots, and a lovingly reconstructed timeline back to 2009.

They need something they can understand quickly, forward confidently, and use to answer a very simple question:

“Has someone like us solved this problem successfully?”

The answer to that question is a different kind of customer story.

For buyer enablement, I usually focus on three main things:

• A relatable customer – similar industry, company type, role, challenge, or situation
• A clear before-and-after story – what was happening, what changed, and how the customer approached it
• Credible evidence of impact – measurable results wherever possible, without burying them halfway down the page

The format is also important.

Your champion may need to forward the story to someone who never attended the demo.

They might copy one slide into an internal presentation.

An executive may skim it between meetings.

Someone in procurement may read only the headline and the results.

In other words, buyer-facing proof needs to travel well.

An helpful test is to remove the salesperson from the equation entirely.

Could a stakeholder who has never spoken to your team understand the problem, recognise the relevance, and explain the result to somebody else?

If the answer is no, the asset probably still depends too heavily on seller narration.

This is one of the ideas I explored in my guide to buyer enablement content.

Customer stories are only one piece of it. I also cover assets such as executive briefs, business cases, decision criteria, pilot plans, implementation roadmaps, and mutual action plans – all designed around helping buyers make progress internally when the seller is no longer in the room.

🎥 This Week’s Video

Sellers can understand what good looks like and still fail to do it consistently.

Often, in enablement, we jump too quickly to another training intervention.

But the problem may have very little to do with knowledge or skill. The behaviour might not be obvious at the moment it is needed. It may be too difficult to perform within the existing workflow. Or there may simply be too little reason for the seller to repeat it.

In this week’s video, I walk through a simple way to diagnose those conditions before deciding what enablement should actually do next.

​

🛠️ Piece of Tech

Sales coaching software is a wonderfully confusing category.

Look at a few vendor websites and you will see similar promises: AI feedback, call scoring, better coaching, more capable reps, measurable behaviour change.

Dig a little deeper and you find products built around very different coaching problems.

So before comparing features, I would make sure I know how to finish this sentence:

“Our coaching breaks down because…”

The answer narrows the field considerably.

“We record hundreds of customer conversations, but managers struggle to turn them into useful coaching.”

In such situations, conversation-led platforms such as Gong, Jiminny, and Avoma become more relevant. Recorded calls provide the evidence, while scorecards, call libraries, feedback, and coaching workflows help managers turn that evidence into development conversations.

“Our reps understand what good looks like, but they do not get enough opportunities to practise.”

Now you are looking at a different type of platform.

Hyperbound and Second Nature put AI roleplay and repeated scenario practice much closer to the centre of the coaching experience. Quantified tackles a similar need with a stronger focus on regulated environments, where approved messaging, proficiency, certification, and compliance standards carry more weight.

“Training, practice, coaching, and readiness are scattered across too many places.”

Broader platforms such as Mindtickle and Allego make more sense when the goal is to connect coaching with learning, certification, practice, readiness, content, and other enablement workflows in a wider system.

Then there is another very common problem:

“Our managers simply do not coach consistently.”

This is where Ambition takes a different route, putting more emphasis on the management rhythm itself: recurring one-to-ones, preparation, coaching actions, follow-up, and visibility into whether those routines are actually happening.

There is overlap between all of these platforms, of course, and you still have a long road ahead of you, but starting with the coaching failure you are trying to solve gives you a much better filter than comparing twenty feature checkboxes.

I recently went deep on this category and compared 9 sales coaching platforms, including their capabilities, pricing, integrations, implementation effort, limitations, and best-fit coaching motions.

The full buyer guide should help you work backwards from the coaching problem you actually have and narrow down which type of platform deserves a closer look.

These are my 3 resource picks for this issue from The Enablement Edge Blog:

• ​Sales Forecasting Methods, Models, and Techniques: A Practical Breakdown for B2B Teams​
• ​Buyer Enablement Content That Accelerates Consensus: 8 High-Impact Assets​
• ​Best Sales Coaching Software in 2026: Which Platform Is Right for Your Team?​

Got 15 seconds? Please share your feedback by hitting the buttons below. Tell me what you liked and how I can make The Enablement Edge newsletter better.

Federico Presicci - The Enablement Edge Newsletter​
​If you expected more from these emails, please let us know (so we can improve) or Unsubscribe to not hear from us again.