Guide · 7 min read
Positioning After an Acquisition
Positioning after an acquisition means deciding, deliberately, what the combined company now is — rather than letting two organizations continue describing themselves as they did before the deal closed. The work is most valuable in the first ninety days, before informal explanations harden into habit.
Vizianary Editorial · Updated
A plain-language definition
Positioning after an acquisition is the decision about what the combined company is now, made explicitly, rather than assumed. An acquisition changes what a company is; someone has to decide whether it also changes how the company describes itself.
Why it matters to leadership
In the absence of a decision, both organizations default to their pre-deal explanations, and customers, employees, and partners are left to infer the relationship between two companies that now share ownership but not a story.
Symptoms
- The acquired team and the acquiring team describe the combined company differently.
- Customers of the acquired company are unsure whether the relationship they had still applies.
- Internal communications describe integration progress rather than a coherent direction.
- Two roadmaps continue in parallel with no stated relationship between them.
Common causes
Positioning work is frequently deferred until after operational and systems integration, on the assumption that narrative can wait. By the time it is addressed, both organizations have already taught their customers and employees an informal, uncoordinated story.
Common mistakes
- Announcing the deal without answering what it changes about the company's position.
- Treating narrative as a communications task separate from the integration plan.
- Letting the acquired brand persist indefinitely without a stated reason for doing so.
Decision criteria
Decide, explicitly, whether the acquisition changes the parent company's category, its customer definition, or only its product portfolio. Each answer implies a different amount of repositioning work, and conflating them leads to either doing too little or too much.
An example
An enterprise AI portfolio built through internal expansion and acquisition had a separate AI story in each business unit, and partners used whichever was convenient. Deciding explicitly whether the company was a portfolio with AI capabilities or an AI platform, and then building one playbook from that decision, let product, sales, and partners present the combined capability with one logic instead of several.
Next steps
In the first ninety days, decide what the acquisition changes about the company's position, communicate that decision to both organizations at the same time, and only then update customer- and partner-facing materials.

