Client impact · Market-rate PE

Exit models stop pulling their own numbers

One post-investment team covered RMB and USD funds, and the same portfolio company was recomputed three times a year — once for valuation, once for KPIs, once for an exit case. We changed three things: a standard collection pack, valuation inputs held as versioned records, and one project spine running from deal pool to portfolio to exit.

Client anonymised by defaultDealFlow, portfolio and VDR on one project spine18 configurable risk indicatorsAES-256 at rest · TLS 1.3 in transit

The institution

Two currencies, dozens of deals, one post-investment team

The money is market-raised RMB and USD fund capital. Three lines run through the manager: investment, post-investment and IR, and finance. The structure is manager — fund — deal, with funds in the tens and live portfolio companies in the dozens.

The front end was ahead of most peers: origination, diligence files and investment committee records were already managed. The chain breaks after closing. Financial statements and operating metrics are chased company by company, formats differ, and revenue recognition or a restructuring of the holding chain silently destroys comparability.

The binding constraints come from outside: LPs expect periodic reporting, valuations have to survive audit and the delegated investment committee, and every input in an exit case must trace back to a collection event or a parameter version.

Before the change: one company, three calculations

The table describes how effort was spent and carries no percentages. Effort saved in post-investment and valuation can only be estimated once we have looked at your actual collection and recompute log from the last quarter.

StepWho carried itHow the effort was spentWhy it never closed
Post-investment collectionPost-investment staff, company by companyNon-standard financial statements and KPIs returned repeatedly; history re-keyed after recognition or restructuring changesNo agreed collection pack, so every reporting season re-aligned definitions from scratch
Valuation recomputeHead of post-investment and finance, in separate modelsComparables, discount rates and liquidity discounts held in personal models; recomputed at quarter end and hard to reproduceAssumptions outside the ledger mean nobody second can rerun the same method
KPI alertingRisk, reading reports after the factThresholds with no baseline and no owner; warnings closed only by a manual quarter-end sweepAlerts lived outside the record, so neither false positives nor misses could be counted
Exit modelling and disclosureIR and financeExit cases re-pulled data from scratch; DPI and IRR disagreed with fund accounting; LP pack and internal monthly pack had two sourcesThe origination pool and the portfolio book never shared one project identity

The judgement

Post-investment bottlenecks on evidence, not on analysis

The team is short of defensible inputs, not short of analytical methods. So the delivery weight sits on collection evidence and parameter versions: every number answers "which collection, which parameter version, reviewed by whom".

Valuation judgement stays with the investment committee and the post-investment lead. The system makes that judgement reproducible; it does not make it.

  • Every figure carries its source and evidence
  • Valuation assumptions versioned, never personal
  • An alert closes only with an owner and a conclusion
  • Exit modelling reuses the portfolio ledger

Three steps we took

Standardise the pack, version the inputs, connect the spine

The order matters: step one does not touch the investment committee, step two does not change valuation policy, step three only removes duplicated data pulls.

01 · Collect

A standard post-investment pack

Each company gets one defined metric set and submission template. Statements go through OCR with the original file retained, and machine extraction runs alongside manual review for one cycle. Data vintage and source are stored as fields.

  • Deliverable: metric set and collection template
  • Deliverable: OCR extraction with review log
  • Reviewed by: post-investment lead and finance

02 · Value

Assumptions become versioned records

Method, comparables, discount rate and haircut parameters enter the ledger with an effective version, so a recompute can be reproduced. Risk alerting runs against the 18-indicator definition set, with hits routed into a disposition queue.

  • Deliverable: valuation parameter ledger
  • Deliverable: alert queue with dispositions
  • Reviewed by: risk and the delegated IC authority

03 · One source

A project spine that reaches exit

Deal pool, document repository, portfolio book and exit model share one project identifier. Exit cases read from the portfolio ledger, and the LP pack plus the internal monthly pack generate from the same underlying record.

  • Deliverable: exit-model to portfolio mapping
  • Deliverable: LP report template map
  • Reviewed by: IR and the finance lead

Modules and security base in this scenario

Module names follow PEPM’s published naming. Scope follows the assessment findings; nothing here is a standard-function guarantee.

DealFlow project poolPortfolio managementVDR document repositoryCorporate data collection and reportingLP portalFund-of-funds moduleRisk model judgementFinancial statement OCRFunction / data / field permissionsAES-256 · TLS 1.3DingTalk · Feishu · WeCom

