Sales says the leads are junk. Marketing says sales never works them. Both departments show up to the pipeline meeting with dashboards that prove their case, and the meeting ends the way it ended last month: politely, with nothing changed.
Here is the position I want you to consider. “Sales and marketing alignment” is usually pitched as a culture problem — joint meetings, shared Slack channels, empathy exercises where each team walks a mile in the other’s CRM. It is actually a contract problem. There is no written definition of a qualified lead. There is no service-level agreement (SLA) for pickup after the handoff. There is no feedback loop when sales rejects a lead. Write the contract and the culture follows. Hold the meetings without the contract and you get friendlier people having the same fight.
This post walks through the marketing sales handoff from first principles: why the blame cycle is structural rather than personal, what the contract needs to contain, why rejected leads are the most valuable asset in your pipeline, who owns this when there’s no chief revenue officer (CRO) to referee, and what good looks like ninety days after you fix it.
Why do marketing and sales blame each other for the same pipeline?
Because both are right. They grade different exams: marketing measures lead creation, sales measures lead quality, and without a shared written definition of “qualified,” each side optimizes a metric the other doesn’t recognize.
Look at the architecture of the incentives. Marketing is accountable for volume — form fills, marketing-qualified leads (MQLs), cost per lead. Every one of those metrics improves when the definition of a lead gets looser. Sales is accountable for close rate and quota attainment. Every one of those metrics improves when the definition of a lead gets tighter. You have built two functions whose scoreboards move in opposite directions, then asked them to share a pipeline. The fight is not a personality conflict. It is the predictable output of the system you designed — or more likely, the system that accreted while you were busy building the product.
This is why the culture-first fixes fail. A joint offsite doesn’t change the fact that the marketing lead still gets paid on lead count and the sales lead still gets paid on closed revenue. The Slack channel doesn’t change it either. People can genuinely like each other and still be structurally opposed. Empathy is not the missing ingredient. Agreement is — specifically, a written, signed agreement about what a qualified lead actually is.
Consider what happens without one. A prospect downloads a comparison guide, and marketing hands the record to sales as qualified. Sales looks at it, sees a job title two levels below the buyer and no company size data, and quietly lets it rot. Marketing counts it as a lead delivered. Sales counts it as noise. Both dashboards are accurate. Neither describes the same reality. Multiply that by every lead this quarter and you have the fight you’re refereeing right now.
The fix is not to make either team more understanding. The fix is to make the exam the same exam.
What belongs in the handoff contract?
Three clauses. A written qualified-lead definition both sides signed. An SLA for first touch after handoff. And a required disposition on every handed-off lead — worked or rejected, and if rejected, why, in one sentence.
That’s the whole contract. It fits on a single page, and the single page matters, because a document nobody can hold in their head is a document nobody follows.
Clause one: the qualified-lead definition
Write down, in plain language, what a lead must be before marketing is allowed to hand it to sales. Not a scoring model with forty weighted signals — a definition a new hire could apply on day one. Company size range. Roles that count as buyers or real influencers. The behavior or stated need that signals intent rather than curiosity. Whatever your business requires, but written, specific, and short.
Then — and this is the part most companies skip — both leaders sign it. Literally. The signature is not ceremony. It converts “marketing’s definition” into “our definition,” and it removes the escape hatch each side uses in the blame cycle. Sales can no longer say the leads were never qualified; they agreed to the standard. Marketing can no longer say sales is too picky; the standard is written down and marketing helped write it. Lead qualification stops being a matter of opinion and becomes a matter of compliance with a document.
Clause two: the pickup SLA
A qualified lead handed to sales gets a first touch within a defined window. You pick the window based on your sales motion — but pick one, write it down, and measure against it. Speed matters more here than most teams assume, and a lead that goes untouched past the SLA is a broken promise with a timestamp, which is a very different thing from a vague sense that sales is slow.
The SLA also protects sales. When marketing floods the pipeline with leads that don’t meet the definition, sales can point at the contract instead of absorbing the volume silently and resenting it. The SLA only binds sales for leads that meet clause one. That symmetry is the point. Each clause disciplines one side and shields the other.
Clause three: mandatory disposition
Every handed-off lead gets a verdict. Worked, or rejected. And if rejected, the rejecting rep writes one sentence explaining why. Not a dropdown code. A sentence. “Too small — under our minimum deal size.” “Champion left the company.” “They’re two years from a budget.”
One sentence per rejection is a trivial ask of any sales rep, and it is the clause that transforms the entire system, because it creates the feedback loop that the handoff has been missing. Without dispositions, leads don’t get rejected — they evaporate. Nobody learns anything from evaporation.
Why do rejected leads matter more than accepted ones?
Because rejection reasons are the cheapest market research marketing will ever get. A monthly rejected-lead review teaches more than a persona workshop.
Think about what a rejection sentence actually contains. It is a frontline salesperson, with real revenue at stake, telling you precisely where your targeting, messaging, or qualification criteria diverge from the market as it exists today. That is intelligence companies pay agencies real money to approximate through surveys and interviews. Your sales team generates it for free, every week, as a byproduct of doing their job — if you require the disposition and then actually read it.
Accepted leads teach you less than you’d think. An accepted lead confirms the system worked, which is useful but not directive. A rejected lead tells you exactly which assumption failed. If a month of rejection sentences clusters around “too small,” your targeting criteria are miscalibrated and you can fix them in the campaign settings this afternoon. If they cluster around “no budget until next year,” your content is attracting researchers instead of buyers, and that’s a messaging problem with a knowable shape. If they cluster around “wrong industry entirely,” your lead qualification definition itself needs an amendment — which is fine, because the contract is a living document, and amendments made from disposition data are how it improves.
Run the review monthly. Thirty to sixty minutes. Marketing leader, sales leader, and whoever owns the contract (more on that below) read the month’s rejection sentences together and sort them into patterns. Each pattern becomes a decision: change the targeting, change the message, or amend the definition. That’s the whole meeting. No slides. It will be the highest-density hour on your revenue calendar, and it costs nothing but the discipline to hold it.
Compare that to the persona workshop. A day of sticky notes producing a fictional character named “Procurement Pete,” built from assumptions the team already held. The rejected-lead review is built from real buyers your team touched this month and the specific reasons they didn’t fit. One of these compounds. The other laminates.
Who owns the handoff when there’s no CRO?
The founder, by default — which means nobody. Assign one named owner of the definition and the weekly review; it does not need to be a new hire.
Here is the mechanism behind the default. In a company your size, marketing and sales each report to you, so the handoff between them lives in the seam between two of your direct reports. Seams have no natural owner. Each leader owns their function and reasonably assumes the space between functions is yours. You, meanwhile, are running the entire company, and “referee the lead-definition dispute” sits somewhere below fundraising, hiring, and the product roadmap on your list. So the seam stays empty. The contract never gets written, or gets written once and never enforced, and enforcement is the entire game. An unenforced SLA is a suggestion. An unread disposition log is a diary.
The fix is smaller than it sounds. You do not need a CRO. You need one named person who owns three things: the qualified-lead definition (including amendments), the SLA report (who’s inside the window, who’s not), and the standing reviews. That person can be your marketing leader, your sales leader, your ops person, or a fractional senior marketing leader — the title matters less than the singularity. One name. When the definition drifts or the SLA slips, everyone in the building knows whose job it is to say so.
There is one trap to name. If the owner sits inside marketing or sales, they will feel gravitational pull toward their home team’s scoreboard, so pick the person with the discipline to hold the contract above their function — or place ownership with someone whose incentives touch both sides. Decision ownership only works when the owner can rule against their own department and make it stick.
What you should not do is keep owning it informally yourself. Founder-as-referee is how you got here. Every dispute escalates to you, you adjudicate from partial context, and both leaders learn that the written rules matter less than winning the hallway conversation. Name an owner, give them the contract, and get out of the seam.
What does good look like after 90 days?
A weekly thirty-minute pipeline review run on dispositions instead of anecdotes. A shrinking rejection rate. And the real tell — sales asking for more leads.
Take them in order. The weekly pipeline review changes character before anything else does. Today that meeting runs on stories: a rep’s read on a deal, marketing’s defense of a campaign, competing recollections of who dropped what. With the contract in place, the meeting runs on records. Leads handed off, leads touched inside the SLA, leads rejected and why. Thirty minutes, because there’s nothing to litigate — the dispositions already settled the factual questions, and the meeting spends its time on decisions instead of forensics. When your pipeline review gets shorter and more useful in the same quarter, the contract is working.
The rejection rate shrinks next, and it shrinks for an honest reason: the monthly rejected-lead review keeps converting rejection patterns into targeting and messaging changes, so each month’s handoffs fit the definition a little better than the last. Watch the trend, not the level. A high rejection rate in month one is not failure; it’s the baseline finally becoming visible. A rejection rate that refuses to move by month three means the review is happening but the decisions aren’t — dispositions are being read and then shelved. That’s an ownership problem, and you know whose name is on it.
The third signal is the one you can’t fake. Somewhere around the end of the quarter, if the system is working, your sales leader stops complaining about lead quality and starts asking for volume. That sentence — “can marketing send us more of these” — is the sound of alignment. Not the offsite kind. The kind where a rep looks at the handoff queue and sees revenue instead of homework. No empathy exercise has ever produced that sentence. A signed definition, an enforced SLA, and a working feedback loop produce it as a matter of course, because sales asking for more leads is simply what happens when the leads are worth working.
Notice what didn’t appear in any of these ninety days: a reorg, a new executive hire, a new tool. The contract runs on the CRM you already have and the people you already employ. What it requires is the decision to treat the handoff as architecture instead of atmosphere.
The handoff is architecture, not atmosphere
Most companies at your stage treat the marketing sales handoff as a personnel issue and cycle through hires, agencies, and offsites hoping the next combination of people will finally get along. The handoff is not a personnel issue. It is a piece of revenue architecture that was never designed, and undesigned systems produce exactly the friction you’re living with. Designing it takes a page, a signature, and someone with the standing to enforce both. If you want a senior partner who thinks about your revenue engine this way — contract first, holistically, tied to pipeline rather than activity — that conversation is worth thirty minutes of your quarter.