Nobody Dropped It. Nobody Was Holding It.

I get it… when a deal falls apart, the first instinct is to find the opportunity owner and ask what happened.

Somebody must have fumbled. Find them, coach them up, move on.

At least a lost deal gives you that much. It's a record. It's sitting in your pipeline right now with a reason attached, and anybody in the company can look at it.

The expensive failures don't leave a record.

There are two of them in most lean B2B companies, and they sit at opposite ends of the same funnel. A lead that dies before it ever becomes a deal, so there's nothing to review and nothing to coach. And a customer to whom a rep promised something (something that nobody wrote down): they don't churn and may not complain very loudly, but they just quietly stop being easy.

Neither one throws an error. Nothing turns red. Both die in the gap between two people who each assumed the other one had it. No fumble. No dropped ball. Just a ball that was never actually in anybody's hands.

That gap is the handoff. You've got two of them: marketing to sales, and sales to whoever keeps the customer after the money changes hands. And in most companies with a thin internal function, nobody has ever written down what either one is.

Two versions of how that plays out below. Both invented stories. Not clients, not composites of specific accounts, no real names or numbers. The patterns are real.

Version one: the lead marketing thought sales called

Marcy runs marketing. She's the whole department, which is a sentence a lot of you may identify with.

She's got scoring set up. Somebody requests pricing, hits a threshold, and flips to Marketing Qualified Lead. From her seat, that's the handoff. She did the thing. The record moved.

Marcy has a rule of her own, and hers is deliberate. She doesn't chase reps about individual leads. She tried that once. It went badly, and it ate a week she didn't have. When you are the entire marketing department, the only way to survive is to build the system and then trust the system to do its job.

Rick's been selling there for nine years. Rick has his own rule, which lives entirely in Rick's head: if there's no direct phone number and no company size, it's a tire-kicker, and Rick has a number to hit.

