From Proposal to Funded Traders: How a Prop Firm Launched on cTrader and Scaled Globally in One Year

About the Client

The client is a proprietary trading firm headquartered in Oceania, founded by an operator who had never run a prop firm before. There was no existing platform, no legacy CRM, and no book of clients to migrate — the business existed as a plan, a brand, and a launch date.

The product line is conventional prop firm fare done carefully: evaluation challenges across a ladder of account sizes, a verification phase, and a funded phase with profit-share payouts. What turned out to be unconventional was the audience. Although the firm is based in Oceania and built its brand for a domestic market, its traders arrived from everywhere. By the end of the first operating year, registrations had come in from more than ninety countries, and the firm’s three largest markets were in South Asia and West Africa. Its home market accounted for well under a tenth of sign-ups.

That distribution shaped almost every product decision that followed — from the languages the trader-facing portal had to speak, to the payment rails it had to support, to the price ladder the challenge catalogue had to cover.

The Launch

The engagement began in Month 0 with a signed proposal for Trader’s Room Prop. Firm Edition on cTrader, bundled with a Competitions Expansion, Top Gainers / Leaderboards, an Affiliates Module, the Express Checkout page with API, and two PSP gateways for deposits.

Our standard delivery window for a build of this shape is three to six weeks across four stages — Discovery, Development, Testing, Deployment. This one landed at the fast end of that range.

Kickoff was in the second half of Month 0. The trader-facing environment was stood up, branded, connected to the client’s cTrader white label, and wired to a transactional email service inside the same window. The first trader registered in Month 1, under thirty days after the proposal was signed. The first challenge was purchased five days later. The first payout to a funded trader was processed the same week.

That last point matters more than the first. Plenty of platforms can show a login page in a month. This one ran the complete prop firm loop — registration, checkout, challenge account provisioning, evaluation, funding, and a profit-share withdrawal back out to the trader — inside the launch month. The client’s team was operating a real business, not a staging environment, by the end of Month 1.

Platform Expansion

The firm launched on cTrader, which suited an audience that skews toward newer retail traders and a brand that wanted a modern web-first trading experience.

By Month 5, demand from IB partners and from traders in markets where MT5 is the default had made a second platform worth the operational cost. We provisioned a new MT5 service, connected manager credentials, and — critically — ported the firm’s existing challenge logic across so that the evaluation rules, phase progression, and payout conditions behaved identically on both platforms. That parity work was completed in Month 6.

The firm ran two trading platforms in parallel from that point forward without splitting its challenge catalogue, its CRM workflows, or its reporting. Traders picked a platform; the business logic stayed in one place.

Modules Delivered

Trader’s Room Prop. Firm Edition

The core of the deployment. The Trader’s Room gave traders a single portal to buy challenges, submit KYC documents, monitor challenge performance against live rules, review trading history, request payouts, and manage their profile. Behind it, the built-in CRM handled the manual steps the automation could not — task queues, lead assignment, document review, and withdrawal approvals.

The client approached us wanting the operator side to be runnable by a very small team. The task engine is what made that possible: challenge account creation, evaluation pass and fail events, funded account provisioning, and payout requests all land as structured, typed tasks with their own payloads and approval paths. Across the first year the platform absorbed a five-fold increase in operational task volume without the client adding operational headcount.

Express Checkout Page with API

This became the firm’s commercial front door. Rather than pushing prospects through a registration flow and then a separate purchase flow, the Express Checkout page combines challenge browsing, selection, payment, and account registration into one step, with affiliate referral tracking built in.

The client’s team iterated on this page harder than on anything else in the build. Over the first year we shipped changes to its sorting and filtering, added tabbed navigation by evaluation step and account size, exposed the underlying API so the page could be rebuilt inside the client’s own marketing site, adjusted the fields captured at signup, and repeatedly reworked how upsells surface at the point of purchase.