Acceptance measures

All four measures, wording untouched

This engagement uses all four measures published on the client impact index. In the consistency formula the tiers are read here as diligence basis — portfolio ledger — exit model. For the filing cycle, "template issued" is the arrival of the LP data request or report template and "consolidated submission" is delivery of the finalised pack.

How we recomputed them here

MeasureCalculation (as published)Recomputation in this engagementSample and timing
Filing cycleCalendar days from template issued to consolidated group submissionTimestamps from request arrival to final submission, never a mock report; two consecutive cycles in the same format comparedBoth the RMB and USD report sets, including the post-audit annual version
Manual fallback hoursOvertime hours during filing season ÷ people involved, from system-captured effortCounted only for chasing data, re-returns and quarter-end manual recomputes, taken from logged effort rather than recollectionReported per reporting season, kept separate from implementation hours
Definition consistencyShare of identical metrics where the three tiers agree with zero varianceA fixed metric set — revenue, net profit, ownership, cost, latest valuation — compared across the three stages per company; a variance closes only when a collection record or a parameter version explains itSample must include thinly reported private companies, not only the well-documented ones
Alert precision on reviewShare of triggered warnings confirmed as real risk by the businessEach alert stores a disposition owner and a conclusion; confirmed and unconfirmed shares are computed at quarter end, and misses are listed separately so "no false positives" is never read as "no misses"Reported per alert type across two full quarters
A valuation is defensible when a second person can reach it again using the same method.Catalpa delivery methodology

500+

institutions served on the platform (company disclosure, not this manager)

14,000+

funds covered (platform book basis, not one client)

5.6RMB tn+

assets covered (RMB, platform book basis)

60%+

share of engineering staff (company basis)

Where this approach does not apply

An individual angel manager with single-digit live deals and no recurring external disclosure is better served by shared documents plus a valuation assumption sheet; modelling the collection process costs more than it returns. It is also the wrong tool for teams that only raise or broker and hold no lasting valuation duty — every benefit here rests on the same company being computed more than once a year.

Questions specific to post-investment delivery

Mechanism answers. They are not valuation, audit or compliance advice.

Past quarters were valued on a different basis. Do we restate them?
No. The new basis applies from the effective date of the parameter version. Prior quarters keep their original value flagged "not comparable", with a second column recomputed on the new basis purely for trend reading. A number already delivered to LPs is never overwritten in place; it can only be corrected through a restatement trail. Where an auditor requires restatement, the reasoning attaches to that period instead of replacing it.
Portfolio companies will not report, or only publish an annual account. What now?
We tier by data availability instead of forcing one standard. Listed and registered names draw on public disclosure; private companies combine annual accounts with structured interviews, and every metric records its vintage and source tier. Alert thresholds are graded by data freshness so a twelve-month-old figure cannot raise a current-period conclusion. There is no staff-entry feature that fills the gap: a missing period shows as not collected and enters the chasing queue.
How tight do permissions on valuation data need to be?
All three levels at once: function controls who reaches the valuation module, data controls which funds and companies are visible, field controls the assumptions, cost basis and the LP-facing figure. Exports and sensitive operations leave a trace, supported by desktop behaviour monitoring. Cross-team isolation is configured on both the fund and the deal axis, and any exception is granted explicitly and recorded.
How are USD funds and multi-currency handling dealt with?
On the software side we configure the fields, approval requirements and disclosure templates that USD cross-border compliance work needs, and we fix one FX reference date so valuation, contributions and return figures convert on the same day rather than on three. Compliance judgement and filing responsibility stay with the licensed entity; we are the software and data-governance party and do not issue opinions on their behalf.
How does this connect to audit and LP enquiries?
Through one source and attached evidence. Reports generate from the portfolio ledger and its parameter versions instead of being exported from a personal model, and every reported figure drills down to the collection record, the supporting file and the reviewer. Audit periods and LP questions then become filtering and export work rather than recomputation — which is exactly why manual fallback hours is an acceptance measure here.

Next step

Bring last quarter’s valuation workpaper

A 45-minute assessment: we check which inputs have evidence behind them, which assumptions exist only in one personal model, and what the shortest route from standard collection to a shared exit source looks like.