Lisa Tricarico ran a Highspot instance at Justworks. By every reasonable measure, she was doing it right — paths built, content tagged, rep adoption nudged into the green. Then she asked her vendor a simple question: can you put guidance inside the workflow where my reps actually live?

The answer she got back was another Salesforce tile.

Ready to transform artificial intelligence from a buzzword into your personal revenue generator?

HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.

Inside you'll discover:

Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.

Get Your Guide

Two months later her team was on Spekit. Not because Spekit is the second coming. Because the question she asked was the wrong question to ask a 2010-era enablement platform — and the platform's answer told her exactly which decade it was still designed for.

That's the moment. That's the whole shift in one anecdote.

Here's what I want you to sit with: in February, Seismic and Highspot — the two largest sales enablement platforms in the market — merged into a $6B "category leader." Every analyst I read called it defensive consolidation. Gartner quietly told customers to prefer single-year renewals until the go-forward platform is clear. Forrester retired the label "sales enablement" in their Q1 2026 landscape and replaced it with revenue enablement. Josh Bersin estimated $4B is sunk into legacy LMS infrastructure that now has to be unwound and warned, "once you've used an AI-Native platform you won't go back."

These are not three separate trends. They're one architectural collapse.

The job in 2026 is not picking a better LMS. The LMS-as-product era is over. The job is designing the learning fabric that replaces it.

For fifteen years we treated the enablement tech stack like a buffet. LMS over here for certifications. CMS over there for content. Conversation intelligence in a third browser tab. Coaching tool in a fourth. Each tool optimized for its own dashboard, each vendor selling its category as the center of the universe, each rep silently swivel-chairing between six logins to do one job.

That model worked when the question was did the rep complete the module? It is breaking — visibly, painfully, in front of paying customers — now that the question is did the rep close the deal faster because of what they learned?

The merger is the news. The Forrester reframe is the category reset. The Bersin warning is the architectural verdict. Read together, they say the same thing: storage-first, portal-dependent, preparation-focused tools were built for a sales motion that doesn't exist anymore.

If you've been quietly suspecting that your LMS is the thing slowing your team down, you're not wrong. It's not the tool. It's the architecture the tool was built on. And without something connecting training to behavior in the deal, the reinforcement layer is where most programs leak — it's why most onboarding investments fail past week one. That math hasn't moved. What's moved is what the system of record needs to do.

It needs to stop being a course catalog. It needs to start being a fabric.

A fabric is not a platform. It is the connected set of layers that, together, deliver the right learning intervention to the right rep at the right moment in a deal — and feed the result back into the revenue number that pays everyone's salary.

You can run a fabric across multiple vendors. You can run it across one consolidated suite. The vendor question is downstream. The fabric question is which layers do we own, which do we rent, and which are we leaking through.

Let me give you the canvas.

Six layers. Draw them as a stack on a whiteboard. The arrows go up (each layer feeds the one above) and down (the top layer feeds revenue attribution back to the bottom). Every enablement program has all six — the only question is whether they're connected or whether you're paying for six tools and a swivel chair.

Layer 1 — Content Source of Truth (CMS). One repository, version-controlled, AI-tagged. Where the truth lives. If your reps don't know which deck is current, you don't have this layer — you have a graveyard of decks people guess at.

Layer 2 — Certification & Structured Learning (LMS). Paths, assessments, compliance. Did they learn it. This is what most of us mean when we say "LMS" — and in the fabric model it's one layer, not the whole thing.

Layer 3 — Reinforcement Engine (Spaced Microlearning). Drip cadence, retrieval practice. Did it stick. The Ebbinghaus curve hasn't been repealed; reps still forget 70% of what you taught them in 24 hours unless something reinforces it.

Layer 4 — Practice Surface (AI Role-Play + Call Review). Simulation, scoring, manager review. Can they do it under pressure. Allego's research found reps who receive AI feedback remembered 50% more after 48 hours than those who got human-only coaching. That's not a vendor stat — that's an architectural argument.

Layer 5 — In-Deal Coaching (Workflow-Embedded). Salesforce, email, conversation intelligence nudges. Are they doing it on live pipeline. This is the layer Lisa Tricarico's old vendor couldn't deliver — and it's the layer that explains why tool purchases don't move behavior unless the habit architecture changes underneath them.

Layer 6 — Revenue Attribution (LMS ↔ CRM ↔ BI joined view). Cohort win rate, ramp delta, stage velocity. Is it moving the number. Gartner predicts AI-driven enablement orgs will hit 40% faster sales-stage velocity by 2029 — but only the orgs that can prove the lift will get the budget to keep going.

That's the fabric.

Forward this section to one peer who's about to sign a multi-year LMS renewal. They'll thank you.

Here's the pattern I keep seeing when I sketch this with enablement leaders: the first three layers are mostly intact, layers 4 and 5 are partially intact and politically owned by three different teams, and layer 6 doesn't exist — there's a Looker dashboard somewhere with course completions on it, and there's a separate CRM dashboard with pipeline on it, and nobody has joined them.

If that's you, the two highest-leverage layers to invest in are 5 and 6. Not because the others don't matter. Because layers 1 through 4 will look like waste to a CRO until layers 5 and 6 prove they're not.

