Skip to content
Funded EngineeringCustom EAs and MQL5 engineering Free diagnosis

Your rules, built into MT5.Checked trade by trade before it goes live.

We build MetaTrader 5 Expert Advisors from your written rules, then check every trade against them on your broker's tick data. You see the report before the final payment.

Get your free diagnosis on Telegram

Opens t.me/fundedengineering. Tap Message and send rules, or anything you like. The word just tells us which build you read.

An EA built from 9 written rulesMT5 Strategy Tester · real ticks
Trades a checker written from the rules expected248
Trades the EA took248

0 rule breaks in 7 checks. Run twice with the same .ex5, 0 different trades.

Read the 13-page report (PDF)
  • Each build here links to its full report
  • Written contract before any payment
  • Final payment after your own test
  • No signals, no performance claims

The verified build

Code that looks right is easy. Code you can check is the job.

A coder, or an AI, can write an EA that compiles and trades. The hard part is knowing it trades your rules and nothing else. Every build here is made to show that.

  1. Your rules, as decisions

    We rewrite your rules as numbered decisions. Every gap, like a touch or a close, gets resolved in writing before any code.

  2. The code

    MQL5 for MetaTrader 5, with your limits as settings you can read and change.

  3. A trade-by-trade match

    Every trade compared with a reference: a checker written from your rules, your TradingView list or your SQX list. On your broker's tick data.

  4. Your risk rules, one by one

    Daily and total loss limits, news windows, sessions and position caps, each one tested in the MT5 Strategy Tester.

  5. A log of every no

    When the EA skips a signal, the log records which rule stopped it and when.

  6. Your MT5 first

    You run it on your own terminal before the final payment, with the report in hand.

What each project includes is listed in its written quote. The risk-rule checks and the decision log come with the builds that need them.

Measured builds

Three builds. One figure each, and the full report behind it.

Measured in the MT5 Strategy Tester. Each report states its data, its tick quality and its limits. A backtest is a simulation of the past. These reports show whether an EA follows its rules, not whether a strategy makes money.

Cover of the report: An EA coded from 9 written rules. Verification report.
Cover of the 13-page report

248 of 248

Written rules to EA

9 written rules. A checker built from the rules alone expected 248 trades. The EA took the same 248.

XAUUSD M15 · Jan 2025 to Oct 2026 · 13 pages

Read the report (PDF)
Cover of the report: From TradingView to MT5, trade by trade. Verification report.
Cover of the 8-page report

520 of 637

TradingView strategy to MT5

A direct conversion matched 280 of TradingView's 637 trades. The MQL5 version we built matched 520 on entry, side and exit. The report gives the cause of each of the other 117, 85 of them by design, and of the 48 extra trades it took.

XAUUSD H1 · Jan 2025 to Oct 2026 · 8 pages

Read the report (PDF)
Cover of the report: Why the EA said no. Every rule's verdict logged on every bar.
Cover of the 8-page report

626 of 1,202

A decision log inside the EA

A gold EA took fewer trades than its signals. The log built into it showed it stopped 626 of 1,202, and the top reason, 465 times, was not a filter. Its own trade was still open.

XAUUSD H1 · Jan 2025 to Oct 2026 · 8 pages

Read the report (PDF)

The difference

Where a quick code job stops, and a verified build keeps going.

TopicA quick code jobA verified build
Starting pointYour description, read the way the coder reads itYour rules as numbered decisions, every gap resolved in writing with you
Proof it matchesA backtest screenshotEvery trade compared with a reference, each mismatch with its cause
FillsAssumedMeasured on your broker's tick data
A skipped tradeYou guess whyThe log names the rule and the time
If it can't be built as writtenBuilt anywayWe say so before you pay, with what can be built instead
PaymentOften upfrontMilestones after a written contract, the last one after you test it

What you receive

A build you can check, not just run.

  • The written spec. Your rules as numbered decisions, agreed before coding.
  • The EA. The .ex5 licensed for your own use, your limits as settings. Source code with a transfer of rights when your project includes it.
  • The verification report. Trade by trade against the reference, on your broker's tick data, with every difference explained.
  • Installation guide and settings. So it runs the same on your terminal as in the report.
  • A correction period, set in your contract. If the EA departs from the spec in that time, we fix it at no extra cost.

What we don't do

  • Promise results. We build software that does what your rules say.
  • Sell signals or manage anyone's money.
  • Decompile an EA. We only change code you own or have the right to change.
  • Tune a strategy to look good in a backtest.
  • Ask for your logins, passwords or payment before a written contract.

How an engagement runs

The final payment falls due only after you have tested the EA.

Every project is quoted in writing for your case, after the free diagnosis. A typical build takes 1 to 3 weeks once the spec is agreed.

  1. Free diagnosis

    Send your rules, .pine, SQX list or EA. Usually within 48 hours of your material, you get every gap we found and what a verified build would involve.

  2. Written quote

    Options with scope, deliverables, milestones and dates.

  3. Contract, then milestones

    Nothing is paid before a written contract.

  4. You test it

    On your own MT5, with the verification report.

  5. Final payment

    Only after the build does what the spec says.

Questions

Before you message us.

Do you promise results?

No. We build software that does what your rules say, and we show you that it does. Whether the rules make money is your strategy's question, and a backtest is a simulation of the past.

What do I send for the free diagnosis?

Whatever you have: written rules in any format, a .pine file, an SQX strategy or trade list, or your EA's source code, plus the broker you use. Message us on Telegram and send the word shown on this page.

Is my strategy kept confidential?

Yes. Your rules, files and reports are used only for your diagnosis and your build. Nothing is published or reused without your written consent, and the same commitment goes into your contract. You can start with a summary of your rules and send the full detail once you decide to go ahead.

What if my rules can't be built exactly as written?

We tell you in the diagnosis, with the reason and what can be built instead. Sometimes the honest answer is that it can't, and you hear that before you pay anything.

Why not use an AI or a faster coder?

You can get code that compiles that way. What you won't get is evidence that it trades your rules and only your rules. When we converted a Pine strategy directly, it matched 280 of 637 trades. Closing that gap took measuring every trade, and it stays invisible until someone does.

Do you work from Pine, StrategyQuant or MT4?

Yes. We move TradingView and StrategyQuant strategies to MT5 with a trade-by-trade comparison, and migrate MT4 EAs to MT5. The published case is a Pine strategy. SQX and MT4 builds are checked the same way, against your own trade list.

I already run an EA. Can you help?

Yes. With its source, we can add daily and total loss limits, news windows and session rules without changing its signals, and show you, as part of the delivery, that with the limits set to neutral it takes the same trades as before. With only the .ex5, we can still audit what it does by running it in the tester and reading its history, though not why it does it rule by rule.

Who owns the code?

You get the .ex5 licensed for your own use. Source code with a transfer of rights is available and quoted in writing.

What happens after delivery?

A correction period starts on delivery, with its length in your contract. If the EA departs from the spec in that time, we fix it. Changes to your rules after that, or a rebuild for a new MT5 version, are quoted as new work.

What does it cost?

Every project is quoted in writing for your case, after the free diagnosis, with milestones you can see before you commit.

How do I know it's really you?

Our only official contact is the direct messages of @fundedengineering on Telegram. Anyone else who writes to you as us isn't us. We never ask for payment before a written contract, and never for your logins or passwords.

Send your rules. Get the diagnosis.

Every gap in your rules marked, what a verified build would involve, and a written quote. Free, with no obligation to go ahead.

Get your free diagnosis on Telegram

Tap Message and send rules, or anything you like.

Follow the measured builds on Telegram