What to put in your request, how to read private replies, and how scope and deliverables are agreed.
Service Guides · Updated 2026-10-09
Development implements trading rules you define as code, a strategy file for the tool or a backtest report. It does not recommend strategies or parameters or guarantee returns. We do not manage customer accounts or receive API keys.
Choose the markets and describe the trading universe, entry rules, exit rules and deliverables. Capital rules and the backtest period and benchmark are optional. Explain what is still undecided; open questions can be clarified during review.
You can attach images, PDF, code, Excel or CSV reference files: at most 10 MB each, 20 MB total and five files. Executables and macro-enabled files are not accepted. Never include passwords, API keys or account credentials.
After submission, keep the receipt number and access key. Together they open your private thread, where questions, replies, progress and result files appear. Do not share the access key with other people.
We review the request, clarify open questions and prepare a rule sheet. Confirm the universe, order timing, allocation, costs, supported environment and deliverables. Scope, price and revision terms must also be agreed before work starts. Submission alone does not confirm development or delivery.
A verified license that includes development is handled within its quota. Missing, expired or exhausted licenses result in a quote enquiry. The raw key is not stored. Payment and next steps are arranged through Kmong; this site takes no payment. Check the current sales status and supported scope.
Research explanations are educational, not investment recommendations. Development implements rules defined by the customer; work scope and payment are confirmed separately.