Account Mapping: Who Can Buy Product Two

What account mapping actually answers after an acquisition

Nobody in the combined business reliably knows which of the new offerings fits which existing customer. Sales gets a list anyway and is asked to work it. The result is a high volume of attempts against a low hit rate, and from the outside it reads as a discipline problem rather than a sequencing one.

Account mapping is the exercise that answers it. Which customers already appear in more than one of the acquired systems? Which offering fits which customer type structurally, independent of who happens to know somebody there? The overlap analysis between the customer bases is the part that produces the shortlist.

Our position: this round is not preparation for the work. It is the work. It decides which conversations should happen at all, which is why we put the data side in order first and only then talk about sequences and messaging.

Three groups fall out of it, and all three are useful. Some customers fit a second offering and the responsible function is already known. Some fit, but nobody knows who decides. And some do not fit at all, because the business model does not need the second product. That third group is the real return on the exercise, because it stops costing you meetings.

Manuel Hartmann, Founder and CEO of SalesPlaybook, worked through this mechanism with Christian Reichert, Chief Revenue Officer of Shiftmove, in his LinkedIn newsletter Diary Of A CRO. Shiftmove came out of the merger of Avrios and Vimcar and has added further acquisitions since. The observations in this article come from that conversation.

From the LinkedIn newsletter Diary Of A CRO by Manuel Hartmann.

Why your best contact cannot buy your second product

The customer is happy, your contact takes every meeting, and the second offer still goes nowhere. That looks like a sales problem and is not one. The person who signed for the first product simply has no authority over the second, and nobody checked before the conversation started.

Christian Reichert describes it with an example from his own market. The fleet manager buys fleet management. The electronic logbook, however, is a compliance matter, and the tax or finance function decides on it. Both products belong to the same group, both fit the same customer, and the best available contact can sign for one and not the other.

The set of people involved in a purchase decision is what sales calls the buying center. The change after an acquisition is not that this set gets bigger. It is that there are suddenly several of them inside the same company, one per product line. A single-product vendor never had to make that distinction.

The maths in the deal model and the maths in the field

The acquisition is meant to raise revenue per customer, lower acquisition cost and make retention more stable. That is a fair expectation. It assumes the customer bases absorb each other, and that assumption is rarely tested. It is calculated.

The difference between those two things is the whole article. A number in the model is a hypothesis about willingness to buy. What becomes of it is settled by a question the model does not contain: inside these companies, who is actually permitted to commission the second product?

One play per segment, not one for the group

Once the mapping is done you have a sorted list, and the second reflex is to work it with a single uniform approach. That overloads the team at the small end and underserves the large one. Both errors cost the same thing, which is the opportunity the acquisition was meant to buy.

Segments differ less in product than in who decides and how many people that is. The approach follows from that.

Building several relationships inside one large account is what sales calls multithreading. At enterprise level it is not an optional refinement. It is the only method that finds a second buying center at all.

Practically, all of this needs one shared CRM instead of four separate ones, otherwise the overlap never becomes visible. We usually build that on HubSpot, as a Diamond Partner. For groups with several legal entities, our page on group-wide CRM describes how that is cut.

“We merged” is not a reason to buy

The announcement feels like a conversation starter and reads differently at the other end. It is about the vendor, not the customer, and it answers no question they currently have. Opening with it spends your first paragraph on information that concerns nobody.

What works is the mapping result, translated into the recipient's language. Not “we belong together now”, but the specific reason this particular customer would gain something from a second offering. That is more work per contact and considerably less work overall, because the list got shorter first.

The difference is measurable in the opening line. “We have combined Avrios and Vimcar and now also offer logbooks” is an announcement. “Your logbook currently runs separately from your fleet, and your tax team maintains it twice” is an observation about the reader. Only the mapping makes the second version writable, which is also how you can tell whether it happened.

Four contacts and four systems are the vendor's problem to solve

Your customer did not ask for the merger. They notice it as friction: two invoices, three contacts, a support desk that cannot find the case. That friction feeds churn directly, and it does so before a second product is ever discussed.

After its merger at the end of 2022, Shiftmove spent 2023 migrating to one contact person per customer. That is the unglamorous half of the synergy and the half that comes due first. Four companies means four contacts, four CRM systems and four cultures at the start, and none of those four resolve themselves by announcement.

That a group of several entities can in fact reach one shared foundation is not a promise, it is documented. We built exactly that for the agency group Jung von Matt: 140+ FTE Agency Group New Business Revenue Operating System. And that growth inside the existing base is a systems question rather than a motivation question shows in 5x More Deals and >2x Growth From Existing B2B Customers with HubSpot.

The underrated synergy is access to larger customers

The first reflex after an acquisition is to integrate everything: one platform, one login, one invoice. That is reasonable and correct in principle, but it is rarely what pays first. The value appears earlier, and it appears somewhere the integration plan does not mention.

A corporation with twenty thousand employees does not want four point solutions from four vendors, any of which might be gone next year. It wants a small number of durable partners. An acquisition makes a group large enough to be considered at all, and that is the synergy that works before any technical consolidation.

Our position: optionality is already a buying argument before anything is merged. The enterprise customer has put the vendor through procurement, security review and data protection. If that same vendor can supply another module tomorrow, it tips the comparison, even when only one is in use today.

Christian Reichert draws the boundary himself, and it belongs here. Optionality tempts you into over-building. Do not buy what the customer needs in five years if the rollout takes three. The option has to belong to the customer, not to the sales target.

How you know whether it worked

Progress is easy to mistake for activity in the first months. Meetings, proposals and touchpoints all rise after an acquisition regardless. Whether the maths works shows up only where the customer signs again, or does not.

What cross-selling promises is not only more revenue per customer. A customer using two to four offerings from the same vendor churns less often. That becomes visible in net revenue retention, meaning revenue from the existing base including expansion and cancellation. At Cito we reached it in under six months: 175% Net Revenue Retention with TOP 20 Clients in less than 6 months.

That number is the more honest gauge than any activity statistic, because it cannot be moved by making more calls. It moves when the mapping was right.