Managing Requirements, Testing, and Payments in Trading Strategy Outsourcing
Summary
This first-person account describes problems encountered when commissioning a custom trading strategy through a community marketplace. The author says the requirements were fixed, the quoted price was accepted, and deadline extensions were tolerated, yet the project still ended unsatisfactorily. The advice focuses on reducing ambiguity before work starts: discuss each requirement in detail, agree on timelines and acceptance expectations, and use voice or remote conversations when written descriptions are unclear.
The author also recommends having the developer test the complete workflow before acceptance, rather than relying on incremental checks or claims that a problem is due to the client’s use of the software. The payment guidance is to avoid releasing the final installment solely because a delayed developer requests it; tie payment to agreed deliverables and testing. This is an individual anecdote, not a systematic assessment of providers or a trading method, but it offers practical project-management lessons for commissioning algorithmic trading software.
Key ideas
- Clarify the complete strategy specification and acceptance criteria before paying or development begins.
- Agree on a delivery schedule and connect final payment to completed, verified deliverables.
- Ask the developer to test the full workflow before acceptance and conduct the client’s own checks.
- Use direct voice or remote discussions to resolve technical requirements that are difficult to explain in writing.
- The recommendations come from one client’s experience and do not compare providers systematically.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.