Institutional
A desk built for size
Block-scale execution, negotiated transactions, and API access to the same settlement and custody rails individuals use — designed for funds, family offices, and wealth platforms. Planned offering, pending registrations.
Schedule time
Book the institutional conversation
Strategy, allocations, and platform — directly on the calendar.
Execution
Negotiated blocks and structured processes with the same atomic delivery-versus-payment guarantee as every other transaction on the rails.
Integration
API access for order flow, positions, and reporting — settlement instructions in, custody confirmations out.
Why institutions choose integrated rails
One counterparty surface, one audit trail, and custody that doesn’t require a second onboarding.
The job you are hiring a desk for
An institution moving size in a private name is solving four problems at once, and only one of them is price. Information leakage — every party who learns you are a buyer makes the trade worse. Counterparty completion — a signed term sheet is not a settled trade, and private transfers fail on consent more often than on price. Custody and titling — the position has to land in a record that survives an audit and a transfer agent’s review. Evidence — you need to prove afterwards who authorised what, and when.
A desk that solves one of those and outsources three is not a desk. Ours is built so the same rails carry all four, which is the argument for integration rather than assembly. How size changes the transaction →
What integration removes
The reconciliation you stop doing
- One onboarding. Eligibility and entity documentation are verified once into an Investor Passport and reused per record, rather than re-papered per deal.
- One settlement guarantee. Delivery-versus-payment on the same rails as every other transaction — shares and cash move together or not at all.
- One audit trail. Authorisation is recorded per record by B5 Secure™, so the compliance record is a by-product of the workflow rather than a monthly reconstruction.
- One custodian relationship. Positions land at Investor Services — including inside self-directed retirement vehicles where a client structure requires it.
- One reporting surface. Positions, capital activity and documents in the same place as the transactions that created them.
The integration questions worth asking us
- What is the data model for a party, an account, a position and a transaction — and is it versioned?
- Where is eligibility enforced: in the client, or server-side per record?
- What exactly is written to the audit record on each state change, and how is it exported?
- What happens to an in-flight transaction when a consent or a right of first refusal fails?
- Which reports are available as an API call rather than a file someone emails?
Those are the questions we would ask, and building on custody rails is the longer answer. On the asset side, the wrapper decides administration as much as it decides liquidity.
What this desk does not do
It does not provide investment advice, recommend or endorse any offering, or act as a broker-dealer or investment adviser. It does not evaluate sponsors on your behalf — that work stays yours. And it does not promise liquidity: a private position is illiquid until a specific right or window is confirmed in the documents.
Talk to the desk → Platform overview
Demonstration & reference experience. Institutional capabilities are illustrative of planned functionality and subject to registrations that are not yet in place. Not an offer or solicitation of any security or service.