Skip to content
Nexus Prop LLC

Operator guide

How to start a prop firm.

Everything a funded-trader firm needs to launch, ordered from the decisions that constrain everything else down to the ones you can revisit — program design, risk and payout rules, market data, payment processing, live risk enforcement and fraud.
By Ethan Warmuskerken, Founder, Nexus Prop LLCLast reviewed

Key takeaways

  • Program design precedes platform selection; you cannot evaluate a platform against rules you have not written.
  • Market data and payment processing set your cost floor and your launch date, and both are decided by parties who do not work to your timeline.
  • Mainstream processors do not serve prop firms. Plan for a specialist acquirer, and start that application before you choose a platform.
  • Launch readiness means acceptance scenarios passing against your own rules, not a feature demo.

The sequence

  1. 01

    Define the business and program boundaries

    Entity, jurisdictions, who you will accept as a customer, and your compliance posture. These constrain everything downstream and are expensive to revisit after launch.

  2. 02

    Write the program document

    Account sizes, evaluation structure, drawdown model, daily and maximum loss, consistency rules, minimum days, scaling and payout policy — precise enough to be configured without interpretation.

  3. 03

    Map the complete trader journey

    Every transition from first visit to payout, including the unhappy paths: failed verification, chargeback, breach, dispute, reset. Each needs an owner and a communication.

  4. 04

    Design risk and operator permissions

    How rules are enforced, who can override, what is recorded, and how a decision is explained to a trader afterwards.

  5. 05

    Select and connect external services

    Payments, payouts, identity verification, market data and email. Start these early — approval timelines are outside your control.

  6. 06

    Prove launch readiness

    Run acceptance scenarios end to end against your own rules, with real edge cases, before announcing a date publicly.

1. Program design comes before everything

You cannot evaluate a platform, price a data feed or write a risk rule against a program you have not defined.

Account sizes and evaluation structure

One phase or two, what each phase proves, and what a trader gets on passing. This is the product; everything downstream is implementation of it.

Drawdown model

Trailing, static or end-of-day, calculated on balance or on equity, and whether it locks at initial balance. Four common models, materially different outcomes, and traders will read the difference closely.

Daily loss and maximum loss

The thresholds, what time zone the day rolls at, and whether an open position at the boundary counts. Each of these is a dispute waiting to happen if left implicit.

Consistency and minimum days

Whether a single outsized day can carry an evaluation, and whether it can carry a payout. Two separate rules that are routinely confused for one.

Payout policy

Split, frequency, minimum threshold, whether profit carries between periods, and what a buffer retained against the balance means in practice.

Scaling and reset pricing

How a funded account grows, and what a reset costs. Reset revenue is a meaningful share of most programs and needs deciding early, not bolted on.

2. Risk and payout rules have to survive an argument

A rule is finished when two people configure it identically and a trader who fails by it can be shown exactly why. "Maximum drawdown of 5%" leaves at least four questions open: five percent of what, measured when, against which balance, and does an open position count. Every one of those becomes a support ticket, and eventually a public complaint, if the answer is decided after the fact.

The related decision is who is allowed to say what happened. If the trading platform computes a fill and the back office computes a different one, there is no defensible position when a trader disputes a breach — the firm is arguing with itself in front of a customer. Risk authority covers how to draw that boundary and what to test before signing with any vendor.

3. Market data is the decision that sets your cost floor

Traders need real-time prices, and real-time prices are licensed. This is usually the largest recurring line in a new firm's budget and the one first-time operators underestimate most, because it is billed per user per month rather than as a flat platform cost — so it scales with exactly the thing you are trying to grow.

Which provider you need is decided by the asset class you are evaluating on, not by preference:

What each asset class requires

Evaluating onWhat you needNotes
FuturesCME Group licensing (CME, CBOT, COMEX, NYMEX) plus a feed and a simulated execution environmentThe most common starting point. Exchange fees are per subscriber and reported monthly; the licensing obligation is yours or your vendor's, and it is worth knowing which.
CFDsA liquidity or pricing provider, and a jurisdiction-aware view of who you may offer them toLower data cost, materially higher regulatory surface. The constraint is rarely technical.
CryptoExchange or aggregator data; 24/7 operationCheapest data to source. The cost moves into operations: there is no overnight window and no natural daily boundary for rules that assume one.
Equities and FXPer-venue market data agreements; FX via an aggregator or prime feedEquity data entitlement reporting is its own discipline. FX has no single tape, so your reference price is a choice you have to defend.
Prediction marketsVenue APIs; contract and settlement modellingNewest category, least settled tooling, and evaluation rules written for continuous markets often do not transfer.

