Why PEG Should Change How You Think About Channel ROI — Part 2

If you haven't read Part 1, the short version is this: Craig Booth's argument is that most partner programs are built to manage partner relationships rather than to create demand. The program is necessary but not sufficient. What's missing is a structured GTM motion that actually changes how partner sellers behave. Part 2 is where the book builds that out in detail.

A lot of this aligns with things I've believed in practice for a long time. But Booth puts a level of structural rigor around it that I found genuinely useful. These are the ideas I'm taking into my own work.

The Planning Has to Start With Real Numbers

How much channel planning still runs on gut feel is something that kept hitting me throughout these chapters. We set revenue targets, divide them by partner count, and hope the math works out. Booth's approach starts somewhere different: with the actual data inputs needed to build a credible plan.

The Territory Revenue Roadmap model requires a handful of things going in: your revenue target, how many active sellers each CAM manages per quarter, average active sellers per partner, deal size, sales cycle length, targeted engagement rates (meetings as a percentage of accounts touched), conversion rates from meeting to quoted opportunity, and close rates.

None of that is exotic. But the discipline of actually having those numbers — clean, agreed-upon, consistently defined across the program — is rarer than it should be. Most channel teams I've worked with have a revenue target and a rough sense of pipeline. The middle variables are fuzzy. Engagement rates vary by rep. Conversion definitions differ by partner. Deal sizes get averaged across wildly different deal types.

What the Territory Revenue Roadmap forces is clarity about the relationship between activities and outcomes. If you need $4M in net new business, you can work backwards to the number of partners needed, the seller units required, and the outreaches that have to happen to generate enough pipeline. In Booth's example: 15 partners, 218 seller units, 653 outreaches. That level of specificity makes conversations with leadership a lot cleaner. It also makes it much harder to have a productive conversation about underperformance when you're not managing to those variables in the first place.

Revenue Roadmap Reports are designed to be a foundational baseline — rooted in data-driven expectations rather than top-down quota math. That framing matters, because it shifts the territory planning conversation from allocation to calibration.

Target Account Planning: Revenue With a Name on It

The Account Mapping piece takes the territory-level math down to the partner level. Rather than assigning a revenue number to a partner and hoping they figure it out, the Partner Revenue Roadmap Account Mapping process starts with accounts: specifically, accounts where relationships exist or can be developed.

The inputs are a revenue target for the period, the number of personas being targeted, solution sales metrics, market development metrics, and MDF cost per lead. From there, the model calculates how many target accounts, seller units, and closed deals are needed to hit the number — along with the specific pipeline math (meetings, opportunities, outreaches) broken out by solution.

This changes the conversation between CAMs and partners. Instead of "here's your quota," you're working through "here are the 27 accounts we think you can work, here's what we need to generate from them, and here's the solution mix that gets us there." That's a planning conversation. It's also a more honest one, because it makes the assumptions visible rather than leaving them implicit in a revenue target nobody fully trusts.

One structural point worth noting: Booth recommends focusing on one sales play per seller per quarter, cycled across quarters. The full target account mapping and account assignment process runs on a 90-day cycle. You enable sellers in the first four weeks of each quarter, but enablement and account mapping stay as ongoing monthly activities. Building up 40 active sellers takes time — you'll likely fall short in the first two or three quarters. But over time, you build a stable of reliable sellers who consistently produce. That compounding effect is the point.

Market Development: Actually Connecting Spend to Outcomes

The MDF chapter is one I've been thinking about since I read it. Most MDF programs I've worked with operate as a spend allocation exercise: partners get budget, they spend it on events or campaigns, and the connection between that spend and actual pipeline is vague at best.

Booth ties MDF directly to cost per lead by channel: outbound, events, and inbound. In the example from the book, outbound generates 2.2 opportunities at a total cost of roughly $2,158, events generate 1.1 at about $1,079, and inbound generates 0.4 at roughly $360. With a 50% MDF policy, you're funding half of each. The model tells you exactly what you're paying for leads from each source.

That's a completely different framing than "we have $X in MDF budget to allocate this quarter." It forces a question channel teams should be asking more often: which market development activities are actually generating qualified pipeline, and at what cost? If you're not asking that, you're not optimizing MDF — you're just spending it.

