Look for period definitions, trade count, gains, losses, costs, drawdown, and consistent treatment of excluded activity. We supply the strategy and guide your setup through ChatGPT or Claude. Choose fully autonomous trading or approval before each trade. In autonomous mode, the AI executes without a separate permission request each time.
Your next decision
Ask how the whole record differs from selected examples.
Ask for a consistent measurement basis
A useful performance discussion identifies the reporting period, the trades counted, the treatment of losses and costs, and the basis of any return calculation. Keep those definitions stable when comparing periods or products. A selected screenshot cannot supply the missing account history, and a testimonial cannot substitute for a methodology. Bring specific questions to us so a historical figure remains a clearly defined piece of information rather than a promise about your next decision.
Distinguish a simulation from live use
A backtest evaluates rules against a historical setup with assumptions about execution and costs. Live activity introduces the actual operating environment, venue conditions, and decisions made during the period. Compare each kind of evidence for what it can establish. A simulated result does not become a live record because its chart looks convincing, and a short live trial does not become a long-term performance study. Keep the evidence labels attached when discussing either with us.
Use examples to understand the calculation
An arithmetic example is useful when its assumptions are explicit. If an agreed profit base were $100, a 15% share would be $15; that says nothing about how much an account will earn. Similarly, frequent small wins can be outweighed by fewer large losses. Keep illustrative calculations separate from actual trading records. Their purpose is to clarify a relationship between numbers, not to create a substitute history or imply that a particular outcome is typical.
A customer experience to consider
Read Martin Cook’s original account.
“I have a young family and there are better uses for a free hour than refreshing a price. I wanted to get away from seeing winning screenshots that never showed the whole account. What helped was looking at my own record instead of selected testimonials. It means a lot to me that I had a positive month of $8,400 I could trace through the records.”
Read the original review ↗Individual experience; not a forecast of your results.
Look at what remains after costs
Many small winning trades can produce a weak net result when charges consume too much of each gain. Compare the total gains, total losses, and relevant costs for the same period, rather than the number of positive trades alone. More trading activity is not automatically more progress. When reviewing an account, distinguish the cost of using the software from the costs generated by trading decisions, because reducing one does not necessarily reduce the other.
Separate the filter from a probability forecast
Our default strategy filter rejects opportunities below an internal 80% confidence score. That score is a strategy input, distinct from the historical win rate and not automatically an independently calibrated probability of winning. A filter can make a process selective without ensuring that every accepted trade succeeds. Ask what the score means within the workflow, and review the resulting gains, losses, and exposure rather than treating a single number as a complete risk assessment.