Custom software & automation case study
TidalCap is a role-aware investor operations portal with separate experiences for investors, account representatives, and administrators over one shared fund, series, holdings, ownership, document, and reporting model.
Project facts
The challenge
Investment operations do not fit neatly into a generic dashboard. Investors need a clear view of only their own funds, series, holdings, performance, and documents. Representatives need a cross-client view, but only for the relationships assigned to them. Administrators need control over onboarding, assignments, investments, funds, holdings, documents, reporting, and corrections.
The system had to model the operation itself, not just display a few tables. Fund structures, series participation, investor ownership, document access, representative assignments, and reporting outputs all needed to agree with each other across separate user experiences.
The solution
BlueSail modeled the operation directly. Funds contain series. Series connect to underlying holdings. Investor commitments connect clients to those series. Representatives connect to defined groups of clients. Documents can be associated with the right investor, investment, fund, and series.
From that model, TidalCap creates three purpose-built experiences: investors see their own portfolio and documents, representatives work across assigned client relationships, and administrators manage the complete operating model and reporting workflow.
The broader point is not that BlueSail only builds private-equity software. TidalCap demonstrates the ability to learn a complicated operation, model its data and permissions, and build production software around how the business actually works.
The build
Financial model and metrics
The portal is built around a relational fund, series, holdings, investor, commitment, ownership, and document model. That structure lets the system calculate and display investor-level and series-level performance without flattening the business into a generic account table.
Per-investor calculations include invested amount, ownership percentage, committed amount, unfunded commitment, total distributions, distribution count and last distribution date, current portfolio value, net gain, MOIC, DPI, RVPI, and TVPI. XIRR is implemented separately using irregular cash flows and terminal NAV.
The same operating model supports fund cash flows, corporate actions, distributed or converted holdings, and ownership-based views of the portfolio.
Documents and reporting
Documents are uploaded, tagged with the right investor, investment, fund, and series context, and delivered through role-scoped portal views. Download status and timestamps are tracked so administrators and representatives can see which documents have been accessed and which are still pending.
The reporting layer turns operational data into usable outputs: individual investment-summary PDFs, bulk PDF bundles packaged as ZIP files, login and session activity spreadsheets, filtered client-overview spreadsheets, stock and holding reports, CSV import templates, and targeted email lists by fund, series, representative, or selected client group.
Those outputs matter because investment teams often need the same information in several formats: investor-facing summaries, internal review documents, operational spreadsheets, and communication lists for specific fund or series audiences.
Permissions and activity history
TidalCap enforces access at multiple layers: authenticated sessions, role-based dashboard routing, API route checks, database helper functions, and PostgreSQL row-level security policies on core tables.
Investor access is matched to the authenticated user behind that investor record. Representative access is limited to the clients assigned to that representative. Administrators have the broader operating view needed to manage funds, series, clients, representatives, documents, and reports.
The platform also retains operational history: data-change audit records, login and logout session activity, consent history, document-download state, and document activity. That gives the firm a clearer record of what changed, what was accessed, and when.
Correction workflows
Financial and investor systems need correction paths because real operating data changes. TidalCap includes workflows that keep authentication records, investor records, public user records, and linked investment records aligned when client information changes.
Investment changes trigger recalculation of series investor counts and fund totals. Core table changes can be recorded with old and new values, which helps preserve context around operational corrections instead of leaving changes invisible.
What it replaced
BlueSail builds custom software around the way your business actually works, including the data, permissions, reporting, and correction paths generic tools miss.