The outreach metrics breakdown illustrates something worth sitting with: outbound is doing the heavy lifting (539 outreaches vs. 13 events and 18 inbound), but it's also the most resource-intensive per opportunity. Understanding that split, and what it costs, is the starting point for any real conversation about market development investment.

MP3: The Four Stages in Practice

The MP3 methodology has been building across the whole book, but these chapters are where it comes into full focus. Four stages: Strategy Resourcing, Account Mapping, Define Execution Plan, and Measure Results.

What I appreciate about it is that it's structured like an operating system for channel GTM, not just a planning template. Each stage has specific inputs and outputs.

Strategy Resourcing is about sales plays, solution prioritization, positioning around core customer issues, leveraging partner relationships, and defining the incentive structure. Account Mapping defines the target account list, scores accounts against ICP, scores existing relationships, and assigns accounts to sellers. Define Execution Plan determines the outreach mix: direct connect, referrals, the 4-3-2-1 prospecting approach, email sequences, call campaigns, social media. Measure Results tracks prospecting activity, active partner seller count, conversion rates, and revenue outcomes.

The transition from planning to behavioral change is genuinely hard to execute — and Booth is honest about that. The methodology doesn't just tell you what accounts to target. It tells partner sellers how to go after those accounts, in what sequence, with what tools. That specificity is what separates a functioning partner GTM motion from a well-intentioned binder that sits in a partner portal and gets opened twice a year.

Building Sales Plays That Actually Work

The sales play construction framework is detailed. A few principles stood out as genuinely useful to me.

The buyer's journey has to be the spine. Booth maps a five-stage process: Discover, Educate, Validate, Close, Launch. Each stage has a clear goal, specific deliverables, and defined exit criteria. Building a sales play without that spine means sellers end up with tactics but no context for where those tactics fit in the buyer's decision process.

The messaging sequence matters more than any single message. The three-email outreach structure is a logical progression: an introduction email that defines the problem and core benefit, an objection-handling email that anticipates and addresses pushback, and an offer email with a clear call to action. Each builds on the previous. Most partner enablement I've seen gives sellers one generic template and calls it done. That's not a sequence — it's a one-shot attempt.

The pitch deck's job is to generate the next meeting, not close the deal. Three to five slides: here's the problem, here's the outcome our solution enables, here's how it works, here's the next step. The goal is to move the buyer to a validation or demo stage. That distinction shapes how you train partner sellers to use it.

Partner Impact Scoring is a tool I'd want built into every CAM's quarterly planning process. Score partners on four criteria — competency, target market reach, program level attainment, and sales priority for your solution — on a 10/5/0 scale. Total the scores, divide by four, and you get a read on where to focus enablement time. High impact is 35-40, favorable is 30, and below that you're working with a low-strength partner relationship that needs a different kind of attention. The same scoring framework works at the individual seller level too.

Seven Principles of Effective Enablement Delivery

There's a section in the book I didn't expect to find as useful as I did: a framework for how to actually deliver an enablement session. Booth opens with an anecdote about a Channel Manager who kicked off his training with "My product sucks!" — deliberately. The product he was selling had a reputation for consuming vast amounts of power, overheating, and eventually failing. Leading with that defused the audience immediately, took the major objection off the table before it could derail the session, and grabbed everyone's attention at once. That CM knew his audience and understood what they were going to walk in thinking.

That story is the setup for seven principles that apply to any enablement presentation. I'm paraphrasing from memory here, but the core ideas are worth keeping:

Know your audience. What seems important to you may not be what's important to them. Talk to your partner contact beforehand to understand who's attending and what they actually need to get value from the session.

Frame the presentation. Tell people upfront how long you need, and stick to it. The average attention span for a presentation is five to ten minutes. The CM in Booth's example kept his content to 20 minutes, which meant setting the agenda in the opening so attendees knew how long they needed to stay engaged.

Tell them what you're going to tell them. Define the agenda explicitly. "In the next 30 minutes I'm going to cover why customers are buying this, three unmatched benefits, two use cases that consistently close, and how to make $40K in margin." That sets expectations and gives people a reason to stay focused.

Explain the payoff. Opening statements should always address why the audience should care. Communicating what's in it for them keeps people engaged in a way that product overviews rarely do.

Encourage participation. Questions are a signal of engagement. Skilled presenters pick up on those cues and adjust in real time — but you also have to manage the flow so questions don't derail the session.