For futures specifically, most firms end up on Rithmic, Tradovate or NinjaTrader, or dxFeed for real-time data and simulated execution. These are proven and widely used, and there is nothing wrong with any of them — but they are all priced per active user per month on top of whatever you pay for the platform itself, and that combined per-seat figure is what determines whether your unit economics work at 50 traders and at 5,000.

This is the specific problem Nexus Connect exists to solve. It is licensed real-time market data plus the simulated execution environment, at $20 per active trader per month with no minimum and no platform fee — where an active trader means one who placed at least one order that month, not an account you provisioned. Run your own numbers against your current or quoted stack on the pricing calculator; the comparison that matters is total per-seat cost at the trader count you actually expect.

4. Payment processing is harder than it looks, and it will not be Stripe

Almost every first-time operator plans to take payments with a mainstream processor and discovers the problem late. Prop firm evaluations sit in a category that mainstream processors treat as high risk: the product is an intangible with a payout obligation attached, chargeback exposure is real, and the model is close enough to categories they decline outright that underwriting rarely gets comfortable. Firms are routinely declined at application, and — worse — sometimes onboarded and then offboarded months later with funds held during a review.

That second failure is the dangerous one. Losing your processor after launch means you cannot sell evaluations, cannot process resets, and are explaining a freeze to traders who are mid-evaluation. It is a business-continuity risk, not a procurement detail.

What actually works is a specialist high-risk acquirer, or several. The catch is that the good ones have volume thresholds, and a pre-launch firm with no processing history is exactly who they will not call back. So the sequence matters: start these applications before you select a platform, because approval timelines are weeks and they are outside your control.

5. Risk enforcement, while traders are live

Written rules are worth nothing if they are enforced after the fact. Breach determination has to happen against live account state — the same state the trader can see — or you are informing someone hours later that a trade they placed and watched settle has failed them, which is the single most common source of public complaints about prop firms.

Practically this means real-time position and P&L that reconcile to the authoritative record rather than being computed independently in the browser, protective orders applied at platform level so a rule cannot be traded around, and a scheduled liquidation path for daily boundaries. It also means an operator can answer "why did this account fail" precisely, without an engineer.

6. Fraud, which arrives sooner than you expect

Funded-trader programs attract organised abuse because the payoff is asymmetric: the cost of an evaluation is small and the payout is not. The common patterns are coordinated trading across accounts, hedging the same instrument in opposite directions across two accounts so one always passes, identity reuse across sign-ups, and payment fraud at purchase.

None of these are visible from a single account viewed on its own, which is why firms usually discover them at payout — the most expensive possible moment, when the money is already owed and refusing it is a public argument. Detection has to run across accounts and across the customer graph, and it has to inform a human decision rather than execute an automated denial: denying a payout on a probabilistic signal is a reputational cost that compounds.

Nexus firms also see signals from the shared fraud network — patterns and identities flagged across participating firms, so abuse that has already been seen elsewhere does not have to be learned again at your expense. Fraud prevention covers the signal types and how cases are assembled.

What most first-time operators underestimate

Three things, consistently. First, that program rules need to be written to a standard that survives an argument — 'maximum drawdown of 5%' leaves at least four questions unanswered. Second, that payout operations are a real function requiring people, evidence and consistency, not an afterthought. Third, that support volume is a direct function of what the trader cannot see for themselves.

The firms that struggle are rarely the ones with the worst software. They are the ones that launched before their rules were unambiguous.

Buyer checklist

  • Program document precise enough that two people configure it identically
  • Every trader-journey transition has an owner and a communication
  • External provider applications started before platform selection concludes
  • Acceptance scenarios written, including disputes and chargebacks
  • A defined answer to 'why did this account fail', producible without an engineer

Want the platform side in one document?

The Nexus Prop Capability Overview covers the full capability set — trading, risk, CRM, payouts, fraud and support — in a form you can circulate internally while comparing options. Enter an address and it opens immediately.

One address, used to send the file and occasional operator guides. No sharing, no reselling, unsubscribe in one click. See our privacy policy.

Apply the guide to your firm.

Bring your program document, or the questions blocking it. Both are useful starting points.