What do I do when the CRO and CMO can't agree on lead handoff?

Direct Answer

When your CRO and CMO can't agree on lead handoff, the problem is almost never the two of them. It is the absence of a shared, numerically defined contract between their two functions. You fix it by replacing the argument with arithmetic: build a single bidirectional service-level agreement (SLA) that defines what a "qualified lead" is in objective, behavior-based terms, sets response-time and acceptance commitments on both sides, instruments the handoff so every lead is tracked from creation to closed-won or closed-lost, and ties a meaningful slice of both leaders' variable compensation to a shared revenue number rather than to their individual functional metrics.

The disagreement persists because marketing is measured on volume and sales is measured on conversion, and those two incentives point in opposite directions at the exact moment a lead crosses the line. Until you change what each leader is paid and praised for, no amount of mediation will hold.

The work is roughly two weeks to design the contract, one quarter to operationalize it, and one to two quarters to see the trust rebuild. Do not delegate this to a RevOps analyst as a "process project." This is a leadership intervention that you, the CEO or the person both leaders report to, must personally own from kickoff through the first quarterly business review where the new numbers are read aloud.

This is one of the most common and most expensive forms of organizational dysfunction in a revenue team, and it is also one of the most fixable, because the fix is mechanical rather than interpersonal. The sections below give you the full playbook: why the conflict happens, the exact diagnostic to run in your first week, the structure of the lead-handoff contract, the compensation changes that make it stick, the meeting cadence that maintains it, the failure modes to watch for, and the metrics that tell you whether it is working.

Why This Conflict Happens Almost Everywhere

1. The Two Functions Are Measured on Opposing Variables

The single most important thing to understand is that your CRO and CMO are not being unreasonable. They are each responding rationally to the scoreboard you gave them. Walk through the math.

Your CMO is almost certainly measured on marketing-qualified leads (MQLs), pipeline contribution, cost per lead, and marketing-sourced pipeline as a percentage of total. Every one of those metrics rewards volume. If the CMO loosens the lead-scoring threshold by ten points, MQL count jumps, cost per lead drops, and the marketing dashboard turns greener.

Nothing on the CMO's scorecard penalizes a low-quality MQL.

Your CRO, meanwhile, is measured on win rate, sales cycle length, quota attainment, and pipeline conversion. Every one of those metrics is *diluted* by a low-quality lead. When a rep spends ninety minutes on a discovery call with someone who downloaded an ebook and has no budget, no authority, and no timeline, the rep's effective selling capacity drops, win rate falls because the denominator inflated, and average cycle length stretches.

The CRO's scorecard punishes exactly the lead the CMO's scorecard rewards.

This is not a personality clash. It is a structural contradiction baked into your incentive design. As the influential SiriusDecisions (now part of Forrester) research established years ago, organizations that align marketing and sales around shared definitions and shared metrics grow significantly faster than those that do not.

Forrester's later analyses of B2B revenue waterfalls reinforced the same point: the handoff is the single highest-leverage and highest-friction junction in the entire revenue process. If you remember one thing, remember this: you cannot mediate your way out of a problem that your compensation plan is actively creating.

2. "Qualified" Is an Adjective, Not a Definition

Ask your CRO to define a qualified lead and you will hear something like "someone ready to buy." Ask your CMO the same question and you will hear "someone who fits our ideal customer profile and has shown intent." Both answers are reasonable. Neither is operational. Neither one can be checked by a computer, which means neither one can be enforced, which means every single lead becomes a fresh opportunity to argue.

The classic frameworks each capture a piece of the truth. BANT (Budget, Authority, Need, Timeline), originated by IBM, is the oldest and remains useful as a sales-acceptance checklist. CHAMP (Challenges, Authority, Money, Prioritization) reorders the emphasis toward the buyer's problem.

MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion), developed at PTC in the 1990s by sales leaders including Jack Napoli and Dick Dunkel, is the gold standard for *complex* deal qualification. The mistake teams make is treating these as the lead-handoff definition.

They are not. They are deal-stage frameworks. The lead-handoff definition needs to be lighter and earlier, because at handoff you are not asking "will this close" — you are asking "is this worth a salesperson's first hour." The disagreement festers because the team never built that lighter, earlier, mutually-agreed definition.

They borrowed a deal framework, applied it at the wrong stage, and then blamed each other when it produced friction.

3. The Handoff Is Invisible, So Both Sides Argue From Anecdote

The third structural cause is measurement. In most companies the moment a lead crosses from marketing to sales is the least-instrumented step in the entire funnel. Marketing can tell you precisely how many MQLs it generated.

Sales can tell you precisely how many deals it closed. But ask either side what happened to the 4,000 leads in between and you get hand-waving. The CRO says "marketing leads are garbage." The CMO says "sales never works the leads." Both are arguing from the last bad anecdote they personally witnessed, because neither has the data to argue from the distribution.

This is why the diagnostic in the next section is non-negotiable. Until you can put a single, jointly-trusted report on the table that shows lead-by-lead what happened — who created it, when sales touched it, how many times, whether it was accepted or rejected and why, and what it ultimately became — your two leaders are not having a disagreement.

They are having a faith-based dispute, and faith-based disputes do not resolve. They escalate.

4. The Conflict Is Often a Proxy for an Unspoken Strategy Gap

Sometimes the lead-handoff fight is real and sometimes it is a stand-in for a deeper unresolved question: *who do we actually sell to, and how do we actually go to market?* If marketing is generating SMB-shaped leads while sales has quietly pivoted to enterprise, no handoff SLA will fix that — the two functions are aiming at different targets.

