MT5 Grey Label Setup: A Step-by-Step Launch Walkthrough for New Brokers
Setting up an MT5 grey label is mostly a matter of making decisions in the right order. This walkthrough takes a new broker from the first conversation to the first live clients, and points to the places where people usually lose time.
Step 1: Decide the shape of the business
Write down your target clients, markets, account types, expected volumes and budget. These choices drive everything that follows, from the setup you pick to the integrations you need.
Compare the available options in our setup guide and shortlist two.
Step 2: Confirm scope in writing
Ask for the written scope of each shortlisted setup: included access, trading groups, logins, symbols, support hours and exit terms. Note what is optional and what it costs.
Sign only when the scope and price are clear. Questions to ask are in our decision guide.
Step 3: Prepare your brand and legal basics
Gather your logo, colours, company description and account type names. Prepare client agreements, risk warnings and a privacy policy. Settle company and banking questions if you need them; see company formation.
Step 4: Configure the platform
Work with your provider to configure branding where supported, trading groups, symbols, leverage and account types. Review each setting against your written plan.
Keep a record of the configuration so you can explain and repeat it later.
Step 5: Connect your supporting systems
Add the systems your business needs: a CRM, payment providers and, if applicable, liquidity or a bridge. Many are optional and priced separately. Start with the minimum that lets you onboard and fund clients safely, then add more.
Step 6: Test everything
Test registration, verification, account creation, funding, trading, withdrawals and reports with demo and small live accounts. Test failure cases. Fix what you find before launch. Use the setup checklist to confirm coverage.
Step 7: Launch small and learn
Open to a small group of clients first. Watch onboarding, funding and support closely, and collect the questions clients ask. Improve your wording, your workflows and your support before scaling marketing.
A one-page plan
The seven steps work best when they are visible on one page, with an owner and a date for each.
| Step | Output | Owner | Evidence |
|---|---|---|---|
| 1. Business shape | One-page brief | Founder | Signed brief |
| 2. Scope in writing | Agreed scope document | Founder and provider | Signed scope |
| 3. Brand and legal | Logo, texts, policies | Brand and compliance leads | Approved files |
| 4. Platform configuration | Groups, symbols, rules | Operations lead | Configuration export |
| 5. Systems | CRM, payments, website | Technical lead | Test records |
| 6. Testing | Test report | Everyone | Report with fixes |
| 7. Soft launch | First clients | Founder | Daily review notes |
Print it, put it on a wall and update it weekly.
A worked example of step two
A founder wants the scope in writing before paying. The provider’s draft lists "grey label setup" and "branding". The founder asks for specifics and receives a revised document: a client limit, a group limit, the symbols, which branding elements are included and which are not, whether the Manager API is included, support hours and exit terms.
The document is longer, but each line is something the founder can test. When a disagreement arises later about whether a change was included, the document answers it. This is why scope in writing is the most valuable step in the walkthrough.
Step four in detail: configuring the platform
Sit with your provider and walk through the configuration against your brief. For each group, confirm the name, purpose, leverage, margin and stop-out rules, spreads or markups and commissions. For symbols, confirm the categories and any special trading hours.
Ask for an export or screenshots of the final configuration and keep them with your records. If something is changed later, you can compare it with the original and know exactly what differs.
Step six in detail: the test plan
Write a test plan with specific cases and expected results:
- Register, verify, fund and trade with a test account.
- Request a withdrawal and see the review flow.
- Break things on purpose: a rejected document, a failed payment, an unavailable symbol.
- Check the emails and messages clients receive.
- Compare balances and trades between CRM and platform.
Run the plan twice, once with the team and once with outsiders. Fix issues in between and note the changes.
Step seven in detail: launching small
Invite a small group of known people first. Watch the platform, payments and support closely, and respond to each message quickly. Hold a short review each day for the first week.
After the soft launch, decide what to fix before opening wider. A modest delay now is much cheaper than fixing problems in front of many new clients. See the setup checklist and the roadmap for more detail.
Mistakes in a grey label setup
- Starting the build before the scope is in writing.
- Preparing brand assets after the platform is configured.
- Testing only the happy path.
- Launching to everyone on day one.
- Not recording the final configuration.
Each mistake is easy to avoid by following the steps in order and keeping evidence at each one.
A launch-day timeline
Morning: confirm that the platform, CRM, payments and support are ready and everyone knows their role. Midday: open registration to the planned group. Afternoon: watch the first accounts through verification and funding. Evening: hold a short review of what happened and fix urgent issues. Repeat each day for the first week, then move to a weekly review.
Weekly rhythm during setup
Hold a twenty-minute meeting each week with the same agenda: progress against the plan, blockers, decisions needed and next steps. Keep a visible list of decisions with owners and dates. This light structure keeps momentum and surfaces problems early, when they are still small.
Frequently asked questions
How long does a grey label setup take?
It depends on scope, branding and third-party approvals. Plan a dependency chain and treat dates as targets. See the launch timeline guide for an illustrative schedule.
What should be in the written scope?
Limits, symbols, branding elements, access and API, support hours, pricing and exit terms.
Do I need a CRM before launching?
Most brokers do. Check what your setup includes and what is quoted separately.
How do I test properly?
Use a written plan with expected results, include failure cases and repeat the tests after fixes.