12 Prop Firm Software Red Flags to Investigate Before Buying
A red flag is not an automatic rejection. It is a signal that a material question remains unresolved. Strong vendors should be able to turn many of these into documented answers.
1. Pricing conflicts across the vendor's own pages
Different public figures can reflect stale pages, plan changes or different scope. Do not choose whichever number you prefer; request a dated written quote and clarify which page is current.
2. “Unlimited” without a definition
Unlimited accounts may describe billing rather than technical capacity. Ask about concurrency, API throughput and fair-use or infrastructure constraints.
3. Platform logos without commercial scope
Support for MT5, cTrader, Match-Trader or TradeLocker does not tell you who supplies licences, bridge/broker connectivity, market data or support.
4. “Real time” without a measurable path
Risk latency should be tested from source trading event through enforcement, not inferred from dashboard refresh speed.
5. Roadmap security presented like current certification
A planned SOC 2 project is not a SOC 2 report. Ask for current evidence and scope.
6. Revenue/profit share without a defined base
Gross revenue, net revenue and net profit produce different economics. The agreement should define deductions and reporting.
7. No usable data export
If customer and account state cannot be exported in machine-readable form, switching cost can become material.
8. Migration promise without data inventory
“Full migration” is vague until customer, account, challenge, KYC, payout, affiliate and history objects are enumerated.
9. Zero-downtime promise without rollback
A migration plan should define what happens when reconciliation fails, not only the intended success path.
10. Essential feature available only as custom work
Custom development can be fine, but price, delivery, acceptance, maintenance and IP rights should be explicit before vendor selection.
11. SLA percentage without exclusions/remedies
99.9% on a marketing page is not equivalent to a contract that defines measurement and escalation.
12. Pressure to sign before scope is written
If a commercial deadline prevents the vendor from documenting the architecture, fees and obligations that drive your decision, the discount may not compensate for uncertainty.
How to resolve a red flag
| Signal | Evidence that can resolve it |
|---|---|
| Pricing ambiguity | Dated order form with scenario pricing |
| Feature ambiguity | Live demo + written scope |
| Integration ambiguity | Architecture/third-party responsibility matrix |
| Reliability ambiguity | SLA + status/incident evidence |
| Exit ambiguity | Export test + contract clauses |
Use our due diligence framework, demo checklist and contract checklist to turn unresolved signals into evidence.
FAQ
Does one red flag mean I should reject a vendor?
No. It means you should resolve the issue before relying on the claim or signing the agreement.
What is the biggest red flag?
Any unresolved issue tied to a mandatory workflow, material cost, data portability or operational continuity deserves priority.