Book a scoping call →
Solutions by outcomeNever miss work26Every call, lead and enquiry answered, routed or captured.Get paid faster32Money collected, matched and reconciled without chasing.Fill the diary12Fewer no-shows, fuller weeks, less phone tag.Answer without staff16The repeated questions handled, the rest escalated.Join up the systems77Data entered once, moving everywhere it is needed.Verify and secure15Real customers in, fraud and fakes out.Prove you are compliant8Obligations met by default, evidence captured automatically.Run it for me12Someone watching, someone answering, every month.
Solutions by capabilitySMS & messaging28Voice & call flows22Verification & identity13WhatsApp & chat5Video & telehealth4Email & notifications4Flow automation3Unified conversations2Contact centre5Delivery & tooling2Compliance & records5Workflow automation49Trade & job management8Applied AI8Self-hosted platforms7Payments & billing29Run it for me4
All 198 builds Describe it in plain English Venture models Instant scope & price Free tools Search everything Connections Integration guides Workflow library By integration Partnerships Contract roles Honest comparisons Field notes Work we have built Colabs How it works Platforms & licensing Pricing Book a scoping call
Home / Work / ICT Trading Indicator & Strategy Suite
Trading tools Colabs venturePublished

ICT Trading Indicator & Strategy Suite

A 35-model ICT engine in Pine Script, plus 70 single-model builds sharing one core.

What we set out to build

To turn a large body of discretionary trading methodology into something mechanical, testable and publishable.

What was built

  • A master engine implementing 35 models with a strategy twin for backtesting
  • 70 single-model files sharing one engine, so a fix lands everywhere at once
  • A 30-setup indicator with a bias engine, market-structure breaks, trade boxes and a performance dashboard
  • A multi-timeframe fork running the engine at higher timeframes
  • A port of the model suite into Python for real backtesting against the research engine

What it achieves

  • The suite runs inside a hard platform ceiling of 100,256 compiled tokens, which required measuring every version against the limit rather than discovering it at compile time
  • The Python port makes the models testable with the same statistical rigour as every other strategy in the research engine, rather than being judged by eye on a chart
The hard part: Pine Script has a compile-token ceiling that inlining blows through fast. Fitting a 35-model engine underneath it, twice, meant treating token count as a design constraint from the start.

The stack

Pine Script v5/v6, Python.

Common questions

How was this built?

This was built through Colabs, our sister company. A founder brought the idea and the domain knowledge, Colabs brought the team, the founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.

What state is it in?

Published. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.

Can you build something like this for us?

That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.

Where to next

If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.

Want something like this built?

The catalogue prices the patterns behind this work. Describe your version and the engine will scope it, including an allowance for anything nobody has costed.

Describe it in plain English → See all work