If the company has shifted toward a product-led motion but the CRO still wants every signup routed to a rep, the friction is a strategy artifact. Before you build the contract, you must be honest about whether the disagreement is *operational* (fixable with an SLA) or *strategic* (fixable only by you making a decision about market and motion).

The diagnostic below will tell you which one you have.

A specific and common variant of this strategy gap is the *segmentation mismatch*. Marketing builds its lead engine around the segment that is cheapest and fastest to generate volume in — often the smaller, higher-velocity end of the market — while sales, chasing larger average deal sizes to make quota, has drifted upmarket without anyone formally deciding to.

Each function is behaving sensibly in isolation. Together they produce a handoff where marketing delivers exactly the leads sales does not want, sales rejects them, and both sides feel righteous. The tell is in the data: when you segment the cohort analysis by company size, you will see marketing's volume concentrated in one band and sales' wins concentrated in another.

If you see that, the lead-handoff SLA is the second problem. The first problem is that no one has decided, in writing and with your signature on it, which segment the company sells to this year. Decide that, cascade it into the ICP, and *then* build the handoff contract on top of a settled foundation.

5. The Tooling Has Quietly Diverged

A subtler structural cause is that marketing and sales are often running on systems that were never reconciled. Marketing lives in a marketing automation platform — HubSpot, Marketo, Pardot — with its own lead-scoring model, its own field definitions, and its own idea of what a "lead" is.

Sales lives in a CRM — Salesforce, HubSpot CRM, Dynamics — with its own object model of leads, contacts, accounts, and opportunities. The sync between the two is frequently built once, by a junior administrator or an outside contractor, and never audited again. Fields drift.

A lead marked "qualified" in the marketing platform lands in the CRM with the qualification flag stripped, or duplicated against an existing account, or routed to the wrong owner. When that happens, the CRO genuinely sees garbage and the CMO genuinely sent gold — and both are telling the truth, because the truth was corrupted in transit.

Before you assume the disagreement is about judgment, verify that the *plumbing* is intact. A surprising share of lead-handoff feuds are, at root, an unmaintained integration that no single person owns.

The First-Week Diagnostic: Replace Opinion With Data

You cannot fix what you cannot see, and you cannot get two leaders to agree on a solution while they still disagree on the facts. Spend your first week building one shared picture of reality. This is the foundation; skipping it guarantees the rest of the intervention fails.

1. Pull the Lead-Level Cohort Analysis

Take a defined cohort — every lead marketing passed to sales over a representative 60- or 90-day window, long enough ago that most have reached a terminal outcome. For each lead, assemble these fields in one spreadsheet or one report:

• Creation source and campaign — so you can see which channels produce which outcomes. Webinar leads and "contact us" leads behave nothing alike, and lumping them together is how both sides end up half-right.
• Lead score at handoff — the actual number, so you can later test whether the score predicts anything.
• Time to first sales touch — measured in business hours, not calendar days. This single number will likely shock everyone in the room.
• Number of sales touches — calls, emails, and sequence steps. A lead "worked" with one email is not a lead "worked."
• Accepted or rejected by sales — and if rejected, the structured reason from a fixed dropdown.
• Terminal outcome — closed-won, closed-lost, disqualified, or still open, with revenue if won.

This report is the most important artifact of the entire intervention. Build it once, manually if you must, and make it the single source of truth.

2. Compute the Four Numbers That End the Argument

From that cohort, calculate four figures and put them on one slide:

• Lead acceptance rate — the percentage of passed leads that sales formally accepted. If this is below roughly 60 to 70 percent, you have a genuine lead-quality problem and the CRO is partly right. If it is above 85 percent, the quality complaint is mostly anecdotal and the CMO is partly right.
• Median time to first touch — and the percentage of leads touched within your target window. In most underperforming organizations this number is far worse than either leader believes. Industry studies of lead response, including the well-known Harvard Business Review research on "The Short Life of Online Sales Leads," found that the odds of meaningfully qualifying a lead drop by orders of magnitude when first contact slips from minutes to hours. Speed is not a nicety.
• Conversion by lead score band — group leads into score tiers and show the accept rate and win rate of each. If the high-score band converts dramatically better than the low-score band, the model works and the threshold is the only thing to negotiate. If the bands all convert the same, the scoring model is noise and must be rebuilt.
• Working rate — the percentage of passed leads that received at least the agreed minimum number of touches before being closed. A low working rate is the data that quiets the "sales never works the leads" objection or confirms it.

3. Run the Joint Read-Out, Not Two Separate Ones

Put the CRO and CMO in the same room, with you present, and walk through these numbers together exactly once. Do not let either leader pre-spin the data to their team beforehand. The goal of this meeting is narrow and explicit: agree that *this* is the shared picture of reality.

You are not solving anything yet. You are establishing that from this point forward, both sides argue from the same dataset. When someone reverts to anecdote — and someone will, usually within the first ten minutes — point at the report and ask, "Where does that show up in the cohort?" That phrase, used consistently, is how you retrain a team to reason from distributions instead of from grievances.

4. Listen for the Anecdotes — They Tell You Where the Pain Actually Lives

While you build the cohort report, run a parallel qualitative pass. Spend an hour with three or four front-line salespeople and three or four marketers, separately, and ask one open question: "Walk me through the last lead handoff that frustrated you, start to finish." Do not lead the witness.

Just listen and take notes. The anecdotes are not data — that is what the cohort analysis is for — but they tell you *where in the process* the pain concentrates, which helps you read the quantitative report faster. If every salesperson tells a story about a lead with a fake phone number, you will know to look hard at the "bad data" rejection bucket.

