PE Portfolio Roll-Ups: Unifying Analytics After Seven Acquisitions

The Analytics Integration Problem in PE Roll-Ups

When a private equity firm executes a roll-up strategy—acquiring five, seven, or ten add-on companies and folding them into a platform business—the financial engineering looks clean on paper. Synergies are quantified. EBITDA accretion is modeled. But the operational reality is messier: you now own seven different data warehouses, seven different BI tools, seven different reporting standards, and seven different definitions of what "revenue" actually means.

This is where most PE firms stumble. While the deal teams focus on purchase price allocations and debt structures, the portfolio company operations teams inherit a fragmented analytics landscape that makes it nearly impossible to answer basic questions: What is our consolidated revenue run rate? Which add-on is underperforming? Where are the quick wins for cost synergies? How do we track KPIs against our value-creation plan?

The traditional answer has been to license Looker, Tableau, or Power BI and hire a team of BI engineers to rebuild everything from scratch. That's expensive, slow, and often results in a platform that feels foreign to the acquired companies' teams. There's a better path: consolidating analytics on managed Apache Superset with AI-powered query generation and API-first architecture, which lets you unify data governance without ripping out the tools your teams already know.

This article walks through the real mechanics of analytics consolidation in PE roll-ups—from data architecture decisions to governance models to cost optimization. We'll ground this in the constraints PE firms actually face: integration timelines measured in months, acquisition teams that move fast, and the need to capture synergies without burning cash on platform overhead.

Understanding the Roll-Up Acquisition Model

Before we dive into analytics, let's establish what a PE roll-up actually is and why it creates such acute data integration challenges.

A roll-up strategy in private equity involves acquiring multiple smaller companies in the same or adjacent markets and consolidating them under a single operating platform. Unlike a traditional add-on acquisition (where you buy one company and integrate it), a roll-up is a systematic approach: you acquire company A, then B, then C, and so on—each one adding revenue, customers, and operational capability to the platform.

The value creation logic is straightforward: buy fragmented, low-margin, locally-operated businesses; consolidate them; standardize operations; eliminate redundant overhead; and sell the unified platform at a higher multiple. The buy-and-build strategy emphasizes operating efficiencies and economies of scale that emerge when you merge add-on companies and align them around shared processes.

But here's the problem: each acquired company typically has its own finance function, its own ERP system (or spreadsheets), its own KPI definitions, and its own reporting cadence. When you're integrating seven acquisitions over 18–24 months, you can't wait for a perfect data foundation. You need to report consolidated results to your LP investors, track synergy realization, and give portfolio company management visibility into performance—all while the integration is still happening.

This is where analytics becomes a critical value-creation lever. PE firms that excel at tracking portfolio company data post-acquisition gain an operational advantage: they spot issues faster, identify synergy opportunities earlier, and make better capital allocation decisions.

The Analytics Fragmentation Challenge

Let's make this concrete. Imagine you've just acquired seven companies in the staffing and recruiting space. Here's what your data landscape looks like:

Company A (your platform): Uses Tableau on top of a Snowflake data warehouse. Finance team has built 15 dashboards over two years. They define "revenue" as invoiced amounts. They track weekly KPIs.

Company B (first add-on): Uses Looker on top of a Postgres database. Revenue is defined as cash collected. They report monthly.

Company C: Uses Power BI on top of a SQL Server. Revenue includes accrued amounts. They report quarterly.

Companies D–G: Use a mix of Google Data Studio, Metabase, and custom Python scripts. Some have data lakes; some have data marts; some have Excel files that are "source of truth."

Now, as the PE firm, you need to:

• Consolidate revenue reporting across all seven entities (each with different definitions)
• Build a single KPI dashboard for the board and LPs
• Track synergy realization (cost savings, revenue synergies, working capital improvements)
• Give each portfolio company management team visibility into their performance relative to plan
• Do all of this without breaking the reporting that each company's team relies on day-to-day

The naive approach is to pick the "best" BI tool (usually the one the platform company already uses) and force everyone else to migrate. This creates several problems:

Disruption: Teams lose access to the dashboards they use to run their business. The migration takes 6–12 months. During that time, reporting quality degrades, and management attention is diverted to integration instead of value creation.

