For Operating Partners
One data foundation pattern across your portfolio, so every company reports the same way and every add-on joins the same numbers.
A standardized, code-defined data platform deployed in each portfolio company: the same structure, access model, and conventions, in accounts each company owns.
After the add-on
The value creation plan waits on spreadsheets.
Every acquired company keeps its own ERP, customer list, and chart of accounts
Monthly reporting to the sponsor is assembled by hand, differently at each company
Margin, inventory, and customer questions across entities take weeks to answer
Portfolio companies rarely have a data team, and big-firm quotes don't fit the budget
What I do
The same foundation in every portfolio company
I build each company's data foundation from the same proven pattern. Reporting becomes comparable across the portfolio, and the next add-on is a few weeks of work, not a new project.
Each company gets its own repository generated from one versioned template: Snowflake provisioned with Terraform, dlt ingestion, dbt models, and role-based access with masking. Improvements to the pattern roll out to every company through template updates.
Data from every entity's ERP and systems in one place, with no ERP migration required
Shared customer, item, and account definitions, so numbers agree across entities
Access controls on payroll, pricing, and margin, with an audit trail
Documentation and a runbook, so the company is never dependent on one person
How it works
Start with one company, then repeat
- Assessment (1 to 2 weeks, fixed fee): for the platform company, a clear plan covering systems, entities, and what the sponsor needs to see.
- Foundation Build (typically 4 to 8 weeks, fixed price): the data foundation, built and handed over.
- Add-on onboarding (fixed price per add-on): each new company's systems mapped into the shared definitions.
- Fractional Data Engineering Lead (optional, monthly): ongoing ownership for companies without a data team.
No lock-in
What the company keeps
Everything is built in accounts the portfolio company owns and pays for directly, with the code, documentation, and access handed over. That holds up in diligence and at exit: the buyer gets a documented, governed data platform, not a dependency on a consultant.
Accounts in the company's name from day one. Infrastructure as code, version-controlled models with tests, a documented access model, and a runbook. Security posture is built to regulated-industry standards, so it holds up to a buyer's technical diligence.