If every marketer tells a story about a campaign that drove huge volume and then heard nothing back, you will know to look hard at working rate. Use the stories to generate hypotheses; use the cohort to confirm or kill them. Never the reverse — leading with anecdote is exactly the trap that got the organization here.

5. Audit the Integration Before You Trust the Numbers

Before you present the cohort analysis as truth, spend thirty minutes with whoever administers the CRM and the marketing automation platform and confirm the data is not lying to you. Check three things specifically. First, does the handoff timestamp actually fire when a lead is *routed* to a rep, or when the rep *opens* the record — those are very different numbers and confusing them poisons the speed-to-lead metric.

Second, are touch activities reliably logged, or do reps make calls and emails outside the system that never get recorded — undercounted touches make working rate look worse than reality. Third, is there a deduplication problem inflating or deflating volume? An unaudited integration can make either leader look bad through no fault of their own.

Verify the plumbing, then trust the report.

6. Classify the Problem: Operational or Strategic

By the end of the read-out you should be able to name the problem precisely. If acceptance is low *and* the low-score band genuinely under-converts, you have a quality and threshold problem — operational, fixable with the contract below. If acceptance is reasonable but time-to-touch and working rate are poor, you have a sales-execution problem — also operational, but the fix lands more on the CRO's side.

If the leads are well-formed and well-worked but still do not convert, you have a strategy or product-market-fit problem, and no SLA will rescue it. If the cohort splits cleanly by company size — marketing's volume in one band, sales' wins in another — you have the segmentation mismatch described earlier, and the fix is a strategy decision, not a contract.

Name the problem out loud, in one sentence, in front of both leaders. The contract that follows assumes an operational problem; if yours is strategic, pause and resolve the strategy first, because building a handoff SLA on top of an unsettled go-to-market strategy is building on sand.

Building the Lead-Handoff Contract

The output of this intervention is a written, signed, bidirectional SLA. "Bidirectional" is the word that matters: it imposes obligations on *both* functions. Marketing commits to lead quality and definition; sales commits to speed and effort.

A one-sided SLA — common, and worse than useless — just hands one leader a stick to beat the other with and deepens the conflict.

1. Co-Author One Behavior-Based Definition of a Sales-Ready Lead

This is the heart of the contract and it must be written *jointly*, in one room, by both leaders, ideally with their top operator from each side present. The definition has two halves.

The first half is fit: explicit firmographic and demographic criteria drawn from your ideal customer profile. Industry, company size band, geography, role seniority, and any disqualifying attributes. Fit should be as close to binary as you can make it, because fit rarely changes and rarely needs to be argued.

The second half is engagement or intent: observable behavior that indicates readiness. A demo request. A pricing-page visit.

A high-intent form fill. Attendance at a bottom-of-funnel webinar. Multiple sessions on the product or solution pages within a short window.

The discipline here is that every criterion must be observable and machine-checkable. "Seems interested" is not a criterion. "Visited the pricing page twice in seven days" is.

The reason for this strictness is simple: a definition a computer can evaluate is a definition that cannot be argued about. You eliminate the disagreement by eliminating the ambiguity.

Distinguish clearly between a marketing-qualified lead (MQL) and a sales-accepted lead (SAL). The MQL is what marketing produces against the agreed definition. The SAL is what sales formally accepts after a quick verification. The gap between MQL volume and SAL volume *is* the lead-quality metric, and making that gap visible is half the battle.

2. Set Numerical Commitments on Both Sides

The contract must contain specific numbers, not adjectives. On the marketing side: a minimum monthly MQL volume, a minimum acceptance rate (for example, "at least 75 percent of passed MQLs will be accepted by sales"), and a commitment that every MQL carries complete, accurate data — no leads with a first name and nothing else.

On the sales side: a maximum time to first touch (for example, "every MQL receives a first human contact attempt within one business hour for high-intent leads, four business hours for standard"), a minimum number of touch attempts before a lead can be closed (a documented cadence — for example, "no fewer than six attempts across two weeks via at least two channels"), and a commitment to disposition every lead with a structured reason within a fixed window.

These numbers should be *defensible*, drawn from the diagnostic, and *negotiated* — not imposed by you. When both leaders have argued the numbers and signed them, they own them. Set targets that are demanding but achievable in the current quarter; the contract loses force the moment one side can credibly claim the target was never realistic.

3. Define the Rejection Loop With Structured Reasons

Sales must be able to reject a lead, because a no-questions-asked rejection valve is what makes the CRO trust the system enough to participate. But rejection must be *structured*, never a black hole. Build a fixed dropdown of rejection reasons: out of ICP, bad or missing contact data, duplicate of an existing opportunity, no engagement on contact, competitor, student or job-seeker, and so on.

A rejection requires a reason code; a free-text "not good" is not permitted.

Those structured reasons are gold. Aggregated weekly, they become the most actionable feedback marketing has ever received. If forty percent of rejections are "bad contact data," that is a form-and-enrichment fix marketing can make this week.

If forty percent are "out of ICP," the targeting or the score model needs work. The rejection loop converts the conflict's heat into a prioritized to-do list. The rejection reason codes are not bureaucracy; they are the highest-signal product backlog marketing will ever get.

4. Instrument Closed-Loop Reporting

The contract is only as real as your ability to measure compliance. Before go-live, ensure your CRM and marketing automation platform are wired so that every lead is traceable end to end: source, score, handoff timestamp, first-touch timestamp, every subsequent touch, accept/reject status and reason, stage progression, and terminal outcome with revenue.