The in-deal coaching layer is where the swivel-chair tax shows up most painfully — it's the gap Spekit, SalesHood, Allego, and Mindtickle are all racing to own. None of them is "the answer." Each of them is an example of what the layer looks like when it works.

The revenue attribution layer is where credibility is won or lost. If your dashboard is still showing courses-completed-this-month, you're answering a 2019 question — the same trap I unpacked in the metric that felt like proof but wasn't. The dashboard a CRO will fund is the one that joins LMS completion + CRM stage progression + win rate by cohort, with a 90-day window so behavior change has time to settle.

I want to be careful here because the easy move is to dunk on Seismic and Highspot, and every analyst is already doing it. That's not the point.

The point is what the merger is evidence of. Two market leaders consolidating defensively, while the analyst community is openly recommending single-year renewals, is the strongest possible signal that the architecture underneath the platform is what's tired — not the people running it. The merger is the symptom; the fabric collapse is the cause.

The contrarian read is real, though, and I won't ignore it: PE-backed consolidation has won before by owning the data fabric and the CRM integrations that AI-native upstarts depend on. It is genuinely possible that the merged Seismic ships an agentic execution layer in 18 months and the upstarts get squeezed. What evidence would tell you that scenario is playing out by Q4 2026? Watch two things: how aggressively the combined entity opens its data layer to third-party AI, and whether their pricing holds. PE-backed consolidation historically expands margins, not lowers prices.

For now, the buyer move is the same either way: sign nothing multi-year until you know which roadmap survives. Treat this as the highest-leverage 12-to-18-month negotiation window of the decade. We'll come back to that audit in a future issue — for now I just want you holding the leverage, not signing it away.

I'm not going to pretend you can redesign your entire stack in a quarter. Most teams I talk to are still trying to get reps to log into the LMS they already paid for.

The fabric is the lens. The work in front of you is honest mapping.

Put the six layers on a whiteboard. For each one, write the vendor (or vendors) you're using today. Then ask three questions:

That's it. No new platform. No RFP. No vendor demo cycle. Just three questions and a whiteboard.

If the answer to question 2 is "layer 6" — revenue attribution — that's where I'd put the next dollar. Not because it's the sexiest layer. Because it's the layer that lets you keep all the other ones.

Here is the question every enablement leader I respect is starting to ask quietly: when LMS + CMS + coaching + analytics collapse into one fabric, who in the org actually owns it? L&D? Sales Ops? RevOps? A net-new revenue enablement function?

That question is its own future article. I'll just plant the flag here: the org-chart fight is coming. The leader who walks into the executive room with the canvas already drawn — and a clear answer to which layer reports to whom — is the one who comes out the other side owning the function. The leader who waits for someone else to draw the canvas first finds themselves reporting to that person.

You don't have to win that fight today. You do have to be the one holding the marker.

[PRODUCT CTA: Learning Fabric Blueprint — TBD. If a Learning Fabric Canvas one-pager or the existing AI Readiness Audit fits the pillar, drop it in here. Soft tone suggestion: "If you want the canvas as a one-pager you can hand to your CRO, the Learning Fabric Blueprint walks through each layer with vendor-by-layer examples and the three questions above. Grab it below."]

So my question to you is this:

When you put the six layers on the whiteboard, which one are you leaking through right now — and what is it costing you in deals you'll never see in the pipeline?

Hit reply and tell me. I read every one.

Until next time my friends… ❤️, Enablement

Key Concepts from This Issue

The Learning Fabric Canvas The Learning Fabric Canvas is a six-layer reference architecture developed by Ryan Parker in Love, Enablement that replaces the legacy LMS-as-product model with a connected fabric for delivering revenue-attributable learning to sales reps. It consists of six layers: (1) Content Source of Truth (CMS), (2) Certification & Structured Learning (LMS), (3) Reinforcement Engine (spaced microlearning), (4) Practice Surface (AI role-play + call review), (5) In-Deal Coaching (workflow-embedded), and (6) Revenue Attribution (LMS↔CRM↔BI joined view). It solves the practitioner problem of evaluating enablement tech as a connected system rather than as a stack of disconnected point solutions.

Key Data Points

Related Analysis

If You're Asking...

What is the Learning Fabric Canvas? The Learning Fabric Canvas is a six-layer reference architecture developed by Ryan Parker in Love, Enablement that helps revenue enablement leaders evaluate whether their LMS, CMS, coaching, and analytics tools form a connected system or a fragmented stack. It replaces the LMS-as-product model with six explicit layers from content source-of-truth through revenue attribution.

Is the LMS dead in 2026? The LMS-as-standalone-product category is collapsing, but the LMS function — certification and structured learning paths — remains one layer of a broader learning fabric. According to Love, Enablement's Learning Fabric Canvas, the LMS is layer 2 of six, not the entire architecture, and modern sales enablement programs need all six layers connected.

What does the Seismic-Highspot merger mean for sales enablement buyers? The Seismic-Highspot merger (announced February 2026, ~$6B combined valuation) is widely read by analysts including Gartner as defensive consolidation, with an 18-36 month integration window during which feature releases will stall. Love, Enablement recommends signing nothing multi-year until the surviving roadmap is clear and treating the window as the highest-leverage negotiation moment of the decade.