Breakout Systems
Breakout logic with realistic treatment of false starts and slippage on the entry.
Most strategies fail the move from idea to production not because the idea was wrong, but because it was never specified precisely enough to test. We write the rules down until they are unambiguous, test them honestly, and then automate what survives.
On a breakout systems engagement this means starting from what you already have — an idea, a spreadsheet, a running system, or a set of results that do not add up — and working from there rather than insisting on a rebuild. Where the honest answer is that the work is not worth doing, that is what you will be told.
What you get
- Translating a discretionary method into explicit, testable rules
- Entry, exit, filter and position-sizing logic specified in full
- Automation in Python or MQL, running unattended on your infrastructure
- Documentation that lets you or another developer maintain the system
How the work runs
Scope
A short call and a written scope: what the system must do, what data it needs, what counts as done. Fixed price where the scope allows it.
Build
Work in reviewable increments, with running code you can see rather than a status update. Assumptions are surfaced as they arise, not at the end.
Test
Independent testing against the acceptance criteria agreed in the scope, including the failure cases.
Handover
Source code, documentation and a walkthrough. You own the result and can maintain it without us.
Tell us what you are trying to build
Describe the problem and we will tell you plainly whether we can help, roughly what it would take, and what it would cost. If it is not a fit, we will say so.
Discuss Your Strategy