Sales Management Code

Cracking the Sales Management Code (Jordan & Vazzana) is the definitive empirical framework for measuring and managing sales force performance. Its central contribution is a taxonomy that separates the three levels of sales performance measurement by how manageable they are — and the insight that most sales organizations focus on the level they cannot control (business results) while underinvesting in the level they can directly control (sales activities).

The framework eliminates a fundamental confusion in sales management: the belief that because you cannot manage outcomes directly, you should measure only outcomes. The code, when cracked, shows a clean chain of cause and effect from activity to outcome to result.

The Three-Level Hierarchy

Every sales performance metric falls into one of three categories:

Level 1: Business Results (Unmanageable)

These are the outcomes the board and CEO care about most, but which no sales leader can directly control:

  • Revenue Growth
  • Market Share
  • Gross Profit
  • Customer Satisfaction

Business Results are determined by the cumulative effect of many people’s efforts across the entire organization. You cannot tell a salesperson to “go produce more revenue.” Revenue is an outcome, not an action.

Business Results, which are wholly unmanageable but whose associated metrics are determined by the achievement of specific Sales Objectives.

Level 2: Sales Objectives (Influenceable)

The mid-layer: objectives that the sales force can be directed toward, but that still cannot be directly commanded — only influenced by ensuring the right activities are in place:

  • Market Coverage — Is the sales force large enough and deployed correctly to cover the target market? (Percentage of market opportunity covered, rep vacancy rates)
  • Sales Force Capability — Are salespeople skilled enough to execute? (Deal win/loss ratio, percentage of deals advancing by stage, sales cycle length)
  • Customer Focus — Are salespeople targeting the right types of customers? (Revenue from new customers, revenue growth from key accounts, customer retention)
  • Product Focus — Are salespeople selling the right mix of products? (Revenue by product, cross-sell rate, number of unique products per rep)

You cannot command your salespeople to be more capable, but you can send them to training. You cannot mandate more market coverage, but you can begin hiring.

Sales Objectives, which can be directly influenced and whose associated metrics can be driven by managing certain Sales Activities.

Level 3: Sales Activities (Manageable)

The only level management can directly control through day-to-day instruction:

  • Number of sales calls made per rep
  • Percentage of reps using CRM
  • Number of account plans completed
  • Dollars spent on rep training

Sales Activity metrics are used to quantify and track the day-to-day “doings” of the sales force.

The foundational principle:

Activities can be managed — outcomes can’t.

The practical implication: if a sales leader is frustrated with their revenue results, the correct intervention is not to pressure salespeople to “close more deals.” The correct intervention is to trace the chain backward from the Business Result to the relevant Sales Objective to the Sales Activity that needs to change — and then manage that activity.

Management stops begging for outcomes and starts directing the behaviors that will cause a chain reaction from Activities to Objectives to Results.

The Planning and Managing Sequence

The planning process runs top-down: Define the Business Results you want → Identify the Sales Objectives that most efficiently produce those results → Select the Sales Processes and Activities that directly influence those Objectives → Set quantified targets for all levels.

The management process runs bottom-up: Manage the Activities → Trust that the Activities will drive Objectives → Trust that Objectives will drive Results.

Plan from the top to the bottom, and then manage from the bottom to the top.

This reversal is the most counterintuitive and most important operational insight in the book.

The Five Sales Processes

Sales Objectives are driven by executing the right Sales Processes. Jordan & Vazzana identify five core processes:

1. Call Management Improves the effectiveness of individual customer interactions. Relevant when salespeople regularly have face-to-face or phone interactions where the outcome depends on quality of execution. Scripts, discovery question frameworks, objection-handling guides, and post-call analysis are all Call Management tools.

2. Opportunity Management Helps salespeople navigate complex, multi-call sales cycles. Relevant when deals require multiple stakeholders, multiple meetings, or stages that are hard to advance without a structured approach. Stage-gate criteria, deal review processes, and qualification frameworks (BANT, SPIN, MEDDIC) live here.

3. Account Management Maximizes the long-term value of selected customers. Relevant for sellers pursuing multiple opportunities over time with the same customer. Requires collaboration on account planning, executive alignment, and proactive identification of expansion opportunities.