The conversion result was strong for a cold-traffic prop firm: 29% of everyone who registered went on to activate at least one challenge.

Challenge Engine and Product Catalogue

The Challenges module let the client’s team create, edit, translate, categorise, and publish challenge types themselves, with full control over drawdown mode, daily and total loss limits, profit targets, minimum trading days, duration, payout percentage, repeat conditions, and consistency rules.

They used it. By the end of the first year the firm had built and maintained 40 distinct challenge configurations across six price categories, spanning small entry accounts through six-figure funded sizes, plus a competition category. New configurations were added in six separate waves as the firm learned which price points its actual audience — rather than its assumed audience — was buying.

That catalogue was authored entirely by the client’s own team through the CRM. No configuration change required a development ticket.

Challenge Promo Codes

Promotional pricing turned out to be the firm’s primary acquisition lever, and the promo code engine got a workout that few deployments match. The client’s team created 407 promo codes in the first operating year, with control over discount percentage, single or multi-use, new-user or existing-user eligibility, applicable challenge types, usage caps, and separate validity and usage windows.

Promo code volume tracked the firm’s campaign calendar almost perfectly, peaking alongside its two biggest acquisition months. Across the year, promo code redemptions ran at roughly 1.1 uses per challenge activation — meaning discounting was not an occasional tactic but the default commercial motion, and the firm needed tooling that could keep up with it rather than gate it behind support requests.

Challenge Upsales

The upsale module let the firm attach optional paid extras at the point of challenge purchase — most commonly an upgraded profit split at the funded phase, and additional drawdown headroom. Each upsale maps to a specific challenge condition and rewrites the values across the whole challenge chain, so a trader who buys the upgrade at evaluation carries it through to funding automatically.

We built the first upsales in Month 1 and refined the checkout behaviour repeatedly through the year, including how the price reverts when a trader dismisses the upsale prompt and how upsales render on the express checkout page.

Affiliates Module and IB Referral Logic

The Affiliates Module gave traders a route to apply as partners from inside their own Trader’s Room, with referral URLs, promo materials, performance reporting on referred signups and purchases, and commission withdrawal. On the admin side, the client’s team approved applications, configured commission structures as a percentage of challenge purchases and of withdrawals, and mapped IB groups to specific trader account groups through Referral Logic — including access paths to account groups that are not publicly listed.

This became a genuine acquisition channel rather than a checkbox. By the end of the first year, roughly 9% of all registered traders had been approved as affiliate partners, and 22% of all registrations were attributable to an IB referral. We extended the module in Month 6 with an expanded multi-tier structure, and raised the affiliate account limit to three accounts per partner at the client’s request.

Competitions Expansion and Leaderboards

Competitions were part of the original scope and ran from the launch month, with signup windows, start and end dates, milestone tracking, real-time performance analytics, and automatic winner reporting. The firm ran competition events in its launch month and again mid-year, with KYC enforcement wired into competition entry.

KYC, AML, and Compliance Controls

Document upload, review, and approval ran through the CRM from Month 1, with AML scoring available on the trader record. The firm applies verification selectively — traders can evaluate freely, but identity verification gates the funded phase and the payout path, which is where the compliance risk actually sits. Over the year we tightened the document-to-KYC status matching and rebuilt the mobile KYC experience after the client flagged it.

Payments

The build included two PSP gateway integrations plus bank transfer forms and crypto/wallet forms for both deposits and withdrawals. Ninjacharge sat above the gateways as the payment aggregator and routing layer, directing transactions to whichever PSP the client selected rather than acting as a processor itself.

The payment picture reflects the firm’s geography: with traders in ninety-plus countries, a single card processor was never going to be enough, and the manual bank and wallet forms carried real volume alongside the automated rails. On the withdrawal side we added a second gateway mid-year, built separate bank withdrawal forms for different corridors, and created a dedicated email template for the new withdrawal route.

Email, Notifications, and Languages

