Capability · Platform delivery
PEPM joins pre-investment, portfolio, post-investment and disclosure into one flow with no manual hand-offs. Approval logic follows your committee rules; nineteen business systems read one data dictionary. At go-live we accept two things: UAT pass rate and a filing rehearsal run on live definitions.
Position
High customisability means one thing here: approval and process flows are adjusted to the client’s rules. How many steps sit between screening and committee, whether a decision can be returned, who may write to a valuation field, whether USD and RMB vehicles follow the same route — your policy decides these, not the edition you bought.
The technical commitment is equally narrow: data moves end to end without breakpoints. Projects, funds, entities, valuations and filings reference each other under one dictionary, so nobody exports three spreadsheets at month end and stitches them together.
An investment platform delivered without a data dictionary degrades into manual reconciliation in its first filing season: the system stores fields, the report needs definitions, and overtime covers the gap. That is why platform delivery is step two, after a signed blueprint.Catalpa delivery method
The inputs are the signed dictionary and swimlane map from the blueprint. Each step produces a reviewable record; we do not let a later step start before the previous one closes.
Field by field we check source and refresh frequency, then turn swimlane nodes into configurable workflow items. Output: configuration list and work-breakdown structure.
Screening, diligence, committee, closing and exit levels, co-signing and return paths are rewritten from your policy. Clients do not adapt to our defaults. Output: workflow baseline.
Visibility is cut by role and by entity; valuation, cost and LP contact fields carry separate read-write rights. Output: role-to-field permission matrix.
Historic projects, funds and entities are de-duplicated against the dictionary; unmappable items go on an exception list for the business to decide. Output: migration scope and per-table reconciliation.
Mobile access through DingTalk, Feishu, WeCom and WeChat; LP and GP portals and the encrypted document service open per disclosure audience under the same permission model. Output: integration list and joint-test log.
The business writes the test cases, we execute them. One consolidated filing is produced with live definitions before cutover, and a parallel period follows. Output: UAT report and rehearsal record.
8–16 weeks is the standard implementation range, counted from agreement of the work-breakdown structure. Multi-line groups are split into phases rather than compressed.
| Artefact | Typical duration | Acceptance method |
|---|---|---|
| Workflow engine: approval, committee, return paths | Within 8–16 weeks | Node-by-node walk-through against policy; baseline signed |
| Legacy migration with per-table reconciliation | Within 8–16 weeks | Opening and closing counts and key amounts agree; exceptions closed |
| Permission matrix (function, row, field) | Within 8–16 weeks | Role sampling plus privilege-escalation cases that must fail |
| Mobile and IM integrations | Within 8–16 weeks | Joint-test log; approvals complete on mobile end to end |
| LP and GP portals, disclosure templates | Within 8–16 weeks | Trial dispatch per audience; LP confirms visibility |
| UAT suite and filing rehearsal | Before go-live | Agreed pass rate plus one live filing produced from the platform |
Hand-over pack
Workflow baseline, migration reconciliation, permission matrix, UAT and rehearsal record. These four are what we re-read at quarterly review, and what you negotiate extension budgets against.
Capability base
The lists follow our published product scope. Every item maps to a configurable node and a set of fields today, not to a roadmap promise.
Pre-investment
The project pool keeps origin and follow-up history; diligence files attach to one entity record, and committee packs read from the same data.
Portfolio
Multi-round dilution is computed rather than retyped; closing data lands straight in the post-investment ledger, with USD-fund cross-border reporting on the same source.
Post-investment
Portfolio and sub-fund indicators update monthly against thresholds; valuation and exit models consume the same post-investment records.
Cross-cutting
Eighteen warning indicators recalculate across the full risk surface, and every trigger and confirmation stays on record.
Cross-cutting
One experience across DingTalk, Feishu, WeCom and WeChat; LP and GP portals sit inside the same permission system.
Cross-cutting
Risk assessment, automated extraction and dedicated agents sit inside existing steps and emit structured, reviewable fields.
The rebrand keeps the PEPM name. Modules open singly or combine into one investment chain, always sharing the same dictionary.
Names follow the published product series on pepm.com.cn. Consolidation and filing scenarios read one dictionary, so definitions stop drifting.
Deployment
Public cloud, private cloud and an isolated intranet change where the software runs, not what it does. Fields, workflows, permissions and filing outlets stay identical, so a move to intranet needs no reconfiguration and no dropped module. On intranet, data leaves no outbound path and operational actions are logged to the standard your locality requires.
Edition fit
Standard covers one business line across the investment chain. Advanced adds fund-of-funds look-through and external disclosure. Professional serves multi-line groups and online supervision. The difference is measured in managed objects, filing outlets and permission tiers, not in interface polish.
Evidence
Post-go-live value is not measured by satisfaction. Our client-impact pages give five anonymised settings and four acceptance definitions — filing cycle, manual-reconciliation hours, definition-consistency rate and alert confirmation rate — signed at blueprint stage and recalculated at acceptance.
Acceptance definitionsAny institution that wants to skip the data dictionary: workflow configuration then makes definitional decisions on your behalf, and the bill arrives in the first filing season. Anyone looking for a licensed service — asset management, fundraising or investment advice: Catalpa supplies software and consulting only, and does not take on duties that require a financial licence.
A single-fund GP under fifteen people, or a standard-edition buyer with no definition maintenance, should also wait.
These answers match our contract terms and acceptance method, so they can go into an approval note unchanged.
Next step
We run your approval levels end to end in front of you, separate what is configurable from what needs the dictionary first, and set out phasing across the 8–16 week range.