Pulse ← Book Summaries
Reviews and Expert Analysis · book-summary

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

👁 0 views📖 1,601 words⏱ 7 min read📅 Published

Direct Answer

Cracking the Sales Management Code by Jason Jordan and Michelle Vazzana argues that most companies track hundreds of sales metrics but fail because they don't distinguish what they can actually manage — and that the key is to manage sales activities and objectives, which drive business results you can only monitor, not control. The book's central insight is a three-level hierarchy of metrics: business results (revenue, profit, market share) that you cannot directly manage; sales objectives (customer acquisition, retention, share-of-wallet) that you can influence; and sales activities (calls, meetings, proposals, pipeline work) that you can directly control.

Managers waste effort trying to "manage revenue" — a result — when they should manage the activities and objectives that produce it. The book then maps the core sales processes (call, opportunity, account, and territory management) a sales force must run, and shows how to build metrics, CRM, and management cadence around the manageable activities.

For a 2027 RevOps leader, Cracking the Sales Management Code is foundational — it explains which metrics to instrument and manage and why "you can't manage results, only the activities that create them" is the principle behind every effective sales dashboard, forecast, and coaching cadence.

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

flowchart TD A[Sales Activities<br/>calls, meetings, proposals<br/>YOU CONTROL] --> B[Sales Objectives<br/>acquisition, retention, share-of-wallet<br/>YOU INFLUENCE] B --> C[Business Results<br/>revenue, profit, market share<br/>YOU MONITOR] A -.manage these.-> A C -.you cannot directly manage.-> C

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

flowchart LR A[Sales Force Management] --> B[Call Management: individual interactions] A --> C[Opportunity Management: deals/pipeline] A --> D[Account Management: existing customers] A --> E[Territory Management: market coverage] B --> F[Manage the right process for your motion] C --> F D --> F E --> F

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

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.

FAQ

What is the main idea of Cracking the Sales Management Code? That companies track too many sales metrics without distinguishing what they can actually manage — and that the key is to manage sales activities and influence sales objectives, which drive business results you can only monitor, not directly control.

You can't "manage revenue"; you manage the activities that produce it.

What are the three levels of sales metrics? Business results (revenue, profit, market share) — you monitor but cannot directly manage; sales objectives (acquisition, retention, share-of-wallet) — you can influence; and sales activities (calls, meetings, proposals, pipeline work) — you can directly control and manage.

Confusing these levels is the root cause of failed sales management.

Why can't you manage business results directly? Because results like revenue are lagging outcomes of many factors, some outside the rep's control — you can't tell someone to "go make revenue." You monitor results to know where you stand, but you drive them by managing the activities and directing the objectives that produce them.

This redirects management energy to where it actually works.

What are the core sales processes in the book? Call management (individual interactions), opportunity management (working deals/pipeline), account management (growing existing customers), and territory management (market coverage). Different sales forces emphasize different processes; the manager's job is to identify and manage the processes — and their activities — that matter for their motion.

How does Cracking the Sales Management Code apply to RevOps? It is foundational — it tells RevOps which metrics to instrument and manage: build dashboards, CRM, and coaching cadence around the manageable activities and influenceable objectives, not just unmanageable results.

The leading-vs-lagging-indicator distinction, activity-based coaching, and actionable dashboards every RevOps team builds trace to this framework.

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.

Sources

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

Keep reading
Was this helpful?  
⌬ Apply this in PULSE
Gross Profit CalculatorModel margin per deal, per rep, per territory
Related in the library
More from the library
franchise · franchisesShould I open or buy a Ned Stevens Gutter Cleaning franchise in 2027?revops · current-events-2027How do you forecast new business pipeline in 2027?franchise · franchisesShould I open or buy a Sky Zone franchise in 2027?franchise · franchisesShould I open or buy a Nurse Next Door franchise in 2027?revops · current-events-2027How do you migrate CRM platforms without losing data in 2027?franchise · franchisesShould I open or buy a Maid Right franchise in 2027?revops · current-events-2027How do you reduce CRM data decay in 2027?revenue-architecture · gtm-designHow do you architect revenue operations for a developer tools company in 2027?revops · current-events-2027How do you design a RevOps tech stack in 2027?revops · current-events-2027How do you implement MEDDICC across a sales team in 2027?revops · current-events-2027How do you build a capacity model for sales hiring in 2027?revops · current-events-2027How do you build a warm outbound motion in 2027?revops · current-events-2027How do you build a customer health score in 2027?revops · current-events-2027How do you build a customer handoff process from sales to CS in 2027?