Discuss your projectLimited partners, clients, and co-investors sign in to see statements, capital account activity, documents, and notices, limited to the entities and accounts they hold. Figures come from the fund administrator and the firm’s connected records, and nothing is published until someone at the firm approves it.
Illustration of an investor portal built by Baybloom: a capital call notice prepared from the fund administrator’s figures, statements and documents by fund, and access limited to each investor’s entities.
Investor relations, finance, and operations leads at private equity, growth equity, and venture capital firms, family offices, and wealth managers and registered investment advisers. Investors and clients ask for statements, tax documents, and notices by email, and each answer means finding the right file and checking who may receive it. The portal puts those answers on a screen, with access set by entity and account and approval before anything is published.
The workflow
The steps we see most often in this kind of operation.
Features
Commitments, contributions, distributions, and balances by fund and entity, read from the fund administrator rather than retyped.
Quarterly reports, statements, tax documents, and agreements organized by fund and entity, with each document visible only to the contacts permitted to see it.
Notices prepared from the administrator’s calculations, approved internally, published to the right contacts, and tracked as viewed and acknowledged.
Investor entities, their contacts, and signatories in one record, so access follows the entity rather than a distribution list kept by hand.
Documents and notices staged, reviewed, and approved inside the firm before investors can see them, with each approval recorded.
Onboarding steps and requested documents for wealth management and advisory clients, with each client’s status visible to the team.
Your first release
How the work runs
We start with the people doing the work and the systems around it, then write down the first release: what it includes, what it leaves for later, the integration decisions, and the acceptance criteria. Nothing is built until that scope is agreed.
We build in releases you can review as the work takes shape, using realistic data. Every release carries tests, a security review, and documentation. Integrations are tested against real records, with exceptions visible.
Your team receives the documentation, the runbooks, and the training to run the system, and we stay on for continued engineering when you want it.
Scope and price
Every project is priced from a written scope. These are the factors that move it most.
Each fund, feeder, and co-investment vehicle, and each investor entity with several contacts, adds access rules and documents to set up and test.
Data feeds update the portal automatically, while reports or portal exports need import and checking steps, and several administrators multiply that work.
How many people review a document or notice, and which categories need sign-off, shapes the publishing workflow and its testing.
Viewing documents is the smallest scope; acknowledgments, onboarding, subscriptions, and e-signature each add workflows and integrations.
Private equity firm with several funds
At a private equity firm with several funds, quarterly statements often go out as attachments from investor relations, with distribution lists maintained by hand and capital call notices sent the same way. A first release records each investor entity, its contacts, and what each contact may see, reads statements and capital account activity from the fund administrator, and publishes documents by fund and entity once someone at the firm approves them. Investors sign in to a library limited to their entities, and every view and download is logged. Capital call notices with acknowledgment tracking are a natural next step.
Questions
What buyers ask before a project like this starts.
Sometimes the administrator’s portal is enough. A firm builds a portal when it wants capital accounts beside its letters, reports, and notices, one sign-in across funds and administrators, or access and approval rules the administrator’s portal does not support.
Access is set by investor entity and account and checked on the server for every page, search, and download. A contact who represents several entities sees each of them and nothing else, and changes to access are recorded.
Capital account balances and activity come from the fund administrator’s reports or data feed, and other figures come from the firm’s connected records. The portal shows those records; it does not calculate capital accounts itself.
Data handling, retention, and access are agreed in writing and designed with the firm’s compliance team. The portal keeps a log of what was published, who approved it, and who viewed it, and we build to the rules the firm agrees rather than offering legal or regulatory advice.
Yes. For advisers, the portal usually starts with onboarding and document collection, then adds statements and reports drawn from the custodian and the firm’s portfolio accounting system, with each client seeing only their accounts.
Investors sign in through an identity provider with multi-factor authentication, set up as agreed with the firm, and staff sign in with the firm’s Microsoft 365 or other identity provider. Accounts for departing contacts can be closed by investor relations without engineering help.
The portal moves into ongoing support with monitoring, fixes, and small changes, and additions such as capital call notices or onboarding are scoped as next phases. Access rules and documentation are kept current alongside the firm’s compliance team.