Prop firm trader churn: a weekly breach checklist

Prop firm growth lead reviewing a dashboard after a week of trader churn and challenge breaches
Photo by Joshua Mayo on Pexels

It is Friday afternoon. A growth lead has the dashboard open: challenge sales are steady, breaches have jumped, refunds are up and second purchases have dipped. The total churn figure is red, but it does not say whether traders hit a loss limit, disputed a charge or lost trust in the product.

Read the week by cohort

Start with purchase week, challenge type, platform, country, acquisition source and payment method. Compare each cohort at the same age, such as day 7, day 14 and day 30. A new cohort should not be judged against customers who have had three months to return.

Keep these outcomes separate:

  • Challenge failure: the trader breached a stated rule or timed out.
  • Customer exit: the trader passed or failed, then made no further purchase within your chosen window.
  • Payment loss: a refund, dispute or failed renewal reduced collected revenue.
  • Funded account attrition: the trader stopped trading, breached or closed an account after funding.

Set a consistent window for a second purchase. A 30-day window is useful for weekly trading, while a 60-day view can catch slower decision cycles. Report both purchase rate and net collected revenue. A discounted repeat sale can raise the first figure while lowering the second.

Separate breaches from exits

A breach is not automatically a retention failure. If the trader understood the daily loss limit and exceeded it, changing the rule or offering an instant reset may weaken risk controls. If breaches cluster around confusion about the reset time, equity calculation or news restrictions, the likely problem is communication or product design.

Pull breach reason and timestamp alongside support contacts and account activity. Check whether the trader saw the rule before checkout, acknowledged it, and could find it in the dashboard. Look for these signals:

  • Breaches concentrated around a platform or server-time change.
  • Support tickets asking how daily drawdown is calculated.
  • High breach rates among one affiliate, campaign or landing-page cohort.
  • Accounts with no login or first trade after purchase.
  • Disputes following a rule breach, payout rejection or delayed response.

Do not treat all of these as the same fix. A rule-comprehension issue calls for clearer disclosure and onboarding.

A suspicious acquisition source may need tighter affiliate review. A payout complaint needs an operations investigation, not a win-back email.

Price the leak before changing offers

Use a contribution view, not gross sales. The following are typical market ranges for planning, not audited figures.

Actual costs vary by country, payment mix, provider, contract and challenge price. Add your own processor statements and staff costs before changing the offer.

Cost lineTypical market rangeInclude in the calculation
Card processing2.5% to 4% plus $0.20 to $0.40 per paymentCross-border fees, currency conversion and refunds
Affiliate commission20% to 40% of attributed salesCommission basis, coupon stacking and reversals
Chargeback fee$15 to $35 per disputeLost transaction value and staff handling time
Support handling$4 to $15 per ticketFully loaded labour and repeat contacts

For each cohort, calculate collected revenue minus refunds, chargebacks, commissions, processing and support. Keep payout liabilities and risk exposure visible as separate lines. A high second-purchase rate is not healthy if repeat buyers generate more disputes or costly support than contribution.

Run the checklist this week

Use one working session with growth, support, payments and risk. Assign an owner and a date to every action.

  1. Freeze the definitions. Write down what counts as churn, breach, refund and second purchase. Keep the observation window consistent.
  2. Export the last eight to twelve weeks. Include order ID, challenge type, source, country, payment status, breach reason, support contact and subsequent purchase.
  3. Match records safely. Use customer or order IDs. Limit access to payment data and do not put card details in marketing tools.
  4. Build age-matched cohorts. Compare day 7, 14 and 30 outcomes, rather than mixing recent buyers with older accounts.
  5. Rank breach reasons. Show count, share of purchases and change from the prior period. Separate technical or unclear-rule complaints from ordinary limit breaches.
  6. Inspect the three largest loss sources. Review one campaign, payment route and support issue at a time. Check the actual journey, not just dashboard labels.
  7. Read a sample of tickets. Review at least 20 recent conversations if volume allows. Tag confusion, product complaint, payout issue, payment concern or no response.
  8. Reconcile repeat orders. Separate full-price purchases, discounted retries and purchases made after a pass. Compare net contribution and dispute rate.
  9. Choose one controlled change. For example, clarify the daily loss calculation on the rules page. Avoid changing the rule, price and email sequence together.
  10. Set a review date. Check leading signals after seven days and cohort outcomes after 30 days. Record what would make you keep or reverse the change.

If a small team needs help keeping campaign notes organised, the prop-firm.ai AI marketing agent is priced at $99 a month. It does not replace the trading, payments or compliance records needed for this review.

Time the second challenge purchase

Do not send the same offer to every failed trader. A trader who breached on day one, a trader who completed most of the challenge and a trader who passed have different reasons to buy again. Use the event and support history to choose whether to send an explanation, a product update or a purchase offer.

Test timing against your own purchase cycle. A practical starting point is to wait until the breach notice has been delivered and the trader has had time to review it, then test an offer after 24 to 72 hours. Keep a holdout group. Compare net revenue per eligible trader over 30 days, including refunds, disputes and support cost, not just email clicks or conversion.

Any discount or retry must follow the published rules and local requirements. State whether it buys a new challenge or resets an existing one, what rules apply, and whether the previous breach remains recorded.

Avoid language that implies a purchase improves the chance of a payout. If traders are contacting support about a decision, resolve that case before adding a sales prompt.

Track these measures together:

  • Eligible traders reached and offer acceptance rate.
  • Net contribution per eligible trader, with a holdout comparison.
  • Refund, chargeback and complaint rates after the offer.
  • Subsequent breach rate and funded-account quality.

Stop doing these things

  • Stop reporting one blended churn number without cohort age or outcome type.
  • Stop counting discounted repeat orders as retained revenue before costs.
  • Stop sending purchase offers before resolving breach or payout complaints.
  • Stop changing rules and marketing at the same time without a controlled test.

Frequently Asked Questions

How should a prop firm measure trader churn?

Define the event and time window first. Track challenge failure, no subsequent purchase, payment loss and funded-account attrition separately, then compare cohorts at the same age.

When should a prop firm offer a second challenge?

Test timing after the breach notice has been delivered and the trader has had time to review it. A 24 to 72 hour delay can be a starting test, but use a holdout and measure 30-day net contribution, refunds and disputes.

Should a prop firm offer a discount after a challenge breach?

Only if the offer fits the published rules and the economics work after commissions, processing, support and payment losses. Explain whether the offer is a new challenge or a reset, and do not use it to obscure a complaint or payout issue.