Merger Integration Kickoff Deck Workflow in Figma

The first integration kickoff after an acquisition can become a 60-slide container for everything anyone knows. Strategy, systems, people, customers, legal constraints, and branding all compete for space. The result may look polished while leaving the audience unsure what changes Monday morning.

Pitchdeck lets a team build the presentation in Figma and deliver it as an interactive deck or export it for PowerPoint, Keynote, or Google Slides. The harder task is information control: show enough context to coordinate work without turning uncertain plans into apparent commitments.

Decide what the meeting must produce

Write the decisions and actions the kickoff should enable before making slides. A practical outcome might be agreement on the first 30 days, named workstream leads, escalation routes, decision rights, and a cadence for resolving dependencies.

Separate four categories of information:

• confirmed facts, such as the transaction scope or effective date;
• approved decisions, such as reporting lines already communicated;
• working assumptions that still need validation;
• open questions with an owner and due date.

Give these categories a consistent visual treatment. A confident headline should never turn a working assumption into a promise. Add an “as of” date to volatile slides and identify the authoritative source for financial, legal, HR, security, and customer claims.

Build the story around coordination

A useful kickoff sequence often moves from shared context to operating mechanics:

1. Why the combination exists and what success means.
2. What is explicitly in and out of the first integration phase.
3. Principles for customers, employees, operations, and risk.
4. Workstreams, outcomes, leaders, and decision rights.
5. The first milestones and cross-workstream dependencies.
6. Known risks, unresolved questions, and escalation paths.
7. The next working session and required preparation.

Avoid opening with a dense project plan. The audience first needs a stable mental model for why the work is organized this way. Conversely, do not end with inspirational statements and no owners. Each workstream slide should state a near-term outcome, accountable lead, contributors, inputs, and the next decision.

Design for two organizations at once

Terminology is rarely shared on day one. One company says “customer success,” the other says “account management.” Product tiers, regions, security classifications, and internal acronyms may also conflict.

Create a small terminology table and use paired labels until language is agreed. Do not silently impose one organization’s vocabulary. Use team and role names rather than unexplained acronyms, and include a glossary only for terms the audience genuinely needs.

Make ownership diagrams readable without relying solely on brand colors. Labels, shapes, and grouping should explain the relationship. Check contrast and text size in the room or video-call layout where the deck will be presented.

Keep sensitive detail controlled

Integration decks often contain employee, customer, commercial, or security-sensitive information. Define the audience for each version before sharing. Keep restricted appendices separate when possible, minimize personal data, and avoid placing confidential notes behind decorative covers in a broadly distributed file.

Use version identifiers and a clear owner. Retire outdated exports so a stakeholder cannot unknowingly present last week’s assumptions. The pitch deck version-control workflow provides a useful broader model; integration work needs even stronger labeling because facts and permissions can change daily.

Choose the delivery format deliberately

An interactive presentation is useful when the core team controls the meeting and wants motion, embedded material, or a polished narrative. An editable PowerPoint or Google Slides file may be better when workstream leads must update their sections in familiar tools. A PDF is useful as a fixed reading copy but poor as the live source of an evolving plan.

Pitchdeck can export from the approved Figma deck into the downstream format. Test that format rather than assuming the Figma presentation is the final artifact. Open the exported deck in the application stakeholders will actually use. Check text, charts, links, images, video fallbacks, speaker notes, and slide order.

For the tradeoffs, use which Figma presentation export format should you use?. Choose one canonical source and record where edits must be returned; otherwise the Figma file and office deck will diverge immediately.

Rehearse the decision moments

Do a content rehearsal with the integration lead and one representative from each major workstream. Stop on slides that imply a decision, deadline, dependency, or organizational change. Ask:

• Is this confirmed, assumed, or proposed?
• Who can approve it?
• Which other workstream depends on it?
• What should the audience do after seeing this slide?
• Is the information appropriate for every recipient?

Then rehearse the actual presentation environment. Check remote readability, screen sharing, link access, embedded content, presenter handoffs, and a static backup. Keep detailed inventories in an appendix or linked workspace instead of shrinking them onto slides.

Turn the deck into an operating artifact

Within a day of the kickoff, publish the approved reading copy, decision log, owner list, and next meeting schedule in the agreed location. Mark questions answered during the meeting and route unresolved items to the correct forum. The deck should point to the system of record; it should not become a shadow project-management tool.

Before release, verify every sensitive claim, date, owner, dependency, and access permission. Pitchdeck helps the design team maintain a coherent story and create the required presentation output. Integration leadership still owns truth, confidentiality, and the decisions the deck is designed to produce.