Enable the strategy, not just the product. The balance between product knowledge and sales strategy is something most enablement sessions get wrong. Too much product, not enough "here's how to actually sell it." The CM's pitch was about use cases, selling benefits, and making it easier for the partner to present the solution — not a feature walkthrough.

Always end with a call to action. Booth references a statistic that 64% of salespeople never ask for the business. Enablement presentations have the same problem — they build up to nothing. The presentation is the setup for a specific next step. Define it. Include it. And make the ask specific: not "let us know if you have any questions" but something more like "would you give me 10 minutes of your time, three days a week for three weeks, if I could show you how to create and close a $40K margin deal?" Sell what's in it for them, not what's in it for you.

New Channel Math

The New Channel Math model ties a lot of this together in a way that I think is practical and underused. It starts with active sellers, assigns each four target accounts, and builds from there.

40 active sellers covering 4 target accounts each gives you 160 accounts in coverage. Apply a market-stage engagement rate (18% for a new market, 22% for growth, 10% for mature, 5% for decline) and you get a projected meeting count. Apply a 30% conversion rate from meeting to deal registration and multiply by average deal size to get your new funnel value. In the example: 22% engagement on 160 accounts = 35 meetings, 30% conversion = 10.5 deal registrations, at $150K average = $1.575M new funnel value.

The market dynamics adjustment is what makes this more honest than a flat engagement rate model. If you're going into a new market where customers are actively evaluating options, your engagement rate is going to look different than if you're working a mature market where everyone already has a platform in place. Applying one number to both situations produces a forecast that's either too optimistic or too conservative. Tuning the model to market stage makes the output meaningfully more credible.

The 5-4-2 Management Principle

This is one of the more operationally specific ideas in the book, and it resonated with me because it addresses something that most channel management guidance completely ignores: how do you actually manage the day-to-day rhythm of active seller engagement?

The 5-4-2 model works like this: a CAM focuses on a defined set of active sellers, makes four daily connections (via email or direct call) to monitor progress and address prospecting challenges, and requires at least two direct conversations per month with each active seller. Those conversations are specifically about capturing 4-3-2-1 prospecting progress — helping sellers work through issues with engagements, messaging, meeting preparation, or deal development.

The connection between daily rhythm and data quality is something worth flagging. If sellers become unresponsive, the right response is to cycle them out and bring in new sellers. The primary job of every partner manager is to cultivate active sellers — not to keep the same roster indefinitely.

Weekly tracking is managed through a simple color-coded reporting dashboard covering four metrics against goals: Active Sellers, Account Engagements, Deal Registrations, and Quarterly Revenue. In the example from the book, the goals are 40 active sellers, 160 account engagements, 30 deal registrations, and $1M in quarterly revenue. The actual numbers (26 sellers at 65%, 102 accounts at 46%, 12 registrations at 40%, $297K revenue at 30%) tell an immediate story about where execution is breaking down and where to intervene. That kind of visibility is a significant departure from how most channel management conversations happen today.

The benefits Booth outlines for this approach are what you'd expect: better resource allocation from focusing on a defined set of sellers, enhanced accountability through regular structured check-ins, scalability as territories can be adjusted based on active seller productivity, and improved sales outcomes from the combination of targeted account focus and consistent engagement. The less obvious benefit is that this process creates a rhythm. It makes the work of managing partner sellers feel like a structured operating cadence rather than a series of reactive check-ins.

ChannelOps Dashboards: Seeing Inside the Engine

Most channel dashboards show partner-level aggregates. Revenue by partner. Pipeline by partner. Deal registrations by partner. Those numbers tell you which partnerships are delivering in aggregate, but they don't tell you why performance looks the way it does — or what you'd need to change to move it.

The MP3 ChannelOps dashboard approach drills into: active partner sellers broken out by partner and by CAM, account coverage details, prospecting activity at the role and account level, outreach outcomes by type, sales play effectiveness, conversion rates from meeting to funnel, deal size and close rate trends, and individual partner and CAM performance over time.

The practical value of that level of data is that you can actually diagnose problems. If a partner's pipeline is down, you can tell whether the issue is seller activation, account coverage, engagement rate, or conversion. Each diagnosis points to a different intervention. Compare that to "your pipeline is down, what's going on?" — which describes most of the partner QBR conversations I've been in.

