Go-to-market strategy
Your company acquires a smaller product. How do you integrate it into your existing GTM strategy?
Find out why the company bought the product before touching messaging. Protect the acquired customers first by telling them what changes, what stays, and who to contact.
Then choose between standalone, bundled, or merged based on how much the two customer bases overlap. Settle who sells or promotes what, and plan one joint story and one visible integration win in the first ninety days, with a date to revisit the choice.
4 min read
Free 10-minute mock
Practice “Integrating an acquired product” free
Your first mock interview is free (10 minutes). No card needed.
Why the company bought it decides the plan
Most answers start with the press release. The acquisition thesis should come first, because it decides everything after. A company might buy a product to reach a new segment, fill a gap in its own product, remove a competitor, or hire a team. Each one leads to a different go-to-market.
This is also a second-order question. Acquired customers fear price rises and a shrinking roadmap. Your own customers wonder what changes for them. The acquired team knows its customers better than anyone and may be about to leave. A strong answer handles all three.
Standalone, bundle, or merge
| Option | When it fits | Risk |
|---|---|---|
| Standalone | Different buyers, a strong brand, little overlap | Two teams and two stories, slow to combine |
| Bundle | Overlapping buyers who would value both | Discount pressure and confusion over which to buy |
| Merge | The same buyer, and the product fills a gap | Churn among acquired users who liked it as it was |
A workout app that just bought a nutrition tracker
“I’d want to know why we bought it. Here we’re a workout app with a paid subscription, and we just acquired a popular nutrition-tracking app with its own subscribers. If the thesis is that people who track food stick with their workouts longer, I’d check overlap first. Imagine only fifteen percent of the tracker’s paying users also use our app. That says keep it standalone for now and offer a bundle. Merging would force most of their users into an app they never chose. The first message goes to the tracker’s users within a week of the announcement. Their price, their data, and the app stay as they are for at least a year, and here’s who to contact. Silence reads as bad news, and the app store reviews will say so. Then I’d offer both subscriptions together at a discount, promoted inside each app to people who fit. The integration win for the first ninety days is simple. Workouts show up in the food log, so calorie targets adjust. At day ninety I’d look at bundle uptake, churn among the tracker’s users against their old baseline, and whether bundle users retain better. That tells us whether a merge is worth considering next year.”
Protecting the customers you just bought
- What changes and what doesn’t, in plain words, within days of the announcement.
- Timelines for any change, with the earliest date anything moves.
- Pricing commitments that are specific and dated.
- Data and privacy. Ask for consent before combining accounts or data.
- A named contact or support path that works from day one.
Bring the acquired team into this. They know which customers are nervous and which promises were made in the past.
Settling who sells or promotes the acquired product
In a business software deal this means account ownership and sales compensation. In a consumer deal it means which app promotes the other, the rules for cross-promotion, and whose revenue target the bundle counts toward. Either way, if nobody’s target includes the new product, nobody pushes it. Product marketing doesn’t own pay plans. It should still raise the gap with whoever does.
Where acquisition answers go wrong
“I’d bring the messaging under our brand, announce the acquisition with a press release and customer emails, update the website, and train the team on the new product.”
This reads like a sensible launch checklist. It starts from the announcement, assumes a merge, and skips the thesis and the overlap check that should decide the merge. Start from why, protect the acquired customers, and choose the relationship on evidence. Moving fast on a merge is the related trap. A forced migration in the first quarter can lose the customers the company paid for.
Follow-ups on integrating an acquisition
| They follow up with | The concern | Your answer |
|---|---|---|
| The acquired team resists repositioning. | Influence | Use their customer knowledge and show them the data behind the choice |
| When would you keep a separate brand? | Brand judgment | When buyers differ and the brand carries trust you would lose |
| The two products overlap in features. | Rationalizing the product | Keep the one with more usage, with a migration path and a date |
| What do you tell your own customers? | Two audiences | What they gain, and that nothing changes for them yet |
More questions in this category
Frequently asked questions
- Should I assume the acquired product gets merged?
- No. Start with why the company bought it and how much the customer bases overlap. Staying standalone for a year is often the right call.
- Where does sales compensation fit in a PMM answer?
- Raise it as a dependency. You won’t own it, but a team with no incentive won’t promote the new product, and the owner should hear that from you early.
Guides that help with this question
All guidesFree 10-minute mock
Practice “Integrating an acquired product” free
A Mokk session asks this question, follows up on your answer, and scores it on five competencies. Your first mock is 10 minutes, scored like a full interview. No card needed.
Your first mock interview is free (10 minutes). No card needed.
Practice “Integrating an acquired product” free
10 minutes · no card needed