10 Must-Have Features in a Forex Broker CRM for 2026: A Shopping List
Use this list in a demo. For each feature, ask for the quick test and watch whether the vendor can do it with your data. A feature that cannot pass its test is not a feature.
1. Registration and onboarding
Test: register a fake client in two languages and watch the data reach the pipeline with its source attached.
2. KYC review
Test: upload a document, reject it with a reason and approve a second one. Check the audit trail.
3. Account provisioning
Test: open an MT5 account from the CRM on a test server. See the Manager API guide.
4. Deposit and withdrawal approval
Test: approve one deposit and reject one withdrawal, and check balances and records.
5. Payment provider connection
Test: process a small payment end to end and reconcile it.
6. IB and partner commissions
Test: model your commission structure and compare the result with your own spreadsheet.
7. Reporting
Test: produce your weekly five reports from sample data. See our reporting guide.
8. Support tools
Test: raise, assign and close a ticket with a template reply.
9. Roles and security
Test: create a restricted user and try to reach something they should not. See the security guide.
10. Exit and export
Test: export all client data in a usable format and ask how long notice takes. Use the full buyer’s checklist.
Score and compare
After the demo, give each feature a pass, partial or fail. Add a column for what the vendor said it would cost to fix a partial.
Comparing the totals of passes and fixing costs across two or three vendors gives you a sensible shortlist, and gives you a negotiation list for the one you pick.
A scoring sheet for the ten features
Score each vendor from one to five on each feature, using what you saw in the demo.
| Feature | Weight | Vendor A | Vendor B |
|---|---|---|---|
| Registration and onboarding | |||
| KYC review | |||
| Account provisioning | |||
| Deposit and withdrawal approval | |||
| Payment provider connection | |||
| IB and partner commissions | |||
| Reporting | |||
| Support tools | |||
| Roles and security | |||
| Exit and export |
Multiply score by weight and total. Where two vendors are close, look at the rows with the highest weights.
A worked example of a weighted choice
A buyer gives KYC and funding high weights because they affect conversion, and gives reporting a medium weight. Vendor A scores higher on reporting; Vendor B scores higher on KYC and funding. After weighting, B wins narrowly.
The buyer then asks both vendors to address their weakest rows and revisits the scores. B’s lead holds, and the buyer chooses B with a clear reason that can be explained to partners.
What to pay for and what to skip
Pay for onboarding, funding, partner management and security first. Skip add-ons you cannot yet use, such as advanced scoring or elaborate dashboards. You can add them later when real data shows what you need.
See our CRM buyer’s guide for the contract points.
Why the order of features matters
Features are not equal. Onboarding and funding affect revenue directly. Security and exit affect risk. Reporting and support affect operations. If your budget is limited, buy in this order: onboarding and KYC, funding and payments, account provisioning, security and permissions, then reporting, partners and the rest.
Vendors often present features in an order that suits their sales story. Rearrange them to suit your needs before you compare.
A short list of demo questions
During demos ask: Show me a client who is rejected and resubmits. Show me a failed deposit. Show me how a partner’s commissions are calculated. Show me who changed this record and when. Show me how to export all client data.
If a vendor cannot answer these live, the feature probably does not work as described.
Contract points tied to features
If a feature is critical, name it in the contract as a deliverable with an acceptance test. If a feature is promised for later, ask for a date and a remedy if it is late. Verbal promises about future features are easily forgotten.
Turning scores into a negotiation
After scoring vendors, use the results in negotiation. Show each vendor the rows where it scored poorly and ask what it will do about them, with dates. Ask whether any price reduction or extension is possible while the gaps remain.
Vendors often have more flexibility than their first quote suggests, especially when you are specific. A negotiation based on a clear scoring sheet is easier and less personal than one based on general impressions.
Revisiting the scores after launch
After three months of use, score the system again against the same list. Some features will have turned out to matter more or less than you thought. Share the updated scores with the vendor and use them to prioritise improvements. The exercise keeps the relationship focused on outcomes.
Budgeting for features you will add later
You may not need every feature at launch, but you will probably want some within a year. Ask each vendor which features are modules, what they cost and how long they take to enable. Add a modest line to your three-year budget for future modules.
It is better to see the price now than to be surprised later. Vendors who sell modules at a fair price and enable them quickly are easier to grow with than those who need a new project for each addition.
Frequently asked questions
What features should I score?
The ten in the sheet, weighted by your priorities.
How do I weight them?
By their effect on conversion, cost and risk in your business.
Should I test every feature?
Test the ones with the highest weights, with your own scenarios.
Can I add features later?
Sometimes. Ask about price and delivery time.