Frequently asked questions
What should you settle before starting?
Straight answers about rules, testing, broker access, oversight and the limits of automation.
Bring questions before credentials
A useful first discussion covers your intended strategy, instruments, broker and the person who will monitor the workflow. You do not need to send account passwords, private keys or payment details through the contact form. We use the initial conversation to establish whether the rules are specific enough to test and whether the proposed connection appears practical. If it is not a suitable fit, we explain the obstacle rather than starting a configuration that cannot be assessed properly.
Rules and historical testing
Do I need an existing strategy?
Yes. We implement and test rules you supply; we do not select investments or invent a trading method for your account. A useful starting point states the market, signal, order type, position size and exit condition. If parts are discretionary, we can discuss whether they should remain manual.
Can a backtest predict live results?
No. A backtest shows how specified rules behave against selected historical data and assumptions. Live prices, liquidity, costs and broker responses can differ. We provide the test period, trade records and assumptions so you can examine what the result does and does not represent.
What if my rules change?
We document the current configuration before changing it. A revised rule should be tested and reviewed as a new version, particularly if it changes order sizing, instruments or exits. The time and cost depend on the scope of the change, which we discuss before starting additional work.
How long does initial configuration take?
A narrowly defined workflow often takes two to four weeks after we have complete rules and the necessary technical information. Broker access, data gaps and unresolved decisions can extend that window. We set out the expected stages and dependencies in the written scope.
Connections and responsibility
Which brokers can you connect?
Compatibility depends on the interface and permissions available to your account, not just the broker's name. We review documentation and required order types before confirming a scope. We cannot grant access, change a broker's terms or promise that a third-party interface will remain unchanged.
Do you need my broker password?
Do not send passwords or private keys through the enquiry form. If a project proceeds, we discuss the broker's supported access method, suitable permissions and how you retain control or revoke access. The connection approach must be documented and tested before live use.
Does the bot run without supervision?
A workflow can process defined conditions, but someone must review alerts, broker activity and changes in circumstances. We agree what the system should do when a connection fails and who should respond. If you cannot provide the necessary oversight, live automation may not be suitable.
Can risk controls prevent losses?
No. Position limits and pre-order checks address specified operational conditions. Market moves, gaps, execution differences and outages can still cause losses. We explain what each control checks, when it runs and which events remain outside its reach.
Scope and support
Is setup included in the monthly plan?
Recurring plans describe access and support for a defined configuration. Initial implementation may require separate work, depending on the rules, data and broker interface. We provide a written scope and final price for your approval before starting work or charging a paid plan.
What happens after handover?
You receive configuration notes and a review routine, and the agreed support plan sets out how to raise technical issues. You remain responsible for monitoring the account and deciding whether to keep a strategy active. Material rule or connection changes may need a separate review.
The most useful question is not whether a bot can place an order. It is whether everyone involved can explain why it placed one, what the broker reported and when it should stop.
Biotrons team
Still have a technical question?
Send us the outline of your proposed workflow without sharing account credentials.
Ask a question