Broker switch post-mortem: what improved and what did not
Posted: Tue Oct 06, 2026 7:02 am
I switched raw accounts once last year after a month of rising reject rates on stops during London open.
What improved: fewer rejects, slightly tighter median spread on EURUSD in the first hour, and a deals tab I trusted more for forensics.
What did not: my expectancy. Same playbook, same mistakes, same revenge click after CPI. The broker was not the edge. Execution pain had been a convenient story.
Post-mortem rule I keep: after any switch, run thirty live sessions before declaring victory, and keep the old account's cost log for comparison. If behaviour metrics are unchanged, the switch was plumbing, not progress - which can still be worth it, just name it honestly.
I also kept size unchanged for those thirty sessions. If you size up to celebrate a switch, you will not know whether execution or behaviour moved the needle. If rejects return after the switch, I reopen the post-mortem instead of assuming I imagined the old problem. The honest label for most of my switches is "plumbing upgrade". That label keeps me from rewriting the playbook every time the login changes.
What improved: fewer rejects, slightly tighter median spread on EURUSD in the first hour, and a deals tab I trusted more for forensics.
What did not: my expectancy. Same playbook, same mistakes, same revenge click after CPI. The broker was not the edge. Execution pain had been a convenient story.
Post-mortem rule I keep: after any switch, run thirty live sessions before declaring victory, and keep the old account's cost log for comparison. If behaviour metrics are unchanged, the switch was plumbing, not progress - which can still be worth it, just name it honestly.
I also kept size unchanged for those thirty sessions. If you size up to celebrate a switch, you will not know whether execution or behaviour moved the needle. If rejects return after the switch, I reopen the post-mortem instead of assuming I imagined the old problem. The honest label for most of my switches is "plumbing upgrade". That label keeps me from rewriting the playbook every time the login changes.