The fastest useful milestone in SteadyEdge is not creating a bot. It is creating a bot and getting a real backtest result you can inspect.

What this is

This article gives you the shortest accurate path from a fresh account to a completed backtest in the current product.

When to use it

Use this article if:

you are new to SteadyEdge
you want your first real result quickly
you do not want to manually design every part of a strategy yet

Before you start

Complete these prerequisites first:

create an account and sign in
verify your email
connect at least one validated exchange account

For speed, this article assumes you will start from a template rather than build every setting manually.

Step by step

Step 1: Open the bot builder

Go to Dashboard -> Bots and create a new bot.

If you prefer the fastest possible setup, choose a template on the first step instead of starting from a blank configuration.

Step 2: Fill the basic trading context

In the Basic step, confirm:

exchange account
symbol
side
leverage
position sizing

If you selected a template, many strategic defaults may already be filled, but you still need to confirm the account and market context.

Step 3: Make sure the strategy is valid

A useful starter bot needs more than a name. In practice, the minimum meaningful configuration should include:

at least one entry filter
a usable exit definition such as take profit or stop loss
sensible sizing for the connected account

Templates usually help by pre-populating more of this structure.

Step 4: Save the bot

Click Save Bot. Saving stores the configuration, but it does not start live trading.

After saving a new bot, the current flow returns you to the dashboard.

Step 5: Launch the backtest

From the dashboard, find your bot row and click Run Backtest.

In the current product:

the standard run flow uses an initial_balance of 1000
Free plan users can use short periods and their backtests are forced public
paid plans can access longer periods and can choose whether the run is public

Step 6: Open the result

After the run is submitted, open the Backtests workspace or follow the result link directly. The run will appear as pending, then running, then completed or failed.

What you should see

At the end of this flow, you should have:

one saved bot
one backtest record in Backtests
a visible status for that run
a result page you can return to later

Common mistakes

skipping email verification and only discovering the restriction when the run is blocked
building from scratch before understanding filters, exits, and sizing
assuming Save Bot also means Start Bot
choosing a period your current plan does not allow
treating a pending run as failed instead of queued