Already built it? Send the file.
If your strategy exists as code — NinjaScript, thinkorswim Thinkscript, Python, Pine Script, or plain text — you don't have to re-describe it in the form. Upload the file. We read it, map it to the engine, and send the mapping back to you in plain English before anything is scored. Nothing runs until you say the mapping is right.
Same product, same price. $49 a report. Nothing else to buy.
Because your code and our engine are different machines, and translation between them has to be checked by the one person who knows what the rule is supposed to do: you. The mapping we send back lists exactly what will be tested and, just as importantly, anything in your file the engine can't test — a disabled block, a broker-specific setting, a feature outside our model. You look at the list, tell us it's right or it isn't, and only then does it run. The mapping is a contract: your source is translated to one of nineteen engine families with explicit parameters, and every construct that doesn't survive translation is itemized in a DROPPED list with a reason — irrelevant, unsupported, or material. You approve or correct the mapping before execution. If a dropped item is material to the rule's identity, the honest answer is that the wizard can't test it and we'll say so rather than score a different strategy than the one you wrote.
Three steps, and you hold the middle one
Send the source
One file, up to 1 MB. Include your email. If you know how many versions of the idea you tried before this one, say so — the report discounts for it either way.
Approve the mapping
You get an email listing what will be tested, in plain English, plus everything in your file the engine can't test and why. Nothing is scored until you reply and confirm.
Same test as everyone
Your rule runs through the same engine, the same coin-flip twins, the same costs, the same unseen years. Score, verdict, and plain answers — identical to the form door.
The honest scope
This door is for single-rule intraday futures strategies — roughly what the form on the front page can express, arriving as code instead of clicks: one entry idea, one exit model (which can combine a stop, up to two targets, a move to breakeven and a trailing or chandelier stop, with the clock as backstop), up to three conditions, on one-minute bars or any bar size up to an hour. Length is not the test. A NinjaScript or Thinkscript strategy carries a lot of boilerplate and can run a thousand lines and still be one rule; we read all of it. What belongs elsewhere is a portfolio of strategies or a full framework, which is an audit conversation, not a report.
If your file is a multi-leg system, an indicator stack, a portfolio, or something discretionary wearing code's clothing, we won't pretend it fits. We'll tell you in the mapping email, and if you want it examined anyway, that's a human audit — a separate engagement, $499, by request only.
Files we read: .cs (NinjaScript) and .py are mapped by the engine’s reader; .ts (Thinkscript, or paste it into a .txt), .pine and .txt are mapped by hand, through the same confirmation step, and take a day or two longer. Comments in your code are read as testimony — if a comment says which years you developed on, the report treats those years as seen.
Upload your strategy
Four fields and a file. The mapping comes back to the email you give here.