A 90-day post-merger consolidated reporting playbook

Three months after a merger closes, leadership wants one number for total revenue, one number for combined margin, and one number for unified pipeline. The data team usually has three numbers for each, all from different systems, all explainable, none reconciled. The 90-day window to fix this is shorter than most teams plan for — and the playbook below is what we use to get a credible consolidated view in front of leadership before the formal integration project is anywhere close to done.

We have run this playbook on engagements ranging from a tuck-in strategic acquisition to a multi-hundred-million-dollar combination of operating companies. The shape of the work is remarkably consistent. The sequencing matters more than the tooling. And the cost of waiting for the full ERP or CRM integration before producing a consolidated view is much higher than the cost of producing one with informed shortcuts.

Days 1-30: stabilize before you unify

The first month is not about combining the data. It is about making sure each side's numbers are correct on their own, in their own systems, before you try to add them together. Half of every post-merger reporting incident we have investigated traced back to one side's pre-merger numbers being slightly off in ways that nobody noticed until the consolidation made them visible.

We open the engagement by reconciling each entity's headline numbers to its own audited financials for the prior two quarters. If the management reports do not match the audited statements, that gap needs to be understood and documented before any consolidation work begins. The same goes for pipeline, customer counts, and any operational metric leadership will be asked about in the first 90-day all-hands.

Day-30 deliverable

• A reconciliation memo per entity matching management reports to audited financials
• A single source-of-truth list of each side's pre-merger headline KPIs with definitions
• A documented inventory of known measurement differences between the two entities
• A short list of metrics that will need redefinition (rather than simple summation)
• A stakeholder map naming the executive owner for each consolidated KPI

Days 31-60: unify the definitions before unifying the data

By day 30 each side's numbers are stable. The next 30 days are about getting agreement on what the combined metrics will mean — not how to compute them yet, but what they will represent. This is the harder problem. Most measurement differences between two companies are not technical mismatches; they are different policy choices that have been encoded in the data over years.

We force the definitional conversations in a small set of working sessions: finance for revenue and margin, sales operations for pipeline and qualified leads, customer success for retention and churn, ops for unit economics. Each session produces a one-page metric definition for the combined entity — usually drafted by us, signed off by the executive who will be accountable for that metric on the new leadership dashboard.

Days 61-90: ship the consolidated view

By day 60 the definitions are locked. The last 30 days are about producing a real consolidated dashboard against those definitions. We deliberately do not wait for full ERP or CRM integration. Instead, we use one of a few proven shortcuts that get leadership credible numbers in time for the first quarterly board meeting after the merger closes.

Shortcuts that work

• Scheduled exports from both source systems into a shared lakehouse or warehouse, refreshed nightly
• A thin mapping layer that translates each side's chart of accounts into the combined definitions
• A consolidated semantic model built once and shared across reports
• RLS configured at the entity level so each leadership team can still see their own pre-merger view
• A clear 'as of' label on every visual so users know what level of reconciliation has been applied
• A parallel-run period where the consolidated dashboard ships alongside each side's legacy reports for 30 days

Where companies overspend

The most common post-merger reporting failure mode is not under-investment. It is waiting for the full integration project to finish before producing any consolidated view at all. By the time the systems are unified, leadership has been making decisions on Excel hand-calculations for nine months and has lost confidence in the data team. Recovering that confidence is more expensive than the shortcuts above ever would have been.

The second-most-common failure mode is the opposite — rebuilding too quickly. Teams sometimes push for full system replatforming inside the 90-day window, on the theory that one consolidated stack is cheaper than two. It almost never is. The merger creates urgency around the reporting outputs, not around the underlying platforms. Treat them as separate decisions on separate timelines.

Anti-patterns from the trenches

• Combining definitions without retaining the pre-merger view — leadership loses the ability to compare to prior periods
• Letting each side's reporting team continue to operate independently — definitional drift starts again within a quarter
• Treating data integration and definitional unification as the same project — they run on different cadences
• Building the consolidated dashboard before reconciling each entity's standalone numbers
• Skipping the executive sign-off on each combined definition — disputes surface in the board meeting instead
• Trying to build a perfect unified data model in 90 days — the consolidated view ships, the model takes a year

What good looks like at day 90

A successful 90-day program produces three things: a single consolidated leadership dashboard that everyone trusts, a metric register with executive ownership per KPI, and a stable handoff to whichever team is going to own the consolidated reporting long-term. The dashboard is not the deliverable. The dashboard is evidence that the deliverables — definitions, ownership, reconciliation — are in place.

The one-line takeaway

Post-merger consolidated reporting is a definitional and organizational problem first, and a data integration problem second. Stabilize each side, lock the combined definitions, then ship a credible view using informed shortcuts. The platforms can be unified on a longer clock.