How we work — four stages, in this order, every time.
The process is the same whether the project is one Expert Advisor or a payment platform. You see running software at the end of stage two — not at the end of the project — and you sign off on behaviour, not on a demo.
- First contact
- Reply within one working day
- Specification
- Written, signed off, versioned
- Updates
- Written, at least weekly
- Handover
- Source · docs · support window
Specification
Requirements, rules, edge cases and acceptance criteria written down and signed off. It is the document we build against and you test against.
- A scoping call — 45 minutes, engineers on our side
- A written specification: what it does, what it must never do, how we will know it works
- Architecture and data-flow sketch, stack, environments
- Fixed price and milestones, or a monthly block with a roadmap
- NDA before any of this if you prefer
Specification document · estimate · plan
Prototype
A working build on your data, your platform and your accounts, early enough that changing direction is cheap.
- Thin end-to-end slice: the riskiest part first
- Runs on your demo server, staging gateway or test devices
- Visual debugging and logging left on so you can see why it did what it did
- Review together; adjust the specification if reality disagreed with it
Running prototype · revised specification
Build & verify
Full implementation with the evidence to prove it matches the specification.
- Phased delivery — a working release at the end of every phase
- Automated tests; for trading: tick-accurate backtests, walk-forward, forward run on demo
- For payments: state-machine tests, idempotency and reconciliation runs
- Load and failure testing where the system will face it
- Security review of data handling before anything touches production money
Release candidates · test reports · documentation
Deploy & support
Deployment, monitoring, a changelog you can read, and a defined support window with a named engineer on the other end.
- Deployment on your infrastructure or our cloud, with monitoring and alerts
- Handover: source, build scripts, runbooks, architecture notes
- Support window with response times written in the contract
- Optional retainer: a monthly engineering block for what comes next
Live system · handover pack · support window
Start with our specification template.
The same document every project of ours begins with. Fill in what you know and send it to us — or use it with any developer. The gaps become the agenda for the first call.
Trading system
Markets, entry and exit rules, risk, edge cases, reporting, testing, delivery. Nine sections, five pages.
Software project
Users, scope, integrations, data and security, non-functional needs, edge cases, delivery. Nine sections.
Three ways to work with us.
Single product
One EA, indicator, integration or app, specified up front and delivered against that specification.
Phased platform build
A system delivered in phases — MetaTrader side, service layer, client app — with a working release at the end of each.
Monthly engineering block
A standing block of hours each month for a product that keeps moving, with priority response and a roadmap review each sprint.
Pricing follows scope. Every proposal comes with a number.
Written updates, real overlap.
- A named engineer as your point of contact for the whole project
- Written progress updates at least weekly; a shared board you can read any time
- Overlap with European and US business hours guaranteed in the contract
- Demos on your environment at the end of every phase
- Your repositories, your cloud accounts, your CI — we work inside them
What we ask of you
- Someone who can answer questions about the rules within a day or two
- Access to a demo server, staging gateway or test devices at stage two
- Sign-off on the specification before build, and on each phase before the next
Start with the specification.
A short call, then a written scope with a price. No obligation either way.