Design the regulated service around execution, liquidity, custody, fiat flows, monitoring, disclosures and provider dependencies.
Why this workstream matters
Map whether the company acts as principal, broker or platform; who controls customer assets and orders; how price and liquidity are obtained; how fiat settles; and how customer, market, sanctions and transaction risks are controlled.
Model-specific questions
- Execution and order flows
- Custody and wallet control
- Liquidity venues and counterparties
- KYC/KYB, sanctions and KYT
- Fiat, banking and payment dependencies
- Pricing, conflicts, reconciliations and disclosures
How it connects to the application
Outputs must be consistent with the ownership structure, product and information flows, providers, business plan, staffing assumptions, policies and system behaviour. Any inconsistency should be resolved before filing or implementation.
Client inputs and dependencies
We confirm required founders, group records, product documentation, vendor information, system access, markets, transaction assumptions and responsible client personnel during scoping. The proposal separates adviser work, client responsibilities and third-party costs.