One operator sees a challenge breach and sends the trader a discount code for another attempt within minutes. Another pauses the offer, checks why the account failed and contacts only traders whose behaviour suggests they still want to trade.
They make opposite calls on the same event. The first treats every breach as a sales trigger. The second treats it as a signal that needs context.
The second approach is usually the better starting point. A breach can mark the end of a paid challenge, but it does not tell you whether the customer is dissatisfied, temporarily out of funds, confused by a rule or ready to buy again. Treating those cases alike creates noisy retention metrics, unnecessary discounts and messages that can make a bad experience worse.
The breach is not the churn event
Prop firms often borrow subscription language for a transaction business. A trader buys a challenge, tries to pass it, then may or may not buy another. A breached account is an outcome within that purchase, not necessarily churn.
If the trader has not bought again after 30 days, that is a useful cohort measure. It is not proof that the trader has permanently left.
Start by defining the event you are trying to change. A repeat-purchase rate should count unique buyers who make another paid purchase within a stated window, not every checkout attempt or every account created.
Keep separate measures for challenge completion, breach, refund, funded-stage progression and repeat purchase. Otherwise a campaign can appear to improve retention simply because more buyers purchase a second account, even if complaints or refunds rise with them.
Also separate breach causes. A hard rule breach after a large loss is different from a challenge expiring with no trades, or a trader failing a daily loss limit after an abrupt change in market conditions.
Firms can classify a failure using events already available in the platform, such as rule breached, account expired, no activity, payment dispute or support contact. Keep the categories small enough that support and marketing teams apply them consistently.
- Rule breach: identify the specific limit reached and whether the trader had viewed the relevant rule.
- Expiry or inactivity: distinguish a deliberate pause from a trader who did not understand the challenge window.
- Service issue: flag platform interruptions, delayed data or a support case that remains unresolved.
- Payment or conduct risk: suppress sales messages where a refund, chargeback or abuse review is open.
This classification has a practical effect. It stops a trader who is disputing a charge from receiving a cheerful repeat-purchase offer, while letting a satisfied buyer who simply breached a rule receive a clear path to try again.
Find out what the second purchase means
A second challenge sale can indicate renewed intent, but it can also be a low-quality transaction. A deep discount may bring back buyers who would have returned at full price. It may also attract rapid repeat attempts from customers who have not understood the rules or cannot afford another loss. Track the reason for purchase where possible, and compare repeat buyers by breach cause, challenge type, acquisition source and offer received.
The ranges below are typical planning ranges for testing, not audited results or universal industry standards. Your entry price, rules, challenge duration, payment mix and customer geography can move them materially. Use your own historical cohorts as the reference once event tracking is reliable.
| Measure | Typical market range | What to check |
|---|---|---|
| Paid entries breached or expired within 30 days | 40% to 70% | Separate breaches from expiry and inactivity |
| Breached buyers making a second purchase within 30 days | 5% to 15% | Compare by breach cause and original offer |
| Repeat-purchase discount tested | 10% to 20% | Measure contribution after discount and fees |
| First repeat-purchase offer window | 3 to 14 days after breach | Test timing against support contact and account activity |
Do not read the second row as a target. A firm with a lower repeat rate but fewer refunds and stronger funded-trader progression may have a healthier customer base than one with a higher rate driven by aggressive couponing.
Break out gross sales and contribution. Subtract the discount, payment processing, affiliate commission and any variable servicing cost. Then check refunds, disputes and downstream progression over a suitable period.
Ask a short, optional question after the result is clear: what stopped the trader from passing, and would they consider another attempt? Keep the response choices useful to operations, not just marketing. For example, offer rule confusion, platform or support issue, strategy failure, lack of time and no interest. Do not make access to the next challenge conditional on completing a survey.
Make the offer fit the failure
The common mistake is to treat the second challenge as a recovery product that every breached customer should buy. It is still a financial purchase with a real cost to the trader. A retention programme should make the next step clearer, not imply that another payment will recover the first one or guarantee a funded account.
Build eligibility around customer state. A trader with no unresolved case, a clear rule breach and recent platform activity might receive an option to review the rule and purchase again.
Someone who breached during a confirmed platform incident should first receive a service resolution. A buyer with a payment dispute should not receive a promotional email until the case is closed. If the business offers a restart, state what it includes, when it expires and whether the original challenge rules still apply.
A breach is evidence about an account. It is not consent to receive another sales pitch.
Discount depth needs a control group. If every eligible trader gets 20% off, there is no way to tell whether the promotion caused an extra purchase or simply reduced revenue on purchases that would have happened anyway. Start with a small holdout, then compare full-price, modest-discount and non-price messages across comparable cohorts. Keep the test long enough to capture the purchase window and short enough that conditions do not change substantially between groups.
Try a sequence of choices rather than a single coupon:
- Offer a rule recap or a short explanation of the failure event, with no purchase prompt.
- For eligible traders, explain the available challenge options and the relevant terms in plain language.
- Test a modest repeat-purchase incentive against a no-discount message, then review margin and refund rates.
- Stop promotional contact after purchase, opt-out, complaint or an unresolved support issue.
Keep the copy factual. Avoid language that suggests a trader is due a win, close to success or likely to pass if they buy again. Those claims can damage trust and create compliance risk, especially where eligibility, rules or payout conditions are not prominent.
Build a breach-to-purchase sequence
Timing should follow the account state, not an arbitrary automation delay. A trader needs the result and any relevant explanation before receiving a sales message. A brief pause also gives support teams time to identify a platform issue or a disputed decision. The sequence can be automated, but eligibility and suppression rules need to be owned by a person.
- At breach or expiry: send the account outcome, the rule or condition involved and a route to support. Do not attach a discount to this transactional message.
- After the result is understood: check for open tickets, refunds, chargebacks, opt-outs and known service incidents. Suppress promotional contact where any of these apply.
- Within the next few days: invite feedback or provide a relevant rule explanation. Use a different message for inactivity, expiry and a hard breach.
- Only for eligible buyers: present the next challenge option, its price and terms. If testing an incentive, make the end date and eligibility clear.
- After the test window: stop the sequence and report purchases, margin, refunds, complaints and opt-outs by cohort.
Set a frequency cap across email, SMS, paid retargeting and affiliate messaging. A trader who receives an email, a push alert and a retargeting ad about the same breach can experience the sequence as pressure, not service. Make the event taxonomy available to each channel, and ensure that a purchase in one channel suppresses all remaining prompts.
A small team can manage the workflow in a CRM and a shared campaign calendar, provided events and suppressions are dependable. If marketing production is the bottleneck, prop-firm.ai pricing describes an AI marketing agent at $99 a month. That is a tool option, not a replacement for accurate account data, approval of claims or decisions about who should receive an offer.
Measure contribution, not coupon redemption
Review the programme as a cohort, not as a campaign screenshot. For each breach week, compare eligible traders who received an offer with a holdout or another suitable control. Include the original challenge purchase in the customer history, but do not count it as revenue caused by the repeat-purchase campaign.
A weekly dashboard can include:
- Eligible breached buyers, split by failure reason and acquisition source.
- Message delivery, click and repeat-purchase rates, with a clear 7-day or 30-day window.
- Net revenue after discount, affiliate commission, processor fees and refunds.
- Chargebacks, complaints, opt-outs and support contacts per 1,000 messages.
- Later progression, such as challenge completion or funded-stage entry, reported separately from repeat sales.
Look for displacement. If an offer raises the number of discounted purchases but lowers the share of full-price repeat orders, the campaign may be moving purchases forward or discounting buyers who were already ready. Compare overall contribution per eligible buyer, not only conversion among people who opened the email. Open rates are a delivery diagnostic, not proof of commercial impact.
Set a stop rule before launch. For example, pause if complaints or refunds exceed the control by a pre-agreed margin, or if the repeat-sale lift does not cover the incentive and operating costs.
Review performance across the main breach categories. A positive average can hide a harmful result for traders with unresolved support issues, while an apparently weak average can conceal a useful offer for a narrow, well-defined segment.
This advice does not apply where the breach is part of an unresolved service failure, the account decision is under review, or law and firm policy require a different contact process. In those cases, resolve the underlying issue first and do not use a second-challenge offer as the remedy.
Frequently Asked Questions
How soon should a prop firm offer another challenge after a breach?
Send the breach outcome and relevant rule details first. A promotional offer can follow once the result is understood and checks for open support cases, refunds, disputes and service incidents are complete. Test a 3 to 14 day window against your own cohorts.
What is a typical second-challenge purchase rate?
A broad planning range is 5% to 15% of breached buyers purchasing again within 30 days. Treat that as a starting point, not a target, and segment by breach cause, offer, acquisition source and challenge type.
Should a prop firm discount a second challenge?
Test a modest discount against a no-discount control, and compare contribution after fees, commissions and refunds. A discount is not useful if it reduces margin on buyers who would have purchased at full price or increases complaints and disputes.
