How the build process works
A build has four stages and one fixed scope. You approve the rule sheet before code is written, you see the validation report before deployment, and you keep the source.
Idea validation
The assistant collects the idea and an analyst turns it into a rule sheet: market, instrument, timeframe, entry, exit, stop, time filters, sizing and session, with a list of assumptions. You approve or change it.
Deliverable: rule sheet. You approve: the rule sheet.
02 · 3 business daysBuild
A Pine Script v6 strategy written to the approved rule sheet, with alert messages ready for an execution bridge.
Deliverable: strategy source code and alert templates. You approve: nothing at this stage.
03 · 3 business daysTests
Backtest with costs, walk forward, Monte Carlo, parameter sensitivity and a fit check against the drawdown and daily limit of your account, with a pass or not pass per test, plus a challenge pass simulation under the rules of your prop firm and account size.
Deliverable: validation report with a challenge pass simulation for the firm and account in your brief. You approve: the report: deploy, change the rules, or stop.
04 · 2 business days + first live tradeDeployment
Alerts on your chart, an execution bridge (TradersPost, PickMyTrade or PineConnector, depending on your account platform), the account connection, and the first live trade watched together.
Deliverable: alerts, bridge setup, account connection and a deployment guide. You approve: go-live.
What a validation report contains
- Approved rule sheet and data window
- Backtest: trades, win rate, profit factor, average R, net, max end-of-day drawdown, worst day
- Account fit: results against the limits of your account
- Walk forward: table of windows
- Monte Carlo: 5th percentile drawdown and net, blow rate, distribution
- Sensitivity: map of results
- Challenge pass simulation: firm, account size, rules version date, share of paths that reach the target, median days, causes of the other paths. A simulation from modeled trades, not a prediction of your evaluation result
- Verdict: pass or not pass per test, and a recommendation: deploy, change the rules, or stop
- Assumptions and limitations: costs, data, and what the tests do not detect
Challenge pass simulation. We replay the strategy's modeled trades through 1,500 Monte Carlo paths under the exact rules of your prop firm and account size: profit target, drawdown model, daily limit, minimum days and consistency rule. The report shows the share of paths that reach the target without breaking a rule, the median days to target, and what ended the other paths. It is a simulation from modeled trades, not a prediction of your evaluation result.
The report, section by section →
Communication
- Ordering: the assistant on this site, by text or voice; a brief goes to the analyst, who replies with a quote within 24 hours on business days.
- A human at any point: ask the assistant; the reply comes by email within 24 hours.
- During a build: email, one thread per build.
- After go-live (Build and deploy): 30 days of email support, reply within 24 hours.
What the service does not do
- Trade on your account, or store your login details or keys.
- Deploy a strategy that did not pass the tests.
- Promise that an evaluation is passed, that payouts follow, or that results repeat. Modeled and live results are published separately.
- Publish your rules. The build log shows an anonymized row only.
- Build for platforms other than TradingView and Pine Script.