This closed-loop reporting must be visible to *both* teams in *one* dashboard. Two dashboards mean two versions of the truth and the argument restarts. One dashboard, jointly owned, is the referee that is always in the room.

5. Define the Escalation Path Before You Need It

Every contract needs a referee mechanism for the disputes the day-to-day process cannot resolve, and that mechanism must be written *before* the first dispute, when emotions are low. Spell out three things. First, *who decides* a contested lead — typically the two operators in the weekly review, by looking at the record together against the written definition, not by seniority or volume of complaint.

Second, *what happens at deadlock* — if the operators cannot agree, the question goes to the monthly pipeline council and the leaders decide jointly; if the leaders deadlock, it comes to you, and you decide quickly rather than letting it fester. Third, *the standing rule that no dispute blocks the work* — a contested lead is still worked by sales while its status is adjudicated, because the customer does not care about the internal argument and a delayed first touch is the one cost no one can recover.

Writing the escalation path down does two things: it gives the team a pressure-release valve, and it signals that disputes are *expected and handled*, not catastrophic.

6. Set the Contract's Own Review and Amendment Rules

The SLA must contain a clause about itself: how often it is reviewed and how it gets changed. Markets shift, products evolve, channels decay, and a contract that cannot be amended will simply be ignored once it stops matching reality. State plainly that the SLA is reviewed and re-ratified every quarter at the QBR, that either leader may propose an amendment at the monthly council with supporting data, and that amendments require both signatures plus your awareness.

This turns the contract from a brittle artifact into a living agreement. It also removes a favorite escape hatch — "the SLA is outdated, so I am not bound by it." If it is outdated, the rule says you amend it; you do not abandon it.

7. Put It in Writing and Have Both Leaders Sign It

Produce a real document — two or three pages, not thirty. It states the lead definition, the bidirectional commitments with their numbers, the rejection process, the closed-loop reporting cadence, the escalation path, and the review-and-amendment schedule. Both the CRO and the CMO sign it.

The signature is psychological, not legal: it converts a conversation that can be relitigated every Monday into a commitment that has a name and a date. Distribute it to both full teams so every rep and every marketer can see exactly what was promised in both directions. Resist the urge to make it long or lawyerly — a contract no one reads is a contract no one follows.

Two pages, plain language, signed.

Compensation: The Change That Makes It Permanent

Everything above is necessary and none of it is sufficient. You can build a perfect SLA, instrument it flawlessly, and watch it erode within two quarters — because the SLA asks for one set of behaviors while the comp plan still pays for the opposite. Process changes are overwritten by incentive structures every single time. This is the step most companies skip, and skipping it is why the lead-handoff fight is perennial rather than one-and-done.

1. Create a Shared Revenue Metric Above Both Leaders

Both the CRO and the CMO must carry a number that *neither one controls alone*. The cleanest version: a meaningful portion of each leader's variable compensation — a common starting range is 15 to 30 percent — tied to a single shared outcome. Net new revenue and qualified-pipeline-that-converts are the two most common choices.

The mechanism matters more than the exact metric. The instant both leaders are paid partly on the *same* number, the lead-handoff conversation transforms. It stops being "your problem versus my problem" and becomes "our problem," because a lost lead now costs the CMO real money and a slow-worked lead now costs the CRO real money.

You have made the externality internal.

2. Add a Quality Gate to the Marketing Plan

Volume-only incentives are the original sin of marketing compensation. As long as the CMO's team is paid purely on MQL count, it is rational for them to flood the top of the funnel. Fix it by gating volume on quality: marketing's pipeline or MQL bonus only pays out if the *acceptance rate* stays at or above the SLA threshold.

Generate 5,000 MQLs at a 50 percent acceptance rate and the bonus does not pay. Generate 3,500 at 80 percent and it pays in full. Overnight, the CMO's team has a financial reason to *raise* the lead-scoring threshold — the exact behavior the CRO has been begging for, now self-enforcing rather than mediated.

3. Add a Speed-and-Effort Gate to the Sales Plan

Apply the symmetric discipline to sales. A portion of sales-manager or rep variable pay — or an SPIFF, or a leaderboard with teeth — should be contingent on SLA compliance: time-to-first-touch within the window and minimum touch cadence completed before any lead is closed-lost. This removes the CRO's escape hatch.

The CRO can no longer say "the leads are bad" while reps cherry-pick a third of them and ignore the rest, because ignoring them now costs the reps money. Speed and effort become self-policing.

4. Make the Quarterly Number Public Inside the Company

Once per quarter, in the business review, read the shared metric and the SLA-compliance numbers out loud, with both leaders in the room and their teams aware. Public accountability is a powerful and nearly free enforcement mechanism. Neither leader wants to be the one whose side missed the commitment in front of peers.

Sunlight does most of the maintenance work for you.

A caution: do not over-engineer the comp change. You are adjusting incentives at the margin to align direction, not rebuilding the entire plan. A 15-to-30 percent shared component plus two quality gates is plenty.

If you make the change too large or too complex you will create new distortions and new arguments, and you will have traded one problem for another.

5. Avoid the Three Compensation Traps

Three predictable mistakes will undo the comp change if you let them. The first is the lagging-metric trap: tying the shared component to closed revenue in a business with a six- or nine-month sales cycle means the incentive pays out long after the behavior, and the feedback loop is too slow to teach anyone anything.

