Strategy Builder Flow

The Strategy Builder is a five-step setup wizard:

1. Basic Info
2. TWAP Config
3. Entry Conditions
4. Exit Config
5. Review and Create

1. Basic Info

What You Configure

• Strategy Name
• Market
• Entry Side

Why It Matters

• The strategy name becomes the identifier you read later in runtime and history views.
• The market defines where the workflow will operate.
• The entry side defines the initial trade direction.
• If Auto Exit is enabled later, the exit side runs opposite the entry side.

What to Watch Out For

Use names that stay readable later, for example:

• BTC EMA Cross Long
• ETH VWAP Reclaim
• SOL Breakout Long

The name does not change the strategy logic, but it does affect whether you can identify the correct strategy quickly under pressure.

2. TWAP Config

What You Configure

• Total Size
• Leverage
• Execution Interval
• Chunk Configuration
• Order Type

Why It Matters

This step defines how the strategy enters, not just how much it enters.

• Chunking splits the total size into smaller executions over time.
• Execution Interval controls the spacing between those executions.
• Order Type sets the trade-off between price control and completion.

TWAP Trade-Offs in Plain Language

• More chunks means smaller pieces, a smoother execution profile, and usually a longer overall entry.
• Fewer chunks means larger pieces, a more aggressive profile, and usually a shorter overall entry.
• Shorter intervals complete faster, but they compress execution and can behave more aggressively.
• Longer intervals spread execution out, but they keep the strategy active for longer.
• Market order type favours completion.
• Limit order type favours price control, with a higher risk of partial completion or missed fills in fast moves.

How to Use Estimated Execution

Use the estimate panel as a sanity check before moving on:

• Total Chunks tells you how many separate entry slices will be sent.
• Chunk Size tells you how large each slice is.
• Estimated Duration tells you how long the overall entry plan may run.
• Order Type confirms whether the strategy favours completion or price control.

If the estimate feels too fast, too slow, or too aggressive for the market, adjust here before you add conditions.

What to Watch Out For

• A gentle-looking TWAP can still create large risk if Total Size or Leverage is too high.
• A limit-based TWAP can look clean in the estimate and still underfill in a fast market.

3. Entry Conditions

What You Configure

Entry conditions can use:

• Indicator logic
• Price logic

Indicator conditions include:

• Indicator
• Timeframe
• Operator
• Comparison Target
• Value
• Multiplier (optional)

Comparison targets can be:

• Value
• Indicator
• Price

Price conditions include:

• Operator
• Compare To Value / Indicator
• Value
• Multiplier (optional)

Why It Matters

Creating the strategy does not start the trade immediately. Entry begins only when the configured conditions say it can begin.

If you configure more than one condition, all configured conditions must be true before the entry starts.

Plain-Language Example

Example: if you require Price above VWAP and RSI above 50, the strategy waits until both are true. One true condition is not enough.

What to Watch Out For

• Keep the logic simple enough that you can validate it from the chart and market context.
• Timeframe choice matters. A reasonable rule on one timeframe can behave very differently on another.
• Enable Auto-Exit means the position will exit automatically when the exit conditions are met. If it stays disabled, the strategy completes after entry execution and goes straight to Review and Create.
• Enable Loop Mode re-runs the full entry and exit cycle on completion until a stop condition is reached.

4. Exit Config

What You Configure

• Whether Auto Exit is enabled
• Exit conditions, when they are part of the current builder configuration

Why It Matters

This step decides what happens after entry finishes.

• If Auto Exit is enabled, the strategy continues into an exit phase instead of stopping immediately after entry.
• If Auto Exit is disabled, this step is skipped and the builder goes straight to Review and Create.
• If multiple exit conditions are available and configured, all of them must be true before the exit begins.

What to Watch Out For

• Do not assume exit begins immediately just because the final entry chunk finished. Exit still follows the configured logic.
• If Auto Exit is disabled, make sure you already know how the position will be managed afterward.

5. Review and Create

The final step is the review screen. Check the overview, the entry setup, and the exit setup if there is one. Press Create in Studio to compile the configuration into a node graph.

What Happens on Create in Studio

Pressing Create in Studio compiles everything you configured into a Strategy Studio node graph:

1. The graph is added to your Studio library.
2. Studio opens with the new graph loaded so you can inspect, adjust, and run it.
3. Any inputs the builder could only approximate (time and profit/loss conditions, TWAP slice math, limit price offsets, loop "max iterations") appear as amber note nodes and are listed as warnings — finish them by hand in Studio.

The logic maps to nodes like this:

• Market / entry side → data.candles plus the side wired into the entry exec.
• Each entry/exit condition → an indicator node + logic.compare; a cross condition uses ind.crossover.
• Entry → an exec gated to fire only when you're flat (position guard).
• Optional auto-exit → a reduce-only exec gated on being in a position.
• Total size / timeframe → frontend fields (ui.number / ui.timeframe) you can set from the order ticket.

From here the strategy runs in Studio (backtest / paper / live) or from the order form's Pro menu — see Strategy Frontends. Standalone "quick conditional strategies" are no longer created or run on their own.