Fund administration

If doubling AUA means doubling your operations team, we should talk.

Service more funds and investors without hiring at the same rate.

Specialized operating context · Controlled implementation

Operational systems

Four practical places to begin.

NAV and close operations

NAV Close Control Tower

Which funds are at risk, what is blocking the close, and who owns the next step, with the evidence attached.

The accounting platform remains the system of record
The system does not calculate or approve NAV

Reconciliation and exceptions

Exception Intelligence

The history, evidence and likely cause of a reconciliation break, assembled before an accountant opens it.

Read-only access is the default
Recommendations are clearly separated from facts

Investor and client service

Investor and Client Service

A permission-aware view across documents, operations and client history, with a drafted response for a person to approve.

The user sees only records already allowed by existing permissions
Human approval is required before external communication

Document operations

Document Operations

Notices, statements and subscription documents become validated records, each field linked to the page it came from.

Original documents remain attached to every extracted record
Human validation is required for defined financial fields

Investor onboarding

Try the onboarding portal from both sides.

Upload a sample package as the investor, then review it as the administrator: classified documents, fields with their source quotes, and a correction request. Open source, runs on Claude.

Try the investor onboarding demo

Control boundary

AI prepares the work. People retain financial judgment.

Every suggestion carries its evidence. Cash, NAV approval and the books stay behind existing controls and named people.

Fund administration

Where would another 50% of volume create strain first?

Bring one workflow. We start there.

Discuss the workflow