In long-cycle businesses, anchor the shared metric to *qualified pipeline created that subsequently advances past a defined stage* — a leading indicator that moves inside a quarter — rather than to closed-won alone. The second is the gameable-gate trap: if marketing's quality gate is "acceptance rate," a cynical team can pressure sales to accept everything and call it quality.

Defend against this by pairing the acceptance gate with a downstream check — accepted leads must also *convert to opportunity* at a minimum rate — so that rubber-stamping acceptances does not unlock the bonus. The third is the complexity trap: if the new plan needs a spreadsheet and a meeting to explain, reps and marketers will not internalize it, and an incentive nobody understands changes no behavior.

Keep the shared component to one number, the gates to one or two conditions each, and the whole thing explainable in ninety seconds. Aligned-but-simple beats perfect-but-opaque every time.

6. Sequence the Comp Change Carefully

Do not spring the new compensation structure on either team mid-quarter as a surprise. Announce it at a natural boundary — the start of a quarter, ideally aligned with the SLA go-live — and explain the *why* before the *what*. Frame it honestly: "We are adding a shared component because lead handoff is a shared outcome, and it is not fair to ask either team to fix it while the scoreboard rewards the opposite." Give people the arithmetic so they can model their own pay.

A comp change introduced with transparency builds trust; one introduced by stealth breeds exactly the cynicism that corrodes the SLA. Run the new plan in parallel with the old metrics for the first quarter as a "shadow" so everyone can see how it would have paid out before it pays out for real — this removes fear and surfaces any unintended distortion while the stakes are still zero.

The Operating Cadence That Keeps It Alive

A signed SLA is a document. An *operating cadence* is what turns the document into a living system. Without a rhythm of joint review, the contract yellows on a shared drive and the old habits creep back.

The reason is simple: organizational behavior reverts to its prior state unless something actively holds the new state in place, and a one-time kickoff event has no holding power. The cadence is that holding mechanism. It also serves a second purpose — it gives both functions a regular, low-stakes forum to surface friction *while it is still small*, before any individual frustration has compounded into a leadership-level grievance.

A team that meets weekly to tune the handoff almost never has a handoff crisis, because crises are just small problems that were never given a venue. Three meetings, run relentlessly, sustain the fix.

1. The Weekly Handoff Review (30 Minutes, Operators)

Every week, the top revenue operator from marketing and the top from sales — typically the marketing-ops and sales-ops or SDR leaders — meet for thirty minutes. They review one dashboard: last week's MQL volume, acceptance rate, time-to-touch, working rate, and the rejection-reason breakdown.

The output is a short, concrete action list — "fix the form field causing bad data," "re-coach the two reps missing the touch SLA." This is the maintenance layer. Most friction is caught and resolved here, small and early, before it ever escalates to the leaders.

2. The Monthly Pipeline Council (60 Minutes, Leaders)

Once a month the CRO and CMO themselves meet for an hour to look at trend lines rather than last week's noise. Is acceptance rate climbing or sliding? Is conversion by score band still holding?

Are the rejection reasons shifting? This is where they jointly tune the system — adjust the score threshold, retire an underperforming channel, refine an ICP criterion. Crucially, the *leaders* make these calls *together*, which keeps both invested in the outcome and prevents the contract from feeling like something imposed on one of them.

3. The Quarterly Business Review (Leadership + You)

Each quarter, with you in the room, both leaders present the shared scorecard and the SLA-compliance results to senior leadership. This is where the comp consequences land and where the SLA itself is formally re-ratified or amended for the next quarter. Markets move, ICPs evolve, channels decay; the contract is a living document, and the QBR is its scheduled checkpoint.

It is also where you, the executive sponsor, reaffirm publicly that this matters — and that reaffirmation is itself part of the maintenance.

4. Run the Meetings With a Fixed Agenda and a Visible Decision Log

A recurring meeting without a fixed agenda decays into either a status readout or a gripe session, and both are useless. Give each of the three meetings a rigid structure. The weekly handoff review: five minutes on the dashboard numbers, ten minutes on the rejection-reason breakdown, ten minutes on the resulting action list, five minutes confirming last week's actions actually closed.

The monthly council: trends first, then one or two proposed tuning decisions, then a check on whether any escalations need leader resolution. The QBR: scorecard, comp results, SLA re-ratification. In every meeting, keep a single running decision log — a shared document that records what was decided, by whom, and when.

The log matters because memory is partisan; six weeks later the CRO and CMO will remember a past decision differently, and the log ends that argument in five seconds. The decision log is the institutional memory of the alignment, and it is nearly free to maintain.

5. Watch for the Meeting Going Quiet

A counterintuitive warning sign: if the weekly handoff review suddenly has nothing to discuss and ends in five minutes for several weeks running, do not assume you have won. Sometimes a quiet meeting means a healthy system. But sometimes it means the operators have stopped surfacing problems because raising them feels like criticizing the other team, or because nothing ever changes when they do.

Probe it. Ask directly: "Are there frictions we are not putting on the table?" A handoff process is never perfectly frictionless; if the meeting has gone silent, either you have achieved something remarkable or you have lost the candor that makes the meeting work. Find out which.

6. Protect the Cadence Ruthlessly

These meetings will be the first thing both leaders try to skip when the quarter gets busy. Do not let them. The cadence is not overhead; it is the immune system of the alignment.

The weeks a team skips the handoff review are the weeks the small frictions compound back into a full-blown feud. Treat a cancelled handoff review as the warning sign it is, and as the executive sponsor, occasionally drop into one unannounced — your presence, even quarterly, signals that the cadence is not optional and that you are watching the trend lines yourself.

Common Failure Modes and How to Avoid Them