Cost: Enterprise BI licenses (Looker, Tableau, Power BI) charge per user or per viewer. When you consolidate seven companies, you're suddenly paying for hundreds of users across multiple tools. The bill can exceed $500K–$1M annually.

Rigidity: These platforms are built around a hub-and-spoke model where a central team controls the data model and dashboard creation. In a roll-up, you need flexibility: some companies want to self-serve; others need centralized reporting; some have compliance requirements that demand specific audit trails.

Governance complexity: Each acquired company has different data quality standards, schema designs, and metric definitions. Building a single source of truth requires months of reconciliation work—and that's before you've even started building dashboards.

Why Managed Apache Superset Works for PE Roll-Ups

Managed Apache Superset offers a different approach. Instead of forcing a centralized, top-down BI architecture, it lets you build a federated analytics model where each company's data stays where it is (or migrates to a shared cloud data warehouse) but reporting is unified through a single platform.

Here's why this matters for PE:

Superset is open-source and lightweight: You're not paying per-user licensing fees. You're paying for infrastructure and managed services. That means you can give every stakeholder—from the CFO to the junior analyst—dashboard access without blowing up your budget. D23's managed Superset offering handles the operational overhead, so your team doesn't have to.

API-first architecture: Superset is built on APIs, which means you can embed dashboards directly into your internal systems, portfolio company websites, or investor portals. You're not forcing everyone to log into a separate BI tool; dashboards come to them.

SQL-first approach: Superset doesn't abstract away SQL. For data teams that are already writing SQL (which most are), this is faster than learning a proprietary query language. You can onboard data sources quickly without waiting for a data modeler to build a semantic layer.

AI-powered query generation: Modern Superset implementations include text-to-SQL capabilities powered by LLMs, which means less-technical users can ask questions in natural language and get answers without writing SQL. This dramatically reduces the support burden on your data team.

Flexibility in data architecture: You can connect Superset to Snowflake, Postgres, BigQuery, Redshift, or any other database. You're not locked into a single vendor. This is critical in roll-ups where acquired companies might already have data in different systems.

The result: you can consolidate analytics without forcing a one-size-fits-all BI platform on companies that have different needs.

Building the Unified Analytics Foundation

Let's walk through how you'd actually build this in practice.

Step 1: Data Consolidation (Not Homogenization)

Your first instinct might be to build a single, unified data warehouse where all seven companies' data lives. That's the right long-term goal, but it's not the right starting point.

Instead, create a hub-and-spoke data architecture:

• Hub: A central cloud data warehouse (Snowflake, BigQuery, or Redshift) that holds consolidated metrics, KPIs, and cross-company views.
• Spokes: Each acquired company's existing data systems remain in place. You layer a transformation and consolidation process on top.

Why? Because you can start reporting consolidated KPIs in weeks, not months. You don't have to migrate all seven companies' operational data into a new system before you can answer basic questions.

Here's the workflow:

1. Extract: Pull daily or weekly extracts from each company's data source (ERP, accounting system, CRM, etc.).
2. Normalize: Transform each company's data into a standard schema. This is where you reconcile revenue definitions, fix date formats, align customer IDs, etc.
3. Load: Push normalized data into your central hub.
4. Model: Build consolidated views in the hub that answer roll-up questions (total revenue, consolidated EBITDA, synergy tracking, etc.).
5. Visualize: Point Superset at the hub and build dashboards.

Meanwhile, each acquired company can continue to use their existing BI tools for day-to-day operations. You're not disrupting their workflow; you're adding consolidated visibility on top.

Step 2: Metric Governance

One of the biggest traps in PE roll-ups is metric chaos. If Company A defines "revenue" as invoiced amounts and Company B defines it as cash collected, your consolidated revenue number is meaningless.

You need a metric governance layer. This is simpler than it sounds:

Create a metrics registry: A single source of truth that defines every metric used in your dashboards. For each metric, document:

• Name: What is this metric called?
• Definition: Exactly how is it calculated? (SQL query, formula, source system, etc.)
• Owner: Which team owns this metric? Who do you ask if there's a discrepancy?
• Frequency: How often is it updated? (Real-time, daily, weekly, etc.)
• Lineage: Which source systems feed into this metric?

