Integration Governance for Multi-Entity Roll-Ups: Structure, Reporting, and Shared Services

A roll-up strategy that closes acquisitions faster than it builds governance infrastructure eventually breaks. The problems that emerge are predictable: subsidiary management teams operating under inconsistent authority, intercompany transactions without written agreements, qualified retirement plans that unknowingly violate controlled group coverage rules, debt covenants tracked on spreadsheets that are never reconciled, and financial reporting packages that satisfy no one's information needs. None of these problems requires a complex transaction to create. Each is the consequence of treating governance design as something that comes after the acquisitions rather than something that enables them.

This sub-article is part of the Roll-Up Platform Consolidation M&A Legal Guide. It covers the full scope of integration governance for multi-entity roll-up platforms: holdco board and committee structure, subsidiary officer appointments, the single-entity versus multi-entity operating model decision, shared services agreement design across accounting, HR, IT, legal, and procurement functions, intercompany services pricing and transfer pricing methodology, ERP and billing system consolidation timing, delegation of authority matrix design across capex, hiring, and contract thresholds, chart of accounts harmonization, financial reporting package design for lender and investor compliance, compliance program consolidation across employment law, safety regulation, and data privacy, employee benefits plan harmonization and the Section 414 controlled group analysis, brand and trademark management across acquired entities, litigation and risk management coordination, debt covenant tracking across multiple facilities, investor reporting cadence and content, and a structured 30/60/90-day integration playbook for each add-on acquisition.

Acquisition Stars advises roll-up sponsors, independent sponsors, and private equity groups on the legal and structural elements of multi-entity integration. Nothing in this article constitutes legal advice for any specific transaction or platform.

Holdco Board Composition and Committee Structure

The holding company board is the highest governance authority in a multi-entity roll-up. Its composition and the scope of its authority over subsidiary operations define the governance tone for the entire platform. A roll-up sponsored by a private equity fund typically structures the holdco board with a majority of investor-designated seats, one or two seats for operating management, and one or more independent directors with relevant industry or operational expertise. The specific seat allocation is governed by the holdco's operating agreement or shareholders agreement and reflects the relative economic positions of the equity holders.

Board committees are established to focus ongoing oversight on areas that require sustained attention without consuming full board meeting time. An audit committee with responsibility for financial reporting oversight, internal controls, and auditor relations is standard for any platform that has or anticipates institutional debt. A compensation committee that sets executive pay at the holdco level and approves subsidiary management compensation above defined thresholds prevents informal pay compression or leapfrogging across the platform. Some platforms establish an integration committee, particularly in high-acquisition-velocity phases, to provide oversight of the integration playbook execution and escalation for integration issues that require board-level input.

Committee charters should be written documents that define each committee's authority, the types of matters within its scope, the quorum and voting requirements for committee decisions, the reporting cadence to the full board, and the process for escalating matters outside the committee's authority to the full board. Committees without charters operate on informal understandings that become sources of dispute when governance stress occurs, typically during underperformance, a contested senior hire, or an exit process. Written charters cost little to prepare when governance is functioning and considerable goodwill to reconstruct after a conflict has emerged.

Subsidiary Board and Officer Appointments

Each subsidiary entity in a multi-entity roll-up is a separate legal person with its own governance requirements under the laws of its state of formation. A limited liability company requires at minimum a manager or a managing member with authority to bind the entity. A corporation requires at minimum a board of directors and the statutory officer positions required under its state of incorporation, commonly a president, a secretary, and a treasurer, though those positions may be held by the same individual.

In a roll-up context, subsidiary governance is typically structured to give the holdco clear control while preserving the local management authority that makes the acquired business function. A common structure has the holdco itself serving as the sole member or managing member of each subsidiary LLC, with holdco-designated officers serving in the statutory officer roles at each subsidiary. The acquired business's CEO or general manager operates under an employment agreement with the subsidiary, but their authority is defined and bounded by the delegation of authority matrix rather than by an independent board mandate.

