Cracking the Sales Management Code by Jason Jordan and Michelle Vazzana: Summary, Key Lessons, and RevOps Takeaways

Published June 13, 2026 · Updated June 13, 2026

1. Part One — The Problem With Sales Metrics

1.1 Too Many Metrics, None Manageable

Jordan and Vazzana open with a problem every sales org recognizes: companies drown in sales metrics — CRM dashboards track dozens or hundreds of numbers — yet performance doesn't improve, because most of those metrics can't actually be managed. Tracking a number is not the same as being able to change it through management action. The book's mission is to cut through the metric overload and identify the few metrics a manager can genuinely act on to drive performance.

1.2 The Three Levels of Metrics

The book's signature framework is a hierarchy of three metric levels, and confusing them is the root cause of failed sales management. Business results sit at the top — they are outcomes you monitor but cannot directly control. Sales objectives sit in the middle — they are goals you can influence. Sales activities sit at the bottom — they are what you can directly manage. The error is trying to manage the top level; the fix is managing the bottom and middle levels that drive the top.

2. Part Two — What You Can Actually Manage

2.1 Business Results: Monitor, Don't Manage

Business results — revenue, profit, market share, growth — are the outcomes everyone obsesses over, but Jordan and Vazzana insist you cannot directly manage them. You can't tell a rep to "go make revenue"; revenue is a lagging result of many factors, some outside the rep's control. You monitor results to know where you stand, but managing them directly is impossible — a liberating insight that redirects management energy to where it works.

2.2 Sales Objectives: Influence

Sales objectives — customer acquisition, customer retention, and share-of-wallet (selling more to existing customers) — sit in the middle. You cannot fully control them, but you can influence them through strategy and focus. Objectives are the strategic levers between activities and results: a manager directs the sales force toward the right objectives (e.g., emphasizing retention or new acquisition) to shape the results.

2.3 Sales Activities: Control

Sales activities — calls made, meetings held, proposals sent, accounts planned, pipeline worked — are what a manager can directly control and manage. This is where management action actually lands: you can require, coach, and measure activities. The book's core prescription: manage the activities (which you control) and direct the objectives (which you influence), and the results (which you monitor) follow. This inverts the typical obsession with results-only management.

3. Part Three — Managing the Sales Force

3.1 The Core Sales Processes

Jordan and Vazzana identify the core sales processes a sales force runs — call management (individual sales interactions), opportunity management (working deals through the pipeline), account management (growing existing customers), and territory management (covering a market). Different sales forces emphasize different processes depending on their motion, and the manager's job is to identify and manage the processes that matter for their business — instrumenting the activities within each process.

3.2 Building Metrics Around Manageable Activities

The practical payoff: build your CRM, metrics, and dashboards around the manageable activities and influenceable objectives, not just the results. Instead of a dashboard of unmanageable result-metrics, track the activities you can coach (within the relevant sales processes) and the objectives you're directing toward. This makes the metrics actionable — a manager looking at the dashboard knows what to do, not just what happened.

3.3 The Management Cadence

Finally, the book stresses a management cadence that operates on the manageable levels — regularly coaching activities, reviewing the processes, and directing objectives — so management consistently acts where it can affect outcomes. The cadence turns the framework into ongoing practice: managers spend their time on the activities and objectives they can move, rather than staring at results they can only watch.

Frameworks at a Glance

• Three levels of metrics — business results (monitor), sales objectives (influence), sales activities (control).
• You can't manage results — only the activities and objectives that drive them.
• Manage activities, direct objectives, monitor results — the core management prescription.
• Core sales processes — call, opportunity, account, and territory management.
• Build metrics around the manageable — instrument activities and objectives, not just results.
• Management cadence — coach activities and direct objectives consistently.

What Holds Up, What Has Aged

What holds up: the three-level metric hierarchy is timeless and foundational — it underpins every modern RevOps dashboard, leading-vs-lagging-indicator distinction, and activity-based coaching model. "Manage the activities, not the results" is gospel for 2027 sales management. What has aged: the book predates modern conversation intelligence, AI activity capture, and signal-based selling, so the *activities* tracked and *how* they're captured have evolved (AI now auto-captures and analyzes the activities the book says to manage). But the principle — distinguish what you can manage from what you can only monitor — transfers cleanly to the AI-instrumented 2027 sales org.

