People and accounts
- Client management
- Leads
- Trading account management
- Partner and affiliate management
Our own brokerage product
A technology platform designed to centralise brokerage operations, customer management, workflows and integrations. One record per client, one place to work.
Built around the queue your operations team works through every morning: who registered, who is waiting on documents, and who needs an answer.
Product interface visual. Sample data only, not real client information.
Modules are enabled and configured per deployment. Nothing here forces a process on you that your team does not already use.
In a brokerage, who can see a document and who can approve a withdrawal matters more than any feature list. Roles are defined per deployment, and actions leave a record.
| Role | Typically can |
|---|---|
| Support | See client records and history, raise requests, not approve them |
| Compliance | Review documents, approve or reject onboarding |
| Finance | Process funding requests and reconcile them |
| Management | See reporting across the operation, set permissions |
An example arrangement. Yours is configured to match how your team is structured.
Where the platform exposes an interface, yes, so trading accounts and client records stay connected. With sTrader that link is built in. With a third-party platform it is an integration we scope per case.
Usually yes, and migration is planned as part of the project. We run the import on a copy first so you can see exactly what arrives before anything goes live.
Only the roles you allow. Document access is a permission like any other, and we document exactly what each role can reach before the deployment goes live.