Transactional email ran through a dedicated service from launch, with the firm building out 445 email templates across its lifecycle events — confirmations, challenge credentials, evaluation results, funding notifications, certificates, and payout confirmations. The client’s team managed verbiage themselves through the Email Verbiage module, and we twice ran bulk propagation of the English templates into every other supported language as the catalogue grew.

The portal ran in five languages in active trader use. Slack and Telegram notifications kept the operator team on top of task creation without sitting in the CRM all day.

Email confirmation rate held at 73% across the year — high for a prop firm audience acquired largely through paid and affiliate traffic, and a useful signal that the acquisition funnel was pulling real people rather than junk registrations.

Certificates

The firm leaned on achievement certificates as a retention and social-proof mechanic — certificates on evaluation pass and on successful withdrawal, delivered by email with the option to route copies to the support desk. We built the certificate flow in Month 1 and reworked the templates and delivery logic several times through the year, eventually merging the certificate email with the funded-account-opening email so a passing trader received one clean message instead of two.

Custom Development

The firm was an unusually active development partner. From kickoff through Month 12 we logged and delivered 110 development tickets — a median of five days from request to resolution, with 59% closed inside a week.

The work clusters into four themes:

Checkout and conversion. Field changes to the registration and express checkout forms, thank-you page routing logic, Google Tag Manager and Google Tags instrumentation, alert timing, a challenge selection slider, and repeated adjustments to how upsells and pricing render.

Trading data presentation. Decimal precision on trading history, date and time formatting in exports, a replacement for the traded-lots chart, additional statistics on challenge accounts, statistics calculation for failed challenges, and a rebuild of the daily reporting data logic.

Payout and phase workflow. A reworked withdrawal workflow, a change from trading days to calendar days for withdrawal eligibility, a redesigned phase approval flow, separate bank withdrawal forms by corridor, an initial balance field on the withdrawal task, and a change to surface “days since last payout” to funded traders in place of minimum trading days.

Operator tooling. Custom task export fixes, task action field backfills, admin-side challenge account creation with credential emails, trigger-based disabling of completed accounts, and duplicate task resolution.

Two things stand out. First, almost none of this was scope repair — the platform did what the proposal said it would from Month 1. It was a firm learning its market in public and asking the platform to keep up. Second, the requests got more sophisticated over time: Month 1 tickets were about logos and colours; Month 10 tickets were about reporting logic and payout cadence mechanics.

What the Data Says

All figures below are indexed and relative. Month 1 is the launch month.

Growth

The firm soft-launched in Month 1 and spent its first quarter with a small cohort while the catalogue, checkout, and affiliate program were built out. Commercial scaling began in Month 6 and accelerated sharply.

Series	Month 1	Peak month	Growth
New registrations	baseline	Month 8	11×
Challenge activations	baseline	Month 9	25×
Challenge accounts provisioned	baseline	Month 9	20×
Platform email volume	baseline	Month 9	6×
Operational tasks processed	baseline	Month 9	5×

Month 9 was the firm’s operational peak — it set the high-water mark simultaneously for challenge activations, challenge accounts provisioned, tasks processed, email volume, promo codes created, and evaluation accounts opened. Six independent series peaking in the same month is the signature of a business scaling as one system rather than one channel running hot.

Registrations peaked one month earlier, in Month 8, which is the pattern you want: acquisition led, and purchasing followed a month behind as the funnel converted.

The Payout Engine

For a prop firm, payouts to funded traders are the outcome metric. They are the only number that proves the model works end to end — that traders can actually pass, actually get funded, and actually get paid.

Measured by quarter against the launch quarter as baseline:

Period	Payout volume (indexed)	Payout events (indexed)
Months 1–3	1.0× (baseline)	1.0×
Months 4–6	0.2×	0.2×
Months 7–9	1.4×	0.6×
Months 10–12	12.2×	2.4×