There's also a point Booth makes about paying for data that I think is underappreciated. Build a margin incentive into deal registration in exchange for detailed 4-3-2-1 prospecting activity data. Partners submit what they're required to submit. If you want richer data, you need to give them a reason to provide it. Compensating for that data submission changes the behavior — and it turns data entry into something that feels like a partnership rather than an audit.

Are Ecosystems the Answer?

The final chapter of the book addresses a question that's become hard to avoid in partner circles: is the ecosystem model the solution to the channel's revenue creation problem?

Booth's answer is nuanced, which I appreciate. He's genuinely supportive of ecosystems — the co-innovation model, partners contributing complementary expertise, the broader coverage and community-centric approach are all real advantages. But ecosystems still have the same core problem as traditional models: opportunistic sales behavior. Still reactive. Still no structured demand creation. Still difficult to get account alignment across multiple partners in a coordinated way.

The pros and cons table he presents lays this out clearly. Fulfillment models have low investment cost and fast time to market, but limited sales process control and no execution visibility. Ecosystem and platform models add flexibility, co-innovation, and broader coverage, but still rely on unstructured GTM practices. Structured Partner Performance (the MP3 model) improves revenue and channel ROI, creates active sellers, structures sales creation, and provides execution visibility — but requires investment in tools and training and demands a real behavioral shift.

The point isn't that ecosystems are wrong. It's that the next wave of ecosystem innovation has to include a structured performance element. The reach and co-innovation power of ecosystems, combined with the structured methodology of MP3, is where the real opportunity is.

Is MP3 Just for Resellers?

Worth addressing directly, because it's a natural question. Structured performance applies across partner types. Referral partners benefit from sales plays that equip them with compelling messaging and target account mapping capability. MSPs benefit from co-sell strategies, account mapping, and co-branded plays that help them generate new sales rather than just renew existing clients. Influence partners get structured and targeted messaging to support their social outreach. Services partners get the same sales play framework applied to upsell motions within their existing customer base.

The underlying principle — measuring inputs, production, and outputs, and clearly defining what you want each partner type to do, how to do it, and when — applies universally. The specific execution looks different for each partner type. The model is the same.

Is Technology Enough?

There's a section in the FAQ chapter that I found validating because it names something I've seen cause real problems in channel programs: what Booth calls the "Frankenstein" tech stack. A collection of point products, each solving a specific problem, that don't integrate well and don't share a unifying methodology. The stack grows over time as new tools get added to address new gaps, and the result is a channel technology environment that creates inefficiency rather than eliminating it.

Booth's view is that a channel tech stack needs to integrate cleanly with the three core systems every company runs on: ERP, CRM, and Martech. Without that foundation, the data is fragmented, the workflow is disjointed, and the analytics are unreliable.

But the more important point is that technology alone doesn't solve the underlying problem. Generative AI in the channel is promising, but purchasing decisions are still based on trust. The combination of structured performance and strong, leveraged relationships is what drives results over time. Technology can accelerate the model. It can't replace it.

The Real Challenges With MP3

Booth doesn't skip the challenges, and I think that makes the book more useful. Here's how he frames the honest difficulty of implementing this model:

It requires a fundamental shift in partnering approach. Years of operating with a program-centric model create muscle memory. MP3 asks partner leaders to shift their focus from managing programs to building active seller communities and running prospecting processes. That's a different job description, and it takes time to rewire.

It changes the role of PAMs. Partner Account Managers under this model are responsible for developing and managing active sellers and administering a target account mapping process. That's a different skill set than what most PAMs were hired and trained for. Some will adapt. Some will need different support.

It depends on clean data. The whole model runs on robust data collection — to build revenue roadmaps, manage the acceleration process, and run the ChannelOps dashboards that make execution visible. Not every partner will be willing or able to provide that data without structured incentives to do so.

It requires new tools and process integration. Implementing MP3 means introducing new workflows that have to fit into existing systems. The initial setup needs training and fine-tuning. Booth's note here is that once companies are operating inside the MP3 process, many job functions actually become more streamlined — but getting there requires upfront investment.

His overall position is that these challenges are real and solvable, and the benefits outweigh them. I'd add: knowing what the challenges are going in is half the battle. Plenty of channel transformation efforts stall not because the model is wrong but because the change management wasn't planned for.

