Every project runs through the same five gates. You approve each gate before we start the next, and you can stop at any gate with a complete deliverable in hand. Nobody gets locked into a six-month build because they paid for a discovery call.

1. Discovery — free, 30 minutes

You describe the market, the instrument, the capital, the constraints and what you have already tried. We ask uncomfortable questions: how were the entries chosen, what data was used, what happens on expiry day, what is the worst loss you would accept. You leave with an honest read on feasibility. If the idea has a fatal flaw, you hear it here, for free.

2. Specification — the document everything else depends on

We write the strategy down in unambiguous terms: universe, session times, entry and exit conditions, sizing, pyramiding rules, stop logic, risk caps, data sources, holiday and expiry handling, and the behaviour on every failure we can think of. Ambiguity is where money leaks, so nothing gets coded until this is signed.

3. Build — readable code in your repository

Python by default, C++ where latency justifies it. Deterministic replay so a decision can always be reconstructed, structured logs for every signal including the ones that did not trade, and tests around the boring killers: partial fills, reconnects, duplicate orders, stale quotes, post-close bars.

4. Validation — the part people skip

Costs modelled per leg, realistic fills, walk-forward folds, parameter surfaces rather than single points, regime splits and stress windows. You get the report, the trade-by-trade log and the code that produced both. If the honest answer is that the edge does not survive costs, we say so in writing — that is a successful engagement too, just a cheaper one than finding out live.

5. Deploy and monitor

Containerised deployment on your cloud account with your broker credentials. Heartbeats, alerting to Telegram or email, a kill switch, daily reconciliation against the broker statement, and a runbook so you are not dependent on us at 09:15. Ongoing support is a separate, cancellable retainer — never a lock-in.

Working style

  • Weekly written status, not vague reassurance.
  • All decisions and rejected ideas logged, so future-you knows why the code looks like that.
  • Fixed scope with a fixed price, or an hourly retainer for open-ended work. Your choice.
  • NDA on request, before you send anything sensitive.