One of four products in one stack. The same page structure on all four, so comparing them is reading rather than hunting.
ForgeCRM
The back office: client records, onboarding and KYC workflow, the trader’s room your clients log into, and IB and affiliate management.
What it removes.
The reconciliation between your CRM and your trading platform. There is no nightly job comparing two views of the same client, and no window during which the two disagree. It also removes the migration project that usually stands between you and moving: the IB tree and closed history come with you.
Capabilities.
- 01
One client record
The account a client trades on and the record your team edits are the same row. A change is not propagated; there is nowhere to propagate it to.
- 02
Trader’s room
Clients manage their own documents, deposits, withdrawals and account settings. Requests arrive already validated rather than as email.
- 03
IB and affiliate management
Multi-level partner structures with commission rules you configure. An existing tree migrates with its levels and history intact.
- 04
KYC workflow
Document collection, review states and audit trail, with your own approval steps. Who approved what, and when, is recorded.
- 05
Roles and audit
Per-role permissions over every back-office action, and a log of who did it. Answering "who moved this client" is a query.
The claim is one system. This is where it is either true or not.
How it connects to the rest of the stack.
Not "integrates with" — there is nothing between these to integrate. Each line below names what actually crosses, and what does not have to happen as a result.
- ForgeCRM ForgeTerminal
- Account state, group and leverage are read directly by the terminal. A client sees a change the moment your team makes it.
- ForgeCRM ForgeQuote
- Pricing rules attach to groups defined here, so commercial terms follow the client rather than being maintained twice.
- ForgeCRM ForgeRails
- A withdrawal request raised in the trader’s room is the same record the payment layer acts on, with the same approval trail.
Technical detail.
| Migration | Accounts, balances, open positions, closed history and IB structure. |
|---|---|
| Trader’s room | Client-facing, on your domain and branding. |
| Permissions | Role-based, per action, with an audit log. |
| Integrations | KYC providers — see missing items below. |
Interface.
No screenshots yet. Real interface captures and a short video are outstanding (brief §11). A stock mock-up would be the one thing this page cannot afford: the pitch is that the product exists, and a fabricated screenshot argues the opposite to anyone who looks closely. The demo environment is the honest substitute until the assets exist.
Questions that come up.
Not written yet. The brief asks for three or four questions that actually come up in sales calls. Those have to come from someone who has sat in them — inventing plausible-sounding questions would produce a section that answers nothing a real buyer asked.
4open items on this page
- Screenshots of the back office and the trader's room, and a short interface video (brief §11).
- Which KYC and AML providers are integrated today.
- Whether the audit log is exportable, and in what format, for a regulator asking.
- FAQ — needs real sales-call questions.
Listed because a page that hides what it does not know is the thing this audience is checking for. Figures among these will each need their measurement definition before they can appear — see execution transparency.
See it before you decide.
ForgeCRM is not sold separately. The demo gives you the whole stack, because that is the only way to check whether the connections above are real.