Process
How does a strategy reach testing?
A defined sequence keeps the rules, dependencies and handover visible before live execution is considered.
First, describe the intended behaviour
Send a plain-language outline of entry and exit conditions, instruments, proposed position limits and the broker you intend to use. We review whether each condition can be expressed as a testable rule and whether the connection appears technically suitable. The first conversation is also where we identify missing information. You do not need to share passwords or account credentials through the website, and we will not ask you to transfer trading funds.
The work in three review stages
Scope
We agree which strategy, broker connection and controls are in scope. The written scope records assumptions and dependencies, including external data or broker permissions. If the rules still require discretionary judgement, we pause the estimate until the client can clarify them. This prevents an apparently small build from hiding unresolved trading decisions.
Configure
We implement the agreed rules and limits, then test them against historical scenarios with the data range and costs recorded. We examine example orders and blocked conditions. A typical single-strategy setup takes two to four weeks after scope agreement, although access delays, rule changes and broker-interface constraints can extend that period.
Handover
We review test reports, connection events and dashboard alerts with the client. The handover includes configuration notes and instructions for recognising exceptions and pausing execution. The client decides whether the system is ready for live use; a completed technical check is not a prediction of future performance.
An example of a staged handover
A South African trader brings a single rules-based strategy and requests a broker connection. During scoping, the exit rule is found to depend on an undefined manual judgement, so the client rewrites it before configuration starts. We then test the stated rules on historical data, check position limits using example orders and review connection interruptions in a non-live environment. The final meeting covers the test assumptions, dashboard events and the client's pause procedure. Any decision to trade remains with the client.
- Input
- One strategy with a clarified exit rule
- Checks
- Historical scenarios and non-live connection events
- Handover
- Notes, reports and exception walkthrough
What can change time or price?
The main variables are the clarity of the strategy, the number of rules and instruments, the broker interface, and the level of monitoring required. A change to the strategy after testing can require configuration and reports to be repeated. Third-party data access and broker permissions may introduce delays or separate charges. We identify these dependencies in the written scope and ask for approval before adding work that falls outside it.
Start with a short rules outline
Describe the strategy and intended broker so we can identify the first technical questions.