The first financial decision is not the color of the charting screen or the number of currency pairs. It is whether the company will be a technology vendor, an introducing broker, or the regulated counterparty to U.S. retail customers. Those routes can look similar to a trader, but their capital needs, revenue mechanics, compliance burden, and balance-sheet risk are completely different.
A pure platform vendor sells software, connectivity, risk tools, or a white-label front end to licensed financial firms. It may charge setup fees, monthly licenses, per-account fees, API usage, or volume-based charges. An introducing broker acquires and supports customers but routes their accounts to a regulated dealer. A retail foreign exchange dealer, or RFED, stands as counterparty and operates under the CFTC and NFA framework. The CFTC's retail forex rules require counterparties offering off-exchange retail forex contracts to register as an FCM or RFED and comply with financial, disclosure, recordkeeping, and operating standards.
White-label SaaS
Introducing broker
RFED counterparty
Spread and commission
KYC and supervision
$20M minimum adjusted net capital
This is the regulatory floor for a U.S. RFED or an FCM engaging in retail forex, before adding the technology build, operating runway, liquidity arrangements, legal cost, and an internal cushion above minimum capital. A software-only vendor does not inherit that same capital requirement unless its activities cross into regulated dealing or intermediation.
The practical one-liner is simple: do not build an RFED budget around a software-company balance sheet. Before hiring developers, obtain a U.S. regulatory perimeter memo that maps the exact customer journey, who holds funds, who is counterparty, who sets prices, who approves promotions, and who handles complaints.
Revenue should be modeled by legal role. A software vendor can charge a one-time implementation fee of $25,000-$200,000, a monthly license of $10,000-$75,000, a per-funded-account fee of $5-$25, and separate API, support, customization, or hosting charges. An introducing broker usually receives a contractually defined share of spread, commission, or customer activity from the carrying dealer. An RFED may earn spread, commission, financing or rollover income, and other disclosed fees, but it also bears execution, hedging, capital, and conduct risk.
Retail leverage affects volume and risk. CFTC rules set minimum security deposits of 2% of notional value for major currency pairs and 5% for other pairs, commonly described as maximum leverage of 50:1 and 20:1. The CFTC's foreign currency trading guidance also emphasizes disclosure, reporting, and recordkeeping. A model that assumes offshore-style leverage for U.S. retail customers will overstate trading volume and revenue.
Newly funded accounts often trade differently from mature accounts, and inactivity can appear quickly. Build monthly cohorts with separate assumptions for first deposit, first trade, 30-day activity, 90-day retention, and twelve-month retention. The useful revenue unit is not a registered user; it is an active funded account that remains compliant and economically viable.
Planning note: Treat spreads, commissions, rebates, and financing as gross revenue only after confirming the contract and legal role. Then subtract partner share, bonuses, chargebacks, liquidity or execution cost, market-data cost, and variable support to calculate contribution margin.
Compliance is an operating system, not a legal bill paid once at launch. U.S. retail forex rules require risk disclosures before account opening. The required language warns that leveraged off-exchange forex customers can rapidly lose deposited funds and may lose more than they deposit. The detailed obligation appears in 17 CFR 5.5.
Customer reporting also creates recurring systems cost. Under 17 CFR 5.13, RFEDs and FCMs must provide account statements with specified information, generally monthly for active accounts and at least quarterly in certain inactive cases. A platform therefore needs reliable trade capture, cash reconciliation, statement generation, delivery records, and retention controls.
Marketing and affiliate riskBudget for pre-approval, monitoring, takedown rights, archive, and recurring training. One aggressive affiliate can create legal cost, refunds, partner disputes, and channel shutdown.
Cyber and access riskAccount takeover, credential theft, vendor compromise, and denial of service can trigger remediation, downtime, customer loss, notification work, and insurance claims.
Pricing and execution complaintsSlippage, rejected orders, stale quotes, widening spreads, and platform outages must be logged, reviewed, explained, and financially reserved where customer credits may be appropriate.
Third-party concentrationA single KYC vendor, payment rail, cloud region, CRM, market-data feed, or carrying dealer can stop onboarding or trading. Redundancy has a cost, but so does emergency migration.
Customer-outcome pressurePoor customer profitability, high churn, and repeated complaints can damage retention and acquisition efficiency even when short-term volume is high.
Capital and liquidity pressureA dealer may need to reduce exposure, pause distributions, or inject capital after market stress, adverse positions, withdrawals, or a regulatory capital warning.
The financial implication is direct: a low-cost vendor that cannot pass diligence or support records may be more expensive than a premium vendor once migration, remediation, downtime, and examination work are included.
The financial model should work like a chain. Product scope and legal role set startup investment and regulatory capital. Leads, approval rates, funding rates, and retention build active funded accounts. Account activity and contract economics create revenue. Partner payouts, KYC, payment, support, and infrastructure create variable cost. Payroll, compliance, audit, and administration create fixed cost. Working capital, debt service, taxes, capex, and reserves then determine owner cash and payback.
Founders often use a financial model, business plan, and pitch deck together to test these assumptions and explain them to partners or investors. The key is consistency: the customer ramp in the pitch must equal the funded-account cohorts in the model, and the operating plan must include the people and controls required to support that scale.
A forex platform is attractive when it combines compliant distribution, durable retention, reliable technology, disciplined customer acquisition, and enough capital to survive mistakes. It is unattractive when the economics depend on customer deposits, regulatory shortcuts, unstable partner rebates, or volume assumptions that disappear after the first market shock.