Operator invites into a role
Pick an organisation already on the network or invite a new one. The proposal carries the fund, the role and the scope of access it grants.
Product
The fund lifecycle, coordinated end to end.
Fund OS is one system shared by the operator and every service provider on a fund. It carries the fund from first launch step to ongoing governance, and records the whole path as it goes.
01 — Lifecycle
Launch is a workflow, not a folder.
A launch is modelled as a sequence of steps with an owner, a dependency and an outcome. The system knows which step is live, who is holding it, and what has to be true before the next one opens.
What the workflow carries
- Fund identity, structure and jurisdiction captured once, reused everywhere.
- The roles the fund needs filled, and the provider engaged into each one.
- Step-level ownership across organisations, not just inside your own team.
- Blocking conditions made explicit — what is waiting, and on whom.
- Timeline pressure surfaced before it becomes a slipped launch date.
Launch templates are configurable per fund type, so the step list follows your own house process rather than a fixed sequence imposed by the software.
Fund launch — step timeline
01Fund identity & structureOperatorcomplete
02Appoint management company / AIFMOperator → AIFMcomplete
03Appoint fund administratorOperator → Adminin progress
04Appoint depositaryOperator → Depositaryblocked
05Constitutional documents packOperator + Counselwaiting
06Appoint auditorOperator → Auditornot started
Illustrative interface — representative data, not a live fund.
02 — Cross-organisation engagement
Engagement is a two-sided handshake, and it is recorded.
Appointing a provider is not an email. In Fund OS the operator proposes an organisation into a named role on a named fund; the provider accepts, declines, or is substituted — and every one of those outcomes is part of the record.
Provider responds in its own portal
The counterparty reviews the engagement and accepts or declines. Acceptance is what creates access — nothing is opened up unilaterally.
The role is filled, and stays filled
The binding persists across the fund's life. Substituting a provider is an explicit, recorded act with a beginning and an end — not an overwrite.
Engagement — proposal and response
PROPOSEOperator invites Vertex AIFM SàrlRole: AIFMsent
NOTIFYCounterparty portal receives proposalScoped accessdelivered
REVIEWVertex reviews fund, role and scopeVertex AIFM Sàrlopen
ACCEPTEngagement accepted — access createdVertex AIFM Sàrlengaged
BINDRole bound on Lux Private Equity IRecorded eventbound
Illustrative interface — representative data, not a live fund.
03 — Coordination surfaces
Every party has one place that says "your move".
The daily product is a decision queue. Whatever is waiting on you — across every fund and every counterparty — arrives in one list with the context needed to resolve it.
My Work
A single queue of pending decisions: engagements to answer, documents to return, attestations to sign, approvals to give. Each item opens with its fund, role and deadline attached.
Requests
Structured asks between organisations — a document, an attestation, a piece of information — with a defined recipient, a due date and a resolution state.
Documents
Documents are attached to the step and party they belong to, versioned, and reachable from the workflow instead of a parallel drive.
Network
The map of organisations you work with, the roles they hold and the funds they are engaged on — your provider relationships as data rather than memory.
My Work — decision queue
EngagementAccept depositary role — Alpha Credit FundDue in 2 daysyour move
DocumentReturn signed administration agreementLux Private Equity Iyour move
AttestationConfirm NAV oversight for Q2Apex Yield Fundyour move
ApprovalApprove subscription document packPhoenix Growth Fundwaiting on you
RequestProvide audit confirmation letterDue in 6 dayssent
Illustrative interface — representative data, not a live fund.
Network — organisation profile
RoleManagement company / AIFMLux Private Equity Iengaged
RoleManagement company / AIFMApex Yield Fundengaged
RoleCentral administrationAlpha Credit Fundproposed
Contacts3 named users with scoped accessVertex AIFM Sàrlactive
History12 recorded engagement eventsSince Mar 2026audited
Illustrative interface — representative data, not a live fund.
04 — Audit trail
The trail is a by-product of the work, not a task after it.
Because coordination happens inside the system, the evidence is created at the moment of the act. There is nothing to reconstruct later from mailboxes.
- Every action is sequenced, timestamped and attributed to a named user at a named organisation.
- Engagements, substitutions, declines and approvals are all first-class recorded events.
- Records are appended rather than quietly edited, so history stays intelligible.
- The fund's history can be read as a single chronological trail, per fund or per party.
- Export supports internal review, board reporting and provider oversight files.
History can be exported for a fund or a counterparty as a structured file for internal review, board reporting and provider oversight packs.
Audit trail — fund history
14 Jul 09:12EngagementProposed — administratorS. Weber · Operatorrecorded
14 Jul 11:40EngagementAccepted — administratorM. Klein · Adminrecorded
15 Jul 08:03DocumentReturned — admin agreementM. Klein · Adminrecorded
15 Jul 16:27AttestationSigned — depositary reviewL. Reuter · Depositaryrecorded
16 Jul 10:55StepApproved — appoint depositaryS. Weber · Operatorrecorded
Illustrative interface — representative data, not a live fund.
Walk a real launch through the system
The fastest way to judge Fund OS is to watch a launch move through it — proposal, acceptance, request, approval, trail. We will run it with your fund structure in mind.