How to Use the Strategy Builder

There’s a particular kind of trader who hears “no-code strategy builder” and immediately assumes it means “toy version of the real thing.” Fair skepticism. Most of them are. Ours isn’t, and this is the walkthrough that proves it.

The building blocks

A strategy in TradeFIQ isn’t one big form you fill out top to bottom. It’s assembled from small, reusable pieces, each one saved on its own so you can mix and match them across different strategies later instead of rebuilding the same logic five times:

• Entry config: the conditions that decide when a trade opens
• Exit config: the conditions that close it, plus an optional timeout
• Execution config: market or limit orders, a price offset, and retries
• Indicators & Signal config (optional): extra indicators, each with a weight, that add up to a confidence score. The trade only opens when the score clears your threshold

Stop-loss, take-profit and position size live somewhere else on purpose: in a risk profile, which you pair with a template when you create an automation. More on that below.

You build each of these once in Strategy Templates, then compose them into a runnable template. Change your mind about an exit later? Update the exit config once, and every template using it picks up the change. This is the part people usually don’t expect from a “no-code” tool, and it’s the part that actually matters once you’re managing more than one or two strategies.

Setting up your entry conditions

Entry conditions are where most people spend most of their time. This is the logic that decides whether a trade happens at all. The condition builder lets you combine rules like RSI (14) is below 30 and Price is above EMA (200) without writing code. It offers around 30 indicators and candle patterns, from RSI and MACD to Supertrend, Ichimoku and Smart Money Concepts. If you can describe your entry rule in a sentence, you can build it here.

A tip that saves people a lot of grief later: start simple. One or two conditions, not seven. Every extra condition you stack on is one more way your strategy quietly never fires because the market just doesn’t line up with all of them at once. You can always add more once you’ve watched it run for a while.

Configuring exits

This is, unfashionably, the more important half of the strategy. Anyone can pick an entry signal. What decides whether you make money is how disciplined your exits are.

An exit config holds the signal-based ways out, like RSI (14) is above 70, and an optional timeout that closes a trade after a set number of candles. Your hard safety net goes in the risk profile you pair with the template: a stop-loss (fixed, percentage or trailing) and, if you want one, a take-profit. Set a stop-loss. Not “I’ll watch it closely”: an actual stop-loss, enforced at 3am while you’re asleep and the market absolutely does not care.

Some strategies prefer to let winners run with a trailing stop instead of a hard target. Both are supported. Pick whichever matches how you think about risk, not whichever sounds more sophisticated.

Execution details

This is where you choose market or limit orders, a price offset for limits, and how many times to retry an order that doesn’t go through. Market orders fill right away at whatever the book offers. Limit orders protect your price but may not fill in a fast market. There’s no universal right answer. It depends on what you’re trading and whether you care more about getting filled or about the exact price.

Position size is set in the risk profile, and every automation also gets its own capital budget: trades are sized from that budget, never from your whole balance.

Putting it together

Once your building blocks exist, the composer is where you assemble them into a template: pick your entry, exit, execution and (optionally) indicators config, give it a name, and save it. Symbols, timeframe and market (spot or futures) aren’t part of the template. They’re chosen per automation, so the same template can run BTC/USDT on one automation and ETH/USDT on another without duplicating anything.

From there, head to Automations to actually automate it, or run a backtest first if you want to see how it would have performed before it touches real money. Most people should do the backtest first. Most people don’t. Be the exception.