Officer appointment documentation must be maintained at each subsidiary. State LLC acts and corporation statutes require that officer appointments be authorized by the governing body, that they be reflected in the entity's records, and in some states that they be filed with the state. A roll-up that closes multiple acquisitions in a compressed timeline may have subsidiary officer appointments that are informally implemented but never formally documented. This gap creates problems in real estate transactions, banking relationships, regulatory filings, and contract execution where the counterparty requires a certified copy of officer authorization. A comprehensive governance review at each subsidiary shortly after closing is more efficient than locating and correcting authorization gaps under time pressure during a subsequent transaction.

Single-Entity vs. Multi-Entity Operating Model

The foundational structural decision for any roll-up is whether acquired businesses will be maintained as separate legal entities under a common holdco or merged into a single operating entity. This decision affects liability exposure, state tax obligations, contract consent requirements, license portability, qualified plan structure, and the complexity of the accounting and reporting infrastructure. It is also a decision that is easier to make correctly before the first acquisition than to reverse after multiple businesses have been acquired.

The single-entity model concentrates all operations, assets, employees, and liabilities into one legal entity, typically the holdco or a single operating subsidiary. Accounting is simpler because there are no intercompany eliminations. Financial reporting is straightforward because there is only one entity's financials to consolidate. Qualified plan administration is cleaner because all employees are employed by a single entity. The cost of entity maintenance, registered agent fees, state filing fees, and the administrative overhead of separate books is eliminated. The tradeoff is liability concentration: a tort claim, regulatory action, or contract breach at one acquired location is a claim against the single entity that holds all assets.

The multi-entity model preserves a liability firewall between subsidiaries and limits the exposure any single operating unit's problems create for the broader platform. It also preserves existing contracts, licenses, and permits in their original entity, avoiding the consent and assignment process that a merger into the holdco would trigger. State professional licensing boards for industries such as healthcare, insurance, and financial services frequently license the entity rather than its ultimate owner, meaning a merger may require a new license application rather than a simple ownership change notification. The cost of the multi-entity model is ongoing: separate books, separate tax filings in each state where each entity operates, intercompany agreements, and the accounting complexity of consolidation with intercompany eliminations.

Shared Services Agreement Design

In a multi-entity roll-up, functions that are most efficiently provided centrally are typically organized at the holdco or a dedicated shared services entity and delivered to the operating subsidiaries under a formal shared services agreement. The functions most commonly centralized in a roll-up context include accounting and financial reporting, human resources administration and benefits management, information technology infrastructure and cybersecurity, legal services and contract review, and procurement and vendor management. Each function's centralization decision is independent, and platforms frequently centralize back-office functions while leaving operational functions at the subsidiary level.

The shared services agreement is the written contract governing the relationship between the holdco or shared services entity and each operating subsidiary. It specifies the scope of services provided, the service levels applicable to each function, the pricing methodology for the services, the billing and payment terms for intercompany charges, the process for adding or removing services as the subsidiary's needs change, and the dispute resolution mechanism for intercompany billing disagreements. A shared services agreement that is silent on service levels creates no enforceable standard for service quality. One that is silent on billing and payment terms creates cash flow conflicts between the shared services provider and the subsidiary that need cash to fund operations.

Accounting services provided centrally typically include accounts payable processing, payroll administration, monthly close and financial statement preparation, accounts receivable management, and external audit coordination. HR services commonly include recruiting process administration, benefits enrollment and administration, employee relations guidance and documentation, and compliance with federal and state employment law requirements. IT services may include network infrastructure, endpoint device management, software licensing, and cybersecurity monitoring. Legal services at the shared services level typically cover contract review below a defined complexity threshold, compliance calendar management, and coordination with external counsel. Procurement covers vendor selection process, contract negotiation coordination, and consolidated purchasing where volume discounts are available across the platform.

Intercompany Services Pricing and Transfer Pricing

Intercompany pricing for shared services must satisfy two distinct sets of rules that operate independently. For federal and state income tax purposes, transactions between related parties must be priced at arm's length under IRC Section 482 and analogous state provisions. For lender purposes, intercompany charges that reduce subsidiary-level EBITDA affect the subsidiary's ability to comply with financial covenants that are measured at the subsidiary level, and lenders frequently negotiate restrictions on the magnitude of intercompany charges as part of the credit agreement. For minority investor purposes, if any subsidiary has equity holders other than the holdco, intercompany charges that transfer value to the holdco may implicate fiduciary duty analysis.