Four Myths Worth Naming

The book closes with four common partnering myths that Booth argues are the biggest obstacles to adopting structured performance models. I found all four uncomfortable in the right way.

"Build it and they will come." The belief that establishing a partner program, enlisting partners, and educating them on the product will automatically generate revenue. It won't. A good partnering model has to account for market awareness, consumer needs, competition, customer engagement, and evolving market dynamics. Building the program is table stakes. What happens after the program is what drives results.

"What I did in the past will work in the future." The channel landscape changes. Consumption models change. Buyer behavior changes. Replicating past strategies in a different environment produces different results. Revenue leaders who rely on previous successes without adapting end up managing programs that worked five years ago in a market that no longer exists.

"Activity equals results." This one hits close to home. The traditional model focuses on compliance and forecasting — deal registrations submitted, MDF spent, events attended. Those activities don't translate directly to outcomes. What actually matters is the number of active partner sellers, the accounts they're covering, their prospecting activity, and their actual sales achievements. Shifting to those metrics is what makes it possible to demonstrate channel value to company leadership in terms that connect to revenue.

"People care about partner programs." Booth is blunt here: the intricacies of partner program design often go completely unnoticed by the people programs are designed to serve. What partners actually care about is ease of sale and market potential. What customers care about is whether your solutions solve their problems. What your company cares about is revenue generation and sales performance. Designing a world-class partner program that doesn't connect those three things is just overhead.

The through line in all four myths is that they let channel leaders stay focused on inputs — the program mechanics — rather than outcomes. Structured performance models force the shift in the other direction.

What MP3 Actually Solves

Booth is direct about what the model is designed to fix. Program-centric channel models have five persistent problems, and he maps each of them to a specific element of MP3.

Revenue Creation. MP3 transforms passive account managers into active sellers, which revitalizes the sales process at the individual level rather than hoping aggregate partner revenue materializes.

Relevance. MP3 equips partner sellers with an easy-to-execute process, making it both feasible and profitable for partners to invest in proactive prospecting — which in turn increases the vendor's relevance within the partner ecosystem. Partners prioritize the vendors who make it easiest to generate deals. A structured methodology with real incentives changes that calculus.

Enablement. MP3 addresses the knowledge retention gap by offering straightforward selling processes that simplify how partners engage with the sales motion. Most enablement creates knowledge that decays quickly. A step-by-step process that sellers reference repeatedly compounds rather than fades.

Execution. The structured coverage and targeted account mapping framework directly addresses the execution challenges that come with passive sellers. Sellers who don't know exactly which accounts to prioritize and what to do when they get there default to opportunistic behavior. MP3 removes that ambiguity.

ROI. By focusing on activating existing sellers rather than constantly recruiting new partners, MP3 reduces channel costs. The model also improves win rates and reduces the wasted spend that comes from partners who are technically enrolled in your program but not actually selling.

Monitoring prospecting and account coverage trends are the crucial metrics for managing pipeline creation through this model. Not program enrollment numbers. Not MDF utilization. Active sellers and the accounts they're covering.

The MP3 Production Line: How It All Connects

The production line framing is the right mental model for what Booth is describing. The five-step loop works like this: define revenue goals and calculate the active seller inputs and engagements needed for each territory and strategic partner; build Revenue Roadmap Plans identifying those active sellers, target accounts, timeframes, and activities; build your account coverage plan by territory, ICP, and relationship score, then develop your sales plays and enable sellers to execute; performance-manage the prospecting process by capturing active seller account engagement activity and defining KPIs to course correct; then co-sell and develop new pipeline into closed opportunities.

The key word is "loop." This isn't a one-time planning exercise — it's a continuous production process with defined inputs, outputs, and feedback mechanisms at each stage. That's what makes it different from an annual channel planning session.

Is Your Model Money?

The book includes a self-assessment I found genuinely useful as a diagnostic tool. It's 11 yes/no questions designed to score how structured your current channel GTM model actually is. Questions include whether territory and partner revenue plans incorporate sales metrics, timeframes, and target accounts; whether sales plays are developed by solution to streamline selling efforts; whether accounts are targeted and mapped with partners as part of a structured territory plan; whether partner sellers are provided enhanced incentives for prospecting; whether you use a structured prospecting process like 4-3-2-1; whether account engagement and prospecting activity is tracked and attributed to partner-target account outreach; and whether Partner Account Managers are measured on creating and scaling active sellers.