Even a well-designed intervention can fail in predictable ways. Knowing the failure modes in advance lets you steer around them.

1. Treating It as a Process Project Instead of a Leadership Intervention

The most common failure is delegation. A CEO hears "lead handoff" and routes the whole thing to a RevOps analyst or an operations manager as a "process improvement initiative." The analyst can build a beautiful SLA document and a flawless dashboard, but an analyst cannot change two executives' compensation, cannot adjudicate an executive standoff, and cannot make the QBR's shared-number readout carry consequences.

Those are all *authority* problems, and authority is exactly what an analyst lacks. The diagnostic and the dashboard *should* be delegated. The compensation change, the signed contract, and the executive accountability *cannot* be.

If you are the person both leaders report to, your name is on this from kickoff to the first QBR. Delegating the authority parts is the single most reliable way to guarantee the fix does not stick.

2. Building the Definition Without the Operators in the Room

A lead definition co-authored by the CRO and CMO alone, in the abstract, will be elegant and wrong. The people who actually know which leads convert are the SDRs who dial them and the marketing-ops person who scores them. If the definition is drafted by leaders without those operators present, it will miss the practical signal — the specific behaviors that, on the ground, separate a real buyer from a tire-kicker.

Put the top operator from each side in the room. They will argue productively about specifics, and specifics are exactly what the definition needs.

3. Setting Targets Nobody Believes

If the SLA's numbers are aspirational fantasy — a one-business-hour first touch when the team has no SDR coverage to deliver it, or a 90 percent acceptance rate when the diagnostic showed 55 — the contract dies on contact with reality. The side that cannot hit the number stops trying, then stops believing in the SLA, then stops believing in the other side's good faith.

Targets must be demanding *and* achievable in the current quarter, drawn from the diagnostic, and negotiated rather than imposed. It is far better to set a target the team can hit and then ratchet it up next quarter than to set a heroic target that collapses the whole contract in week three.

4. Skipping the Compensation Change Because It Is Hard

Changing executive compensation requires a conversation with finance, possibly with the board, and certainly with the two leaders themselves. It is uncomfortable and slow, so it is the step most often quietly dropped. The result is a perfectly designed SLA running against an unchanged incentive structure — and the incentive structure wins, every time, within a quarter or two.

If you cannot change the formal comp plan this quarter, find an interim mechanism: a shared QBR objective that visibly affects bonus discretion, a public scorecard, an MBO line item. Do *something* that puts a shared outcome into both leaders' personal stakes. The mechanism is negotiable; the principle that both leaders must have skin in the same number is not.

5. Letting the Dashboard Fragment Into Two

If marketing reports its version of the funnel from the marketing automation platform and sales reports its version from the CRM, you will have two dashboards, two definitions of every metric, and two versions of the truth — and the argument will quietly restart underneath the SLA.

There must be one dashboard, one set of metric definitions, jointly owned, that both leaders accept as the referee. When someone says "my numbers show something different," the answer is not to debate the numbers; it is to fix the one dashboard until both sides trust it, and then never maintain a competing one.

6. Declaring Victory Too Early

The handoff metrics often improve fast in the first month — the Hawthorne effect is real, and people behave better when they know they are being watched. A leader who declares the problem solved after thirty good days and dismantles the cadence will watch the gains evaporate by month three.

The fix is not real until it has survived a full quarter *including* a hard month — a quarter-end crunch, a campaign that underperformed, a stretch of missed quota. Keep the cadence and the scrutiny running through at least two full quarters before you trust that the new behavior has become the culture.

7. The Sponsor Goes Silent

The intervention works partly because the organization knows the CEO cares. If you kick it off with energy and then never mention it again, both teams quietly conclude it was a passing initiative and revert. You do not need to micromanage — but you do need to ask about the handoff metrics in your staff meetings, reference the shared number, and visibly treat it as a standing priority.

A few minutes of executive attention a month is the cheapest and most powerful maintenance input available.

What To Do When the Two Leaders Still Won't Align

Sometimes you do all of the above and the conflict persists. When that happens, you have crossed from a *systems* problem into a *people* problem, and it requires a different and more uncomfortable response.

1. Separate "Can't Agree" From "Won't Agree"

There is a critical distinction. *Can't agree* means two competent leaders are trapped in a broken system — the diagnostic and the contract resolve it, because the problem was structural. *Won't agree* means one or both leaders are choosing conflict — protecting turf, avoiding accountability, or unwilling to be measured.

The full intervention above is also your diagnostic for which one you have. If you give two leaders a fair shared dataset, a co-authored contract, and aligned incentives, and one of them *still* will not engage in good faith, the data has just told you something important about that individual.

The system is no longer the bottleneck.

2. Make the Expectation Explicit and Personal

Before concluding anything about a person, be certain the expectation was unambiguous. Sit down with each leader individually and state plainly: "Cross-functional alignment on lead handoff is a core requirement of your role. It is not optional, it is not a nice-to-have, and your performance will be evaluated on it." Some leaders simply have never been told that collaboration is a *deliverable* equal to their functional results.

Say it explicitly, in those words, and give a defined window — one quarter — to demonstrate good-faith engagement.

3. Recognize That Sustained Misalignment Is a Leadership Failure

If, after a fair system *and* an explicit personal expectation, a leader continues to undermine the handoff, you are looking at a leadership-fit problem and you must treat it as one. Persistent, willful executive misalignment is corrosive: it cascades down through both organizations, and every rep and marketer learns that the leaders' feud is the real operating system.

