A sales enablement charter is a short document that sets out what an enablement team is for, who it serves, what it owns, and how its success will be measured.
It is usually one or two pages, signed off by the sales leader the team supports. Its job is to settle questions before they turn into arguments: who builds the pitch deck, who trains managers, and whether enablement is judged on course completions or on what reps do with buyers.
Why enablement teams write a charter
Enablement sits between sales, marketing, product and RevOps, so requests arrive from all of them. Without an agreed scope, the team becomes the place every half-finished task lands, and the work that would move results gets squeezed out.
A charter gives the enablement lead something to point to when a request falls outside the scope. It also gives the sales leader a clear picture of what to expect in a year, which matters when budgets are set. New enablement teams write one in their first quarter. Established teams rewrite theirs when the sales strategy changes, such as a move upmarket or a new method being rolled out.
What goes in a sales enablement charter
Most charters have six sections. Keep each to a short paragraph or a few lines.
- Purpose: the business result enablement serves
- Audience: which roles it supports, in order
- Scope: what it owns and what it hands off
- Partners: who does what with sales, marketing and RevOps
- Measures: the behaviors and results it reports
- Review: when the charter is revisited
- Purpose. The business result enablement exists to serve, in the sales leader's words. "Raise win rates in mid-market deals" is a purpose. "Deliver world-class training" is a slogan.
- Audience. Which roles the team supports, and in what order: new reps, tenured account executives, SDRs, front-line managers, partners. Putting managers on the list is the single most useful line, because they carry most of the follow-through.
- Scope. What enablement owns, and what it hands to others. Onboarding and certification might sit with enablement while the content library sits with marketing.
- Partners. Who does what with each neighboring team, especially sales leadership, marketing and RevOps.
- Measures. The two or three numbers the team will report, plus the behaviors it expects to see on deals. Pick at least one measure that sits in the field, such as whether a behavior shows up in deal reviews.
- Review. When the charter will be revisited, usually once a year and after any major change in strategy.
Charter, strategy and plan
The three documents are often confused. The charter says what the team is for and what it owns, and changes rarely. The sales enablement strategy says which priorities the team will pursue this year to serve that purpose. The plan lists the programs, owners and dates that deliver the strategy, and changes every quarter.
Example
This example is illustrative. Arrowmere, a 600-person logistics firm, hires its first enablement lead. In her first month she writes a one-page charter with the VP of sales.
The purpose reads: "Shorten the time for new account executives to run a full discovery call on their own, and raise the share of mid-market deals with a confirmed decision process." The audience lists new account executives first, then front-line managers, then SDRs. The scope gives her onboarding, certification and manager coaching, and leaves product launches and the content library with marketing. The measures are time to first solo discovery call, and the share of deals in the pipeline review with a decision process the buyer confirmed.
Two months later, marketing asks enablement to run a webinar series for customers. The charter places customer education outside the scope, and the VP settles it in one message.
Where charters go wrong
- Written and filed. A charter nobody reads at budget time has no effect on the work.
- Activity measures only. Completions and attendance are easy to report and say little about deals.
- Managers left out. A charter that does not name managers leaves the most important follow-through to chance.
For the measures worth putting in a charter, see how to measure sales enablement. For how teams are set up by company size, see sales enablement team structure, and for the full readiness picture, the sales readiness guide. The page for enablers shows how an AI sales expert supports reps and managers on live deals.
Related terms
- Sales enablement strategy: the priorities the charter serves
- What is revenue enablement?: the wider version of the function
- What is sales readiness?: the state enablement is trying to produce
FAQ
What should a sales enablement charter include?
A sales enablement charter should include the team's purpose, the roles it serves, its scope, how it works with partner teams, the measures it reports and when the charter is reviewed.
How long should a sales enablement charter be?
A sales enablement charter should usually fit on one or two pages. Longer charters tend to drift into plans, which change every quarter and belong in a separate document.
Who approves a sales enablement charter?
The sales leader the enablement team supports, usually the CRO or VP of sales, approves the charter. Marketing and RevOps leaders should review the scope and partner sections before sign-off.
How often should an enablement charter be updated?
Review an enablement charter once a year, and rewrite it when the sales strategy changes, such as a move to a new segment or the rollout of a new sales method.