The scoring is straightforward. Eight or more yes answers and your model is highly optimized. Six to seven and you're on a good path with room to improve. Four to five and you've started to adopt structured performance elements but significant gaps remain. Fewer than three yes answers and the model is likely costing more than it's delivering.

I'll be honest: most channel programs I've worked with or observed would land in that 4-5 range. Not because the leaders aren't capable, but because the program-centric model is what gets built when there's no structured alternative to build toward.

How to Start

For those sold on the model, Booth's implementation path is practical and staged.

Start by assessing your current state against those 11 questions. Be honest about where the gaps are. The assessment identifies which elements of structured performance are already present and which need to be built.

Then embrace and train — not just your partner sellers, but your internal team. The ISAM and MP3 models require buy-in across the organization. Sales, support, operations all need to understand how these changes affect their roles. Training can't just be a partner-facing exercise.

Execute with pilots. Booth's specific recommendation is to start with three partner account managers and territories to trial the process. That's small enough to manage the risk, collect real data, and refine the approach before scaling. Begin with pilot programs to manage risk and allow for adjustments before a full-scale rollout.

Monitor, measure, and motivate continuously. Establish clear metrics for success, run regular reviews, analyze what's not working, and recognize the teams delivering results. The rhythm of the 5-4-2 management principle applies here — this isn't quarterly check-in territory, it's weekly tracking against goals.

Finally, invest in technology that fits the model. Booth's framing on this is useful: don't buy tools to solve point problems. Buy tools that integrate well with your ERP, CRM, and Martech stack and that enhance your team's ability to execute the structured performance model specifically.

On that note, the book references several tools that are part of the Channel Force ecosystem. Planning IQ handles revenue planning through 14 data inputs, generating territory and partner-level roadmaps that model and predict revenue performance. It moves away from what Booth calls the "Partner and Pray" model toward a "Plan and Perform" approach. Performance IQ captures and displays data on partner and account-level prospecting activities, attributing the value of partner sellers during the sales development phase and ensuring performance metrics align with the benchmarks set in the planning roadmap. Splashmetrics introduces an intelligent buyer's journey platform that tailors solution journeys by persona, guiding economic buyers through content designed to educate, nurture, and compel a purchase decision, with all interactions tracked, scored, and summarized in a sales report. Ringdrop.ai integrates AI Virtual SDR capabilities that handle prospect research, cold calling, and initial lead qualification — removing the most labor-intensive parts of the outbound prospecting process.

I don't have direct experience with these specific tools, but the design logic behind them maps cleanly to the model: revenue planning feeds the production line, performance intelligence monitors it, digital selling tools support partner outreach at scale, and AI SDR capabilities reduce the friction of getting to that first meeting. Whether you use this particular stack or something else, those four functional needs are real requirements for running MP3 at scale.

What I'm Taking Away

I finished this book with a clearer picture of what the next generation of channel programs actually needs to look like. Not better program management. Not more partners. Not a more sophisticated MDF structure. A production line — with the controls, measurement, and accountability of a factory setting. That's Booth's framing, and I think it's right.

A few specific things I'm taking into my own work. Territory and account-level revenue roadmaps as the starting point for every partner planning conversation, not a post-quarter reporting exercise. Partner Impact Scoring as a standard CAM planning tool — not to rank partners but to allocate enablement time with intention. The 5-4-2 management rhythm as the operating cadence for active seller engagement, with weekly reporting that tracks against goals at the activity level. Sales plays built from the buyer's journey outward, with sequenced messaging and a storyboard for each stage. And ChannelOps dashboards that show seller-level execution, not just partner-level aggregates.

If you run a channel program and you can't answer these six questions, you have gaps worth closing: Do you know how many active sellers you have and what accounts they're covering? Can you specify your engagement rates, conversion rates, and close rates by solution? Can you model revenue based on active sellers and account coverage? If the answer to any of those is "not really," that's where to start.

None of this is simple to build. But the direction is clear enough. Partner programs that get structured performance right will have a durable advantage over the ones still managing to top-line revenue reports and annual business reviews. That gap is only going to widen from here.