According to Finance Magnates Intelligence, MT5 accounted for 65% of combined MetaQuotes trading volume in Q1 2026, while MT4 accounted for 35%. Brokers using these platforms have different requirements for commissions, bonuses, and risk management. MetaTrader plugins allow them to implement business rules beyond the platform’s standard settings.
Thus, custom development of plugins becomes relevant when off-the-shelf MetaTrader plugins aren’t enough. But how does a brokerage requirement become a working plugin? This article follows the development process at Takeprofit Tech, from the initial discussion and technical specification to testing, deployment, and ongoing support.
1. Discussion
We start by discussing what you want to achieve, what you have already tried, and what worked or did not work for your team. You explain the business requirements and provide relevant details about your existing setup; we work out how to implement the solution.
For example, suppose you want to award a 20% bonus on deposits of at least $500 to clients living in a particular country. We clarify the promotion’s rules: does the minimum apply to each deposit or to the total deposited during the promotion? Is the bonus available on every qualifying deposit or only the first?
These details help us define how the plugin should work before proposing a solution.
2. Brief Description
After the discussion, we put together an initial outline of how the proposed solution would work, how much it might cost, and how long development might take. The description and estimates are approximate, giving you a first view of whether the proposal fits your needs, budget, and deadlines.
For the bonus example, the proposal might cover a single promotion with a configurable percentage, minimum deposit, and country condition. Supporting several simultaneous promotions would represent a broader scope.
This is the point to distinguish essential functionality from features that could wait. If the proposal does not fit your goal, we return to the discussion and consider what could be adjusted. The estimate remains preliminary because the implementation details have not yet been fully described.
3. Technical Description
We document implementation details; you confirm that the proposed feature list is complete.
The technical description turns the agreed idea into precise behavior. It gives developers a reference for implementation and the broker a reference for checking the result.
For our illustrative plugin, the description could include these scenarios:
- An eligible client deposits $500 and receives a $100 bonus.
- An eligible client deposits $400 and receives no bonus.
- A client outside the selected country deposits $500 and receives no bonus.
The document also specifies which settings the broker can change, such as the bonus percentage, minimum deposit, and eligible countries, and describes how each setting affects the plugin’s behavior.
4. Cost and Duration Estimation
With the technical description confirmed, developers assess the complexity, development time, and estimated delivery dates. Your account manager uses this assessment to calculate project pricing, for example the MetaTrader plugin pricing for the bonus plugin described above.
Unlike the preliminary figures in the brief description, this estimate is based on the detailed requirements. You review and approve it so we can prepare the agreement.
5. Contract Signing
Once the technical description and price are confirmed, we include them in the agreement. You sign the agreement and pay 50% of the project price so we can proceed with development.
6. Start of Development
Development begins on the nearest Tuesday after we receive the first payment. You remain available for weekly testing and feedback until active project development ends.
Your participation is essential to keeping the project on schedule. Questions can arise when a written rule becomes working behavior, and timely answers help development proceed.
For the bonus example, the person reviewing the plugin should understand the promotion’s rules well enough to confirm whether the results match the intended business conditions.
7. Weekly Iteration
AI is transforming MetaTrader plugin development: since 2025, development at Takeprofit Tech has become three times faster.
We develop, test, and deliver the product to you weekly, adding more features with each iteration. You try each version to confirm that development is moving in the right direction.
Each iteration gives the broker something concrete to evaluate. Instead of waiting until the entire plugin is finished, the team can check delivered functionality against the technical description as development progresses.
A review of the bonus calculation might include an eligible deposit, a deposit below the threshold, and an account that does not qualify for the promotion.
Useful feedback identifies the action, expected outcome, and actual result. “We changed the bonus rate from 20% to 30% and made a test deposit. The bonus was calculated at 30%, but the report still showed 20%” gives developers a specific issue to investigate.
These reviews also separate errors from new requirements. An agreed condition that does not work is an implementation issue. A condition requested for the first time is an additional feature.
8. End of Active Development
Once all features have been implemented, we send you the final acceptance letter and an invoice for the remaining development fee.
You confirm that the features delivered in the final week work correctly; those delivered earlier have already been confirmed in previous acceptance letters. You then sign the final letter and pay the remaining invoice.
9. Product Live Server Tests
We install the plugin on your live server or assist your team with installation. You then run it in your trading environment to verify that it works properly.
For the bonus plugin, this means checking that it applies the configured rules to deposits on the live server: qualifying clients receive the correct bonus, while deposits that do not meet the conditions receive none. The same test helps with avoiding conflicts in a multi-plugin setup. If any other bonus plugins already run on the server, check that none of them changes the same deposits or balances. This is the final verification.
10. Ongoing Support
We provide training, configuration assistance, and bug fixes. You provide feedback and pay for support under the agreement.
Once the plugin is in use, the brokerage’s staff need to understand its settings and recognize the difference between configuration and further development.
Changing a bonus percentage through an existing setting is a configuration task. Introducing a bonus that becomes available only after a client trades a specified volume, when the plugin currently checks deposits alone, is a new development requirement. Describing that distinction clearly helps both teams assess subsequent requests.
Conclusion
A MetaTrader plugin takes shape through a sequence of agreed decisions: what it should do, which rules it should apply, which settings the broker should be able to adjust, and how it should interact with the trading server.
The broker contributes throughout the process by:
- Explaining the business rules and exceptions.
- Confirming the proposed scope and technical description.
- Testing weekly deliveries and providing specific feedback.
- Verifying the product on the live server.
This shared work connects the original business requirement to a plugin whose behavior has been defined, implemented, and checked.