The arm's-length standard for shared services is most commonly applied through the cost-plus method: the shared services provider identifies its fully loaded cost of providing each service category, including direct labor, overhead allocation, and technology costs, and applies a markup that reflects what an independent service provider would charge for comparable services. The markup range for routine administrative services such as accounting and HR administration is typically modest. More specialized services with fewer comparable market providers may support a higher markup. The allocation of costs across subsidiaries should follow a rational driver: headcount is a reasonable driver for HR services, transaction volume for accounting services, and device count for IT services. A platform that allocates all shared services costs equally regardless of subsidiary size creates cross-subsidies that distort subsidiary-level financial performance and create conflicts among subsidiary managers.

The shared services agreement should specify whether intercompany charges are billed monthly or quarterly, when payment is due, whether unpaid intercompany balances accrue interest, and how disputes over charges are resolved. Intercompany balances that accumulate without a structured repayment cadence become balance sheet items that complicate lender covenant calculations, tax analysis, and any subsidiary-level debt or equity transaction. Some credit agreements require that intercompany loans or advances be subordinated to senior debt, requiring specific documentation of the terms on which holdco advances to subsidiaries are made and repaid.

ERP and Billing System Consolidation Timing

ERP consolidation is among the most consequential and most frequently underestimated integration tasks in a roll-up. A platform that acquires businesses using different accounting systems, different chart of accounts structures, and different billing and invoicing platforms cannot produce timely consolidated financial statements, cannot efficiently provide lender reporting, and cannot efficiently compare financial performance across subsidiaries. The operational case for ERP consolidation is clear. The difficulty is that migrations are disruptive and the cost of a poorly executed migration, including billing errors, lost receivables, and delayed financial closes, can exceed the cost of maintaining parallel systems for a longer transition period.

The sequencing decision for ERP migration involves balancing consolidation speed against operational risk. A platform that migrates each acquired subsidiary to its standard ERP within the first 30 to 60 days after closing captures the consolidation benefit earliest but also integrates during the period when the newly acquired management team is most distracted by other integration tasks and least familiar with the platform's standard processes. A platform that defers migration to 90 to 180 days after closing allows more time for the subsidiary management team to stabilize under new ownership but runs parallel systems for longer and delays the financial reporting efficiency benefits.

Billing system consolidation carries additional complexity in service businesses where customer invoicing is deeply embedded in operational workflows. A service business that invoices customers based on time and materials tracked in a field management system, or a recurring revenue business where billing is integrated with CRM, may require a more extensive parallel-running period than a business with simple product-based invoicing. The integration playbook should specify whether billing system migration occurs concurrently with ERP migration or on a separate track, who owns each workstream, and what customer communication is required before invoicing transitions to the platform's standard system.

Delegation of Authority Matrix

A delegation of authority matrix is the operational document that translates the holdco's governance authority into actionable decision rights for each level of the management hierarchy. Without a written matrix, subsidiary CEOs make decisions based on their prior experience, which may reflect a much larger or smaller organization's approval culture. Holdco management either over-involves itself in routine subsidiary decisions, creating bottlenecks, or under-involves itself in material decisions, creating risk. The matrix is the mechanism that calibrates authority to the right level for each category of decision.

Capital expenditure authority is typically tiered by dollar amount. Routine maintenance capital, where a subsidiary CEO approves expenditures up to a defined threshold, reflects the operational reality that minor equipment repair and replacement decisions should not require holdco involvement. Growth capital, where larger expenditures or multi-year commitments require holdco CFO or CEO countersignature, reflects the investment thesis-level relevance of those decisions. Major capital commitments, above a threshold that the holdco board has defined as requiring board approval, reflect that the decision involves capital allocation at a scale that bears on investor returns.

