Why Sales Competency Models Fail (and What to Build Instead)

Most sales orgs eventually try to bottle their best reps. Find the top performers, list what they seem to do well, write it up as a competency model, and roll it out so everyone else can copy it. Sensible in theory. In practice it rarely moves the number.

The reps look trained. The model gets a slide. And the gap between your best and your average sellers stays exactly where it was.

The reason is simple. Most competency models name traits, not outcomes. And traits do not close deals. Evidence of buyer commitment closes deals. (This is the framework view of the wider argument in the Sales Enablement hub: enablement is behaviour change, not content.)

The competency mirage

A typical model lists things like "consultative seller", "strong discovery", "customer-centric mindset". They sound right. They are also vague enough that no two managers would score them the same way, and no rep could tell you what to actually do differently on Monday.

Robert Teodorescu and Carl Binder make the distinction that matters here: a competency model describes who someone is, a competence model defines what they produce. In sales, you do not get paid for resilience. You get paid for a qualified pipeline, multi-threaded deals and a forecast that holds.

Where traditional models fall short

The common failure points:

• They stop at naming behaviours. They describe the trait but never tie it to an outcome.
• They are generic. Lifted from a corporate template, with no relationship to your actual deals or buyers.
• They have no stage context. Nothing links the behaviour to a specific point in the sales process.
• They are unmeasurable. You cannot see them in the CRM, so you cannot coach or track them.
• They ignore the system around the rep. They treat performance as a personal quality, not the output of how the team is set up to sell.

The net effect: the model tells you who might succeed. It never tells you what has to happen for a deal to move.

From behaviour to business result

Thomas Gilbert's Behaviour Engineering Model makes the point cleanly: behaviour on its own has no value. It only matters when it produces an accomplishment, and that accomplishment contributes to a business result.

So the unit to manage is not the trait ("good at questioning"). It is the accomplishment ("uncovered a quantified business case and CFO-level engagement inside the first two calls"). One you can argue about. The other you can inspect.

Five traps to design out

• Behaviour without result What it looks like: "Shows strong questioning skills" but never surfaces decision criteria or real pain. The fix: Anchor every competency to an observable accomplishment tied to a deal stage.
• Subjectivity What it looks like: "Collaborative", "creative", impossible to score in the field. The fix: Use objective language tied to buyer milestones and stage exits.
• No sales context What it looks like: One model for transactional SMB reps and enterprise sellers alike. The fix: Build it around your actual motion, buyer journey and deal type.
• One-time rollout What it looks like: An HR document launched once and never seen again. The fix: Make it a live toolset inside CRM prompts, inspection routines and coaching.
• No link to revenue What it looks like: No path from competency to commercial impact. The fix: Start from the business result and work backwards to the behaviours that drive it.

What to build instead: a competence model

Competence is not a personality. It is the repeatable achievement of results the business cares about. Build the model backwards, in four layers:

• Business result. For example: lift enterprise win-rate by 15%.
• Key accomplishments. What has to be true in a deal to get there: economic buyer engaged, business case quantified, buying group mapped.
• Tasks and behaviours. The specific actions that produce those accomplishments: ROI-led discovery questions, multi-threading, a defensible business case.
• Environmental enablers. What the system has to provide: CRM exit criteria, call reviews, manager-led deal inspection.

Designed this way, the model is not a description of good reps. It is an operational standard you can build into how the team sells.

In practice, this competence model takes the form of a skills rubric. Behaviours build into skills, skills group into competencies (the rubric's domains), and competencies drive the results the board inspects: win rate, cycle length, deal value, forecast accuracy. Each skill is scored on the evidence you must see, not opinion, and the same instrument then runs hiring, enablement, growth and performance on one standard. That is the whole answer to "what to build instead", and we go through it in The Sales Skills Rubric.

Where this fits in Closing OS

This is the Enable layer of Closing OS in practice. Design works out what needs to change. Enable builds the standard of good into stage exits, playbooks, CRM workflow and the manager's coaching routine. Run keeps it alive in the weekly rhythm until it shows up in live deals and the forecast call.

A competency list on a wall changes nothing. A competence model wired into stages, the CRM and deal inspection changes what reps actually do, because the standard is now visible at the point of the work. If your "competencies" are not tied to buyer outcomes, your managers cannot coach to them in a deal review, and your reps cannot see them in their tools, the model is decoration. Flip it: start from the result, define the accomplishments, and build them into the system.

Further Reading

• B2B Sales Enablement: A Framework for Revenue Leaders
• Why Sales Training Doesn't Stick (and How to Fix It)
• How to Measure the Impact of Sales Enablement

Related terms

• Sales Rubric: a behaviour-based evaluation framework focused on observable working behaviours rather than claimed competencies.
• Sales Enablement: the function that equips sellers with the content, training, tools and process knowledge to execute effectively.
• Sales Process: the repeatable sequence of stages, activities and exit criteria from first contact to close.
• Sales Playbook: a documented, stage-gated framework defining what sellers should do, ask and evidence at each stage.
• Stage Exit Criteria: the conditions that must be met before a deal advances from one stage to the next.
• Buyer Evidence: concrete signals from a buyer that validate genuine deal progression.