Common questions

Questions worth asking before you automate

Plain answers about setup, responsibility, broker connections and day-to-day oversight.

Colleagues discussing automation rule conditions

Check the fit before configuring anything

Trading automation is most useful when the instructions are explicit enough to test and review. Before discussing a plan, write down what should trigger an order, what should prevent it and who will watch for exceptions. The answers below explain what Tamegallery can configure and what remains with you or an external provider. If a strategy depends on judgement that cannot be written as rules, this type of workflow may not be appropriate.

Strategy and testing

Does Tamegallery choose a strategy for me?

No. You supply the strategy and decide whether it suits your circumstances. We can help express its instructions as configurable conditions and point out ambiguities, but we do not select assets or decide which trades your account should make.

What must I prepare for a first discussion?

Bring a plain-language outline of your entry, exit and pause conditions, plus the broker and order types you are considering. Do not send passwords, account credentials or sensitive financial information. It is fine if some technical details remain open.

What does a backtest tell me?

It shows how a defined set of rules behaved against selected historical data and assumptions. Review the period, data gaps and modelled costs alongside any summary. Live orders may behave differently because markets, spreads and broker responses change.

Can I change rules after setup?

Yes, but treat a meaningful change as a new version to document and test. Altering a condition can change order behaviour in ways a previous test does not describe. We can help review the technical effect before you enable revised settings.

A practical first review

  1. Start with one strategy

    A narrow rule set is easier to explain, test and monitor than several workflows enabled at once.

  2. Read rejected orders

    A rejection can reveal a settings conflict, missing permission or broker-side restriction that needs investigation.

  3. Check external charges

    Broker and data-provider costs sit outside the platform plan unless a written proposal states otherwise.

  4. Practise the pause

    Know how to stop new submissions and how to inspect any order already held by the broker.

Connections, costs and oversight

Will every broker connect?

No. Compatibility depends on the broker's available interface, account permissions and the order types your workflow needs. We review those requirements before proposing an integration. The broker controls its own access decisions and may change its technical interface.

How long does configuration take?

A straightforward workflow or integration often takes one to three weeks after the rules and access requirements are clear. Ambiguous instructions, external approvals, missing data or additional testing can extend the schedule. We discuss the scope before work begins.

Can limits prevent every unwanted outcome?

No. Configured limits can block or pause specified instructions, but market gaps, connectivity, broker processing and the status of existing orders remain external factors. You should understand each setting and maintain an independent account-review routine.

Who watches the bot after handover?

You do. The dashboard records activity and can present available alerts, but it is not an unattended supervision service. Decide who will review exceptions and compare important events with broker records before enabling live use.

When is a plan charged?

We confirm the final price in writing and ask for your approval before charging a paid plan. Ask us to clarify the software scope and any separate broker or data-provider charges before you choose.

Broker status message checked against a workflow checklist