Skip to content
RegonanceFund OS
Request access

Who it's for

Four parties. One record. Four different jobs.

Fund OS is multi-sided by construction. The operator runs the fund and invites its providers; each provider works from its own scoped portal on the same underlying record. Nobody sees more than their engagement grants.

Operator

Management companies & AIFMs

You are accountable for the fund and for the providers you delegate to — but the evidence of that oversight lives in other people's inboxes.

Where it hurts today

  • Launch timelines slip on coordination, not on substantive work.
  • Delegated provider oversight is assembled retrospectively from email and spreadsheets.
  • The same fund facts are re-sent to four organisations in four formats.
  • No single view of what is outstanding across funds and providers.

What Fund OS changes

  • Run the launch as a workflow with cross-organisation ownership on every step.
  • Engage each provider through a recorded proposal-and-acceptance handshake.
  • See everything waiting on you and everything you are waiting on, in one queue.
  • Carry the launch record forward as the ongoing governance record.

Provider

Fund administrators

Your work is well defined; the inputs are not. Most delay is spent establishing what was asked, by whom, and against which version.

Where it hurts today

  • Requests arrive as email attachments with implicit scope and no due state.
  • Chasing missing inputs consumes capacity that is not billable.
  • Each client operator uses a different portal and naming convention.

What Fund OS changes

  • Receive structured requests with fund, role, scope and deadline attached.
  • Return documents against the step they belong to, versioned in place.
  • Work across multiple operator clients from one scoped portal.
  • Have your responsiveness evidenced in the same trail the client reads.

Provider

Depositaries

Your oversight duty depends on knowing what was appointed, what was provided, and what you confirmed — reliably and in order.

Where it hurts today

  • Appointment and delegation facts are communicated informally.
  • Attestations are collected over email and reconciled later.
  • Evidence of what you saw at the time is hard to reproduce.

What Fund OS changes

  • See the appointments and role bindings on every fund you are engaged on.
  • Give attestations and approvals inside the workflow, with the record attached.
  • Retain a standing, sequenced account of what you confirmed and when.

Provider

Auditors

The audit file is often reconstructed from other people's mailboxes. It does not need to be.

Where it hurts today

  • History has to be rebuilt from fragmented sources at year end.
  • Attribution — who acted, in what capacity — is frequently ambiguous.
  • Requesting evidence is itself a slow, manual coordination exercise.

What Fund OS changes

  • Read a sequenced, attributed trail rather than assembling one.
  • Access only the funds you are engaged on, with the scope made explicit.
  • Raise and resolve requests inside the same system the evidence lives in.

Other parties on the fund

Legal counsel, tax advisers, transfer agents and other third-party stakeholders can be engaged into the same coordination surface where a fund requires it, with access scoped to the specific role and fund.

During the private beta we focus on the four core roles above; additional parties are added to a fund on request where the structure calls for them.

Whichever side of the fund you sit on

Operators can start a launch; providers can be invited into one. Tell us which you are and we will show you that side of the system.

Request accessBook a demo