Tolerating it broadcasts that functional politics outrank company results. This may mean a hard performance conversation, a role change, or in the end a departure. It is the most painful move in this playbook and the one executives most often delay — but a CRO and CMO who *will not* align, after every reasonable support has been provided, are more expensive to keep than to replace.

Do not let an unresolved executive standoff become the permanent climate of your revenue organization.

4. Distinguish a Skills Gap From a Will Gap

Before you conclude a leader "won't" align, rule out that the leader simply does not know *how*. A CMO who has only ever run brand and demand-generation may genuinely lack the operational depth to co-design a closed-loop SLA. A CRO promoted from a top-rep seat may never have built a cross-functional contract in their career.

That is a skills gap, and skills gaps are coachable — with a strong RevOps partner, an outside advisor, or a peer who has done it before. A will gap is different: the leader has the capability and chooses not to use it, because the current conflict protects their territory or shields them from accountability.

Coaching fixes the first; only a hard conversation and a clear consequence addresses the second. Misdiagnosing a will gap as a skills gap wastes a quarter on coaching that was never going to land. Misdiagnosing a skills gap as a will gap costs you a capable leader you could have developed.

Spend the time to know which one you are looking at.

5. Look Hard in the Mirror First

Before you act on anyone else, ask the uncomfortable question: did *you* create this conflict and are you now sustaining it? If you set contradictory goals — telling the CMO to maximize volume and lower cost per lead while telling the CRO to maximize win rate and protect rep capacity — you engineered the collision.

If you have praised whichever leader complained loudest most recently, you taught them that volume and conflict get rewarded. If you have let the two report into different parts of the organization with no shared planning rhythm, you structurally separated functions that need to be joined.

Very often the lead-handoff fight is a downstream symptom of an upstream failure in goal-setting, organizational design, and incentive design at the top. Fix that first. Two reasonable leaders given coherent, mutually-reinforcing goals will usually find their own way to a workable handoff.

The executive's primary job here is not to referee the fight — it is to stop *causing* it, and then to build the system that makes the right behavior the easy behavior.

What To Do in the First 48 Hours

If you are reading this because the conflict is acute right now — a missed quarter, a leadership meeting that turned hostile, two executives who will barely speak — you need an immediate move before the two-week diagnostic even begins. Here is the 48-hour stabilization.

1. Take the Conflict Off the Public Stage

The first job is to stop the bleeding visible to the rest of the organization. If the CRO and CMO are sniping in all-hands meetings or in front of their teams, that has to end today, because every public exchange teaches the whole revenue org that the feud is the real operating system.

Meet each leader privately, name what you are seeing without assigning blame, and ask both to keep the disagreement inside a closed room until the process you are about to run produces an answer. You are not solving the problem in 48 hours; you are containing its blast radius so it stops compounding.

2. Reframe It as a System Problem, Out Loud, to Both

In a short joint conversation, say plainly: "I do not think either of you is the problem. I think we have never built a shared definition, a shared measurement, or a shared incentive for this handoff, and that absence is generating the conflict. We are going to build all three.

I am personally owning it." This reframe is disproportionately powerful. It lowers the temperature immediately, because each leader has almost certainly been bracing to be blamed, and it relocates the conflict from a personal contest to a solvable engineering problem. It also commits you publicly, which both leaders will quietly find reassuring.

3. Commission the Diagnostic and Set the Date

Before the 48 hours are up, task your RevOps or analytics lead with building the lead-level cohort analysis, give a hard deadline of two weeks, and put the joint read-out on the calendar now. A scheduled date with your name on the invite converts a vague intention into a commitment the organization can see.

It also gives both leaders something concrete to wait for, which discourages either of them from launching a unilateral fix in the meantime.

4. Resist the Urge to Pick a Side

In the first 48 hours both leaders will lobby you, separately, and each will present a coherent, persuasive case. Do not adjudicate. The moment you side with one before the data exists, you have validated the loudest advocate and taught your organization that volume of complaint beats evidence.

Hold the line: "I am not deciding anything until the cohort analysis is on the table and we have all looked at it together." Patience for two weeks here buys you a durable fix instead of a fast, wrong one.

The Metrics That Tell You It's Working

Run the same scorecard before, during, and after the intervention so progress is visible and arguable from data rather than feel.

1. Lead Acceptance Rate (SAL ÷ MQL)

The headline number. It should climb steadily toward and past your SLA threshold. A rising acceptance rate is the clearest single signal that the definition is shared and being honored. A stagnant one says the definition is still contested or the scoring model still does not work.

2. Speed-to-Lead (Median Time to First Touch)

This should fall hard and stay low. Given the well-documented collapse in qualification odds as response time stretches from minutes into hours, treat speed-to-lead as a primary health metric, not a secondary one. Watch the *distribution*, not just the median — a good median hiding a long tail of multi-day responses is still a problem.

3. Working Rate (Cadence Compliance)

The share of accepted leads that received the full agreed touch cadence before being closed. This proves sales is holding up its half of the bargain and directly neutralizes the "marketing leads were bad" objection — or confirms it, fairly.

4. Conversion by Lead Score Band

Continuously validate that higher-scored leads convert better. The day they stop doing so, your model has drifted and needs a rebuild. This metric keeps the *definition itself* honest over time.

5. Marketing-Sourced Pipeline and Win Rate on Marketing Leads

The downstream proof. If the handoff is genuinely fixed, marketing-sourced pipeline that *converts* should rise and the win rate on marketing-originated deals should hold or improve. This is what connects the handoff machinery to revenue and to the shared comp metric.

6. Rejection-Reason Mix Over Time