Payout volume in the firm’s fourth quarter of operation ran at more than twelve times its launch quarter, on 2.4× the number of payout events — meaning the average payout itself grew substantially as funded accounts matured and traders compounded. The single largest payout month was Month 11.

Funded account provisioning tells the same story from the other end: the firm brought 2.7× as many traders into the funded phase in Months 10–12 as it did in Months 1–3.

Challenge Economics

Metric	Result
Registration → challenge activation	29%
Challenges per buyer	2.06
Buyers purchasing more than once	38%
Evaluation pass rate	27%

The repeat rate is the number worth dwelling on. Nearly two in five buyers came back for a second challenge, and the heaviest cohort bought ten or more. For a prop firm, repeat purchase is the entire unit economic argument — acquisition is expensive, and a buyer who returns three times costs a third as much to serve.

An evaluation pass rate of just over one in four sat in a healthy band: loose enough that traders believed the challenge was winnable and kept buying, tight enough that the funded pool stayed manageable.

Reach and Distribution

Registrations arrived from more than 90 countries. The top five markets accounted for roughly 65% of sign-ups, spread across South Asia, West Africa, Southeast Asia, and the firm’s home market — a genuinely distributed base rather than one country with a long tail. The portal ran in five languages in active use.

Operational Efficiency

Across the entire first year, the firm logged fewer than one support ticket per sixty registered traders.

That is the metric we are proudest of. A prop firm generates a constant stream of questions that are really platform failures in disguise — where is my account, why did I fail, when do I get paid, why hasn’t my certificate arrived. When the Trader’s Room answers those questions on its own, in the trader’s own language, the support queue stays empty and a two-person operator team can run a business serving ninety countries.

What This Proves

A prop firm can be live in under a month. Not a landing page — the whole loop. Registration, checkout, challenge provisioning, evaluation, funding, and payout, running against a live trading platform, inside thirty days of a signed proposal.

The operator should own the product catalogue. Forty challenge configurations and four hundred promo codes were authored by the client’s team through the CRM, not by our developers through tickets. A firm that has to file a development request to change a price point cannot respond to its market. This one repriced, repackaged, and re-promoted continuously — and its peak month was the month it created the most promo codes.

A second platform should not mean a second business. Adding MT5 alongside cTrader in Month 6 did not fork the challenge catalogue, the CRM workflows, or the reporting. The trading platform became a trader preference rather than an operational division.

Scale should not require headcount. Between Month 1 and Month 9 the firm grew challenge activations twenty-five-fold and processed five times the operational task volume with the same small team, at fewer than one support ticket per sixty traders. That gap between growth and operational load is what the automation is for.

Speed of iteration compounds. A hundred and ten development requests at a five-day median turnaround is not a support relationship — it is a product team the client did not have to hire. The firm found its real audience half a world away from where it expected to, and the platform kept up with the pivot.

Key Metrics at a Glance

Metric	Result
Contract signed → first live trader	Under 30 days
Contract signed → first funded-trader payout	Month 1
New registrations, Month 1 → Month 8	11×
Challenge activations, Month 1 → Month 9	25×
Challenge accounts provisioned, Month 1 → Month 9	20×
Payouts to funded traders, launch quarter → Months 10–12	12.2×
Funded accounts provisioned, Months 1–3 → Months 10–12	2.7×
Registration → challenge activation	29%
Repeat buyers	38%
Challenges per buyer	2.06
Evaluation pass rate	27%
IB-attributed registrations	22%
Email confirmation rate	73%
Support tickets	Fewer than 1 per 60 traders
Challenge configurations built	40
Promo codes created (Year 1)	407
Registered traders approved as affiliate partners	9%
Email templates maintained	445
Countries represented	90+
Interface languages in active use	5
Trading platforms	2 (cTrader + MT5)
PSP gateways + aggregator	2 + Ninjacharge routing layer
Development tickets delivered (Year 1)	110
Median ticket turnaround	5 days