Evaluate ownership before the product list
Create a component map covering platform access, hosting, pricing, execution connectivity, CRM, payments and support. For each component record the contracting party, technical operator and escalation contact. A provider may configure a connection without supplying the connected service; keep that distinction visible in the proposal.
Separate implementation work from ongoing operations. Ask who applies changes after launch, where requests are logged and how the brokerage receives an updated configuration record. A complete handover is a specific deliverable, not a closing meeting.
Use the same evidence request for every proposal
| Area | Ask to see | A useful answer contains |
|---|---|---|
| Platform scope | A proposed environment and rights schedule | Named components, access limits and responsibility boundaries |
| Integration | A sample connection and failure test | Expected inputs, outputs, exception handling and owners |
| Operations | A sample incident and recovery procedure | Escalation route, decision authority and validation steps |
| Exit | A migration and data-return outline | Available exports, restrictions and cooperation dependencies |
Use live demonstrations or clearly labelled samples. A screenshot is useful when its environment, date and purpose are explained; an unexplained dashboard does not establish production capability.
Run a focused technical discovery
- Describe your business stage: first launch, replacement, expansion or operational repair.
- List the workflows that cannot be interrupted and the systems they depend on.
- Identify the capabilities you need to retain internally and the responsibilities you want managed.
- Select a small set of acceptance tests and agree who reviews the results.
The discovery output should identify open questions as well as the proposed architecture. A dependency that still needs vendor approval should remain visible in the delivery plan.
Bring a proposal back to the brokerage
A practical review ends with an understandable scope: deliverables, exclusions, dependencies, change process and acceptance criteria. Keep commercial terms attached to the same scope so a lower headline fee is not mistaken for an equivalent service.
For platform-specific requirements, start with MT4 White Label or MT5 White Label. TSG’s infrastructure review can then focus on the parts around that platform: deployment boundaries, data paths, integrations and the operating handover. Confirm any claimed licence, partnership or service commitment through the relevant written evidence.