Insights
Private equity and portfolios
170 guides · page 3 of 4
Landscaping roll-ups: consolidating Aspire, LMN and crew data
A landscaping roll-up integration sequence for job costing, maintenance contracts and crew data when add-ons run Aspire, LMN, Jobber or spreadsheets.
Legacy data after system consolidation: keep, archive, license or delete?
Legacy data after system consolidation needs one of four outcomes. A decision tree routes each record set by legal hold, retention, rights status and value.
Legacy ERPs from acquired plants: archive, migrate or license?
A decision table for a legacy ERP at an acquired company: when to migrate, archive or license plant records, and the rights checks to run before cutover.
Legal holds on acquired company records: what can still be licensed
A legal hold on acquired company records means preserve, not destroy. What can still be licensed, what stays out, and the checklist counsel signs off on.
Lender consent before licensing company data: what credit agreements say
Lender consent to license intellectual property turns on a handful of credit agreement clauses. See what each says, who to ask and what to send the agent.
License data before an exit or leave it to the buyer?
A decision rule by time to exit for licensing data before selling a company, and what each path does to diligence and to the equity story buyers hear.
Licensing data during a sale process: interim covenants and buyer consent
Licensing data during a sale process depends on timing: what to do before signing, between signing and closing under interim covenants, and after closing.
Light-touch or full integration after a software acquisition: what to standardize
Software acquisition integration: standardize security, retention, AI and data-use policy and legal templates, and leave product, roadmap and support local.
Maintenance-mode software products: what their engineering histories hold
Maintenance mode software keeps its value in engineering history: bug fixes, reviews, releases and support outcomes. What to keep and check before licensing.
Market research roll-ups: does respondent consent transfer to the buyer?
Does respondent consent transfer when a market research firm is acquired? What usually carries over, what does not, and a diligence checklist for panels.
Merging Confluence and Notion knowledge bases after add-ons
Confluence migration after an acquisition often drops page history, comments and links. A checklist for merging Notion and Confluence wikis intact.
Migrating customers from an acquired product onto your platform: data checks
Before you migrate customers from an acquired product to your platform, check contract rights, DPAs, hosting region, notice, field mapping and the archive.
Minority and rollover investor consent for a data license
Minority investor consent rights can block a data license. Where they hide in charters and LLC agreements, which words trigger them, and how to clear them.
Moving acquired shops onto one FSM: what happens to legacy job history
In an acquired company software migration, legacy job history is often left behind. Decide per record family what to migrate, archive or keep before cutover.
New revenue streams for mature portfolio companies: where records fit
New revenue streams for a mature business compared: pricing, services, data products and licensing records, with what each needs and how fast it pays.
Non-core software products: sell, sunset, maintain or license the records?
Divest a non-core software product, sunset it, maintain it, or license its records: what each option does to customers, staff and the product's history.
Non-exclusive licenses in the ordinary course: the credit agreement carve-out
How the non-exclusive license ordinary course carve-out in a credit agreement works, and three tests for whether a data license fits it before you sign.
Normalized EBITDA: are data licensing preparation costs an add-back?
EBITDA add-backs for data licensing costs: which preparation costs a quality of earnings review may accept as one-time, which fail, and what to document.
Old backups and tape archives from acquisitions: retain, restore or destroy?
Backup retention after acquisition starts with a hold check. A decision table for old tapes, server images and database backups: retain, restore or destroy.
Operating partner questions to ask every portfolio CEO about data and AI
Fifteen operating partner questions for portfolio CEOs on data and AI, grouped into records, rights and readiness, with what a good answer sounds like.
Operating partner vs portfolio CEO: who decides on licensing company data?
Who makes the portfolio company data decision: management proposes, the sponsor consents where documents say so, and the board approves above thresholds.
Parent company liability for a subsidiary's data license
When is a holdco on the hook for a subsidiary's data license? How liability stays with the signer, why licensees ask for parent guarantees, and alternatives.
Pooling competitors' records after a roll-up: antitrust limits
Antitrust information exchange rules can limit how a roll-up pools rivals' prices, wages and capacity data. The sensitive categories and handling rules.
Pooling several portfolio companies' records into one license: pros and risks
Pooling data from multiple companies into one license: three deal structures, a pros and risks table, and the approval rule each company keeps.
Portfolio data licensing timeline: from screen to payment
The data licensing timeline for a portfolio company, stage by stage: where sponsor, board and lender gates sit, and what makes a schedule slip.
Portfolio data screen: scoring criteria to rank companies for licensing fit
A portfolio data screen rubric: eight weighted criteria, the metadata each one needs, and how to rank companies for licensing fit without sharing files.
Post-acquisition data inventory checklist
A post-acquisition data inventory checklist for day one, day 30 and day 90: secure each system, map record families and confirm the data rights you inherited.
Post-merger application rationalization: decide what to retire and what to archive
A post-merger application rationalization matrix: retain, migrate, archive or retire each system, plus the vendor deletion windows that set the real deadline.
Prior data-sharing agreements at an acquired company: how to find them
How to find data sharing agreements in due diligence and after close: contract keywords, payment traces, API keys, SFTP feeds and privacy notices to check.
Privacy program baseline across a portfolio before any data license
A privacy compliance baseline for portfolio companies: notices, data maps, vendor DPAs, retention, rights requests, and the gaps that stall a license.
Privacy promises after an acquisition: can the buyer use old data in new ways?
Privacy policy after an acquisition: why old records stay bound by the notice they were collected under, and how to find the notices in force.
Private equity in engineering and architecture firms: data and AI value creation
Which engineering and architecture firm records support AI value creation under private equity, mapped by system, with client-owned drawings kept out.
Private equity value creation in distribution: data and AI levers
Value creation in distribution private equity, lever by lever: pricing, forecasting, order automation and data licensing, plus the data each one needs first.
Processor vs controller: why SaaS vendors cannot license customer personal data
Can a SaaS processor use customer data for its own purposes? Generally not. What a processor may do, and which vendor-owned records fall outside the role.
Product rationalization after software acquisitions: which products to sunset
A software product rationalization scoring matrix: rank acquired products on revenue, margin, overlap, technical risk, contract obligations and record value.
Product sunset checklist for software acquirers
A product sunset checklist for software acquirers, with a data-preservation gate that separates customer data from code, tickets and release history.
Proprietary data as an AI moat: how sponsors test it in diligence
Proprietary data moat due diligence in four questions: unique, connected, rights-clear, refreshable. Plus how to license records without losing the moat.
Records a buy-and-build platform accumulates after a dozen add-ons
Buy and build platform data, function by function: the systems and records a dozen add-ons leave behind, and why linked histories across companies matter.
Recovering value from a failed portfolio company: overlooked records
How to recover value from a failed portfolio company: a checklist by asset type, and why operating records must be exported before subscriptions lapse.
Restoration roll-ups: job files, estimates and claims histories
A restoration company roll-up holds job files, drying logs, estimates and claims histories. See which records each branch wrote and which carry outside terms.
Restoration roll-ups: unifying job files and program data
A restoration roll-up integration sequence for unifying job files, estimates and carrier program data across add-ons, with the program checks to run first.
Roofing roll-ups: estimates, inspections and warranty records
A roofing company roll-up holds leads, inspections, estimates, jobs and warranties. See which carry value and where homeowner and insurer limits apply.
Sell-side AI diligence: answers to prepare before buyers ask
Sell-side AI due diligence for portfolio company CFOs: the five answer folders to build before a buyer's AI questionnaire reaches the data room.
Sell-side data readiness for PE-backed home services platforms
Sell-side data readiness checklist for PE-backed home services platforms: consolidated FSM data, a rights trail per brand, privacy records, licensing history.
Selling your company to private equity: what happens to your data
Selling your company to private equity? What buyers review about your records and rights, what the new owner can do with them, and what to document first.
Slack and Teams workspaces from acquisitions: merge, archive or export?
Slack workspace migration after an acquisition: what merging, archiving and exporting each keep, and the export permissions to check before anything moves.
Software acquisition due diligence: AI and data rights questions to add
Six AI and data rights question groups to add to software acquisition diligence, the document that answers each, and the red flags that change a deal.
Software chain of title: IP checks before licensing an acquired codebase
IP chain of title checks for an acquired codebase: founder and contractor assignments, prior deals, open source and customer-funded code before licensing it.