Hiring authority is typically tiered by role level and total annual compensation. A subsidiary CEO may hire operational staff unilaterally up to a compensation threshold, require holdco HR review for managerial hires above a pay grade, and require holdco CEO involvement for senior leadership appointments. Contract execution authority is commonly tiered by total contract value and commitment term, with attention to evergreen or auto-renewal provisions that create long-term obligations. The matrix should address whether a subsidiary CEO may sign a contract that commits the subsidiary to multi-year obligations at a value below the approval threshold, since the present value of a five-year commitment may be material even if the annual payment is not. Debt and credit facility usage is typically restricted to holdco-approved facilities, with any subsidiary-level borrowing outside an approved facility requiring holdco board consent regardless of amount.

Chart of Accounts Harmonization

Consolidated financial reporting across a multi-entity roll-up requires that all subsidiaries use a common chart of accounts, or that the platform maintains a reliable mapping from each subsidiary's legacy account structure to the consolidated chart. Chart of accounts harmonization is the process of migrating each acquired subsidiary from whatever account structure it used under prior ownership to the platform's standard account structure. The goal is comparability: the ability to look at revenue, gross margin, EBITDA, and capital expenditure line items across subsidiaries on the same definitional basis.

The platform's standard chart of accounts should be designed before the first acquisition closes with the consolidation function in mind. This means including account codes for intercompany eliminations, holdco allocations, and integration costs as distinct line items rather than commingling them with operating accounts. EBITDA addbacks that the platform expects to use in lender reporting, such as one-time integration costs, transaction costs, and non-recurring items, are most defensible when they correspond to specific account codes rather than requiring the CFO to reconstruct them from narrative descriptions at each reporting period.

The harmonization process for each acquired subsidiary requires a mapping exercise between the subsidiary's legacy accounts and the platform's standard accounts, a conversion of historical financials to the platform's account structure for the current and prior year, and a transition of the accounting system to the new chart effective from a defined date, typically the beginning of the next fiscal month after acquisition. The accountant or controller responsible for the subsidiary must be trained on the platform's account structure before the conversion date. Conversions that are performed without adequate training of the subsidiary accounting team produce miscoded transactions that require correction during the subsequent month-end close, consuming CFO and controller time at the expense of forward-looking financial management.

Financial Reporting Package Design for Lender and Investor Compliance

The financial reporting package is the structured set of financial statements and supplemental schedules delivered to lenders and equity investors on the schedule defined in the credit agreement and operating agreement. Its design is constrained by contractual obligations: the credit agreement specifies what must be included, when it must be delivered, what level of review or certification it requires, and what definitions govern the financial metrics reported. The operating agreement specifies investor reporting obligations. Designing the package to satisfy both sets of contractual requirements while also being useful to internal management is an exercise in format discipline that is easier to accomplish when the platform's accounting infrastructure is built to produce the right outputs from the start.

Lender-required reporting typically includes monthly or quarterly consolidated financial statements, a compliance certificate signed by a financial officer certifying that the borrower is in compliance with all financial covenants and providing the covenant calculation for each ratio, and notice of any material adverse developments or events of default. The covenant calculation worksheet is often the most labor-intensive component because the financial definitions in the credit agreement, particularly the definition of EBITDA and permitted addbacks, may not correspond directly to any line item in the accounting system. A platform that builds its chart of accounts and reporting template to produce the credit agreement EBITDA definition directly, rather than requiring a manual reconstruction at each reporting period, significantly reduces the risk of reporting error.

Investor reporting obligations are typically less prescriptive in format but more substantive in analytical content. Equity investors want to understand not just the financial results but the operating drivers behind them: where the platform is outperforming the acquisition thesis and where it is not, what integration milestones have been achieved, and what the forward outlook suggests about the timeline to exit. A reporting package designed around these analytical needs, rather than around the minimum contractual obligations, builds investor confidence and reduces the volume of ad hoc information requests between formal reporting cycles.

Compliance Program Consolidation

Each acquired business operates under a compliance framework shaped by its industry, state of operation, workforce size, and the diligence of its prior management. A roll-up that acquires businesses across multiple states or industries inherits a portfolio of compliance postures ranging from disciplined to informal. Compliance program consolidation is the process of assessing the inherited compliance frameworks, identifying gaps, and implementing platform-level policies and procedures that bring all subsidiaries to a consistent standard.

