Skip to content

What it looks like from the portfolio.

Four problems most roll-ups share, whatever the sector.

  1. 01

    Every add-on runs a different CRM.

    One company on a legacy CRM, another on spreadsheets, a third on its own HubSpot portal. No two define a stage the same way.

  2. 02

    I can't see the whole pipeline without a week of exports.

    Portfolio reporting is a manual roll-up, out of date the day it lands.

  3. 03

    We share customers and don't know it.

    The same account sits in three systems under three spellings, so cross-sell and concentration risk stay invisible.

  4. 04

    Integration keeps slipping behind the next deal.

    Each acquisition restarts the same project, and the deal team has already moved on.

What we build.

A common model first, then the feeds into it, then the agents that keep it clean.

01 / 03

Data model

  • Portfolio company

    Each operating company as its own record, with its source system, close date and the team that runs it.

  • Shared customer accounts

    One account per real customer, associated with every portfolio company that sells to it.

  • Common pipeline

    One stage definition with exit criteria, mapped from each company's own stages so history still reads.

02 / 03

Integrations

  • Source-system feeds

    Scheduled syncs from each company's CRM or spreadsheets into the common model, until that company is migrated.

  • Finance and ERP feeds

    Bookings, invoices and revenue by company, joined to the same customer accounts.

  • Roll-up reporting

    Portfolio pipeline, revenue and customer concentration from one data set, in HubSpot or a database behind it.

03 / 03

Agents

  • Onboarding profiler

    Profiles a newly acquired company's CRM: objects, fields, record counts, duplicates and gaps, before the migration plan is written.

  • Cross-portfolio matcher

    Finds the same customer across companies and queues likely matches for a person to confirm.

  • Portfolio digest

    A weekly summary per company and in total, with the deals that moved and the ones that stalled.

FIG. 01PORTFOLIO DATA MODEL06:00 CTSample HubSpot data model for a roll-up: fund, portfolio companies, shared customer accounts, contacts, deals, source records and revenue lines.

Three workflows we start with.

Each one replaces a recurring manual job at the portfolio level.

  1. Workflow 01

    New acquisition onboarding

    TriggerPortfolio company record created

    1. Connect the company's CRM or spreadsheets, read-only
    2. Profile objects, fields, record counts and duplicates
    3. Map its stages to the common pipeline
    4. Start a nightly sync into the portfolio model

    ResultA profiled, mapped company in roll-up reporting before its migration starts.

  2. Workflow 02

    Cross-portfolio match

    TriggerA new account syncs from any company

    1. Normalize the name, domain and address
    2. Match against accounts from every other company
    3. Queue likely matches for review
    4. Associate confirmed matches with one shared account

    ResultShared customers visible across the portfolio.

  3. Workflow 03

    Monday portfolio roll-up

    TriggerEvery Monday, 06:00

    1. Recompute pipeline by company and stage
    2. Compare with last week
    3. Draft the summary with the deals that moved
    4. Send it to the operating partners

    ResultThe weekly roll-up without the weekly export.

Blueprint

How we build it.

A blueprint for a roll-up's portal, assembled from components that already run in production.

  • Scheduled loads that are proved against live data before they publish
  • Verified webhooks and idempotent writes, so a retry never duplicates a record
  • Merge plans reviewed before anything merges
  • Agents and workflow actions that work from the record, with a person approving what matters
Read how those components were built in the field notes.Read the field notes

Figures show illustrative sample data. Names, companies and values in them are invented.

Bring the next acquisition.

Show us the CRMs and spreadsheets you're inheriting. We'll map them to one model with you.