Start with the brokerage workflow
A platform is one part of the launch. Follow a prospective client from registration and account creation to funding, access, trading and operational support. Record which system owns each action and who resolves a failure.
This overview organises the business-system requirements. For a platform-specific proposal use MT4 White Label or MT5 White Label; for the delivery engagement see the implementation scope.
Build the launch dependency map
| Workflow | Component to identify | Open question |
|---|---|---|
| Client onboarding | CRM, client area and verification process | Which system approves account creation? |
| Trading access | MT4 or MT5 environment and supported clients | Which rights and interfaces are available? |
| Funding and reconciliation | Payment services and back-office records | Who authorises and reconciles transactions? |
| Pricing and execution | Market data and bridge/gateway connections | Which provider owns each failure mode? |
| Support and continuity | Monitoring, backups and escalation | Who can operate and recover the environment? |
Compare proposals on the same boundary
Separate implementation charges from recurring services and third-party dependencies. A single headline price can hide different amounts of integration work, access and operational responsibility. Ask each supplier to mark the same component map with included, optional, client-supplied or not available.
Illustrative launch review
Illustrative scenario. A small brokerage plans one platform and one initial instrument set.
Rather than adding every product at once, its review defines account creation, a representative client login, selected pricing and trading checks, a reporting export and an incident route. The acceptance record lists the evidence for those flows and the open dependencies that would block launch.