What a sales competency framework template is
A competency framework answers one question for a selling role: what does good look like, specifically enough that two managers looking at the same rep would land in the same place. The template is the grid that holds the answer, with competencies down the side and levels across the top.
The part that does the work is the behaviour anchor in each cell. An anchor describes something a person did, in language an observer could confirm or deny: not "strong discovery skills" but "asks about the cost of the current approach before proposing anything, and writes the number down". Anchors are what make a level checkable rather than arguable.
Published occupational standards are built the same way. The national standard for a sales executive role in England sets out its requirements as knowledge, skills and professional behaviours rather than as personal qualities (Skills England, Sales executive standard ST0572, accessed 2026-10-25), which is the distinction a usable framework has to hold on to.
A framework is not a scorecard and not a competency model on its own. A model names the competencies; a framework adds levels and anchors so the model can be applied to a person; a scorecard rates one event, such as a single call. This template is the framework, and it includes a separate assessment sheet for recording where each rep actually sits.
When to use a competency framework template
- Promotion decisions come down to advocacy from a manager rather than evidence anyone else can inspect.
- Two managers rate the same rep differently and neither can point at what would change their mind.
- A new hire asks what they need to demonstrate to reach the next level and nobody can answer in specifics.
- Coaching plans keep naming broad skills, so nobody can tell when a gap has actually closed.
- Hiring scorecards and internal levels use different language, so an external hire arrives at a level nobody can map.
Framework, model, matrix or scorecard: which one you need
These four words get used interchangeably and mean different things, which is why teams end up building the wrong artefact. The practical difference is what each one is good for.
| Artefact | What it holds | Use it to | Does not tell you |
|---|---|---|---|
| Competency model | The named competencies for a role, and nothing more | Agree what the job consists of | How good anyone is at any of it |
| Competency framework | Competencies plus levels plus observable behaviour anchors | Make a level decision someone else can check | How one specific call or deal went |
| Skills matrix | Reps down one axis, competencies across the other, current levels in the cells | See coverage and single points of failure across a team | Why a rep is at a level, or what to do next |
| Call scorecard | The behaviours expected in one conversation, rated per call | Coach a specific call and spot trends over several | Whether someone is ready for the next role |
The template
Two sheets. The first is the framework itself and changes a few times a year; the second records where each rep sits and changes every cycle. Keep them separate, because mixing them is how a framework quietly turns into a performance record nobody will revise.
Sheet 1: the competency framework
| Competency | Level 1 (developing) | Level 2 (capable) | Level 3 (strong) | Level 4 (teaches others) |
|---|---|---|---|---|
| Discovery | Asks prepared questions and records answers | Uncovers the cost of the current approach in the buyer's own numbers | Reframes the problem so the buyer describes a need they had not stated | Builds discovery guides others reuse, and coaches the reframe |
| Multi-threading | Works with the single contact who replied | Names every role in the decision and who is missing | Has a relationship with the economic buyer and one detractor | Teaches how to earn a second thread without going around a champion |
| Commercial and pricing | Quotes list price and escalates every exception | Explains the pricing model and defends it without discounting | Trades concessions for terms, and documents what was traded for what | Sets the team's concession guardrails and reviews exceptions |
| Objection handling | Answers the objection as stated | Separates a stated objection from the underlying concern | Handles the concern behind the objection and confirms it is resolved | Builds the objection library from live calls and keeps it current |
| Forecast accuracy | Reports stage and date as the rep believes them | Gives a next step with a date and a named owner on the buyer side | Commits a date and hits it, and flags slippage before it shows in the number | Calibrates other reps' forecasts and challenges optimistic commits |
Sheet 2: the rep assessment record
| Rep | Competency | Level claimed | Evidence cited | Assessor | Agreed level | Review date |
|---|---|---|---|---|---|---|
| [Rep name] | Discovery | [Level claimed] | [The call, deal or artefact that shows it] | [Assessor] | [Level agreed] | [Date] |
| [Rep name] | Multi-threading | [Level claimed] | [The call, deal or artefact that shows it] | [Assessor] | [Level agreed] | [Date] |
| [Rep name] | Commercial and pricing | [Level claimed] | [The call, deal or artefact that shows it] | [Assessor] | [Level agreed] | [Date] |
Prefer a file? Both downloads are free and ungated.
A worked example
Example: fictional company
One rep, one cycle, filled in. The point of the example is the evidence column: every level is tied to something a second person could go and look at.
Ferncastle Analytics sells a reporting platform to mid-market finance teams. Priya Raghavan has been an account executive for fourteen months and has asked what reaching the senior level requires. Her manager, Tom Brennan, assesses her against the framework before the conversation rather than during it.
Priya Raghavan, assessed October 2026
| Rep | Competency | Level claimed | Evidence cited | Assessor | Agreed level | Review date |
|---|---|---|---|---|---|---|
| Priya Raghavan | Discovery | Level 3 | Harborview Metrics call, 2 October: asked what the month-end close currently costs in analyst days and wrote the figure into the recap | Tom Brennan | Level 3 | 2027-01-15 |
| Priya Raghavan | Multi-threading | Level 3 | Marlow & Finch Logistics: three threads named, but the economic buyer has never been on a call | Tom Brennan | Level 2 | 2027-01-15 |
| Priya Raghavan | Commercial and pricing | Level 2 | Two of three closed deals went out at list; the third was discounted without a term traded in return | Tom Brennan | Level 2 | 2027-01-15 |
| Priya Raghavan | Objection handling | Level 3 | Harborview Metrics: the stated objection was price, the concern was the migration window, and the recap addressed the window | Tom Brennan | Level 3 | 2027-01-15 |
| Priya Raghavan | Forecast accuracy | Level 2 | Two commits moved a month late; both had been flagged in the week they slipped, not before | Tom Brennan | Level 2 | 2027-01-15 |
What the assessment turned into
| Gap | The behaviour being asked for | Practice before it is used live | Evidence that will settle it |
|---|---|---|---|
| Multi-threading at level 3 | Earn a call with the economic buyer through the champion, not around them | Role-play the ask with the champion's likely objection to it | An economic buyer on a recorded call before the January review |
| Commercial at level 3 | Trade a concession for a term rather than giving it | Role-play one discount request with a term to ask for in return | One closed deal where the discount is matched by a documented term |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to fill it in
Start from the work, not a skills list
Take three recent won deals and three lost ones and write down what the rep actually did differently. Competencies that do not show up in a real deal are not competencies for this role, however good they sound.
Keep the list to five or six
A framework with fifteen competencies gets filled in once and never revised. Five or six that decide outcomes are enough, and you can add one when you can name the deal it would have changed.
Write anchors an observer could confirm
Each cell describes something a person did, not a quality they possess. If you cannot imagine watching a call and ticking it, rewrite it until you can.
Make the levels about independence, not volume
Levels should separate someone who can do it when prompted from someone who does it unprompted, from someone who teaches it. Volume of activity belongs in the pipeline, not here.
Have two people rate the same rep before you launch
Pick one rep, have two managers assess independently, then compare. Every cell they disagree on is an anchor that is not specific enough yet. Fix those before the framework decides anything.
Require evidence in the assessment sheet
A level with an empty evidence cell is an opinion. Naming the call, deal or artefact is what lets a rep challenge a rating and a second manager check it.
Where these go wrong
Anchors written as adjectives
"Strong negotiator" and "consultative" cannot be observed, so two managers will rate them differently and neither is wrong. This is the single most common reason a framework stops being used.
Using it for performance management on day one
If the first thing the framework does is decide who is on a warning, reps will argue every anchor rather than use it to plan. Run it for a cycle as a development tool first.
One framework for every selling role
An SDR, a mid-market account executive and an enterprise seller do not share a competency set. Shared competency names with different anchors per role works; one grid for everyone does not.
Never revising it
The framework describes how you sell today. When the motion changes and the grid does not, reps are assessed against a job nobody has any more. Put a review date on the framework itself, not only on the ratings.
No calibration between managers
Without a calibration session, levels mean different things per manager, and a rep moving teams appears to gain or lose a level overnight. Calibrate before the framework touches promotion.
Treating a skills matrix as the framework
A matrix of who sits where is useful for spotting coverage gaps, but it carries no anchors, so it cannot tell a rep what to do differently. Build the framework first and derive the matrix from it.
How Revspire turns a competency gap into practice
The weak point in most frameworks is the space between the assessment and the next time the behaviour is needed. A rep leaves a calibration conversation knowing they are level 2 on multi-threading, and the next opportunity to be level 3 is a live call with a real buyer, where the first attempt happens unobserved.
Revspire AI Sales Training & Coaching gives that attempt somewhere to happen first. Reps run AI video role-plays of the specific conversation the anchor describes, such as asking a champion for access to the economic buyer, and get scored against the behaviour the cell names. The manager sees the practice and the live call, so the next assessment cites evidence rather than impressions.
Sales competency framework template FAQs
What is the difference between a sales competency model and a framework?
A model names the competencies a role needs. A framework adds levels and observable behaviour anchors, so it can be applied to a specific person and produce a decision someone else can check. If you can name the competencies but two managers still rate the same rep differently, you have a model and need a framework.
How many competencies should a sales competency framework have?
Five or six for a given role. Frameworks with twelve or more get completed once and then abandoned, because nobody can hold them in mind during a coaching conversation. Add a competency only when you can name a real deal that would have gone differently had it been in the grid.
How many levels should each competency have?
Four works well: developing, capable, strong, and teaches others. The jumps should be about independence rather than activity, so the difference between levels is whether the rep does it when prompted, does it unprompted, or can coach someone else through it.
Can the same framework cover SDRs, account executives and managers?
Not as one grid. The competency names can be shared so the language is consistent across roles, but the anchors have to be written per role, because what good discovery looks like for an SDR booking a meeting is not what it looks like for an enterprise seller. Keep one sheet per role.
How often should the framework be reviewed?
Put a review date on the framework itself and revisit it when the selling motion changes, which in practice tends to be once or twice a year. Rep assessments move faster, usually each quarter. Reviewing the ratings without ever revising the grid is how teams end up assessing people against a job that has changed.
Related templates and reading
- Free templateSales call scorecard templateA weighted 1-5 rubric for scoring recorded calls on agenda, discovery, value messaging, objections, next steps and talk/listen balance.
- Free templateSDR onboarding plan templateA week-by-week ramp plan for SDRs and BDRs: ICP, messaging, sequences, cold calls, qualification and the first qualified meeting, with gates.
- Free templateSales onboarding plan templateA 30-60-90 day plan for new account executives: learn, certify, then sell, with owners, exit criteria and a path to the first closed-won deal.
- Free templateSales battlecard templateA one-page card per competitor: why you win, where they are strong, landmine questions, objection responses and pricing guardrails.
- Blog: how to build the framework this template holdsSales competency framework guide
- Template: turning one gap into a coaching cycleSales coaching template
- Revspire data: the skills reps score lowest onSales skills gap benchmark
Sources
- Skills England: Sales executive (ST0572, level 4, version 1.1) (2026-10-25 (accessed))