2. Part Two — The Three-Level Hierarchy of Sales Metrics

2.1 Business Results: Monitor, Don’t Manage

The top level of the hierarchy—business results—includes revenue, profit, gross margin, and market share. The authors make a counterintuitive but crucial point: these are outcomes, not levers. No manager can directly “manage revenue” any more than a pilot can directly manage altitude. Instead, revenue is the lagging indicator of thousands of activities performed by the sales force over weeks or months. Jordan and Vazzana argue that the common practice of holding sales managers accountable for revenue targets—without giving them a clear set of manageable inputs—is a recipe for frustration and burnout. A typical sales manager might have 8–12 direct reports; if each rep handles 50–100 accounts, the manager is expected to influence hundreds of revenue streams they cannot directly control. The solution is to stop managing results and start managing the activities and objectives that reliably produce them.

2.2 Sales Objectives: The Bridge Between Activities and Results

The middle level—sales objectives—includes metrics like customer acquisition rate, customer retention rate, share of wallet, and sales cycle length. These are intermediate outcomes that are influenced by sales activities but still not directly controllable. For example, a rep can control how many proposals they send (an activity), but they cannot control how many of those proposals convert into new customers (an objective). The authors emphasize that sales objectives are the most neglected level in most CRM systems—companies track activities (calls, emails) and results (revenue, bookings) but fail to measure the strategic objectives that connect them. A practical takeaway for RevOps: design your dashboard to show activity-to-objective-to-result cascades, so managers can see, for instance, whether a drop in retention is caused by fewer follow-up calls (activity) or a shift in competitive positioning (external factor).

2.3 Sales Activities: The Only Level You Can Truly Manage

At the base of the hierarchy are sales activities—the specific, observable, repeatable actions reps take every day: number of calls made, meetings held, proposals sent, pipeline stages advanced, account plans updated. These are the only metrics a manager can directly influence through coaching, training, process design, and performance feedback. Jordan and Vazzana argue that the most effective sales managers spend 70–80% of their time on activity management—not reviewing revenue reports or chasing deals. They provide a simple test: if you can’t pick up the phone and ask a rep to do more of a specific activity today, it’s not a manageable metric. For RevOps, this means instrumenting CRM to capture granular activity data—not just outcome data—and building dashboards that surface activity gaps before they become revenue shortfalls.

3. Part Three — The Four Core Sales Processes and How to Manage Them

3.1 Call Management: The Foundation of Pipeline

The first process—call management—covers the day-to-day interactions between reps and prospects: initial outreach, qualification calls, discovery meetings, and follow-ups. The authors argue that most companies over-engineer call scripts but under-manage call volume and quality. A manageable metric for call management is qualified conversations per week—not just total calls, but calls that meet a minimum qualification criteria (e.g., prospect has budget, authority, need, and timeline). Jordan and Vazzana suggest that managers should coach to call outcomes, not call scripts—for example, reviewing call recordings to assess whether the rep uncovered the prospect’s pain points, not whether they recited a specific opening line.

3.2 Opportunity Management: The Engine of Forecasting

Opportunity management is the process of moving deals through the pipeline from qualification to close. The authors highlight a common mistake: treating all opportunities equally. Instead, they recommend segmenting opportunities by probability and deal size and managing each segment with different activities. For example, high-probability, large deals might require weekly executive check-ins, while low-probability, small deals might only need automated follow-ups. The key metric here is stage-to-stage conversion rate—not just win rate—because it reveals where deals stall. A practical RevOps takeaway: configure your CRM to automatically flag opportunities that have been in the same stage for longer than the median cycle time for that stage, triggering a manager review.

3.3 Account Management and Territory Management: The Strategic Layers

The final two processes—account management (managing existing customer relationships) and territory management (allocating resources across geographic or vertical segments)—are often the least instrumented in CRM systems. For account management, the authors recommend tracking account health scores based on activity frequency, support ticket volume, and contract renewal dates, not just revenue. For territory management, they suggest territory coverage metrics—percentage of target accounts contacted, average number of touches per account, and time allocation across high-value vs. low-value accounts. Jordan and Vazzana argue that most sales managers spend too little time on territory planning because it feels less urgent than chasing deals—but it’s the process that determines whether the sales force is fishing in the right pond. For RevOps, this means building territory assignment models that balance account potential, rep capacity, and travel time, and then monitoring whether reps actually follow the plan.

