Prop Firm Software Buyer Evidence Checklist
Before signing, every material decision claim should have the right evidence behind it. This checklist is deliberately shorter than a feature matrix: it asks whether the facts that drove the purchase are actually proven.
Pricing
- Dated written price for our volume.
- Setup and refundability.
- Billing unit definition.
- Overage/tier transitions.
- All percentage/minimum definitions.
- Mandatory third-party costs.
Product
- Our challenge/risk rules demonstrated.
- Required trading platform demonstrated or technically documented.
- Provisioning failure/retry shown.
- KYC/payout workflow shown.
- Required API/integrations validated.
Scale and reliability
- Capacity requirement written.
- Uptime claim mapped to applicable SLA.
- P1 response/escalation known.
- Third-party outage responsibility known.
Migration
- Source-system inventory reviewed by vendor.
- Objects/state to migrate listed.
- Acceptance criteria written.
- Parallel/rollback plan understood.
- Migration fee/incentive written.
Data/security
- Usable export demonstrated.
- Retention/deletion known.
- Admin permissions/audit shown.
- Current evidence for any required certification.
- Custom IP rights understood.
Contract
- Minimum term/renewal/notice.
- Price-change rights.
- Material sales promises in governing scope.
- Exit assistance.
- Appropriate legal review completed.
Evidence confidence
Mark each item High (contract/live test), Medium (official docs/current written response) or Low (marketing/roadmap/unverified). Resolve Low-confidence items that carry high business impact.
Use the full procurement hub, due diligence framework and evidence map.
FAQ
Do I need written proof for every feature?
No. Prioritize evidence for requirements that materially affect cost, operations, risk, data or the decision to select the vendor.
What if a feature is roadmap?
Treat it as unavailable for a mandatory launch requirement unless the commercial agreement provides an acceptable commitment and risk allocation.