Devin Hartcastle
The first-session leak is a revenue problem
A firm selling 1,000 challenges a month at a $150 average order value has $3,000 to $7,500 in monthly refund exposure if 2% to 5% of buyers request a refund after failing to start. That is an illustrative calculation, not an industry benchmark.
Refund terms determine whether the exposure becomes a cash loss. Support time, payment disputes and weak repeat purchase intent add to the cost.
Many firms treat the sale as the finish line. A receipt arrives, a rules page sits in the dashboard, and the trader is expected to work out platform access, credentials, server selection and the first session alone. The trader has paid, but the firm has not guided them to a useful next action.
First-session activation is not the same as making a trade as quickly as possible. For a challenge, a sensible activation event might be a verified account, a successful platform connection and a rules acknowledgement. A first trade can be a later signal, but it should not become an instruction to trade before the person understands the limits.
Separate the funnel into three outcomes: the trader can access the account, knows the rules that affect the next decision, and chooses to begin trading. If the first two fail, more promotional email will not repair the experience. If the third is delayed because the trader is reading the rules or waiting for a setup, that may be healthy behaviour rather than a conversion failure.
Activation means readiness to trade, not pressure to trade.
Most onboarding flows are built for compliance, not completion
Compliance information has to be clear. The common mistake is treating a link to a long rules document as proof that the trader has understood the few details that can stop an account.
The trader may need to know the daily loss calculation, whether floating loss counts, the reset time zone, prohibited strategies and what happens after a breach. Burying those points in general terms creates confusion that support will later have to resolve.
The opposite mistake is presenting every rule, product feature and promotional offer in one onboarding message. A new buyer does not need a tour of the firm. They need the next action, the information required to complete it and a way to get help if it fails. Keep the sequence short, but make each message do a distinct job.
- Access: show where credentials appear, how long setup usually takes and which platform or server to select.
- Readiness: explain the risk rules most likely to affect a first session, with a direct link to the full terms.
- Recovery: give a clear route for missing credentials, rejected verification, platform errors or a payment mismatch.
- Choice: let the trader decide when to start. Do not use countdowns or bonus pressure to manufacture urgency after purchase.
These steps should be different for a challenge buyer and a newly funded trader. A challenge buyer needs the evaluation rules and account status. A funded trader may need to complete identity checks, review payout terms, confirm payment details and understand any restrictions that apply after funding. Sending the same welcome sequence to both groups saves a few minutes in marketing operations and creates avoidable support contacts.
Map every message to a real state change. If the platform connection is complete, stop sending connection instructions.
If verification is pending, send the correct next step rather than another generic welcome. A lifecycle tool such as prop-firm.ai's marketing agent can help organise those messages, but the underlying account events and permissions still need to be defined by the firm.
Measure activation by behaviour, not opens
Email opens are a weak proxy for readiness. Privacy features can inflate them, and traders can read a message without completing the setup.
Track events in the account or trading platform wherever possible. Agree definitions across product, support and marketing before comparing cohorts, or the dashboard will report different versions of activation.
The figures below are typical planning ranges, not audited cross-firm benchmarks. Use them as prompts for finding friction in a funnel, then replace them with your own cohort data. Platform, geography, verification requirements and challenge type can all move the numbers.
| Funnel event | Typical planning range | What a weak result may indicate | Useful owner |
|---|---|---|---|
| Purchase to successful login within 24 hours | 55% to 80% | Credential delivery, password reset or dashboard friction | Product and support |
| Login to successful platform connection | 65% to 90% | Server selection, platform instructions or compatibility issues | Platform operations |
| Purchase to first trade within seven days | 35% to 65% | Setup friction, low intent, unclear rules or a deliberate wait | Growth and product |
| Support contacts in the first seven days, per 100 accounts | 10 to 30 | Repeated setup questions or unclear rules | Support lead |
Do not optimise the first-trade percentage in isolation. A jump in first trades paired with more early breaches, complaints or refund requests could mean the sequence is pushing unprepared traders into the market.
Segment results by challenge product, platform, country, payment method and acquisition source. Affiliate traffic and paid search can bring different expectations, while a new platform release can affect one segment without changing the rest.
Track time between events as well as completion. A login within minutes followed by no platform connection for four days points to a different problem from a login after a week.
Add reason codes to support tickets, such as credentials, verification, rules, platform and payment. A small, consistent set of codes is more useful than a large taxonomy nobody applies reliably.
Fix the sequence without loosening risk controls
Start by removing uncertainty, not by adding incentives. Put credentials where buyers expect them.
State the normal delivery window and what to do if it passes. Use screenshots or a short platform-specific walkthrough for the steps that generate the most tickets. Keep the loss-limit explanation next to the dashboard status and make the applicable time zone explicit.
Make important rules easy to scan, then link to the full policy. A short rules panel should explain how the daily limit is calculated, which balance or equity measure applies, when the day resets and where a trader can check the current threshold.
Do not simplify away a condition that changes the rule. If the wording cannot fit, show the essential calculation and link directly to the relevant full section.
Before changing the sequence, check whether the issue is actually marketing. Failed logins may be a credential or platform problem. A high number of duplicate contacts may mean the dashboard does not show ticket status.
Traders who connect successfully but wait several days may be choosing their timing. Ask support to review a sample of recent conversations and compare the stated problem with event data.
- Use one message for access, one for rules and one for help, rather than a single crowded email.
- Write platform instructions for the actual product, including server names and the location of credentials.
- Send reminders only when the account state supports them. Suppress connection prompts after a successful connection.
- Keep risk warnings factual. Avoid language that implies a particular trade, pace or outcome is required.
There is a trade-off between detail and speed. More explanation can reduce mistakes, but a long sequence can delay access and prompt message fatigue. Put the information needed for the next action first. Let the trader open deeper explanations when relevant, and test whether those explanations prevent tickets or repeated rule misunderstandings.
Run a controlled activation programme
Choose one segment and one friction point before redesigning the full journey. For example, test the credential message for new challenge accounts on one platform. Do not change the email, dashboard, platform guide and risk copy at the same time. If activation moves, the team needs to know which change plausibly caused it.
- Define the event: choose a measurable readiness action, such as successful platform connection, and record the event consistently.
- Establish a baseline: use several recent weekly cohorts and report both the completion rate and median time to completion.
- Find the blocker: review setup tickets, failed events and a sample of user sessions. Separate technical failure from low intent and deliberate delay.
- Change one step: improve the instruction, placement or recovery route without changing challenge rules or adding trading pressure.
- Check guardrails: compare support contacts, refunds, early breaches, complaints and unsubscribe rates alongside activation.
- Keep or revert: retain the change only if the improvement is sustained and the guardrails do not worsen materially.
Allow enough time to include different trading days and traffic sources. A one-week spike can reflect campaign mix or calendar effects. If volume is modest, compare matched cohorts over a longer period and report the sample size. Do not claim a lift from a handful of accounts.
Assign one owner for each break in the journey. Marketing can own message timing and clarity. Product owns dashboard states and credential access. Platform operations owns connection instructions. Support owns ticket classification and escalation. A weekly review of the top three onboarding issues is usually more actionable than a broad monthly report on open rates.
After reading this, many firms will still make the same mistake: treating a higher first-trade rate as success, even when the real job is to help traders become informed, technically ready and free to choose when to begin.
Frequently Asked Questions
What counts as activation for a prop firm trader?
Use an event that shows the trader is ready to proceed, such as completing verification and connecting successfully to the trading platform. A first trade can be tracked separately. It should not be treated as a target that encourages trading before the trader understands the rules.
How soon should a prop firm send onboarding emails?
Send access instructions as soon as the account is ready, then provide rules and recovery guidance in separate messages. Trigger reminders from account status, not just elapsed time. Stop sending setup prompts once the trader completes that step.
How can prop firms reduce onboarding support tickets?
Identify the most common ticket reasons, then improve the instructions or account status display for those issues. Clear credential delivery, platform-specific connection steps and direct explanations of key risk rules often address repeated questions. Track ticket volume per 100 new accounts to assess the change.
Should a prop firm optimise for the first trade?
Not as a standalone goal. A higher first-trade rate may come with more early breaches or complaints if traders feel rushed. Measure setup completion and readiness alongside first trades, support contacts, refunds and risk outcomes.
