From first lead to first deposit: designing the client chain

Most brokerages do not lack leads. They lose them between stages.

A lead arrives from a campaign and sits unassigned for an afternoon. Then someone calls who does not know a colleague already did. The client uploads a passport to one system and a proof of address to another, and deposits without sales hearing about it.

Each step works on its own. The loss happens at the hand-offs.

This guide covers the stages from first lead to first deposit (FTD), where they usually break, and how to design and measure the chain without relying on anyone else's numbers.

The stages, in order

Eight stages cover most brokerages. You can split or merge some. What matters is that each has a name, an owner and a clear exit condition.

1. Capture. A lead enters from a campaign, a landing page, a referral or a CSV import.
2. First contact. Someone attempts to reach the lead.
3. Qualification. Someone decides whether the lead is a fit, and records why.
4. Account opening. The lead becomes a customer with a trading account, by self-registration or conversion by staff. Conversion is not a deposit; it comes before one.
5. KYC. Identity and address documents are submitted, reviewed and decided.
6. First deposit (FTD). The client's very first deposit. Any later one is a repeat deposit.
7. First trade. The client actually uses the account.
8. Ongoing retention. Contact continues after activation, with someone responsible for it.

Where each stage usually fails

Capture. The same person arrives twice, through two campaigns or a campaign and a manual import, and two agents start working them. Fields from different sources do not line up, so half the records lack a language or a phone country code.

First contact. Nobody owns the lead for the first hours. Or an owner exists, but there is no record of attempts, so a second agent repeats the call and the lead gets annoyed.

Qualification. Status becomes subjective. One agent marks a lead "Qualified" after one unanswered call; another waits for a real conversation. The pipeline looks healthy and means nothing.

Account opening. The lead is re-typed by hand into the trading system. Typos, a second record and a lost link back to the original source follow.

KYC. Documents arrive by email, chat or upload, and live in three places. Compliance cannot see what sales promised; sales cannot see why an account is stuck. The client waits and does not know who they are waiting for.

First deposit (FTD). The deposit lands in the payments system, and sales finds out days later, or never. Meanwhile the lead is called again as if nothing had happened.

First trade and retention. Without a list of accounts that have deposited but not yet traded, no one is accountable for the gap between deposit and first trade. Retention becomes a mailing list instead of a task with an owner.

Design principles

You can fix most of this with rules, before any tooling decision.

One record per person

Whatever the source, a person has one record from first enquiry to account history. Duplicates are linked or merged at capture, not discovered at withdrawal time. If the lead and the customer are two unrelated records, every later report will disagree with itself.

One owner at every stage

Every record has a named assignee, and the hand-off to the next team is an explicit reassignment, not an assumption. "Unassigned" is allowed as a state, but it should be visible and short-lived.

Contact attempts before status changes

Define how many attempts a lead needs before it can be moved to a "no answer" or "lost" type status, and enforce it. This protects leads from being written off after one call, and it gives you honest data on how often your team actually tries.

Written status definitions

Write one sentence per status that says what must be true for a lead to enter it and what moves it out. If two agents would classify the same lead differently, the definition is not ready.

Notifications tied to events

Do not rely on people checking a screen. Decide which events must trigger a message, to whom, and in which language: a new lead assigned, a document uploaded, a KYC decision, a deposit received. Keep templates per language and channel so the client hears from you in the one they speak.

Approval steps where money leaves

Deposits and withdrawals are different risk profiles. Withdrawals should have a named approver, a role that is allowed to approve, and a record of who did. The people who can open accounts do not need to be the people who can release funds.

An audit trail you can read

When a client disputes what they were told, or a regulator asks who approved what, the answer should be a filter on a log, not a search through chat history. Record who changed what, and the values before and after.

What to measure

Start with a few definitions that everyone agrees on. A metric that two managers calculate differently is worse than no metric.

• Lead-to-contact time. The gap between lead creation and the first contact attempt by a human. Decide up front whether an unanswered call counts as contact, and report the median and the slowest decile separately, because the average hides the leads that sat for a day.
• Contact-to-qualified rate. Of the leads that were contacted in a given period, the share that reached "Qualified". Group by source and by agent, but only compare groups of a meaningful size.
• KYC turnaround. Time from the client's first document submission to a final decision. Split it into time waiting on the client and time waiting on your staff, because they have different fixes.
• First-deposit (FTD) rate. Of the accounts opened in a given month, the share that made a first deposit within a window you choose, such as 7 or 30 days. Fix the window in advance and keep it. Always measure by monthly cohort, so a slow month does not look like a bad one.
• Deposit-to-first-trade time. The gap between a first deposit and the first trade. It shows whether onboarding ends at the deposit or carries on into activation.
• Stage ageing. How many records currently sit in each stage longer than the limit you set. This is the daily working view; the rest are for the weekly review.

Resist comparing your figures with figures from elsewhere. Your own trend, by cohort, is the benchmark that matters.

How a connected CRM and platform helps

Every principle above is easier when the CRM and the trading platform work from the same customer record. Deposit and KYC status are then fields on the same record that sales already uses, not an export someone has to request.

In QUANTIX's Brokerage CRM, for instance:

• Facebook Lead Ads and landing-page webhooks feed a lead table, with duplicate linking.
• Statuses are configurable, with required contact attempts before a status can change.
• Each lead has an assignee, notes, an activity timeline and tasks.
• Converting a lead to a customer creates the trading account in one step.
• KYC documents sit in a review queue, where status changes fire notifications.
• Withdrawals are approved in the CRM, and an audit trail records the changes.

Notification rules, templates and integrations are covered under automation and integrations. The CRM does not replace the discipline above. It gives that discipline a place to run. The metrics above are calculated from your own exported data.

Start with the definitions

If you change one thing this quarter, write down your statuses, your owners and your metrics, and apply them to the records you already have. You will find the leaks quickly.

If you would like to see how this chain looks in a working system, you can book a private demo and walk it through with your own stages in mind.