For a seven-company roll-up, your metrics registry might have 50–100 entries. You can store this in a simple Google Sheet or a more sophisticated tool like Atlan or Collibra. The point is that every dashboard in Superset links back to this registry.

When someone asks, "Why is Company A's revenue different in the Superset dashboard than in their local reporting?" you have a clear answer. And when you realize that Company B's definition is more accurate, you can update the registry once and all downstream dashboards automatically reflect the change.

Step 3: Consolidation Dashboards

Now build the dashboards that actually drive value in your roll-up. These fall into three categories:

1. Investor Reporting Dashboards

These are for your LP investors and the investment committee. They answer: "How is the platform performing against our value-creation plan?"

Key metrics:

• Consolidated revenue (by month, by company, by product line)
• Consolidated EBITDA (with detailed P&L)
• Customer acquisition and churn
• Employee headcount and productivity metrics
• Cash flow and working capital
• Progress against synergy targets

These dashboards are typically refreshed monthly and are read-only. They're the "source of truth" for investment performance.

Step 4: Synergy Tracking

This is where analytics directly impacts value creation. Most PE firms have a synergy playbook: we'll eliminate 30% of duplicate G&A, consolidate software licenses, cross-sell customers, etc. But tracking actual realization is hard without good analytics.

Build a synergy dashboard that tracks:

Cost synergies:

• Headcount reductions (plan vs. actual)
• Duplicate software licenses eliminated
• Facilities consolidation (square footage, rent savings)
• Procurement savings (volume discounts on supplies, etc.)

Revenue synergies:

• Cross-sell revenue (customers from Company A buying services from Company B)
• Pricing harmonization (moving lower-priced customers to higher-priced tiers)
• Market expansion (using Company A's customer base to sell Company C's products)

Working capital improvements:

• Days sales outstanding (DSO) improvements
• Inventory turns
• Accounts payable optimization

You can build this in Superset by connecting to your accounting system and creating calculated fields that compare actual results to your synergy plan. As you close each month, the dashboard updates automatically—no manual reporting.

Step 5: Portfolio Company Dashboards

Each acquired company still needs to see their own performance. Don't force them to use your consolidated dashboards; give them their own views that let them manage their business day-to-day.

These dashboards might include:

• Revenue by customer, product, geography
• Gross margin by service line
• Headcount and productivity metrics
• Customer health and churn risk
• Pipeline and forecast
• Operational KPIs (utilization, project profitability, etc.)

The key difference: now all of these are built in Superset and connected to your central data hub. When you need to roll up to the platform level, the data is already normalized and accessible.

Addressing Data Quality and Governance

Data quality is a persistent challenge in roll-ups because you're integrating systems with different standards. Here's how to manage it:

1. Data Quality Checks

Build automated data quality checks into your ETL pipeline. For each data source, test:

• Completeness: Are all expected records present? (e.g., Do we have transactions for all days?)
• Accuracy: Do totals match the source system? (e.g., Does our extracted revenue match the ERP's revenue report?)
• Timeliness: Is data arriving on schedule?
• Consistency: Are values within expected ranges? (e.g., Is revenue per customer reasonable?)

If a check fails, alert the data team and pause the dashboard refresh until the issue is resolved. This prevents garbage data from reaching decision-makers.

2. Data Lineage and Audit Trails

When someone questions a number in a dashboard, you need to be able to trace it back to the source. Superset integrates with tools like dbt (data build tool) that provide data lineage tracking.

For each dashboard, document:

• Which source systems feed the data?
• Which transformations are applied?
• When was the data last updated?
• Who has permission to edit the dashboard?

This is especially important if any of your portfolio companies are in regulated industries (healthcare, financial services) where audit trails are mandatory.

3. Access Control and Security

Not everyone should see all dashboards. A portfolio company's CFO shouldn't see another company's detailed financials. An investor should see consolidated results but not individual company P&Ls.

Superset supports role-based access control (RBAC). You can define roles like:

• Platform Management: Can see all dashboards, edit metrics, manage data sources
• Company Leadership: Can see their own company's dashboards plus consolidated platform dashboards
• Finance Team: Can see detailed financial dashboards
• Investor: Can see investor reporting dashboards only

Assign users to roles, and Superset automatically filters data based on their permissions.

Cost Optimization in Consolidated Analytics

One of the biggest wins in moving to managed Superset is cost control. Let's quantify the savings:

Licensing costs: If each of your seven companies was paying $80K–$150K annually for Looker or Tableau, you're looking at $560K–$1.05M per year. Switching to managed Superset reduces this to infrastructure costs (cloud data warehouse, Superset hosting) plus a managed services fee. For most mid-market roll-ups, this is 40–60% cheaper.

Personnel costs: You don't need a large BI team. One or two data engineers can manage Superset and the ETL pipeline. Compare that to the three to five people typically needed to manage Looker or Tableau across seven companies.

Data warehouse costs: This is the biggest variable. If you're consolidating data into Snowflake or BigQuery, you'll pay for storage and compute. But here's the optimization: most companies over-provision their data warehouses. By carefully managing query patterns and using techniques like materialized views and caching, you can reduce your DW bill by 30–40%.

Time to insight: With text-to-SQL and API-first architecture, your team can build new dashboards and answer ad-hoc questions faster. That means fewer cycles of "Can you pull that report?" and more time on strategic analysis.

Real-World Implementation Timeline

Here's what a realistic 12-month implementation looks like for a seven-company roll-up:

Months 1–2: Discovery and Planning

• Audit each company's data sources, BI tools, and metric definitions
• Map the synergy playbook to specific metrics and dashboards
• Design the data architecture (hub-and-spoke, ETL pipeline, data warehouse)
• Identify quick wins (dashboards you can build in weeks, not months)

Months 2–4: Foundation

• Set up your cloud data warehouse (Snowflake, BigQuery, etc.)
• Deploy managed Superset
• Build the ETL pipeline for the platform company's data
• Create the metrics registry
• Build investor reporting dashboard (using platform data only)

Months 4–8: Incremental Add-Ons

• Integrate data from Companies B, C, D in waves (one per month)
• Build company-specific dashboards as you integrate each add-on
• Refine metric definitions based on what you learn
• Train each company's team on their dashboards

Months 8–12: Optimization and Expansion

• Integrate remaining companies
• Build synergy tracking dashboards
• Optimize query performance and reduce data warehouse costs
• Add AI-powered query generation (text-to-SQL) so less-technical users can self-serve
• Plan for ongoing maintenance and evolution

Why Superset Beats Competitors in Roll-Up Scenarios

Let's be direct about why managed Superset is better than the alternatives for PE roll-ups:

vs. Looker or Tableau: These tools are designed for large enterprises with centralized data teams. They're expensive per user, they lock you into their semantic layer, and they're slow to implement. In a roll-up, you need flexibility and speed. Superset gives you both.

vs. Preset (the commercial Superset offering): Preset is fine, but D23's managed Superset is purpose-built for use cases like yours. You get data consulting, AI-powered query generation, and a team that understands PE operations—not just BI generalists.

vs. Metabase: Metabase is simpler than Superset, which is good for small teams. But it lacks the depth you need for complex roll-up scenarios. You'll outgrow it quickly.

vs. Mode or Hex: These are SQL notebooks, not BI platforms. They're great for exploratory analysis but not for building the consolidated dashboards that drive daily operations.

Embedding Analytics in Your Portfolio

One advanced use case that PE firms often overlook: embedding analytics directly in your portfolio companies' products or customer-facing systems.

Imagine Company A is a staffing firm that sells to enterprise customers. Those customers want visibility into their staffing spend, utilization rates, and cost per hire. Instead of building a separate reporting system, you can use Superset's API-first architecture to embed dashboards directly into Company A's platform.

Same for Company B (a recruiting software company): your customers want analytics on their hiring pipeline, time-to-hire, and cost-per-hire. Embed it.

This creates a competitive advantage and increases customer stickiness. And operationally, it means you're building once and deploying across multiple companies. That's leverage.

Data Consulting and Ongoing Support

One thing that separates managed Superset from DIY approaches: you get access to data consulting expertise. This is critical in roll-ups because you're not just building dashboards; you're solving business problems.

Good data consulting in this context means:

• Synergy identification: Your consultants understand PE playbooks. They can look at your data and say, "You have an opportunity to cross-sell Company C's services to Company A's customers—here's what the addressable market looks like."
• Metric definition: They help you define metrics that actually drive decision-making, not just vanity metrics.
• Data architecture: They design systems that scale as you acquire more companies.
• Training and enablement: They teach your teams how to use Superset effectively, so you're not dependent on consultants long-term.

D23's managed Superset offering includes data consulting as part of the package, so you're not paying separately for strategic advice.

Governance and Compliance in Regulated Industries

If your roll-up includes companies in regulated industries (healthcare, financial services, insurance), you need to think carefully about data governance.

Superset supports:

• Audit logging: Every query, every dashboard view, every data change is logged
• Row-level security: You can restrict data access based on user attributes (e.g., a healthcare provider can only see patients in their practice)
• Data encryption: Data in transit and at rest can be encrypted
• Compliance certifications: Managed Superset providers can offer SOC 2, HIPAA, or other certifications as needed

When you're consolidating data from regulated companies, make sure your data architecture and BI platform support these requirements from day one. It's much harder to retrofit compliance later.

Advanced: AI-Powered Analytics and Text-to-SQL

One of the most powerful features in modern Superset implementations is AI-powered query generation. Instead of asking your data team to write SQL, less-technical users can ask questions in natural language and get answers.

Example: "What's the revenue trend by company for the last 12 months?" The LLM translates that to SQL, queries your data warehouse, and returns a visualization.

For PE roll-ups, this is game-changing because:

• Faster decision-making: When you need to understand a portfolio company's performance, you don't have to wait for a data team member to write a query.
• Reduced support burden: Your data team spends less time answering ad-hoc questions and more time on strategic work.
• Broader access: Non-technical executives can explore data themselves instead of relying on intermediaries.

Text-to-SQL capabilities are built into D23's Superset offering, and they're trained on common PE metrics and KPIs, so they're immediately useful in roll-up scenarios.

Avoiding Common Pitfalls

Based on real implementations, here are the mistakes PE firms most often make:

1. Trying to build a perfect data model before launching dashboards

Don't wait. Build 80% of the way there, launch dashboards, learn what people actually need, and iterate. You'll end up with a better system faster.

2. Centralizing all data too quickly

Keep each company's operational data where it is initially. Consolidate only the metrics you need for roll-up reporting. This reduces risk and speeds up implementation.

3. Ignoring the human side of integration

Your data teams are already stressed during integration. If you suddenly tell them they need to migrate to a new BI tool, they'll resist. Involve them early, show them how Superset makes their jobs easier, and give them time to adapt.

4. Under-investing in data quality

Garbage in, garbage out. Spend time upfront defining metrics, building data quality checks, and validating data. This prevents months of firefighting later.

5. Building dashboards no one uses

Always start with dashboards that solve immediate problems. Investor reporting. Synergy tracking. Company KPIs. Build the exotic stuff later.

Conclusion: Analytics as a Value-Creation Lever

In PE roll-ups, analytics is often treated as a back-office function—necessary but not strategic. That's a mistake. When you consolidate analytics effectively, you unlock value:

• Faster synergy realization: You see cost-saving opportunities earlier and track execution in real-time.
• Better capital allocation: You understand which companies are performing and which need attention.
• Improved operational decision-making: Portfolio company management teams have visibility into their performance and can act faster.
• Reduced integration risk: You can answer questions about the combined entity quickly, which reduces uncertainty for stakeholders.

Managed Apache Superset gives you the platform to do all of this without the cost, complexity, and timeline overhead of traditional BI platforms. You consolidate analytics without centralizing control, which is exactly what PE firms need in a roll-up scenario.

The best time to start building your consolidated analytics is now—ideally before your next acquisition closes. When the add-on arrives, you're ready to integrate its data immediately and start capturing synergies on day one.

If you're evaluating how to consolidate analytics across your portfolio, D23 can help. We work with PE firms and platform companies to build analytics systems that scale with your acquisitions. Reach out to discuss your specific situation.