We turn trading rules you already use into TradingView indicators and strategies, MetaTrader Expert Advisors, and alert-driven order flows. We build to your specification; we do not supply strategies or trading advice.
Tell us what you needSee typical projectsAgreed in writing first, then built and handed over to you.
What we hear from businesses before a project like this starts.
The requests that come up most often for this kind of work, and what each one takes to work properly.
Your rules turned into an indicator with the plots, labels and alerts you describe, and inputs you can tune.
Entries, exits, stops and position sizing as a Pine strategy or MT5 Expert Advisor, so the rules can be tested on history.
MT4 to MT5, MQL to Pine, or MetaTrader to NinjaTrader, checked bar by bar against the original.
Alerts sent by webhook to a small service that places the order through your broker or exchange API, with limits you set.
Fills and results pulled into a sheet or database, so you can review what actually happened.
Repainting, wrong signals on live bars, or errors after a platform update, found and repaired.
Tools that come up most: TradingView, Pine Script v5 and v6, MetaTrader 4 and 5, MQL4, MQL5, NinjaTrader 8, broker and exchange APIs, webhooks, Python.
Concrete pieces, each one something you can open and check when it's done.
Indicators with your plots, labels, tables and alert conditions, and inputs for every number you may want to change.
Pine Script v5 and v6Entries, exits, stops and sizing as a strategy, so TradingView's tester can run it on history.
Pine strategy(), alertsRules executed by MetaTrader with risk limits, session filters and logging.
MQL4, MQL5, strategy testerAn indicator or strategy rewritten for another platform and compared against the original output.
MQL4, MQL5, Pine, NinjaScriptTradingView webhooks received by a small service that places orders through your broker or exchange, within limits you set.
Webhooks, broker and exchange APIs, PythonEvery signal and order logged, and results pulled into a sheet or database for review.
Google Sheets, Postgres, CSVExample packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
A written set of rules turned into a TradingView indicator with alerts.
You get
Example package
An MT4 indicator rebuilt for MT5, Pine or NinjaTrader 8.
You get
Example package
Your strategy as an MT5 Expert Advisor with risk limits and logging.
You get
Example package
Alerts from your existing TradingView setup placing orders through your broker or exchange API.
You get
A futures day trader traded opening-range breakouts by drawing boxes by hand every morning. We wrote a Pine Script v5 indicator and a matching strategy for TradingView. It draws the opening range for any session, plots session VWAP, and marks breakouts that close beyond the range in the direction of VWAP. ATR-based stops and R-multiple targets are drawn on the chart. Alerts fire by webhook to the trader's execution tool, and the strategy version runs in TradingView's backtester so settings can be tested before use.
Pine Script v5, TradingView alerts and webhooks, MQL5
A working example we built to show this kind of work. It is a demonstration, not a client project.
Sample build
TradingView indicator with EMA-cross buy/sell signals, an ATR trailing stop and alert conditions, plus an MT5 Expert Advisor skeleton trading the same rules; a Python port checks the logic and renders the chart on seeded sample data.
Pine Script v5, MQL5, Python, pandas, matplotlib, Docker
About the screenshot: The indicator logic plotted on sample price data. This is not a TradingView or MT5 chart.
The habits that keep this kind of project from going wrong.
We restate your rules in plain language in the scope and agree them before coding. Ambiguity is where most trading scripts go wrong.
Signals are checked on closed bars and live bars, and we tell you where a rule cannot be known until a bar closes.
Anything that places orders has position limits, a loss limit and a kill switch. It runs on a paper or demo account before a live one.
We build what you specify. We do not recommend strategies, manage money or claim any result.
A written scope first, then working progress you can check, then a proper handover.
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
We can't tell you that and won't claim it. We build your rules exactly as specified and show you a backtest; whether the strategy works is your decision.
No. Your rules and code are yours, delivered to you and not reused. We are happy to sign a simple confidentiality agreement.
No. For order automation you create API keys in your own account with trading permission only, never withdrawal permission, and paste them into the service yourself.
You do. You get the full source: the Pine script, the MQL files or the automation service code.
An indicator or conversion usually takes a few days to a week from the signed scope; an Expert Advisor or alert-to-order service one to three weeks.
In the 30 days after handover we fix anything we built at no charge. After that, any further work is agreed in writing before we touch it.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com