CLLegal
Corporate and fund counsel
Vehicle formation, offering documents, manager arrangements, investor terms, and regulatory perimeter.
Fund Builder
Build the first version of your fund stack.
Choose a jurisdiction, strategy, target scale, and operating modules. The interactive builder prepares an indicative architecture, deployment range, and annual capacity estimate you can carry into a launch discussion.
LegalStructure
AdministrationOperations
CustodyAssets
AuditAssurance
LayerStateOwner
Fund vehicleSelectedManager
Technology modulesConfigurablePeregrine
Configure
Fund architecture inputs
01
Vehicle and strategy
Choose the closest structure for an indicative model.
02
Target scale
Adjust the target AUM used in the operating-capacity model.
03
Operating modules
Select the capabilities that should be included in the first architecture.
Provider map
The fund stack usually spans four specialist layers.
The cards below are illustrative provider profiles—not endorsements, appointments, or claims of a formal network. Actual providers must be selected and diligenced for the fund, jurisdiction, strategy, and investor base.
DLLegal
Digital-asset counsel
Token terms, custody responsibilities, onchain transfer controls, distribution boundaries, and technology contracts.
FAAdministration
Fund administrator
NAV, books and records, investor services, financial statements, fee calculations, and regulatory support.
TAAdministration
Transfer and registry services
Investor onboarding, official register responsibilities, transaction processing, notices, and ownership evidence.
TCCustody
Traditional custodian
Safekeeping, cash accounts, settlement, corporate actions, reporting, and operational connectivity.
DCCustody
Digital-asset custodian
Wallet controls, key governance, transaction policies, supported networks, reporting, and digital-asset safekeeping.
AUAudit
Financial-statement audit
Annual audit, valuation evidence, ownership testing, service-provider controls, and financial reporting review.
SCAudit
Smart-contract assurance
Code review, privilege analysis, test coverage, deployment controls, upgrade processes, and incident preparation.
What happens next
Turn the model into a diligenced launch plan.
The browser estimate is the starting point. A real launch plan needs product, investor, regulatory, tax, legal, operational, technology, service-provider, and commercial decisions that cannot be automated by a public calculator.
Validate assumptions
Confirm the vehicle, investor markets, strategy, liquidity terms, and distribution plan with qualified advisers.
Select providers
Run due diligence, compare scope and responsibilities, and establish the official systems of record.
Design data flows
Map inputs, approvals, handoffs, outputs, reconciliations, evidence, access, and exception ownership.
Build and test
Implement the agreed stack, test normal and exception paths, document controls, and prepare operating teams.
Bring the builder output to a working session.
We will turn the indicative selections into a practical scope, identify the decisions that need qualified advice, and map the technology and operational workstreams.