PE Account Mapping in Your CRM: The Three-Layer Hierarchy

The CRM Problem Nobody Talks About

Your CRM wasn't built for PE partnerships. It was built for direct sales - one account, one opportunity, one close. And when you try to shoehorn PE relationships into that structure, you lose the most valuable thing about PE partnerships: the portfolio context.

Here's what happens: An AE closes a deal at a portfolio company. It goes into the CRM as a standard account. Nobody records that it's PE-backed, who the PE firm is, or which operating partner made the introduction. Six months later, you close another deal at a different portco owned by the same PE firm - and nobody connects the dots.

The relationship intelligence that makes PE partnerships valuable disappears into your CRM like water into sand.

The Three-Layer Hierarchy

You need three layers in your CRM to properly track PE partnerships:

Layer 1: PE Firm (Parent Account)

This is the PE firm itself - Thoma Bravo, Vista Equity, Francisco Partners, or whoever you're working with.

What lives here:

• Firm profile: AUM, fund vintage, investment thesis
• Operating team contacts: Operating partners, portfolio services leads, technology advisors
• Partnership status: Prospecting, Active, Strategic, Inactive
• Program tier: Tier 1 (strategic), Tier 2 (growth), Tier 3 (emerging)
• Portfolio count: Total portcos, ICP-matching portcos, deployed portcos
• Aggregate metrics: Total ARR from this PE firm's portfolio, expansion rate, deployment velocity

Layer 2: Portfolio Company (Child Account)

Each portfolio company is a child account linked to the PE firm parent. Standard opportunity management happens here, but with additional PE context.

What lives here:

• Standard account fields (company info, contacts, opportunities)
• PE parent link: Which PE firm owns this portco
• Acquisition date: When the PE firm acquired this company (important for timing)
• Deployment status: Not started, In progress, Deployed, Expanding
• Source: Partner-sourced (operating partner intro) vs. Direct (closed independently, PE connection discovered later)
• Operating partner sponsor: Who at the PE firm championed this deployment

Layer 3: PE Partnership (Custom Object)

This is the layer most ISVs miss. It tracks the overall partnership - not individual deals, but the program.

What lives here:

• Partnership agreement details: Portfolio pricing, SLAs, co-investment commitments
• Program milestones: Pilot complete, first portfolio rollout, QBR cadence
• Value creation scorecard: Aggregate impact metrics across deployed portcos
• Deployment pipeline: Which portcos are next in the rollout sequence
• Relationship health: NPS from operating partner, engagement frequency, escalation history

Setting Up the Hierarchy

In Salesforce

Parent-Child Accounts: Use the native Account Hierarchy. PE Firm is the parent account, portfolio companies are children. This gives you roll-up reporting out of the box.

Custom Object for PE Partnership: Create a custom object called "PE Partnership" linked to the PE Firm account. Track program-level data here.

Custom Fields on Opportunity:

• PE Source (checkbox): Was this opportunity sourced through the PE relationship?
• PE Influence Type (picklist): Sourced / Influenced / Accelerated
• Operating Partner (lookup): Link to the operating partner contact

In HubSpot

Company Associations: Use parent-child company associations. PE Firm is the parent company, portcos are associated children.

Custom Properties on Company:

• PE Backed (yes/no)
• PE Parent (association)
• PE Deployment Status (picklist)

Deal Properties:

• PE Sourced (yes/no)
• PE Influence Type (picklist)

The Reports You Need

With the three-layer hierarchy in place, build these five reports:

1. PE Portfolio Coverage Report

For each PE firm: total portcos, ICP-matching portcos, deployed portcos, pipeline portcos. This shows your penetration rate and identifies expansion opportunities.

2. PE-Sourced Pipeline Report

All opportunities sourced through PE relationships, grouped by PE firm. Shows pipeline value, stage distribution, and conversion rates compared to direct-sourced.

3. PE Value Creation Dashboard

Aggregate impact metrics across all deployed portcos within a PE portfolio. This is the report the operating partner wants for their board deck.

4. PE Deployment Velocity

Average days from operating partner introduction to signed contract, by PE firm. Identifies which PE relationships close fastest and which need process improvement.

5. PE Program Economics

Fully-loaded cost of the PE program vs. revenue generated, broken down by PE firm tier. This is your budget justification report.

Data Hygiene for PE Accounts

Clean data is non-negotiable. Implement these rules:

At opportunity creation:

• Require PE source designation (Yes/No)
• If Yes, require PE firm lookup and operating partner contact
• Auto-link to parent PE account

At deal close:

• Require PE influence type (Sourced/Influenced/Accelerated/None)
• Log partner activities that contributed to the close
• Update PE Partnership object with deployment status

Monthly reconciliation:

• Cross-reference closed-won deals with PE firm portfolios
• Identify deals at PE-backed companies that weren't tagged
• Update portfolio coverage metrics

The Reporting Cadence

Common Mistakes

Flat structure: Treating portcos as standalone accounts with no PE parent link. You lose all portfolio-level insights.

Missing custom object: Tracking program-level data in notes or spreadsheets instead of a dedicated object. It becomes unmaintainable at scale.

No attribution: Closing deals at PE-backed companies without tagging the PE source. You can't prove program ROI without attribution data.

Over-engineering: Building a 50-field custom object before you have 3 PE partnerships. Start simple, add complexity as the program matures.

The three-layer hierarchy isn't glamorous, but it's the infrastructure that lets you prove PE program ROI, scale beyond your first few partnerships, and give operating partners the reporting they need to keep championing your solution across the portfolio.