The Day I Learned That Spreadsheets Don't Cross-Sell

Look, I've been doing this revenue thing for 25 years. I've scaled past $3 billion, led teams of more than 200 people, served as an executive at Cellular Sales (one of the largest Verizon authorized retailers in the country), and built PULSE RevOps. And if there's one thing I've learned, it's this: the spreadsheet that justified your acquisition is lying to you.

Let me tell you a war story.

The $300,000 Mistake I Almost Made

A few years back, a private equity group called me in after they'd acquired a complementary software company. The deal memo promised $2 million in cross-sell synergy in year one. The CEO was a sharp operator—he'd done the math, built the model, and assumed his customers would magically start buying the new product and vice versa.

Six months in, cross-sell revenue: zero.

The two sales teams weren't just failing to cooperate—they were actively sabotaging each other. The acquired reps felt like they were being absorbed and devalued. The acquiring reps saw new colleagues competing for their accounts.

And the comp plans? They were designed to sell the original products, not the new ones. Reps are rational creatures—they follow the comp, not the CEO's PowerPoint slides.

I told the CEO: "You don't need a full-time CRO at $300,000 to $500,000 a year to run this integration. That's like buying a Ferrari to drive to the mailbox. You need a senior operator who's done this before, a few days a month, during the window when this cross-sell motion is hardest to start and easiest to fumble."

Why Cross-Sell Synergy Almost Never Happens on Its Own

Here's what I've seen kill more acquisitions than bad products or bad markets:

Two sales teams do not trust each other. The acquired reps suspect they're being absorbed and devalued. The acquiring reps see new competitors for accounts and attention. Until someone aligns incentives and resolves account ownership, neither team will lift a finger to sell the other's product.

The comp plans point in different directions. Each team is paid to sell its own original product. Nothing in either plan rewards selling across the line, so reps rationally ignore the cross-sell mandate no matter how many times leadership repeats it. Comp drives behavior, and the comp says don't bother.

The pipelines and data do not connect. The two companies ran on different systems, different stages, and different definitions. Until the pipelines are merged into one view, nobody can even see which of your customers are good targets for their product, let alone route the opportunity.

Nobody owns the combined number. The acquirer's revenue leader owns the old book. The acquired leader owns theirs. The cross-sell number—the entire reason for the deal—belongs to no one, which is exactly why it doesn't get hit.

What I Actually Did (And What You Should Do)

In the first 30 days, I mapped the real cross-sell opportunity across both customer bases—by industry, size, and need—so the team chased the deals that would actually close instead of spraying both books with the wrong offer. I audited both comp plans and pipelines. I identified where account-ownership conflicts would flare.

By day 60, I'd redesigned both comp plans so that selling the other company's product was at least as rewarding as selling the original one. I resolved account ownership so reps stopped fighting over who got credit. And I started merging the two pipelines into one view.

By day 90, the combined revenue engine was running on one operating system. Both teams were enabled and incentivized to sell across the line. The cross-sell pipeline was a tracked, accountable number on the forecast—not a hope, not a prayer, not a line in a board deck that nobody owned.

The result? That $2 million synergy number started showing up in the revenue. Not all of it in year one, but enough to make the acquisition pay for itself instead of becoming a write-down.

The Cost of Getting It Wrong vs. Getting It Right

A fractional CRO runs roughly $5,000 to $15,000 a month on a retainer, versus $25,000-plus a month all-in for a full-time CRO. Against the size of the synergy at stake, that cost is trivial: the cross-sell revenue an acquisition is supposed to unlock is usually measured in the hundreds of thousands or millions, and capturing even a fraction of it returns the retainer many times over.

The real comparison is not the retainer versus a full-time salary—it's the retainer versus an acquisition that quietly underdelivers and becomes the thing the board asks about every quarter.

What I Learned the Hard Way

You don't need an integration consultant who maps processes and produces a plan but doesn't own a number or redesign comp. You don't need a full-time CRO at $300,000 to $500,000 a year for a defined integration that has a beginning and an end.

You need a senior operator who's integrated revenue teams before, who owns the combined revenue number through the integration, who does both the analysis and the implementation, and who either hands the running motion to your team or converts to full time once the combined entity justifies it.

The spreadsheet that justified your acquisition almost certainly assumed your customers would buy their product and their customers would buy yours. That synergy does not happen on its own. It happens when someone owns the combined revenue engine, aligns two comp plans, merges two pipelines, and gives reps a concrete reason and a clear path to sell across the line.

I've spent 25 years building and scaling revenue organizations—work that includes scaling revenue past $3 billion, leading teams of more than 200 people, and building the free revenue tools on this site. And I've learned that the highest-leverage thing you can do after an acquisition is put experienced revenue leadership on the integration from day one.

Because the cost of getting it wrong isn't just the retainer—it's the difference between an acquisition that pays for itself and one that becomes a write-down.

*If you're staring at a cross-sell integration that's stalling, I take on fractional CRO engagements through CRO Syndicate—a network of senior revenue practitioners who have actually built the numbers they advise on. Or check out the free revenue tools on PULSE RevOps.

Either way, don't let that spreadsheet lie to you.*

*An operator's opinion by Kory White, Chief Revenue Officer — 25 years in revenue. More at PULSE · CRO Syndicate*