Customer evidence
Proof should be specific enough to check.
StrategyProfiler is early. We are collecting permission to publish real workflows and outcomes, not filling the credibility gap with anonymous praise, invented user counts, or hindsight-selected trades.
Publication standard
Every case study must carry its context.
The objective is to show where the platform found useful risk, saved analysis time, improved a decision, or failed to do so—without converting a backtest or counterfactual into a performance guarantee.
- What the trader was trying to solve
- The MT5/account context needed to understand the result
- What StrategyProfiler, Live Tracking, Mercer, or Archimedes actually observed
- A specific outcome—including cases where the product did not improve the decision
- Customer permission and enough detail for the claim to be checked
Verified case studies are being prepared
Each published story will identify the approved trader or public handle, the account and strategy context, what changed, and the measured outcome. Until those approvals and records exist, this space stays explicitly unfilled.
Founding cohort
Use it on a real workflow and help define the evidence.
Founding users receive direct product access and priority bug review. Case-study participation is optional and nothing is published without permission.