The client is a proprietary trading firm serving retail traders across Southeast Asia. The overwhelming majority of its participants sit in a single home market — close to nine in ten — but the platform has attracted traders from more than fifty countries since launch, with meaningful secondary clusters elsewhere in Southeast Asia and East Asia.
The business model is a classic evaluation-to-funding ladder: traders buy a challenge, prove themselves against drawdown and profit-target rules, and graduate to a funded account where they keep the majority of what they make. What makes this client interesting is how aggressively they iterated on that ladder — and how much money they pushed back out to the traders who cleared it.
When they came to us they had a brand, an audience, and the beginnings of a participant base — and none of the infrastructure a prop firm actually runs on. No trading platform integration, no trader portal, no CRM, no payment rails, no challenge engine. Everything below, we built.
We were engaged roughly five months before the firm opened its doors.
The core deliverable — the Trader’s Room Prop Firm Edition with its built-in CRM — was scoped, configured, and handed over within 46 days of kickoff. The pieces around it moved faster still: the client’s branding, logo, and portal chrome were live in 10 days; the live chat system was deployed and operational in 16 days; the express checkout page — the single-page browse-select-pay-register flow that the whole commercial model rests on — was standing in 13 days. The first payment gateway for challenge deposits was integrated and tested inside of six weeks.
What consumed the remaining runway was not the room. It was the platform.
The original signed scope was an MT5 build. Early in development the client changed direction, and we deployed a cTrader endpoint instead. Before that decision settled, they changed direction again — this time to TradeLocker.
We rebuilt the integration. It ran just under four months from first ticket to production, and it landed in the month the firm went live.
That is the part of a prop firm build nobody puts in a proposal. A trading platform change mid-development is not a configuration toggle; it touches account provisioning, credential handling, trade history ingestion, the challenge rule engine, and every email that references a login. We absorbed two of them and still made the launch window.
The second migration was the client’s own book. In Month 2, over the course of two days, we moved their entire existing participant base and its live challenge history onto the platform — traders, open evaluations, completed evaluations, and pass/fail state, all preserved. The firm did not pause trading to do it.
The trader-facing portal is where participants browse the challenge catalogue, buy, track their evaluation progress, submit documents, and request payouts. We configured it with challenge categories for filtering by account size, a live dashboard, trading history, an economic calendar, support chat, and document upload. More than two thousand trader-facing strings were populated to match the client’s voice, with three interface languages configured against future expansion.
The client sells to a paid-traffic audience, so the distance between “interested” and “paid” had to be near zero. The express checkout page collapses challenge browsing, selection, payment, and account registration into a single form with an API behind it, so the same catalogue can be surfaced on the client’s own marketing pages. It was in the original scope, it shipped inside two weeks, and it has carried every paid sale the firm has made.
This is the module the client used hardest. It gave them control over balance, price, duration, daily and total loss limits, loss-condition mode, profit target, minimum trading days, consistency rules, profit split, withdrawal timing, and trader-facing copy — per product, without engineering involvement. What they did with that control is the subject of the data section below.
We deployed the promo code module in Month 2. It supports percentage or fixed discounts, per-product targeting, new-user versus existing-user rules, global usage caps, active date windows, and bulk generation. The client went on to build 139 codes, including a single-month burst of 116 — effectively an influencer and affiliate campaign run entirely out of the CRM.
Added in Month 8, the upsale module lets traders buy condition improvements during the initial checkout. The client attached a profit-split upgrade — taking the trader’s share as high as 90% — to 10 of their challenge configurations, monetising the checkout page a second time without adding a new product.
Identity verification runs inside the room: traders upload documents, the CRM tracks approval state, and AML scoring is attached to the trader record. Verification volume tracks the funding pipeline rather than registrations, which is what you want — the firm verifies traders when it is about to owe them money, not before.
Every operational event in the system — challenge purchased, demo account needed, evaluation passed, evaluation failed, funded account opened, payout requested, profile change submitted — generates a task with a defined workflow behind it. One hundred percent of the tasks in the client’s CRM are system-generated. No one on the client’s team is manually creating operational work.
We integrated the client’s chosen payment service provider for card and local-currency challenge purchases in the pre-launch build, then added a stablecoin deposit method in Month 2 when the client’s audience asked for it, and a wallet-based payout rail in the same month. Ninjacharge sits above these as the aggregation and routing layer, directing each transaction to the provider the client wants it to land on.
The notifications module pushes task and deposit events into the client’s own channels. Live chat, a support ticket workflow, an admin inbox, role-based permissions across four admin roles, full activity journalling, and a configurable reporting layer round out the operational side.
Nine custom builds went in on top of the standard product. The ones that mattered most:
The consistency chart. Prop firms live and die by consistency rules, and the standard trading history chart did not show a trader whether they were inside or outside theirs. We replaced it with a purpose-built consistency chart in the trader portal — requested in the launch month, delivered in 10 days.
Certificates. Traders who pass an evaluation or draw a payout receive a branded certificate they can share. This became a marketing channel for the client, and they iterated on it three separate times over the first quarter; the fastest turnaround was same-day.
Unified platform credentials. The client wanted a trader’s first challenge password to become their master trading-platform credential rather than issuing a new login per challenge. We reworked the email and provisioning flow to make it so — a change that touched the account creation chain end to end.
Self-service password reset. Following on from the above, traders were given the ability to reset their trading platform password directly from the portal, removing a recurring support burden.
The inactivity rule. In Month 9, the client asked for a new challenge failure condition: evaluations that sit untraded for a defined number of days close automatically. Delivered in 12 days, and it now shows up in the fail-reason breakdown as one of the top three ways an evaluation ends.
Portal notifications, an extended challenge description field, and a crypto deposit method round out the list.
All figures are indexed or expressed as ratios. Month 1 is the launch month.
This is the headline. Comparing the firm’s first quarter of operation to its second, the volume of money paid out to funded traders grew 15.3×. The single strongest payout month — Month 6 — was 11× the firm’s first month of meaningful payout activity.
That growth was not one lucky trader. Payouts spread across a widening pool of funded accounts, and by the end of the observed period roughly two in five funded traders had drawn at least one payout.
Across the full period, for every unit of challenge-fee income the firm collected, approximately 1.7 units flowed back out to funded traders as payouts — before the firm’s own profit share is accounted for.
For a prop firm, that ratio is the credibility metric. Traders talk to each other, and a firm that visibly pays is a firm that keeps selling. Which is precisely what happened next.
| Quarter of operation | Paid challenge sales | Challenge-fee income |
|---|---|---|
| Q1 (Months 1–3) | baseline | baseline |
| Q2 (Months 4–6) | +72% | +49% |
| Q3 (Months 7–9) | +36% | +38% |
Total growth from Q1 to Q3: +134% in sales volume. No quarter went backwards.
The monthly view is spikier, as it always is with paid-traffic acquisition. The peak month — Month 7 — did 8.6× the sales volume and 6.9× the fee income of the quietest month of the first half.
The client’s biggest single acquisition event came in Month 6, when they generated 116 promo codes in one month and pushed them out through their partner network. Registrations that month ran 8.8× the level of two months prior, and promo redemptions peaked the following month at 7.7× their Month 3 level.
The entire campaign — code generation, targeting by product, usage caps, date windows, redemption tracking — was run by the client’s own team inside the CRM, with no development involvement.
The client offers a no-cost trial evaluation as a top-of-funnel product. More than one in four traders who took a free trial went on to purchase a paid challenge. For a product that costs the firm nothing but a demo account, that is a strong return.
Paying buyers averaged 1.8 paid challenges each, and one in three bought more than once — several of them many times over. Repeat purchase, not first purchase, is what makes a prop firm’s acquisition economics work, and the catalogue was deliberately built to support it.
Of evaluations that reached a conclusion, roughly one in twelve cleared the first phase. Of those that reached the second phase, close to half passed it. End to end, approximately one in ten traders who started an evaluation reached a funded account.
The most common ways an evaluation ended were the permitted total loss limit, the permitted daily loss limit, and — after Month 9 — the new inactivity rule.
The client did not launch a catalogue and leave it alone. They launched with a two-phase evaluation family across four account-size tiers plus the free trial. In Month 2 they added a single-phase family. In Month 3 they added a fifth, entry-level account tier across both families and launched an instant-funding family with trailing drawdown. In Month 7 they introduced their lowest-priced express product. In Month 8 they layered the profit-split upsale across the catalogue.
That is 34 live challenge configurations across four product families and five account-size tiers, built in six months — all of it self-served through the CRM.
| Signal | Result |
|---|---|
| Challenge accounts provisioned in under one minute | 94% |
| Tasks generated by the system rather than by staff | 100% |
| Support tickets per trader | fewer than one per four |
| Support as a share of total operational task volume | ~9% |
| Email confirmation rate | 93% |
CRM activity at the operational peak ran 3.2× the launch month and 3.8× the quietest month of the first half. Automated email volume peaked at 2.3× launch-month levels. Through all of it, support remained under a tenth of total task volume — the system absorbed the growth, not the client’s team.
A prop firm can be built from nothing in five months — including two changes of trading platform. The client changed their mind twice about the most structurally significant integration in the stack, and still opened on schedule. That is what a productised room plus a dedicated delivery team buys you.
A book migration does not have to be an outage. An entire existing participant base, with live and historical evaluation state intact, moved across in two days while the firm kept trading.
Product iteration is a self-service activity. Four product families, five account tiers, 34 configurations, 139 promo codes, and a profit-split upsale — none of it required a development ticket. When the client saw an opening in their market, the gap between decision and live product was measured in hours.
Growth lands on the platform, not on the team. Sales volume more than doubled, payout volume grew fifteenfold in a quarter, and CRM event volume more than tripled — while support stayed under a tenth of operational load and 94% of accounts provisioned in under a minute.
And the traders got paid. In the end that is the number a prop firm is judged on, and this one returned 1.7× its challenge-fee income to the people who cleared its evaluations.
| Metric | Result |
|---|---|
| Funded trader payouts, Q1 → Q2 | 15.3× growth |
| Peak payout month vs. first payout month | 11× |
| Payouts returned per unit of challenge-fee income | 1.7 : 1 |
| Funded traders who drew a payout | ~2 in 5 |
| Paid challenge sales, Q1 → Q3 | +134% |
| Challenge-fee income growth, quarter-over-quarter | +49%, then +38% |
| Peak sales month vs. quietest month of H1 | 8.6× |
| Registrations in peak campaign month | 8.8× two months prior |
| Free trial → paid challenge conversion | more than 1 in 4 |
| Paid challenges per paying buyer | 1.8 |
| Buyers who purchased more than once | 1 in 3 |
| Evaluation → funded account rate | ~1 in 10 |
| Challenge configurations built | 34, in 6 months |
| Product families / account tiers | 4 / 5 |
| Promo codes created | 139 (116 in a single month) |
| Accounts provisioned in under a minute | 94% |
| Tasks generated automatically | 100% |
| Support tickets per trader | fewer than 1 per 4 |
| Email confirmation rate | 93% |
| Markets reached | 55+ countries |
| Time from kickoff to core room delivery | 46 days |
| Trading platform changes absorbed pre-launch | 2 |
| Book migration duration | 2 days |
| Custom features delivered | 9 |
Kenmore Design's Prop Firm Edition gives you the CRM, Trader's Room, challenge management, payments, affiliates, and trader operations in one continuously-developed platform. Launch fast and scale without re-platforming.
Launch fast. Scale your prop firm without re-platforming.
