Discretionary, indicator-based, price action or quantitative: we turn your approach into precise rules. Everything else, from the backtest to the bot, is built on them.
A computer can only follow, and test, what's exact. So the first job is to pin down every part of how you trade.
Example rules. A computer can only test what's exact, so this is the first thing we do with every strategy.
Turning the way you describe your entries in your own words into rules a machine can execute consistently.
Defining the indicators, price-action conditions, or statistical signals that drive decisions.
Precise entry conditions, including confirmation logic and what disqualifies an otherwise valid setup.
Stop-loss, take-profit, and time-based exit rules defined explicitly, not left to feel.
How the strategy should behave in low liquidity, high volatility, or news-driven conditions.
A written specification of the strategy's logic: the reference used for backtesting and later automation.
You check it line by line, and it becomes the single reference for the backtest and the code.
Strategy specification · Trend pullback v1
Example document
Every rule is exact enough for a computer to follow. You check and sign off this document before any code is written.
That's common. We work through example trades with you to find the conditions you're actually reacting to, then write them as rules. If part of it can't be made exact, we say so, because that part can't be tested.
A written specification of every rule: entries, exits, stops, sizing and filters. It's the reference for the backtest and the code, and it's yours to keep.
No. Strategy logic is confidential by default, and we sign an NDA on request.
Describe how you trade: rules, indicators, or gut feel. We'll help you formalize it.
