Private-equity growth stories love the acquisition announcement. Customers mostly experience what happens next.
At Accruent (2016–2018), M&A wasn’t a side project — it was a core growth motion. The company completed on the order of ten acquisitions in about two years. I led cross-functional M&A launch teams for four of those integrations in the U.S. and Europe, each pulling in up to ~25 people across departments and hundreds of tracked tasks. That inorganic growth sat inside a stretch when Accruent doubled headcount, tripled valuation, and exited for multiple billions.
What follows isn’t a theory of deal-making. It’s a product-and-launch playbook for the messy middle: the weeks when two products, two customer bases, and two sets of tribal knowledge have to become one coherent experience.
What product (and product marketing) actually own
In a healthy integration, Product doesn’t “rebrand the logo and go home.” We own — or co-own — a few unglamorous essentials:
- Offer clarity: What still sells on day one? What’s deprecated? What’s the path for overlap?
- Customer narrative: Internal FAQ and external FAQ that say the same true thing in different altitudes.
- Roadmap honesty: What lands in 30/60/90 days vs what is aspiration.
- Launch orchestration: The cross-functional drumbeat so Sales, Support, CS, Marketing, Finance, and Engineering aren’t improvising different stories.
If nobody names an owner for those, customers will invent the story for you — usually the scariest version.
The launch-team machine
Every serious launch I’ve led — new product, major revision, or acquisition — shares the same skeleton:
- Cross-functional by default. Almost every department is touched. Even Accounting may need a new orderable line item.
- Increasing pace. Early meetings create alignment months out. As the date nears, cadence tightens — sometimes to daily. I think of it as the increasing drumbeat of a launch.
- Lightweight rules that respect time. People can multitask; they can leave after their update; the tracker is sacred.
- One living plan. Spreadsheet or Smartsheet, owned by the launch lead, with owners and due dates — not a slide that dies after the kickoff.
- Post-launch follow-up. Metrics and cleanup meetings after “go” matter as much as the celebratory email.
M&A launches add emotional load. Acquired teams are proud of what they built. Surviving teams are protective of what already works. Your job is pace and respect, not cleverness.
A practical first-90-days checklist
Days 0–30 — Stabilize the story
- Ship internal + external FAQs (customers of both companies).
- Align Sales on what to sell / what not to promise.
- Map product overlap in plain language (not only architecture diagrams).
- Identify “day-one” support paths so tickets don’t bounce between tribes.
- Name the integration thesis in one paragraph executives can repeat.
Days 31–60 — Make the path visible
- Publish a customer-facing timeline that is conservative enough to keep.
- Decide interim packaging/pricing exceptions with Finance and Sales leadership.
- Start the smallest useful product bridges (SSO, data export, shared account lists) before the grand platform rewrite.
- Run working sessions with acquired PMs and engineering leads — listen before redesigning.
Days 61–90 — Prove one integrated motion
- Land at least one visible cross-sell or combined narrative win.
- Retire conflicting collateral; one battle card beats five legacy PDFs.
- Capture lessons in a reusable playbook so acquisition #5 isn’t folklore.
- Re-evaluate roadmap capacity: integration tax is real — pretend it isn’t and both products suffer.
Messaging: one company, honest overlap
The temptation is to declare “seamless” on day one. Customers smell it.
Better pattern:
- Celebrate what the acquired product does exceptionally well.
- Be explicit about what stays, what merges, and what will take time.
- Give account teams a single talk track for the awkward questions (“Will my product be killed?” “Do I have to migrate this year?”).
At Accruent, a big part of the work was translating features into benefit-based storytelling for facility and asset owners — and making sure acquired offerings enhanced the portfolio instead of confusing it. The writing and the ops were the same job: reduce ambiguity.
People and systems
Integration isn’t only product lines. It’s recommending how teams and tools come together. That requires humility. You won’t know the acquired codebase or customer politics on day three. You can create a fair process: shared criteria, visible decisions, and a bias for customer continuity over internal elegance.
Track hundreds of tasks if you must — we did — but never confuse task completion with customer trust. Trust is whether a facilities leader still believes your roadmap after the press release fades.
Why this still matters
Whether you’re a PE operating partner, a VP of Product absorbing a tuck-in, or a product marketer drafted onto a launch team, M&A success is mostly operational empathy at speed. The deal creates optionality. The launch team creates reality.
I’ve carried those habits forward into later CPO and VP Product roles: clear owners, paced communication, and roadmaps that admit constraints. Acquisitions will keep being a growth strategy in software. The companies that win won’t be the ones with the flashiest announcement — they’ll be the ones whose customers can explain the new story without a decoder ring.
More on the Accruent chapter and what came next: Work History, Product Marketing and Product Leader. Conversations welcome via Contact.