Employment law compliance is typically the highest-urgency consolidation task because violations create individual and collective liability that accrues daily. The platform's employment law compliance review for each acquired business covers: whether offer letters and employment agreements are legally compliant in the subsidiary's operating states, whether the employee handbook is current with applicable state law requirements, whether overtime and wage classification practices are defensible under the Fair Labor Standards Act and state equivalents, whether required workplace postings are current, and whether I-9 documentation for all employees is complete and properly maintained. A subsidiary that has operated informally on employment practices creates inherited liability that the platform assumes at closing without indemnification protection if the representation and warranty coverage does not extend to wage and hour claims.

Safety compliance consolidation applies to any acquired business with physical operations, field workforce, or regulated materials. OSHA compliance obligations, state plan equivalent requirements, and industry-specific safety standards such as DOT regulations for transportation businesses must be assessed at each subsidiary and elevated to platform-level policy where the standard should be uniform. Privacy compliance consolidation addresses state consumer privacy laws, HIPAA where applicable, and data security practices. A platform operating subsidiaries across multiple states must navigate the differing privacy law requirements of California, Virginia, Texas, and other states with enacted consumer privacy frameworks, and cannot assume that a policy compliant in one state satisfies all others.

Employee Benefits Plan Harmonization

Benefits plan harmonization in a multi-entity roll-up is complex primarily because of the controlled group rules under IRC Section 414 and the specific plan qualification requirements those rules impose. When the holdco and its subsidiaries form a controlled group under Section 414(b) or (c), generally when common ownership exceeds 80 percent measured by vote and value for corporations or a facts-and-circumstances test for other entities, all employees of all controlled group members are treated as employed by a single employer for purposes of the qualified retirement plan coverage and nondiscrimination tests, the health plan affordability and coverage requirements under the Affordable Care Act, and the FMLA employee count threshold.

The most immediate practical consequence of controlled group status for a roll-up concerns qualified retirement plans. Each acquired business that maintains a 401(k) plan is subject to the IRC Section 410(b) minimum coverage test, which requires that the plan cover a sufficient percentage of the non-highly-compensated employees of the single employer, meaning all controlled group members. If the platform has subsidiaries with different 401(k) plan designs, some covering all employees and others covering only certain employee classes, the combined coverage across the controlled group may not satisfy Section 410(b). The correction options are plan amendment to expand coverage, plan merger to consolidate into a single platform plan, or reliance on available transition relief periods under the treasury regulations applicable to acquisitions.

Single-employer versus multi-employer plan status is a separate but related issue for businesses that have participated in union-negotiated defined benefit pension plans. A business that is party to a collective bargaining agreement requiring contributions to a multi-employer pension plan brings ongoing contribution obligations and, potentially, withdrawal liability exposure to the platform. Withdrawal liability is calculated under a formula that attributes a share of the plan's underfunding to the withdrawing employer, and it is triggered by a reduction in contributions below a statutory threshold or a complete withdrawal from the plan. A roll-up that acquires a business with multi-employer plan exposure and then reorganizes operations in a way that reduces covered employment must analyze whether the reorganization triggers withdrawal liability before implementing it.

Brand and Trademark Management Across Entities

Brand strategy in a multi-entity roll-up sits at the intersection of trademark law, customer relationship management, and platform value creation. The acquired businesses' trade names and trademarks are assets that the holdco acquires at closing, but the decision about how to use those assets going forward involves more than legal mechanics. Customers who chose the acquired business based on a local brand, a founder's reputation, or a community presence may respond poorly to an abrupt transition to an unfamiliar platform brand. The brand transition strategy must be designed with an understanding of where the acquired customer loyalty actually lives.

Trademark ownership consolidation is a threshold legal task. The holdco should take assignment of all trade name registrations, federal and state trademark registrations, domain names, and social media handles associated with the acquired business as part of the acquisition closing. These assignments should be recorded with the USPTO for federal trademarks and with the relevant state offices for state registrations. A subsidiary that continues to use a trade name or trademark without a formal license from the holdco that owns the mark creates a usage rights gap that would need to be resolved in any subsequent transaction, including a sale of the subsidiary.