So a price request comes in Thursday afternoon. Real company, real budget, comparing three vendors that week. The contact filled out the form in a hurry and skipped the phone number. (Which you didn't require on the form. Oopsie.)

Marcy sees it flip to MQL and moves on. Rick sees it in the queue, applies his unwritten rule, and moves on.

The lead waits four days, decides these people aren't interested in selling to them, and buys from somebody else.

Here's the troublesome part: nobody in the company will ever find out. There's no error message. The quarter closes, the pipeline is soft, and the conversation in the leadership meeting becomes "the leads aren't very good lately."

And the criticism lands on Marcy, who did exactly what she thought her job was.

Version two: the promise nobody wrote down

Tom closes a deal in late March. Good deal, competitive, took four months.

On the last call, the buyer asks whether they can get a custom report showing spend by region. Tom says yeah, we should be able to knock that out in the first month.

He means it. Tom is not lying, and he does what every rep who has ever closed a competitive deal does: answering the last question standing between him and a signature. He writes it in his notebook.

Onboarding kicks off from the deal record, which contains the signed scope. The signed scope says nothing about regional spend because it was written two weeks before the conversation that actually closed the sale.

Read that again, because it's the whole problem. The artifact that carries the handoff was finalized before the moment that won the deal.

Priya runs onboarding, and she's excellent at it. She runs the standard sequence, every time, for everybody. That's not laziness; it's the whole reason she's good. She's got eleven onboardings going at once, and the minute she starts custom-building one of them off somebody's verbal recap, the other ten start slipping.

So she hits every milestone and sends the week-four check-in, exactly as designed. The standard sequence is also the only artifact she has.

Week five, the customer asks where the regional report is. Priya has genuinely never heard of it.

Now the customer will believe one of two things: either the salesperson told them something that wasn't true, or the service team can't keep track of what was sold. Neither one is what happened. Doesn't matter. The relationship is now something the customer has to manage instead of enjoy.

Priya, who did nothing wrong, spends the next two weeks apologizing for a conversation she wasn't in. Then somebody gets pulled off another account to build the report three weeks late, and now two customers are behind.

And here's the part that shows up on no report anywhere: eleven months later, that account renews. It just renews with a question first. A call, a little friction, maybe a concession. It used to renew by email.

What both of these have in common

Neither one of these is a people problem.

Both of them look exactly like a people problem, though. That's the whole trick, and it's why these go unfixed for years.

When a handoff is undefined, it can make your team members look unprepared. Marcy looks like she's sending junk. Rick looks like he's not working his leads. Tom looks like he overpromised. Priya seems to be not paying attention.

Sometimes that's the end of it. Everybody moves on. Other times, people want to get to the bottom of things.

Somebody says something in a meeting. Somebody else gets defensive. And now there's a real fight over the receipts: marketing pulls the MQL report, sales pulls up four garbage contacts from March, both sets of numbers are accurate, and neither one is the problem.

Here's why that's worse than quietly moving on: the fighting feels like fixing. Everybody walks out with an action item, and the action item is almost always training.

A sales enablement session. A lunch-and-learn on what marketing actually sends over. A new rule announced at the Monday meeting in a tone that makes clear somebody's in trouble. We're going to do a better job communicating.

Wrong.

OK… mostly wrong. There's one real exception in these stories, and it's worth naming, because pretending every problem is architectural is its own kind of dodge.

Training is what you do when people don't know the rule. So count the ignorant people here.

Marcy knows the rule. She wrote it. She built the scoring, watched the flip, and made a deliberate call not to spend her week chasing reps about individual records. Ask her to defend it, and she'll do it in one sentence.

Rick knows a rule too—his own. Nine years of pattern recognition, and he could argue it for twenty minutes with examples. You're not teaching Rick anything. You're asking him to permanently override his own professional judgment, from memory, with nothing in place to enforce it, report on it, or flag when it isn't followed.

Priya knows exactly what she's doing. Running the standard sequence for everybody is the only reason eleven onboardings don't turn into four.

And then there's Tom. Tom is the one case where training is genuinely part of the answer. If you're on HubSpot, Salesforce, or anything like them, there is already a place for that promise to live. A note on the deal. A property. A task. Tom has somewhere to put it. He doesn't, and plenty of Toms won't until somebody sits them down and walks them through it. Some of them will resist it after that, too, which is its own conversation.

So yes. Train Tom. That's a real gap, and it deserves a real sit-down.

Just don't stop there, because here's what training alone buys you: not much. Some people will change their behavior in the short term. A few superstars will commit for life. Others will never change. To really address the issues you're facing, your system needs to change to:

• Require that certain fields be filled before the deal moves to Won
• Alert on scenarios that look fishy (based on rules and criteria you set)
• Report on the deals that move to "closed" with key historical details missing (notes, meetings, emails, etc.)

A training session's effects may last about six weeks, right up until the first quarter-end, when Tom is in a hurry, and the field is optional. Then everybody drifts back to the rule that's actually in the system: the absence of one.

That's the distinction worth carrying out of here. Some of this is a definition problem, where four people know exactly what they're doing and nobody ever agreed on what the words mean. Some of it is a compliance problem, where the right move is obvious, and nothing in the building makes it happen. Training moves the second kind for a little while. Only the system moves either one for good.

So here's a free diagnostic before you take the test below. Think about the last three times somebody tried to fix this. If all three were a meeting, a memo, or a training, and nothing in the system changed afterward, you don't have a communication problem. You have a system that has never once been asked to hold the rule.

And both gaps stay exactly as wide as they were. Not quietly. Repeatedly.

The two-answer test

You don't need an audit to find out whether this is happening to you. You need about twenty minutes and a willingness to hear something annoying.

Ask two people the same question. Separately. Do not put them in a room together, because in a room they'll negotiate their way to one answer and you'll learn nothing.

It's called the two-answer test because two answers is the whole finding.

For the first gap:

• Ask your marketing person and your best rep: what makes a lead ready to be called? Two answers mean you don't have a definition. You have a coincidence.
• Ask anybody: when a lead goes quiet, who is holding it right now? If the answer is a shrug or "it's in the CRM," nobody is holding it. "It's in the CRM" is where leads go to die.

For the second gap:

• Ask a rep and whoever handles new customers: what do customers expect to happen in their first 30 days? Two answers mean your onboarding is being run against two different promises.
• Ask a rep and whoever handles new customers: what got promised on the last deal that isn't in the contract? If the rep can name something and the delivery person can't, you just watched the gap happen in real time. If the rep says "nothing," ask a second rep.

Then do the arithmetic.

First gap. Take your average deal size. Multiply it by one. That's what a single lead dying in the first gap costs you this quarter. Now guess how many.

Second gap. This one won't hand you a number, but it will hand you two you can count. Pull last year's renewals. How many closed themselves, and how many needed a call, a concession, or a discount to get across? Then count how many of your last twenty customers have sent you a referral, and compare that to who you were three years ago.

Neither figure is exact. Both are countable, and a countable number is what you carry into a room. "I think leads are falling through the cracks" gets you a training session. "Nine of our last twelve renewals needed a discount to close, and three years ago almost none of them did" gets you a meeting.

That second gap is the sneaky one, by the way. A customer who spent five weeks waiting on something nobody logged doesn't churn that quarter. They just stop being the account that renews without a conversation, and they never send the referral they would have sent. You'll never see that on a report. You'll notice it years later, as a general sense that word of mouth isn't what it used to be.

Why you probably can't fix this on a whiteboard

Anybody can write a definition. Writing one takes an afternoon or less.

Making one that survives contact with your actual business is the hard part, and three things get in the way.

One: it has to match how you really sell, and what you can really deliver

Not how a template says B2B works. If you sell through distributors and direct, or there's a technical evaluation before anybody talks money, or your best leads come from a referral network and never touch a form, then a generic MQL definition will be wrong on day one and everybody goes back to their private rules by day thirty.

The delivery side has the same problem in reverse. If every implementation genuinely is a little different, a standard onboarding checklist is a polite fiction, and Priya knows it before you do.

Somebody has to sit down and describe how the money actually moves through your company, from first touch to renewal. And that somebody has to work there.

Two: it has to live in the system, not on a poster

If you're on HubSpot, the marketing-to-sales half already has a standard place to live. HubSpot's own documentation says the Lifecycle stage property indicates where a contact is in your process and helps you understand how leads are handed off between marketing and sales. That's not a workaround; that's the field's stated job. Plenty of the companies we meet have it sitting there, full of defaults that nobody in the building ever agreed to, which is roughly how they're using the rest of it, too.

The second gap isn't missing tooling either. HubSpot's projects object exists for exactly this, and HubSpot's documentation uses service delivery as its worked example: a deal hits Won, and a workflow spins up a project with its own pipeline instead of jamming four more stages onto the end of your sales pipeline. (Workflows and pipeline rules need Professional or Enterprise, so check your plan before anybody gets excited.)

But the tooling was never the hard part. Somebody has to decide what a deal must contain before it's allowed to close, and then make that stick when a rep is one field away from a signature. That's not a purchase. That requires knowing which promises actually get made in your sales conversations. It also means knowing how your people sell.

Three: somebody is going to lose an argument

There's a reason this has never been defined, and nobody says it out loud.

Rick's rule is currently winning. Tom's flexibility is currently winning. Undefined is not an accident; it's a truce. Write the definition down and somebody loses something they've been quietly winning for years, and they will fight it in the most reasonable-sounding way you've ever heard.

That part needs a referee who doesn't report to either side.

When this isn't your problem

Real disqualifiers, because I'd rather you not book a call you don't need:

• You have a real RevOps function. Then you have someone whose actual job this is. Go ask them.
• Your sales team is the founder, and only the founder. Then you don't have a marketing-to-sales handoff problem. You have a capacity problem, and that's a different post. Fair warning though: you may still have the second gap, and worse than most. When the founder sells, the promises live entirely in the founder's head, and there's no scope document forcing them out.
• Nobody inside will roll up their sleeves. If there's no one with the time and the authority to explain how your business really sells, this can't be fixed from the outside. Not by us, not by anybody. We've tried. It doesn't work.

OK… so what do you actually do

Run the two-answer test this week. That's the assignment.

If you get one answer to all four questions, congratulations, and go read something else.

If you get two anywhere, you've found a gap, and you now know something your leadership team doesn't. That's worth a conversation, whether it's with us or with the person sitting next to you.

If you want it to be us, that's what we do. The B2B Mix® is an embedded HubSpot ops and marketing team, and defining handoffs and building them into HubSpot so they hold is a large chunk of the work we get hired for. Thirty minutes, no deck. Bring the mismatches.

Frequently Asked Questions