Revenue vs. budget, EBITDA margin trends, KPI movement, thesis compliance, and governance exceptions require a structured analytical layer maintained separately from deal execution. Basis tracks every portfolio company against plan, flags deviations with analyst rationale, and delivers the oversight view your team needs — each cycle, aligned to your reporting calendar.
Every dimension that matters between deal close and exit — tracked on a managed monthly cycle, flagged when it moves, and reported in a format your team can act on.
Internal monitoring depends on people with competing priorities. Basis maintains consistent coverage regardless of deal flow, team changes, or quarter-end pressure.
| Area | In-house / deal team | Basis Partners |
|---|---|---|
| Performance tracking | —Reviewed at board meetings and annual fund reviews. Variances accumulate between meetings without structured inter-period tracking. | ✓Monthly performance tracking per company. Revenue, EBITDA, and KPI variance flagged with analyst commentary each cycle. |
| Thesis compliance | —Documented at entry, rarely tested against current data in structured form. Drift surfaces at exit or LP questions — not at the point where action is still possible. | ✓Original thesis assumptions reviewed each cycle against current company data. Divergence flagged with analyst rationale before it compounds. |
| Coverage consistency | —Varies with deal flow, portfolio size, staff turnover, and capacity. The companies generating least noise are typically the least monitored — until they become a problem. | ✓Consistent monthly coverage across the full selected cohort. Coverage does not vary with internal pressure, absences, or competing transaction activity. |
| Management risk | —Noted when changes occur. No structured tracking of key person dependency or team movement as an ongoing risk signal between board meetings. | ✓Monitored each cycle. Key person flags, management team changes, and dependency risks assessed and escalated with rationale. |
| Information rights | —Tracked informally. Late or missing board packs are noted but rarely escalated formally until the relationship warrants it. | ✓Board pack receipt, quality, and information rights compliance logged each cycle. Exceptions flagged as part of the managed governance record. |
| Exceptions register | —Exceptions are handled as they arise. No structured register of what was flagged, what action was taken, and when the issue was resolved or escalated. | ✓Maintained as an ongoing register per company — open items, actions taken, resolution dates, and analyst commentary for each flagged issue. |
A structured view of each portfolio company's position against budget, plan, and agreed KPIs — with variance commentary and trend flags updated each review cycle.
A structured comparison of original investment assumptions against current company data — where the thesis is holding, where it has drifted, and what the divergence implies for the position.
A full record of flagged exceptions across the portfolio — what was identified, when it was raised, what action was taken, and the current status of each open item.
A record of board pack receipt, information rights compliance, management team changes, and open governance items across the portfolio — updated each cycle.
A fund-level summary of the portfolio's position — which companies are performing, which are flagged, and where the most significant risks and opportunities sit across the book.
Concise, structured briefs on each portfolio company — suitable for investment committee reviews, watch-list discussions, and portfolio update meetings.
Start with a focused diagnostic. No commitment beyond the first review.