How it works
A repeatable workflow for turning manual strategies into code
We don't start by coding. We start by eliminating ambiguity. Then we implement with instrumentation so you can verify every trade decision.
The process
From messy inputs to audited outputs
You can send documents, screenshots, or chat exports. We convert them into a spec and an auditable implementation.
- 1Strategy intakeWe accept strategy notes, screenshots, PDFs, Telegram/WhatsApp exports, and screen recordings. NDA available for serious engagements.
- 2Knowledge extractionWe identify explicit rules and hidden assumptions (session boundaries, market conditions, exceptions, "don't trade when…" rules).
- 3Document specificationWe document the strategy in a structured Word document: entries, exits, filters, parameters, and edge cases. This becomes the contract of truth.
- 4Instrumented implementationWe code the strategy with deterministic logging: which rule triggered, why a trade was blocked, and what data was used.
- 5Backtesting + trade audit reportWe run backtests under documented assumptions (spread/slippage/fees). You receive a report plus trade-by-trade audit samples.
- 6Screenshot feedback loopYou annotate trade moments on the chart. We update the spec and the code until parity with the agreed rules is achieved.
- 7Secure deploymentWe can deploy behind Cloudflare Zero Trust for controlled access. You get a release checklist and handover documentation.
We don't guarantee returns. We guarantee engineering deliverables. A typical acceptance criterion is rule‑parity: the implementation matches the signed spec under the agreed execution assumptions.
- • Strategy rules captured unambiguously in a Word spec
- • Trade-by-trade auditability (why a trade happened)
- • Reproducible backtest runs
- • Documented assumptions and limitations
These are the templates we use internally. You can adopt them for your own strategy documentation.
- Strategy automation intake form (DOCX)
- Trading strategy specification template (DOCX)
- Backtest report template (DOCX)
Note: These templates are provided as examples. Adapt them to your market/platform and compliance needs.
- • Repainting / look-ahead bias in indicators
- • Missing "exceptions" that traders apply subconsciously
- • Backtests that ignore spread, slippage, or session rules
- • Strategies that can't be explained trade-by-trade
If you want more detail, read our tech page.
Send your notes, screenshots, or chat exports. We'll turn them into a structured specification and an auditable backtest plan.
We build software and research tooling — not investment advice. See risk disclaimer.