Ready-made trading bot or custom development: what to check before paying
Compare a ready-made trading bot with custom development: source rights, delivered-version checks, payment milestones and support before you commit.

A seller shows you a finished trading bot. It opens trades in the demonstration, and the report shows a profit. Another developer offers to build software around your rules. Before comparing prices, establish what each offer includes and how you will accept the work.
A ready-made bot makes sense when its rules and limits fit your task. Custom development becomes relevant when you can name a specific behaviour the available product lacks. Neither choice makes a strategy profitable by itself.
When a ready-made trading bot is enough, and when to commission one
Suppose you want decisions only after a candle closes, with no new entries once a specified loss limit is reached. If an existing bot supports those rules, the seller demonstrates them and the terms suit you, custom development may be unnecessary.
If the bot decides during the candle and you cannot change that, adjusting an indicator period will not solve the problem. Look for another product or discuss development. But “make it trade better” is not a specification. Write down the behaviour you need first; our completed trading bot specification example can help.
| What to compare | Ready-made bot | Custom development |
|---|---|---|
| Rules | Request a description and a demonstration of your required scenarios | Agree the rules and expected results before work starts |
| Changes | Establish which settings are available and what cannot be changed | Separate required behaviour from future enhancements |
| Handoff | Clarify package contents and licence terms | Agree source delivery, build instructions, dependencies and code rights |
| Acceptance | Discuss a trial or demonstration and cancellation terms | Divide the work into verifiable milestones with payment terms |
| After launch | Ask what happens when the subscription or support ends | Identify who handles defects, updates and compatibility |
These are questions for each offer. An off-the-shelf product is not necessarily closed-source, and commissioning software does not necessarily entitle you to all of its source code.
Source code, licences and costs: what will you keep?
Before paying, request a list of what the price includes: application, source, settings, instructions, test results, installation and support. List recurring subscriptions, data, hosting and third-party components separately. An unknown cost is not zero.
If independence from the author matters, ask whether another developer could build and modify this version. A folder of source files is not enough. You need dependencies, instructions and rights that permit the work. Source access does not automatically grant resale rights or exclusive ownership. Agree usage and rights-transfer terms in writing.
For a ready-made product, ask whether it will still run after payments stop and whether you can export your settings and logs. For a commissioned project, establish which libraries and services remain external dependencies. “You own the code” does not answer those questions.
Account access is a separate issue: which exchange permissions does the bot need, and why? Do not give the seller your account password or a withdrawal-enabled key for a demonstration. Installing software and allowing it to trade on a real account should be separate decisions.
Accept the version you will actually receive
An attractive report may belong to different code or settings. Ask the seller to tie results to a bot version: source or build identifier, parameters, data source, period, fees and execution assumptions. Establish which results came from a backtest, a virtual account or live trading.
Agree how you can check the product before committing: trial access, a demonstration using your scenarios or a separately paid milestone. If advance testing is unavailable, factor that limitation into the decision rather than treating a chart as a substitute.
For custom development, it helps to separate acceptance into three outcomes:
- The rules are implemented. On agreed inputs, the bot takes the expected action and does not open a new trade when the rules prohibit it.
- The delivered build starts. Your actual archive has been checked on the intended operating system and architecture, with required components and installation steps identified.
- Failure and stopping behaviour are explained. The developer demonstrates what happens when data disappears, an order is rejected or the program stops. Instructions address open orders and positions separately: closing a window does not close a position.
Do not replace technical acceptance with a demand to “show a profit.” Correctly implemented rules can still lose money. Our article on backtests, execution and live-account evidence explains the distinction.
An example from XTester. The public XTester Studio packaging guide describes building a standalone Launcher application with a strategy, its source and selected profiles. The author controls which parameters the recipient may change. This provides a concrete deliverable, not evidence of strategy quality.
The guide also describes including seller details and the seller’s own text documents. Recipients accept required documents before robot preparation; this feature needs a compatible Launcher template. The application does not write the seller’s legal terms or assess their fairness. Read them before paying, not for the first time at launch.
These capabilities were checked against documentation, not by running a purchased bot. Our guide to preparing a robot package covers the build process. As a buyer, ask the author to show the final archive, terms and startup on a matching system. Keep the delivered files and their checksums: they help distinguish versions but do not establish code safety.
Support and payment: agree what counts as completed work
“Support included” could mean answering questions, fixing bugs or changing the strategy. Ask the seller to separate these services and specify the support period and contact channel. A first-response target is not a promised resolution time.
Before paying a development deposit, agree milestones, deliverables and checks. Before buying a ready-made bot, clarify refund or cancellation terms, licence restrictions and paid updates. These are questions about the deal, not a claim that every seller must offer a trial or refund.
You can send a short request:
Please list the deliverables, available source code and usage rights, system requirements and recurring costs. Show how my required scenarios can be checked on the version you will deliver. Specify what support includes, how the work is accepted and what happens if an agreed check fails.
Once the answers are clear, compare offers for the same task and scope. If the seller sends another return chart instead, you still lack the information needed to choose. Consider a ready-made bot for behaviour that fits and terms you understand; commission development for a specific missing capability and a verifiable handoff.
This article is informational, not investment or legal advice. A backtest, source delivery and successful startup do not guarantee returns or strategy safety. Live trading can result in loss of funds.