Do not just count rejections — track *why* they happen and watch the mix shift. A healthy intervention shows the rejection reasons migrating from "out of ICP" and "bad data" — definition and plumbing problems — toward residual, lower-volume reasons like "competitor" or "timing." If the same reason dominates the rejection mix month after month, the corresponding fix is not getting made, and the weekly review is not converting feedback into action.

The *trend* in the rejection mix is one of the best early indicators of whether the system is genuinely learning or merely logging.

7. SLA Compliance on Both Sides

Report two compliance percentages every period: the share of marketing's MQLs that met the definition and data-completeness standard, and the share of sales' accepted leads that hit the speed-and-cadence commitments. Reporting both, side by side, is what keeps the SLA *bidirectional* in practice and not just on paper.

If only one number is ever shown, the contract has quietly become one-sided again, and the leader whose number is hidden will eventually notice and disengage.

8. The Qualitative Signal: Has the Argument Stopped?

Less measurable but unmistakable. In a fixed system, the weekly handoff review is about *adjustments* — a form field, a coaching note, a threshold tweak — not *grievances*. When the meeting stops being a fight and becomes a tune-up, the intervention has worked.

That tonal shift is the truest indicator that you have replaced an argument with a system. Watch also for the language your leaders use in unrelated meetings: when the CRO starts saying "our pipeline" instead of "marketing's leads," and the CMO starts saying "our win rate" instead of "sales' conversion," the shared-incentive design has done its deepest work.

The vocabulary change is small, free to observe, and the surest sign the two functions have started to behave as one revenue team.

A 90-Day Action Plan

To make this concrete, here is the sequence compressed into a quarter.

Days 1 to 14 — Diagnose. You personally pull together the lead-level cohort analysis and the four headline numbers. Run the joint read-out with both leaders. Classify the problem as operational or strategic. Get explicit agreement on the shared picture of reality before anyone proposes a solution.

Days 15 to 30 — Design the contract. Lock the CRO and CMO in a room with their top operators to co-author the behavior-based lead definition and negotiate the bidirectional numerical commitments. Build the structured rejection loop. Confirm your CRM and marketing automation can deliver true closed-loop reporting.

Both leaders sign the SLA; distribute it to both teams.

Days 30 to 45 — Align incentives. Work with your finance or compensation lead to introduce the shared revenue component into both leaders' variable pay and add the quality gate to marketing's plan and the speed-and-effort gate to sales'. Keep the change deliberately modest and announce it clearly so no one is surprised.

Days 45 to 90 — Operationalize and sustain. Launch the weekly handoff review and the monthly pipeline council. Watch the metrics weekly. Expect one or two visible failures in the first month — a missed SLA, a disputed rejection — and treat each as a tuning opportunity, not a verdict on the system.

By the end of the quarter, run the first QBR with the new shared scorecard read aloud.

A note on sequencing discipline: resist the temptation to compress this. The most common reason a lead-handoff fix fails is that an impatient executive jumps straight to "design the contract" without the diagnostic, and builds an SLA on assumptions instead of evidence. The two weeks of diagnosis are not a delay; they are what makes everything after them stick, because they replace two leaders' competing beliefs with one shared dataset that neither can dismiss.

Equally, do not let the contract design slip past day 30 — momentum matters, and a diagnostic that sits unactioned for a month curdles into cynicism. The 90-day arc works because each phase earns the right to the next: shared facts earn a credible contract, a credible contract earns an incentive change, and an incentive change earns a cadence that lasts.

Skip a phase and the chain breaks.

Beyond Day 90 — Make It Boring

The goal state is not a celebrated, high-energy alignment initiative. The goal state is a handoff so boring that no one thinks about it. After the first two quarters, the weekly review should run in twenty minutes, the rejection mix should be stable and low, the shared number should be one line on a dashboard nobody argues about, and the CRO and CMO should be spending their joint attention on the *next* hard problem — pricing, segmentation, a new market — rather than relitigating the handoff.

Boring is the win. When the lead-handoff process has become invisible infrastructure, like electricity, the intervention has fully succeeded, and your two leaders have been freed to fight about things that actually move the business forward.

By day 90 you should see acceptance rate rising, speed-to-lead falling, and the weekly meeting shifting in tone from argument to adjustment. If instead a leader is still actively undermining the system, you now have clean evidence that the problem is a person, not a process — and you can act on it with confidence rather than guesswork.

The Bottom Line

A CRO and a CMO who cannot agree on lead handoff are almost never the disease. They are the symptom of a revenue organization that lacks a shared definition of quality, a shared instrument to measure the handoff, and a shared incentive to care about the same outcome. You do not fix this with a mediation session, a team-building offsite, or a stern talk.

You fix it with arithmetic: a behavior-based definition a computer can check, a bidirectional SLA with real numbers and a real rejection loop, closed-loop reporting on one dashboard, and a compensation plan that pays both leaders partly on the same number while gating each side's bonus on its half of the bargain.

Wrap that in a weekly, monthly, and quarterly cadence and protect the cadence fiercely.

Do this and the disagreement does not get *negotiated* — it gets *engineered out*. Lead handoff stops being a recurring fight and becomes a boring, instrumented, self-correcting process, which is exactly what a healthy handoff should be. And if, after a fair system and an explicit personal expectation, one leader still refuses to align, the same intervention has handed you the evidence you need to make a harder personnel decision with a clear conscience.

Either way, you end the quarter with a revenue engine where marketing and sales are pulling on the same rope — because you finally paid them, measured them, and held them accountable as if they were one team, which is the only thing they ever should have been.