Strategy rules
Define entry, exit, position sizing, sessions, filters and multi-timeframe behaviour. State whether decisions use completed bars or incoming updates, and what happens when a signal repeats or a required input is missing.
Strategy & platform tools
Custom EAs, indicators and Pine Script development.
Turn a defined method into software with behaviour you can inspect. OffchainTech scopes custom strategy automation and platform tools around your instruments, account environment and operating decisions.
Rule-to-tool architecture
- 01Define the rule
- 02Resolve the instrument
- 03Apply controls
- 04Record the decision
Illustrative engineering flow. Platform support is assessed for the selected build.
01 / SCOPE
Remove ambiguity before implementation.
Your specification should explain what the system does when conditions agree, conflict or arrive late.
Platform-native tools
Scope MetaTrader EAs and indicators, Pine Script studies or strategies, cTrader cBots, calculators and trade-management panels. Each route needs a version, permitted interface and defined boundary between analysis, alerts and execution.
02 / SCOPE
Give complex instruments explicit rules.
Contract handling belongs in the specification alongside the signal logic.
Futures and options workflows
Describe leg selection, quantities, expiry calendars and rollover triggers. For multi-leg orders, decide how the system responds when only part of the intended position opens, closes or becomes tradable.
Hedging and Greeks
Where required, scope hedge calculations, Greek inputs and exposure displays with named data sources and refresh rules. Define stale-data handling and operator overrides. These are implementations of your instructions, not recommendations about which positions to take.
FROM BRIEF TO HANDOVER
A build you can review.
- 01
Capture examples
Bring written rules, annotated charts and counterexamples. Agree expected decisions for normal and ambiguous cases.
- 02
Choose the runtime
Assess the target platform, data access and execution permissions before fixing the implementation boundary.
- 03
Verify behaviour
Compare rule outputs with agreed examples, including session changes, expiry events and missing inputs.
- 04
Deliver the tool
Hand over the agreed code or build, settings guide, test evidence and clearly documented limitations.
Software tests and operational controls do not guarantee trading returns. Live access, deployment and operating limits are agreed separately.
BEFORE WE BEGIN
Questions worth asking.
Can I start with a discretionary method?
Yes, for scoping. Decisions that depend on judgement need explicit rules or a deliberate manual approval step before implementation.
Will the same rules behave identically on every platform?
That cannot be assumed. Data, event timing and order behaviour must be checked, with any differences documented.
What should I include in the first brief?
Share your platform, instruments, rule examples and desired controls. Include source code only if you have permission to share it; omit credentials.
CONNECTED SERVICES
Build around the whole workflow.
YOUR NEXT STEP
Start with your requirements.
Share the market, platform, existing system and behaviour you need. Please do not include credentials or account secrets.