FAQ

What is the main argument of Cracking the Sales Management Code? The book argues that most sales teams track too many metrics without understanding which ones they can actually control. The core idea is a three-level hierarchy: business results (like revenue) can only be monitored, sales objectives (like customer retention) can be influenced, and sales activities (like calls or proposals) can be directly managed. Effective sales management focuses on the activities and objectives that drive results.

How does the book define the difference between managing and monitoring? Managing means taking direct action to change a metric, while monitoring means observing a metric that is an outcome of other actions. For example, you can manage the number of sales calls made per day, but you can only monitor the resulting revenue. The book emphasizes that managers waste effort trying to control results instead of the activities that produce them.

What are the core sales processes the book identifies? The book maps four essential processes: call management (individual interactions), opportunity management (moving deals through pipeline), account management (growing existing customers), and territory management (allocating resources across regions). Each process has specific, manageable activities that can be measured and improved.

How does this book apply to a RevOps role? For RevOps leaders, the book provides a framework for choosing which metrics to instrument in CRM and reporting systems. It explains why you should focus on activity-based metrics (like pipeline coverage or meeting rates) rather than just lagging results. This helps align sales operations, marketing, and customer success around manageable inputs.

Does the book provide specific metric recommendations? Yes, it suggests categories of metrics tied to each sales process, such as call volume for call management or win rate for opportunity management. However, the authors emphasize that the exact numbers vary by industry and company size, so they avoid giving universal targets. The value is in the logic for selecting metrics, not a fixed list.

Is this book still relevant for modern sales teams using AI and automation? Yes, the core principle remains critical: focus on what you can manage, not just what you can measure. While AI can automate some activities (like call logging or lead scoring), the hierarchy of results, objectives, and activities still applies. The book’s framework helps decide which automated metrics to track and which human-led activities to prioritize.

Bottom Line

Cracking the Sales Management Code is a foundational text on sales metrics and management, and its enduring lesson is that you cannot manage business results — you can only manage the sales activities and influence the sales objectives that produce them. Jordan and Vazzana's three-level hierarchy (results to monitor, objectives to influence, activities to control), their mapping of the core sales processes, and their prescription to build metrics and cadence around the manageable levels are the bedrock of effective sales management and modern RevOps instrumentation. For 2027 RevOps and sales leaders, the principles are more relevant than ever as AI auto-captures and analyzes the very activities the book says to manage. Read it to understand which metrics actually drive performance and which you can only watch — because the difference between a dashboard that changes behavior and one that just reports is whether it's built around what you can manage, which is exactly what this book teaches.

Related on PULSE

• [Way of the Wolf by Jordan Belfort — Cliff Notes Summary & Key Takeaways](/knowledge/bs0020)
• [Rework by Jason Fried and David Heinemeier Hansson — Cliff Notes Summary](/knowledge/bs0317)
• [From Impossible to Inevitable by Aaron Ross and Jason Lemkin — Cliff Notes Summary](/knowledge/bs0053)
• [Sales Management Simplified — Cliff Notes Summary](/knowledge/bs0257)
• [Sales Management. Simplified. by Mike Weinberg — Cliff Notes Summary](/knowledge/bs0229)
• [High Output Management by Andy Grove — Cliff Notes Summary](/knowledge/bs0221)

Sources

• Jason Jordan and Michelle Vazzana, *Cracking the Sales Management Code* (McGraw-Hill)
• Jason Jordan and Vantage Point Performance sales-management research and frameworks, 2024–2027
• Vantage Point Performance metrics-hierarchy and sales-process research, 2026–2027
• Comparison research with leading-vs-lagging-indicator and activity-based-management models, 2026–2027
• Gong and Clari conversation-intelligence and activity-capture research, 2026–2027
• Pavilion and Sales Management Association sales-metrics and management-cadence benchmarks, 2026–2027

Cracking the Sales Management Code review / reviews / rating / review 2027 / review of Cracking the Sales Management Code