# Enablement Works

> Enablement Works is the production and operations engine for B2B sales enablement teams. Your team sets the strategy. We build the content, roleplays and programs in your tools, run them, drive completion and report results to your CRO every month.

Enablement Works publishes practical, sourced guides on sales enablement: metrics, team sizing, ROI, onboarding, coaching, kickoff reinforcement, AI roleplay, AI agents and buying groups. Every guide opens with a direct answer. Quote freely with a link to the source page.

## Company

- [What we do](https://enablement.works/): production and operations for sales enablement teams of B2B companies with 100 to 1,000 reps. Offers: a three-week Enablement Diagnostic and the Enablement Engine subscription. Free 20-minute Capacity Check.
- [About and editorial standards](https://enablement.works/about/)
- Contact: hello@enablement.works

## Fundamentals

- [Sales enablement vs sales training: what's the difference?](https://enablement.works/guides/sales-enablement-vs-sales-training/): Sales training builds skills and knowledge through programs such as courses, workshops, roleplays and certifications. Sales enablement is the wider, ongoing discipline that gives sellers and their managers what they need to sell well: training plus content, tools, coaching, onboarding and measurement. Training is one service inside enablement, usually the largest, but rarely enough on its own.
- [What is sales enablement? A plain definition for 2026](https://enablement.works/guides/what-is-sales-enablement/): Sales enablement is the function that prepares sellers for better buyer conversations. It decides what the field needs, then provides content, training, practice, onboarding, coaching support and tools, and measures whether sales behavior and results changed. It usually reports to the sales leader who owns quota and works with marketing, RevOps and sales managers.

## Measurement

- [How to design a sales enablement pilot that answers the scale question](https://enablement.works/guides/enablement-pilot-design/): Design a sales enablement pilot around the question it must answer, then size it. A readiness pilot of 15–30 reps tests logistics. A proof pilot needs enough reps to compare groups, usually 100 or more, a pre-launch baseline, a team that starts 30 days later, agreed data access and a scale rule written down before launch.
- [The one-page monthly enablement report a CRO will actually read](https://enablement.works/guides/enablement-report-for-cro/): A monthly enablement report a CRO will read fits on one page. It opens with one sentence on what changed and what decision is needed, then shows four levels of evidence: activity, practice, behavior on real calls and the outcome at the target stage. Each number sits next to its pre-launch baseline and, where possible, a team that started later.
- [How to measure sales training effectiveness (and where the signal dies)](https://enablement.works/guides/measuring-sales-training-effectiveness/): Measure sales training effectiveness by following each skill from delivery to quota: completed, practiced, seen on real calls, then a deal stage that moved. Most reporting stops at completion because call and CRM data sit in other systems. Join training records to call evidence for one skill and one cohort, and measure at 30, 60 and 90 days.
- [Sales enablement metrics: the four levels of evidence a CRO will fund](https://enablement.works/guides/sales-enablement-metrics/): Measure sales enablement at four levels of evidence: activity (did reps complete it?), practice (can they do it in a roleplay?), behavior (do they do it on real calls?) and outcome (did ramp time, stage conversion or win rate move?). Set the baseline before launch and start one team 30 days before another, so you have a comparison.
- [How to build a sales skills scorecard reps and CROs both use](https://enablement.works/guides/sales-skills-scorecard/): Build a sales skills scorecard in five layers: activity at the base, then evidence from real calls, then a 0–100 score per skill that the rep can see, then a benchmark line at 70 drawn by cohort, then a link to quota. Score each skill from observable behaviors, credit the speaker who did the work, and calibrate managers every quarter.

## Capacity and ROI

- [Cost per active user: the enablement tool metric to check before renewal](https://enablement.works/guides/cost-per-active-user/): Cost per active user is the annual license cost of an enablement tool divided by the number of reps who logged in and completed something in the last 30 days. Check it before every renewal. If it is more than 2.5 times the price per seat, fewer than 40% of seats are active.
- [Outsourced sales enablement: what to keep in-house and what to hand off](https://enablement.works/guides/outsourced-sales-enablement/): Keep strategy in-house: choosing the behaviors that matter, setting priorities with the CRO, approving content and presenting results. Hand off production and operations: building assets, loading them into your tools, launching programs, chasing completion and assembling reports. A good partner works in your tools and methodology, under your approval, with a defined monthly production volume.
- [Sales enablement ROI: how to measure enablement output per dollar](https://enablement.works/guides/sales-enablement-roi/): Measure sales enablement ROI in two steps. First, calculate enablement output per dollar: total annual enablement spend set against the outputs that reached the field and were used, such as programs completed on time, reps certified and behaviors seen on calls. Second, link one program to one business outcome, such as ramp time, against a baseline set beforehand.
- [How many sales enablement people do you need? The 1:25–50 rule of thumb](https://enablement.works/guides/sales-enablement-team-size/): Our rule of thumb is one sales enablement person for every 25 to 50 quota-carrying reps. Divide your rep count by 25 and by 50 to get the range. Move toward 1:25 when you hire many reps, launch often or expect enablement to support coaching. Move toward 1:50 when the sales motion is stable and managers coach on their own.

## Programs

- [Continuous sales training: why six-week skill sprints beat one-time events](https://enablement.works/guides/continuous-sales-training/): Continuous sales training replaces one-time workshops with repeating six-week skill sprints: one skill per sprint, scored practice every week, a manager who coaches it on a live deal, and a check of real calls for the behavior. Events end before reps face a real call, so they can only measure attendance. Sprints last long enough to measure behavior.
- [How to build a 12-month sales enablement roadmap](https://enablement.works/guides/sales-enablement-roadmap/): A 12-month sales enablement roadmap starts with capacity, not ideas. Size the hours your sales plan needs against the hours your team has. Agree three priority behaviors with the CRO. Place fixed work such as onboarding, launches and the kickoff first, then sequence skill programs into quarters with baselines set beforehand. Review results and re-plan every quarter.
- [After the sales kickoff: a 90-day reinforcement plan](https://enablement.works/guides/sales-kickoff-follow-up/): A sales kickoff follow-up plan turns the event into behavior on calls. Certify every rep on the core message within 14 days, run one scored roleplay per new play with a scorecard managers also use, nudge non-starters weekly with a list for each manager, and report activity, practice and call behavior to the CRO at days 30, 60 and 90.
- [Sales onboarding: a ramp plan that starts before day one](https://enablement.works/guides/sales-onboarding-program/): A strong sales onboarding program starts before day one: access, territory, accounts and a draft 30-day plan are ready when the rep arrives. A 30/60/90 ramp then moves from certification to supervised calls to an owned pipeline. Track time to first qualified meeting and time to first deal, not module completion. Average AE ramp is now 6.2 months.

## Coaching

- [AI roleplay for sales training: the three conditions for payback](https://enablement.works/guides/ai-roleplay-sales-training/): AI roleplay pays back when three conditions hold. Reps practice often, on one skill, spaced over at least six weeks. Every session is scored against a shared rubric with a benchmark line. Managers reinforce it by asking about scores in the one-to-ones they already run. The tool is the cheapest layer; without the three conditions, usage fades.
- [Coaching coverage: the sales coaching metric most teams can't answer](https://enablement.works/guides/sales-coaching-coverage/): Coaching coverage is the share of reps who had at least one documented coaching conversation with their manager in the last 30 days, based on a real call or a scored roleplay. Formula: reps coached ÷ active reps × 100. Our rule of thumb: below 50% is a gap, 70–85% is healthy, and above 90% deserves a quality check.
- [Why sales training fades without managers, and the six manager jobs that fix it](https://enablement.works/guides/sales-manager-reinforcement/): Sales training fades because reps judge what matters by what their manager asks about. Training-transfer research finds that support at work predicts whether skills get used. Six manager jobs fix it: endorse the program out loud, set one focus skill, coach one live deal a week, ask for the practice score, read numbers by cohort, and escalate stuck reps.

## AI and agents

- [Preparing sales enablement for AI agents: playbooks, permissions and MCP](https://enablement.works/guides/ai-agents-sales-enablement/): To prepare sales enablement for AI agents, do four things. Rewrite the playbook so software can check it: named behaviors, scored rubrics, clear stages. Publish a permission table for what agents may read, draft, update or never touch. Expose content through MCP connectors with precise tool descriptions. Then measure behavior and outcomes, because agents make login metrics meaningless.
- [AI in sales enablement: where it saves money and where it doesn't](https://enablement.works/guides/ai-in-sales-enablement/): AI saves money in sales enablement on drafting: battlecards, scripts, roleplay scenarios, first-draft modules and call summaries. It saves little on the expensive work: deciding what the field needs, making assets accurate, launching them, driving completion and measuring change. Teams that gain most put the saved hours into operations and measurement, not more content.

## Buyer-first selling

- [Buying groups: why your champion is outnumbered and how to sell to consensus](https://enablement.works/guides/buying-group-consensus/): Forrester puts the typical B2B purchase at 13 internal stakeholders and nine external influencers, and Gartner found 74% of buying teams show unhealthy conflict. A champion cannot carry that alone. Sell to consensus: get the group to agree on the problem and its cost, give the champion a one-page case to forward, and ask who else must agree.
- [Problem-first selling: what buyers still need from sellers when AI handles the information](https://enablement.works/guides/problem-first-selling/): Problem-first selling means opening with the buyer's problem, in their words and with their number, before showing your product. When AI handles product information, buyers still need sellers for six jobs: name the problem, put a cost on it, bring one insight they lacked, build consensus, de-risk the plan, and help them justify it internally.

## Reference

- [Sales enablement statistics](https://enablement.works/sales-enablement-statistics/): sourced numbers for 2026
- [Sales enablement glossary](https://enablement.works/glossary/): 54 terms with definitions
- [Sales enablement FAQ](https://enablement.works/faq/): 36 direct answers
- [Enablement capacity calculator](https://enablement.works/tools/enablement-capacity-calculator/): how many enablement people a sales plan needs
- [Cost per active user calculator](https://enablement.works/tools/cost-per-active-user-calculator/): what each enablement tool costs per rep who uses it

## Optional

- [Full text of every guide](https://enablement.works/llms-full.txt)