How It Works
You describe the strategy. We build the preview before we talk. The call is for decisions, not for watching us type.
From form to delivery
-
01
Day 1
You describe it
About 10 minutes: your rules step by step and 3 screenshots of your best setups. Then you pick a call time.
-
02
Before the call
We build your preview
Coded in Pine Script v6 with Claude Code, backtested, with 2–3 improvements noted.
-
03
30 minutes
The call
The preview, the backtest verdict and the improvements.
-
04
Your decision
Deposit
If you go ahead, a deposit agreed on the call locks your build slot.
-
05
Scoped on the call
The build
Coding, research, optimisation and automation, with a weekly update.
-
06
Delivery
Handover
Code, dossier and live deployment. The balance is due on delivery.
-
07
14 days
Support
Help with bugs, alerts and deployment questions.
Why we don’t code live
Live coding turns your call into a screen-share of someone typing.
Strategy code needs testing, and testing takes time. When the preview is built beforehand, the 30 minutes go to what matters: does it work, and what would make it better?
You see a finished preview, a verdict and a clear next step — instead of half a script and a promise to “finish it later”.
What happens on the call
30 minutes, four parts.
- 5 minYour strategy, in your wordsWe confirm we understood your rules before showing anything.
- 10 minThe previewThe code, the inputs, and how it trades on your chart.
- 10 minThe verdictBacktest results and the 2–3 improvements we’d make.
- 5 minYour next stepBuild it, fix it or drop it — and what the Full Research Build would add.
If it’s broken, we’ll tell you.
Most strategies have a weak spot.
An exit that gives back too much. A filter that never fires. A market it doesn’t suit. The preview is where those show up — before you spend anything.
If the backtest says drop it, we’ll say drop it, and we won’t sell you a build on it. If it can be fixed, we’ll show you where.
After you decide
Timeline is scoped on the call, with an update at the end of every week.
- KickoffWe lock your rules in writing first, so nothing gets coded on assumptions.
- Weekly updatesWhat was built, what was tested and what the data says — every week until delivery.
- DeliveryFull Pine Script v6 source code, an input guide, the research dossier, the before/after optimisation report, and your automation set up and live-fire tested on your account.
- Support14 days after delivery for bugs, alerts and deployment questions.
Describe it once. See it coded.
About 10 minutes now, and the preview is ready when we talk.
No course. No signals. Code is yours.