Source-aware field guide · 20 answers
Prop Firm Launch Planning
An operator guide to prop-firm product rules, platform and CRM scope, payment handoffs, acceptance evidence and controlled launch decisions.
Published · reviewed for scope, source visibility and answer ownership
How to use this guide
A prop-firm launch joins a published product rulebook to checkout, identity controls, account provisioning, trading data, evaluation logic, CRM states, support, payout review and dispute evidence. Each step may sit in a different system or provider. The operator needs one versioned operating model that names the source of truth, decision owner and handoff at every boundary, including what happens when a connector or data feed fails.
Use this guide to produce buyer-side artifacts rather than relying on a turnkey label. Write the rulebook before selecting technology, then convert each rule into calculation specifications and deterministic tests. Separate the trading platform from CRM, evaluation engine, payment service and operator review. Preserve source values, rule versions, timestamps and notifications so pass, breach and payout decisions can be reconstructed for a trader and an internal reviewer.
TradeLocker publicly states that it is a platform rather than the broker or prop firm and directs account, funding and trading-condition matters to the operator. Match-Trader publicly markets platform solutions to brokers and prop firms, but exact scope remains contract-dependent. The official sources below are starting points, not proof of one proposal's inclusions. Obtain case-specific legal, payment and provider confirmation before launch.
How to Write a Prop Firm Launch Charter
Define the target trader, product, jurisdictions, legal entity, revenue model, platform, systems, providers, rule owner, payment model, launch gates, budget authority, exclusions and stop conditions. Name an accountable sponsor for each workstream.
- Use it to
- Approve the charter before publishing offers, ordering integrations or committing to dates, and update it through controlled governance.
- Check the boundary
- A project charter does not determine regulatory treatment or prove that a payment, platform or other provider has approved the business.
How to Write a Prop Firm Product Rulebook
Specify phase, starting amount, objectives, daily and overall loss, equity or balance basis, reset time, open-position treatment, minimum days, prohibited conduct, pass, breach, retry, payout and appeal rules with worked examples.
- Use it to
- Assign a version and effective date, obtain legal and risk review, and use the same approved source for website, CRM, engine and support.
- Check the boundary
- Ambiguous marketing language creates inconsistent decisions; do not publish a rule that cannot be calculated and evidenced deterministically.
How to Document a Prop Firm Legal Perimeter
Give qualified advisers the entities, countries, customer terms, fees, simulated or live trading model, payout basis, marketing, data and provider roles. Retain dated advice, assumptions, conditions and actions for the actual proposal.
- Use it to
- Link public claims and launch controls to the current analysis and trigger review when the business model or countries change.
- Check the boundary
- Prop-firm labels do not determine legal status. This guide is not legal advice and one jurisdiction's analysis cannot substitute for another.
How to Map Prop Firm Entities and Vendors
Map the contracting entity, customer relationship, website, checkout, identity service, CRM, platform, evaluation engine, market data, payments, support and payout route. Show data, money and decision flows between them.
- Use it to
- Add a RACI, executed contract and escalation route to every boundary, then update the diagram before changing providers.
- Check the boundary
- A connected vendor does not become responsible for customer terms or operator decisions unless the contract explicitly assigns that task.
How to Issue a Prop Firm Platform RFP
Request exact scope for trader channels, accounts, instruments, administration, data, APIs, CRM, rule engine, payments, branding, environments, implementation, support, export and exit. Require included, optional and third-party responses.
- Use it to
- Provide the approved rulebook and common test scenarios so suppliers demonstrate the proposed configuration rather than a generic environment.
- Check the boundary
- TradeLocker and other trading platforms should not be assumed to supply third-party CRM, liquidity, bridge, checkout or payout functions.
How to Scope Prop Firm Connectors
For every integration, document source and target, fields, identifiers, trigger, ordering, retries, duplicate prevention, error queue, monitoring, credentials, owner and recovery. Include account, trade, rule, payment and notification events.
- Use it to
- Run normal, delayed, duplicated, rejected and disconnected cases and reconcile both systems before acceptance.
- Check the boundary
- A vendor logo or claimed integration does not prove support for the exact workflow, version, volume or commercial arrangement.
How to Map a Prop Firm CRM Lifecycle
Define CRM states from prospect and checkout through identity, purchase, account issue, active evaluation, pass, breach, retry, review, payout, dispute and closure. State entry criteria, owner, evidence and permitted transitions.
- Use it to
- Test blocked and reversed transitions and ensure every state can be traced to a payment, platform, engine or authorized staff event.
- Check the boundary
- A CRM status should not itself create a financial or trader decision unless the approved rules and source evidence support it.
How to Accept Prop Firm Checkout and Payments
Test product selection, price and currency, identity handoff, provider approval, successful and failed payment, duplicate callback, refund, chargeback, invoice, CRM state and account creation using stable transaction identifiers.
- Use it to
- Reconcile checkout, provider, bank and CRM records and preserve the merchant approval for the legal entity and business model.
- Check the boundary
- A working payment widget does not prove merchant approval, settlement, country coverage or legal suitability for the offered product.
How to Test Prop Firm Account Provisioning
Verify product, phase, platform, account group, currency, starting amount, leverage, symbols, permissions, credentials and rule version. Include duplicates, retries, delayed creation, wrong mapping, cancellation and reissue.
- Use it to
- Reconcile order, CRM, evaluation engine and platform identifiers and require idempotent behavior before launch.
- Check the boundary
- The operator owns account entitlement and customer communication even when a platform or connector performs the technical creation.
How to Specify Prop Firm Drawdown Rules
State balance or equity basis, static or trailing behavior, high-water mark, daily reset timezone, open positions, deposits or adjustments, commissions, swaps, precision, boundary equality and data source with numerical examples.
- Use it to
- Turn each clause into test vectors with source values and expected outcomes, then bind results to the published rule version.
- Check the boundary
- Names such as daily loss or maximum drawdown are insufficient because different formulas can produce different decisions.
How to Test Prop Firm Pass and Breach Workflows
Create accounts that clearly pass, clearly breach, touch an exact boundary, receive late data, need manual review and later reverse. Verify calculation, timestamp, state, access, notice and audit history for each.
- Use it to
- Require an independent reviewer to reconstruct every result from raw inputs, rule version and recorded decisions.
- Check the boundary
- Do not treat one dashboard label as conclusive when source data, timezone or connector completeness is uncertain.
How to Write a Prop Firm Payout Policy
Define eligibility, calculation basis, waiting periods, identity and payment checks, prohibited conduct review, supporting evidence, deductions, approval roles, method, timing, dispute and reversal treatment in clear customer terms.
- Use it to
- Map each policy step to a system state, named owner and retained record, then test normal and exceptional requests.
- Check the boundary
- Do not promise payout timing or availability beyond the approved terms, provider capability and actual operating process.
How to Design Prop Firm Identity and Abuse Controls
Define proportionate identity, device, payment, account-linkage and behavior reviews, with data sources, thresholds, human escalation, outcome categories, retention and appeal. Separate signals from confirmed findings.
- Use it to
- Test legitimate shared attributes, obvious duplicates and ambiguous cases to measure false positives and reviewer consistency.
- Check the boundary
- A score, IP address or trading similarity alone is not proof of misconduct; decisions need approved rules and reviewable evidence.
What Belongs in a Prop Firm Dispute Pack
Include customer terms and rule version, account and product identifiers, source prices, trades, balances, equity, calculation steps, timestamps, notices, staff actions, system status, relevant logs and the reasoned decision.
- Use it to
- Generate the pack from controlled records and have someone independent of the original action review material disputes.
- Check the boundary
- Screenshots without source, time or context can mislead; preserve machine records and disclose known gaps or outages.
How to Define Prop Firm Data Ownership
List customer, identity, payment, account, order, trade, market, rule, decision, communication and audit data. Name the controller or contractual owner, authoritative system, users, export format, retention and exit rights.
- Use it to
- Obtain sample exports and reconcile them before vendor selection so the firm can support decisions and transitions.
- Check the boundary
- Access to a dashboard does not establish complete export or reuse rights; confirm contracts and applicable privacy duties.
How to Run Prop Firm User-Acceptance Testing
Test purchase, identity, account creation, trading, rule calculations, notices, support, pass, breach, retry, payout, dispute, reporting, permissions, outages and recovery against traceable requirements and expected results.
- Use it to
- Use production-like configuration and synthetic data, record defects and require accountable owners to approve residual risk.
- Check the boundary
- A supplier demo or happy-path test cannot prove the complete customer and operational lifecycle is ready.
How to Write a Prop Firm Cutover Runbook
Sequence product publication, provider activation, configuration freeze, account templates, integrations, monitoring, reconciliation, staff coverage, communication, smoke tests, approvals, rollback triggers and incident contacts with exact owners and times.
- Use it to
- Rehearse the runbook and measure each dependency before opening checkout or migrating existing traders.
- Check the boundary
- Opening sales before evaluation, payment and support controls are accepted can create accounts the operator cannot administer consistently.
How to Build a Prop Firm Incident Plan
Define severity, ownership and evidence for platform, connector, market-data, rule-engine, payment, security and communication incidents. Include containment, decision freezes, trader impact, provider escalation, reconciliation, recovery and post-event review.
- Use it to
- Run tabletop exercises for stale data, delayed trades, duplicate accounts and payment outages before the first live customer.
- Check the boundary
- Automated pass, breach or payout decisions should pause when input completeness or rule-engine integrity cannot be established.
What Belongs in a Prop Firm Go-Live Gate
Require approved legal analysis, customer terms, contracts, provider approvals, rulebook, configuration, integration tests, reconciliation, permissions, training, support, monitoring, incident plan, cutover, rollback and accountable owner attestations.
- Use it to
- List open defects and conditions with severity, expiry and owner; postpone launch when a critical control lacks evidence.
- Check the boundary
- A completed website or platform environment is not a launch approval and should not override missing legal, payment or operational evidence.
How to Review a Prop Firm First Evaluation Cycle
Review checkout failures, account errors, trade-data gaps, rule outcomes, false alerts, support themes, disputes, refunds, payouts, reconciliation, incidents and supplier tickets against assumptions and acceptance results.
- Use it to
- Approve corrective actions and rule or control changes through versioned governance before applying them to new or existing accounts.
- Check the boundary
- Do not change evaluation outcomes retrospectively through undocumented configuration fixes; preserve the rule and evidence applicable to each account.
Primary and official references
These sources establish definitions, standards or official product behavior used across this guide. Follow the exact source and check its current version before a live implementation.