The deal closed on a Tuesday. By Friday the sales team had a spreadsheet: 1,800 customers of the company you just bought, one row each, sorted by annual contract value, with a column that says which of your products they do not own yet. The board deck that approved the acquisition said the combined company would sell your product into their base and theirs into yours. Ninety days later, a handful of those rows have a meeting against them. Most have nothing.
Nobody on the team is lazy, and the list is not wrong. Every company on it is a real customer that could, on paper, buy the other product. The problem is that a list of who could buy says nothing about who has a reason to buy this quarter. A rep looking at row 412 cannot tell whether that account just renewed a competitor for three years or just hired a new head of data who is shopping. So the rep calls the accounts they already know, the inherited list sits, and the cross-sell case that justified the price of the deal quietly becomes next year's problem.
This is a guide to post-merger sales integration from the go-to-market side: what the first ninety days should look like for the people who carry the number, why the cross-sell case is the part that reliably does not happen, and a method a rep can run on an inherited account by hand.
Why the cross-sell case is the part that stalls
The revenue half of a deal is harder than the cost half, and the people who study deals say so plainly. In Bain's 2022 M&A report on revenue gains, executives named overestimating the revenue case as the most cited reason a deal failed, and only half of them said they build expected revenue gains into their deal models at all. The same report found that the most common reason companies failed to capture the revenue they expected was ineffective integration of the product portfolio, with the full go-to-market change named alongside it as the other big obstacle.
Speed makes it worse. Writing in Harvard Business Review in 2024, Jason McDannold and co-authors put it bluntly: acquirers are often "shockingly slow" to integrate their sales, marketing and customer functions, and that delay can turn a good deal into a bad one because sales growth decides whether a merger creates value.
Look at what actually reaches the field after close, and the stall makes sense. The integration office works on systems, payroll, legal entities and the org chart. Sales gets three things:
- A combined account list, usually a CRM export from the acquired company joined to yours on company name or domain.
- A product overlap view, the grid of which customers own which products, with the empty cells highlighted as the opportunity.
- A target, the cross-sell revenue number from the deal model, divided across regions or teams.
All three describe the size of the opportunity. None of them tells a rep which account to call on Monday or what to say when the call connects. That gap, between a list of who could buy and a reason for one of them to buy now, is where the cross-sell case goes to die.
What the deal model knows, and what the rep needs
The deal team built the cross-sell case from aggregate data: how many customers overlap, average contract value, a penetration rate assumption. That is the right way to price a company. It is the wrong input for a rep, who works one account at a time. The table below is the difference.
| Question | What the deal model has | What the rep needs |
|---|---|---|
| Who is the opportunity? | 1,800 acquired customers without product B | The 60 with a reason to look at product B this quarter |
| How big is it? | Average contract value times an assumed attach rate | Whether this account has budget, a project, or a problem product B solves |
| Who do we talk to? | The contact on file in the acquired company's CRM | Whether that person still works there and still owns the decision |
| What do we say? | "Now that we are one company, we can offer you more" | One specific thing that changed at the account, with where it was seen |
| When? | "Year one" in the integration plan | Now, next quarter, or not this year, decided per account |
Every cell in the right-hand column is account research. It is the same work a good rep does before any first call, described in our pre-call research checklist, multiplied by every row on the inherited list. That multiplication is the real reason it does not get done. Nobody budgets eighteen hundred research sessions into the first quarter after close.
The overlap grid deserves a specific warning. It is a whitespace analysis, and like every whitespace view it shows the empty cell, not the reason to fill it. An acquired customer without your product might be the best cross-sell target in the base, or it might have bought a competitor's version eighteen months ago on a three-year contract. The grid cannot tell those apart. Only research can.
The first ninety days, from the go-to-market side
The order matters. Cross-selling into a base you have not stabilized is how you lose the customers the deal was built on. A practical sequence for the first ninety days looks like this.
- Days 1 to 30: protect the base. Call the acquired company's largest and least stable accounts, with the people they already trust in the room. No pitch. Answer what is changing, what is not, and who their contact is now. Competitors will be telling them a version of the story, so yours needs to arrive first.
- Days 15 to 45: set the rules. Decide who owns each acquired account, how cross-sell credit is split between the two sales teams, and what happens when a rep from one side wants to talk to a customer of the other. Unclear ownership is a common quiet killer: when two reps might both get credit, often neither calls.
- Days 30 to 60: research the list. Run every inherited account through the same test before anyone is asked to call it (the method is in the next section). Sort the list into call now, not yet, and skip.
- Days 45 to 90: work the call-now accounts. Start with the accounts that have a reason, a current contact, and a stable relationship. Track meetings and pipeline against those accounts only, not against the whole base, so the number the board sees reflects work that could actually happen.
The protect phase has a clock on it. Integration consultancy PRITCHETT calls 100 days the "customer tolerance point": customers expect most customer-facing issues to be resolved within about 100 days of close, and companies that take longer start to see defection rates rise sharply. That is an argument for not wasting the first ninety days on undirected cross-sell calls. Every call to an acquired customer in that window should either reassure them or give them a specific reason to buy more. A generic "we can now offer you more" does neither.
The reason test for an inherited account
Here is the method. It is the same test that decides whether any name on any list is worth a call, applied to an acquired customer. An inherited account is worth a cross-sell call when you can answer three questions:
- What changed? A new leader in the function your product serves, a public project, a hiring push, an expansion, a new regulation they now fall under, a complaint about the tool your product replaces.
- Where did you see it? A press release, a job post, an earnings call, a LinkedIn announcement, a support ticket in the acquired company's system. A link or a document, not a hunch.
- When did it happen? This quarter is a reason. Two years ago is history.
No reason, no call. The account goes in not yet, and you check it again next quarter.
A worked example
Take a hypothetical. You sell a data observability product. You acquired a data catalog company, and the deal case says catalog customers will buy observability. Two rows from the inherited list:
Account one is a regional insurer, a catalog customer for three years, with a healthy renewal last spring. The overlap grid flags it as an observability opportunity. Research turns up nothing new: same data team, no open data engineering roles, no public data projects, no change in leadership. It fails the test. It goes in not yet, and the right call this quarter is a relationship call from its existing account manager, not a pitch.
Account two is a logistics company, a smaller catalog customer. Research turns up a job post from three weeks ago for a data reliability engineer, and the new VP of Data, hired this summer, posted on LinkedIn about a quarter of late dashboards after a warehouse migration. What changed: a new data leader and a reliability problem. Where: the careers page and the VP's own post. When: the last three months. It passes. The opener writes itself, and it is about their late dashboards, not about the merger.
On the overlap grid both rows look the same. One of them is a call this week and one is a call next year. Multiply that difference across 1,800 rows and you have the gap between the cross-sell case in the deal model and the one the sales team can actually work. If you want the longer list of what counts as a reason, our pieces on trigger events in sales and buying signals go through the common ones.
Check the contact before the account
Inherited CRM data has its own failure mode: the contacts are stale. The acquired company's records were kept by a different team, with different hygiene rules, and the champion on file may have left before or because of the deal. Before a rep calls an inherited account, confirm the contact still works there and still owns the decision. If they do not, find who does. A cross-sell email to someone who left in June is worse than no email, because it tells the customer the new owner does not know who they are.
Who does the research, at the size of an acquired base
The reason test is simple to run on one account. It takes a careful rep somewhere between fifteen minutes and an hour per account, depending on how public the company is. On an inherited base of a few hundred or a few thousand accounts, during the same quarter that reps are also fielding retention calls and learning a second product, it does not get done by hand. Teams usually fall back to one of three options:
- Work the top of the ARR list. Fast, and it points reps at the accounts most likely to be stable and least likely to want a change mid-integration.
- Send everyone the same announcement. Easy to measure, rarely produces a meeting, and it spends the one moment every acquired customer is paying attention on a message about you rather than them.
- Hire an analyst or agency to research the list. Works, and arrives after the 100-day window has closed.
This is the job PitchSmart does. You give it the inherited list and tell it what you sell. It researches every account against that product and returns a plan per lead: pitch, not yet, or skip, which of your products to lead with, the buying signals behind the call with the source for each one, whether the contact on file is still the right person, and an opener built on the strongest verified fact. A plan is allowed to say skip, which matters most on an acquired base, where a wrong call costs more than a missed one. The test above is the same one it runs. You can run it yourself on twenty accounts this week, and you should, so you know what a good answer looks like before you trust anyone else's.
A ninety-day checklist for sales leaders after close
If you own the number after an acquisition, this is the short version of everything above.
- Get the combined account list from the integration team in the first week, and confirm how the two customer bases were matched.
- Name an owner for every acquired account before anyone is asked to cross-sell into it.
- Write down how cross-sell credit splits between the two sales teams, and publish it.
- Run retention calls on the largest and least stable acquired accounts in the first thirty days, with no pitch attached.
- Run the reason test on every inherited account: what changed, where you saw it, when.
- Verify the contact on file before any outreach, and replace stale ones.
- Sort the base into call now, not yet, and skip, and put the call-now accounts in front of reps first.
- Measure meetings and pipeline against the call-now list, and recheck the not-yet list every quarter.
The cross-sell case is not a fiction. The customers are real and many of them could use the other product. What the deal model hands the sales team is a list, and a list is not the problem. The missing reason, account by account, is. For the rest of the expansion motion after the first ninety days, see our customer expansion playbook and the breakdown of cross-sell versus upsell.