The platform's operating license for each subsidiary to use the acquired trade name under the holdco's ownership should be a written trademark license agreement specifying the licensed marks, the territory of the license, the quality control standards the holdco imposes on the use of the mark, and the circumstances under which the license terminates. Quality control provisions in a trademark license are legally required to maintain the validity of the mark: a licensor that does not exercise quality control over a licensee's use of its mark risks "naked license" invalidity, which can destroy the mark's enforceability against third-party infringers. The quality control requirement is satisfied by meaningful supervision of how the mark is used, not simply by including a quality control clause in the agreement without the corresponding oversight.

Litigation and Risk Management Coordination

A multi-entity roll-up accumulates litigation and contingent liability from each acquired business alongside the operating assets. Pre-closing litigation disclosed in the acquisition due diligence is addressed through representations and warranties, indemnification provisions, and, where the exposure is significant, escrow or holdback arrangements. Post-closing litigation that arises from pre-closing operations is typically subject to the seller's indemnification obligation under the purchase agreement, but enforcing that obligation requires timely notice, documentation of the claim, and, in some cases, litigation against the prior owner. Post-closing litigation arising from post-closing operations is the platform's own liability, managed through the platform's insurance program and risk management function.

Risk management coordination across subsidiaries requires a platform-level insurance program that provides consistent coverage across all entities. Commercial general liability, umbrella, workers' compensation, directors and officers liability, and employment practices liability are the core coverage lines that should be evaluated on a consolidated basis. A platform with subsidiaries in multiple industries may require industry-specific coverage lines for some subsidiaries, such as professional liability for healthcare or financial services businesses. The platform's insurance broker should review coverage annually to ensure that newly acquired subsidiaries are added to the consolidated program and that coverage limits remain appropriate for the platform's scale.

Claims management coordination involves a defined process for subsidiaries to report potential claims or incidents to holdco management, a centralized relationship with defense counsel for claims that exceed subsidiary-level authority, and a reporting cadence that keeps the holdco board informed of litigation exposure relevant to the platform's financial position. The holdco's audit committee, if one exists, typically receives periodic updates on material litigation and contingent liabilities as part of its financial oversight function. The credit agreement may also require the borrower to notify the lender of claims above a defined threshold.

Debt Covenant Tracking and Reporting

Debt covenant compliance is a continuous obligation that requires a structured tracking infrastructure, not a periodic accounting exercise. A roll-up with a senior credit facility typically operates under financial covenants that include a maximum total leverage ratio measured as total funded debt divided by trailing twelve-month EBITDA, a minimum fixed charge coverage ratio measured as EBITDA minus capital expenditures divided by total debt service including interest and required amortization, and a minimum liquidity requirement measured as unrestricted cash plus revolver availability. Each covenant uses financial definitions specified in the credit agreement that may differ meaningfully from GAAP definitions, and each covenant is tested on a schedule, typically quarterly, with the compliance certificate due within a defined number of days after the end of the fiscal quarter.

A platform managing multiple credit facilities, including a holdco senior facility, subsidiary-level seller notes, and equipment financing, must track each facility's covenant package independently because financial definitions, measurement periods, and reporting obligations differ across facilities. A covenant calendar that maps all facilities, their testing dates, their reporting deadlines, the financial definitions used in each calculation, the current actual versus covenant threshold, and the projected trajectory should be maintained by the CFO function and reviewed at each management team meeting. Covenant headroom analysis, which models how the covenant ratios change under downside scenarios or as additional acquisition debt is incurred, is a forward-looking input into acquisition pacing and add-on financing decisions.

When a covenant is at risk of breach, the platform's options include a waiver from the lender, a covenant reset negotiated in connection with an amendment, an equity cure where the credit agreement permits additional equity contributions to be added to EBITDA for covenant testing purposes, or an accelerated operational improvement to bring the financial metrics back within compliance before the next testing date. All of these options are significantly easier to execute when the platform identifies the at-risk covenant and engages the lender proactively, before the breach date. Lenders who discover covenant breaches through their own monitoring rather than through borrower disclosure treat the resulting waiver and amendment process as a much higher-stakes negotiation.

