Skip to content
Discuss your project

Software for investment firms.

Give your investors a polished portal with everything they need, your deal team one pipeline it trusts, and your partners every portfolio company’s numbers in one place, ready for the quarterly report. Quarter-end stops being a scramble, and your team gets back to deals and investors.

Illustration of a portfolio monitoring workflow built by Baybloom for an investment firm: KPI and financial requests to portfolio companies, submissions checked by an analyst, and approved figures carried into fund reporting.

Who this is for

COOs, CFOs, investor relations leads, and operating partners at private equity and growth equity firms, venture capital firms, family offices, and wealth managers and registered investment advisers. The deal team works in a CRM, the fund administrator keeps the books, portfolio companies send results as spreadsheets, and investors ask for documents by email. We build the software between those parts. Hedge funds are not covered here, because trading and order management systems are a different kind of work.

What makes it urgent

  • Quarterly reporting depends on one analyst chasing portfolio company spreadsheets and pasting figures into a template.
  • Limited partners are asking for a portal, and statements still go out as email attachments.
  • A new fund brings more investors, more entities, and more capital calls than the current process can track by hand.

What usually breaks

  • Portfolio companies report the same metric under different names, so every quarter starts with cleanup.
  • The CRM holds relationships and the administrator holds capital accounts, and nothing connects the two.
  • Data room review happens in long email threads, with no record of what was checked and who agreed.

The workflow

Before and after the first release.

The steps we see most often in this kind of operation.

Today
  1. Portfolio dataSpreadsheets emailed by each company
  2. Fund reportingA template rebuilt by hand every quarter
  3. InvestorsStatements and notices sent as attachments
  4. Deal flowCRM records, inbox threads, and data rooms apart
With the first release
  1. Portfolio dataRequests, submissions, and checks in one monitoring workflow
  2. Fund reportingReports built from connected records with figures traced to source
  3. InvestorsA portal limited to the entities and accounts each investor holds
  4. Deal flowPipeline, relationships, and diligence documents linked by deal

What we build

Software we build for investment firms.

Investor and LP portals

Statements, capital account activity, documents, and notices for limited partners, clients, and co-investors, with access limited to the entities and accounts each one holds.

Deal pipeline and relationship CRM

Pipeline stages, relationships, and diligence documents linked by deal, either built around DealCloud, Affinity, or Salesforce or as a CRM shaped to the firm’s process.

Portfolio monitoring

KPIs and financials requested from portfolio companies, checked against agreed definitions and prior periods, and reviewed by an analyst before they are accepted.

Quarterly and fund reporting

Fund and investor reports assembled from connected records, with every figure traced to the submission or administrator report it came from.

Capital call and distribution workflows

Notices prepared from the fund administrator’s calculations, reviewed and approved internally, published to investors, and tracked until each one is settled.

Client onboarding and document collection

For wealth managers and registered investment advisers, onboarding steps and requested documents gathered in one place, with each client’s status visible to the team.

AI review of data rooms and documents

Terms and figures extracted from data rooms, agreements, and reports, linked to their source pages, and approved by a person before anyone relies on them.

Your first release

What the first release could include.

In the first release

  • A record of funds, vehicles, investor entities, and portfolio companies, with the relationships between them agreed once
  • Portfolio monitoring: requests to portfolio companies, a submission form or upload, validation against agreed definitions, and an analyst review queue
  • A connection to the fund administrator’s reports or data feed, so capital account figures are read rather than retyped
  • Roles and permissions for deal, finance, investor relations, and portfolio company users, with every view and export logged
  • One quarterly report assembled from connected records, with each figure traced to its submission

Usually later

  • An investor and LP portal for statements, capital account activity, documents, and notices
  • Capital call and distribution workflows connected to the fund administrator
  • AI review of data rooms and documents, with a person approving every result

Systems it may connect

  • Fund administrators, through their reports, portals, and data feeds
  • Portfolio accounting and investment reporting systems
  • CRMs such as DealCloud, Affinity, and Salesforce
  • Virtual data rooms and document storage
  • Microsoft 365: Outlook, SharePoint, Excel, and Entra ID
  • Custodians, through statements and data feeds

How the work runs

Scoped in writing, built in releases, handed over to your team.

Scope

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.

Build and test

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.

Handover

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

What shapes the scope and price.

Every project is priced from a written scope. These are the factors that move it most.

Funds, vehicles, and entities

Each fund, feeder, co-investment vehicle, and investor entity adds records, access rules, and reporting definitions to design and test.

Administrator and custodian data access

Some administrators and custodians provide data feeds and others only reports or portal exports, which decides how much of the work updates automatically.

Portfolio reporting definitions

Agreeing on metrics and definitions across portfolio companies takes work before monitoring and fund reports can be built on them.

Access and approval design

Permissions across deal teams, investor relations, portfolio companies, and investors, and the approvals before anything is published, need careful design with the compliance team.

Private equity firm with several funds

Portfolio results arrive through one workflow, and the quarterly report is built from them.

At a private equity firm with several funds, quarterly reporting often starts with an analyst emailing every portfolio company for KPIs and financials, then pasting the replies into a template while the fund administrator’s capital account figures are retyped beside them. A first release sends each company a request with the agreed definitions, checks submissions as they arrive, and puts anything unusual in front of an analyst before it is accepted. Capital account figures are read from the administrator’s reports, and the quarterly report is assembled from those records with each figure traced to its source. An investor portal for statements and notices is a natural next phase.

Questions

Questions from investment firms.

What leaders in this industry ask us first.

Does this replace DealCloud, Affinity, or Salesforce?

Usually not. The CRM stays the record for relationships and the deal pipeline. We connect it to portfolio monitoring, fund reporting, and documents, or build the workflow the CRM does not cover. Where a firm has outgrown its CRM, replacing it is scoped as a separate decision.

Do you replace our fund administrator?

No. The fund administrator keeps the books and remains the record for capital accounts. We read its reports, portal exports, or data feeds so the firm’s portals and reports show the administrator’s figures instead of copies typed by hand.

How are regulatory and recordkeeping obligations handled?

Investment firms answer to regulators such as the SEC, and those obligations belong to the firm. Data handling, retention, and access are agreed in writing and designed with the firm’s compliance team before any records are connected. We build to those agreed rules and do not give legal or regulatory advice.

How does AI review of data rooms and documents work?

The software reads documents in a data room or folder, extracts the terms or figures the team asks for, and links each result to the page it came from. A person reviews and approves every result before it is used. Which AI providers may receive documents, and how they are stored, is agreed in writing first.

How do portfolio companies submit their numbers?

Each company receives a request with the metrics and definitions the firm agreed, and submits through a form or a spreadsheet upload. Submissions are checked against those definitions and prior periods, and anything unusual goes to an analyst before it reaches a report.

Where should an investment firm start?

Usually with the work that repeats every quarter by hand, which is often portfolio monitoring or fund reporting. Those records then support an investor portal, because the portal shows figures the firm has already checked.

What happens after the work goes live?

Each release moves into ongoing support with monitoring, fixes, and small changes, and larger additions are scoped as the next phase. Documentation and access records are kept current, so the firm’s operations team or IT provider can run the systems alongside us.

Discuss an investment firm project.

Tell us about the workflow and the systems around it.
We’ll come back with a written scope for a first release.