Nothing in your stack is replaced, migrated or reconfigured. We connect to what you already run, build anything your desk needs that does not exist yet, and show you the money before you commit to turning a single agent on.
01Days 1 to 2
Read access and a scoping call
Half a day of your IT team. We take read credentials and walk your desk workflows with whoever actually runs them.
You: half a day
02Days 3 to 7
We connect and reconcile
Atlas joins your records per entity. We check every figure against your own reporting and do not move on until they agree.
You: nothing
03Week 2
Your first list, with amounts
Twenty to forty findings, each with what it is worth and the records behind it. This is the point where you decide whether any of this is real.
You: read it
04Weeks 2 to 3
Custom modules and go live
Anything non standard is wired in, then you pick which functions start and at what level. A clean MT5 stack is usually live in week two. An in-house platform with unusual rails takes the third week.
You: choose the levels
What you give us. What we do with it.
You provide
Read access to your trading platformMT4, MT5, cTrader or in-house
Read access to your payment providersCard acquirers, local rails, wallets
Read access to ticketing and booksWhatever your desk already uses
Your signed partner agreementsSo rebate runs can be checked against them
One named person to sign offUsually the COO or head of operations
We do
Connect and verify every sourceReconciled against your own reporting
Join it into one graph, per entityClients, trades, deposits, tickets, partners
Build whatever is non standardIn-house platforms, regional rails, bespoke rebates
Run the agents read-only firstNothing is written anywhere until you say so
Hand you one list with amounts20 to 40 lines, records attached to each
What we read from. None of it is replaced.
Trading
MT4MT5cTraderIn-house platform
Payments
Card acquirersLocal railsE-walletsBank transfer
Service
TicketingLive chatKYC providerLedger and books
If something on your desk is not on this list, it becomes a custom module and is built into the integration. That is the part that decides whether you go live in week two or week three.
Everything brokers ask us first.
A CRM that does the work instead of recording it. It reads the same systems your team reads, finishes the routine work on its own, and brings you the few decisions that move money or touch a counterparty.
One monthly fee, with no setup cost and no implementation invoice. It covers every agent, every entity, every seat and the integration work itself, so there is no second invoice. We quote the figure on the scoping call, once we know your entities and which functions you want live.
Because a setup fee makes both of us optimise for the wrong thing. We would rather carry the integration cost and keep you for years than charge for a project and hand over something nobody adopts.
We build it. Custom modules for your workflows are part of the integration, not a change request. And anything we ship afterwards is included for as long as you are paying the monthly fee.
No. BrokerOS reads from MT4, MT5, cTrader or your own platform and writes back only what you approve. Nothing is replaced, migrated or reconfigured.
One to three weeks. A standard MT5 stack with common providers is usually live in week two. An in-house platform, unusual regional rails or bespoke partner structures push it to week three, because those modules get built rather than configured.
About half a day on day one for read credentials, and a scoping conversation with whoever runs each desk. After that the work is ours until you are choosing autonomy levels.
Only if you set it to. Every function starts at Approval. Money leaving the business to a counterparty is never autonomous at any level, and above an amount you set, everything asks a named person.
Every action is stored with what it read, what it changed, why, and who approved it, so a single decision can be reconstructed with the information the agent actually had at the time. Most brokers bring their compliance officer to the first call, and it usually ends the objection rather than starting it.
In your region. Entities stay separated from each other, and what Atlas learns on your book stays on your book. Every read is scoped and logged.
They stop clearing the same queue every morning. At one deployment four people moved onto client-facing work. The agents take the repeat work, not the judgement.
Then you have spent half a day and you stop. You see the first list in week two, before any agent has written anything anywhere, and you decide from there.
Your fee does not move with client count, seats or volume. Growing your book does not cost you more, and adding a jurisdiction is a conversation rather than an automatic repricing.
Six brokers, from an 8,000 client retail book to a group holding three licences. We cannot name them, which is the honest answer and the same answer they get about you.
Start Monday. Know by week two.
Day one we take read access. In week two you get one list of what we found, with amounts and the records behind every line. Decide after that.