Investor Reporting Cadence

Investor reporting obligations for equity holders in a roll-up holdco are typically less prescriptive in format than lender reporting obligations but more consequential for the platform's relationship with its capital partners. Equity investors who receive consistent, informative reporting are more likely to support add-on acquisition capital needs, provide introductions to potential acquisition targets, contribute operational expertise when subsidiaries encounter challenges, and maintain reasonable expectations about return timing and exit process. Investors who receive irregular or opaque reporting develop their own interpretations of platform performance that may be less favorable than the actual results warrant.

Monthly reporting to equity investors typically covers consolidated financials for the prior month with comparison to the same period in the prior year and to the annual operating budget, a cash position and liquidity update, and a brief narrative from the platform CEO covering the most significant operational developments, integration milestones, and any material items requiring investor awareness. The monthly package is a monitoring tool rather than a strategic communication: it should be delivered on a consistent schedule and in a consistent format so that investors can assess trends rather than spending time on format differences from month to month.

Quarterly reporting is the appropriate cadence for strategic communication. The quarterly investor letter, delivered within 45 days after each fiscal quarter, should provide a subsidiary-level financial breakdown, an update on the platform's acquisition pipeline and integration status, a KPI dashboard that tracks the operating metrics most relevant to the investment thesis, a forward-looking view on the next quarter's expected performance, and any material developments in the competitive environment, regulatory landscape, or operational situation that investors should understand. Annual reporting includes audited consolidated financial statements, a full variance analysis against the acquisition thesis, and an updated assessment of the path to exit including valuation benchmarks and comparable transaction activity.

30/60/90-Day Integration Playbook for Each Add-On

A playbook-driven integration approach converts the institutional knowledge from prior acquisitions into repeatable process. Platforms that integrate their first several acquisitions ad hoc, with each integration team reinventing the approach, accumulate integration debt: uncompleted tasks from prior acquisitions that consume management attention during subsequent ones. A written playbook with defined owners, deadlines, and completion criteria eliminates the reinvention problem and makes integration velocity a predictable function of the platform's operational capacity.

The first 30 days after closing focus on legal and financial control. The tasks in this phase include: transferring bank accounts and payment processors to the platform's banking relationships, updating entity governance documents to reflect the new ownership structure, obtaining new insurance certificates naming the holdco as additional insured, verifying that the delegation of authority matrix has been communicated to the acquired management team, completing the I-9 audit for all employees, initiating the chart of accounts mapping exercise, and migrating payroll to the platform's payroll provider. These are not optional tasks: each represents a control failure that compounds the longer it remains unresolved. Day-30 completion of this phase is a realistic target for a platform with a practiced integration team and should be a hard deadline in the playbook.

Days 31 through 60 focus on operational integration. The tasks in this phase include: completing ERP migration initiation or establishing a parallel-running timeline with a defined migration date, onboarding the subsidiary's management team to the shared services platform for accounting, HR, and IT, completing the employment law compliance review and issuing updated offer letters or handbook acknowledgments where required, initiating the 401(k) plan controlled group analysis with the platform's benefits counsel, implementing the brand license agreement and trademark assignment documentation, and delivering the first monthly financial reporting package that includes the new subsidiary. This phase is where the most friction typically occurs, because it requires the acquired management team to adopt new tools and processes while continuing to manage their operational business.

Days 61 through 90 complete the foundational integration. The tasks in this phase include: completing the chart of accounts conversion and reconciling the first full month of financial activity under the platform's account structure, finalizing the benefits plan harmonization decision and enrolling employees in the appropriate platform plan, completing the shared services agreement execution, delivering the first consolidated financial reporting package to lenders that includes the new subsidiary's results, completing any remaining compliance program gap remediation, and conducting a 90-day integration review with the platform's management team to identify any unresolved issues and assign responsibility for their resolution. The 90-day review should be a structured document, not an informal conversation, so that the lessons from each integration inform the playbook update for the next acquisition.

Frequently Asked Questions