Why ever would you involve a customer in your account planning activities? Because that’s the only way to gain strategic alignment between the two organizations and maximize the mutual benefit of the relationship.

4. Territory Management Allocates selling effort efficiently across a large number of potential customers. Relevant for salespeople making proactive outbound sales calls where some prospects are more valuable than others.

5. Sales Force Enablement Improves the sales force’s ability to execute: training, coaching, tools, content, onboarding.

The critical distinction between training and coaching:

Whereas training is designed to instill common knowledge across a sales force, coaching is used to build a salesperson’s abilities based on her unique development needs. Don’t prescribe a remedy without first examining the patient — particularly when the remedy is an invasive procedure.

Pipeline as a Dual-Purpose Tool

The sales pipeline serves two distinct purposes that must be separated:

  1. Forecasting — Looking forward: how much revenue will close in the next 30/60/90 days? This is a Business Results metric.

  2. Salesperson effectiveness — Looking at skill: are salespeople advancing deals effectively through each stage? Is anything getting stuck? This is a Sales Objective metric.

By identifying where a seller’s deals are getting stuck in the sales cycle, a manager can provide guidance or support to help the salesperson move further down the path to success.

Most organizations mix these two uses into a single pipeline report and end up with data that is mediocre for both purposes.

The Maturity Model for Sales Processes

Jordan & Vazzana describe four stages of sales process maturity:

  1. Ad hoc — No standard process; each rep sells as they think best. Unpredictable and inconsistent.
  2. Informal — A process exists but usage is neither monitored nor measured. Largely ignored.
  3. Formal — Process is enforced and periodically reviewed for effectiveness.
  4. Dynamic — Continuous monitoring; the process is proactively adjusted when market conditions change.

Companies with more developed sales processes enjoy greater sales performance.

The progression from ad hoc to dynamic is not just an internal efficiency gain — it is a compounding competitive advantage.

The Curse of Intimacy

One of the framework’s counterintuitive warnings for experienced sales teams:

There is a “Curse of Intimacy” that sometimes settles on a sales force that enjoys long-term relationships with its customers. After years of repeated interactions, salespeople can become numb to subtle signals from their customers that would be completely apparent to a bystander.

Long relationships breed assumptions: “He’ll let me know if there’s a problem.” Customer satisfaction surveys are the antidote — they provide a “sterile, non-threatening environment” where candid feedback emerges that would never surface in a comfortable relationship.

Connection to SaaS Sales Architecture

Blueprints for a SaaS Sales Organization extends the Sales Management Code framework into the SaaS context. The key metric shift:

In SaaS, the goal is MRR in dollars-per-month, the input is leads, and everything in between is a conversion point, including the tools and the salespeople.

The SaaS-specific management dashboard must include: Suspects → MQLs → SQLs → Commits → Live accounts → MRR, with the inter-stage conversion rates tracked for each funnel step. The Sales Activities that matter shift in SaaS:

  • Speed matters more: inbound leads responded to within 5 minutes are 21x more likely to qualify than those responded to an hour later
  • Outbound SDR metrics: appointments set per day per rep (average: 1, great: 2+), appointment-to-held rate, positive email reply rate (~3%)
  • The “78 Rule”: compounding MRR over 12 months means 1 new customer per month at the start of January generates 78 months of cumulative MRR by December

Practical Implementation

The six-step implementation sequence:

  1. Carefully define the Business Results you want
  2. Identify (through analysis) the Sales Objectives that most efficiently lead to those Results
  3. Select a process or processes that can directly influence the Objectives
  4. Choose specific Activities within those processes that you can manage day-to-day
  5. Quantify targets for all Results, Objectives, and Activities
  6. Manage

The insight is that if you want certain outcomes, you have to do specific things.

The framework’s elegance: it makes the vague command “go sell more” actionable. Instead of pressuring the Business Result, you identify the two or three Activities that are causal — and manage those.

  • Predictable Revenue — Ross’s system provides the specific Activity architecture (SDR dials, email touches, follow-up cadences) that the Sales Management Code framework would classify as Level 3 metrics
  • Customer Success — Customer health scoring and CS activities follow the same Activities → Objectives → Results logic; CS metrics like adoption and support call volume are Activities that drive Objectives like renewal rates