Prop Firm Software Vendor Due Diligence: Verify Claims Before You Depend on Them
Technology vendors publish useful information, but marketing claims, pricing pages and contracts answer different questions. A good diligence process records each material claim, its source, verification date and whether it is contractual.
Evidence hierarchy
| Evidence | Best use |
|---|---|
| Signed agreement/order form | Commercial obligations and scope |
| Terms/SLA/DPA | Legal/service/data conditions |
| Live product demonstration | Current functional capability |
| Technical documentation | Integration/API behavior |
| Pricing/product page | Public commercial/product signal |
| Case study/testimonial | Lead for reference verification, not independent proof |
Company and contracting entity
Identify the entity named in the agreement, jurisdiction, invoice issuer and contact details. Confirm that the entity promising the service is the one you can enforce the contract against.
Pricing diligence
Capture setup, recurring, usage, percentage economics, third-party costs, renewal and price-change rights. Resolve contradictions between pages. For example, our research has identified conflicting public pricing signals in some vendor material; those discrepancies should trigger a written clarification rather than an assumption.
Product claim diligence
Convert each critical claim into a live test. “Supports MT5” becomes “create a challenge purchase and provision the required MT5 environment.” “Real-time risk” becomes a timed breach scenario with audit evidence.
Scale and uptime claims
Ask whether account counts, firm counts and uptime statistics are independently measured, customer totals, cumulative historical figures or current production. Separate marketing statistics from contractual capacity/SLA.
Security claims
Do not convert a roadmap into a certification. Tradaxi, for example, publicly references a SOC 2 roadmap; that is not the same as holding a current SOC 2 report. Request current evidence for any certification that materially affects procurement.
Reference calls
If the vendor provides customers willing to speak, ask about incidents, migration, support, billing surprises and what they would change—not only what they like. Choose a reference with similar volume and architecture if possible.
Migration proof
Ask for the exact data objects that can be imported, the source-system dependencies and the acceptance/rollback process. “Zero downtime” is a valuable objective but should be mapped to your actual source environment.
Diligence log
- Claim.
- Source URL/document.
- Date verified.
- Evidence type.
- Open question.
- Vendor written response.
- Contract reference if material.
This is the same evidence-first principle used across Prop Firm Vendors. See our technology benchmark, demo checklist and contract checklist.
FAQ
Can I trust vendor case studies?
Use them as provider-supplied evidence and a starting point for reference checks, not as independent verification.
What if two vendor pages conflict?
Flag the discrepancy, ask for written clarification and make the governing proposal/contract explicit before relying on the figure.