01 / 03
Specification
Make every rule explicit.
We turn your written strategy into an approved specification, including entries, exits, sizing, risk limits and examples.
Independent algo development · India
Your rules.
Engineered with
discipline.
Custom strategy software and backtesting for traders who want to understand exactly what their system does, how it was tested, and where its limits are.
ALGOZ / PROJECT SYSTEM01 — 03
Method, made visible↗
01DefineApproved rules
02ValidateFresh evidence
03DeliverUsable release
NO BLACK BOX PROMISES→CLEAR HANDOVER
A considered process for custom trading software.
From a written strategy to a reviewed releaseScroll to understand the work
01 / THE APPROACH
A trading idea is only as useful as its decisions.
What happens at entry? What stops a trade? Which conditions invalidate the signal? We make those decisions explicit before writing the system that follows them.
02 / WHAT WE DO
From idea to
working system.
Each project is scoped around your rules, the evidence required, and the broker workflow you intend to use.
02 / 03
Research
Test what the data can show.
We build reproducible backtests with costs, trade logs, drawdowns and clearly stated data and execution limits.
03 / 03
Software
Ship code you can operate.
We develop documented custom software and a handover path. Any live broker integration follows the applicable approval route.
WHAT YOU CAN EXPECT
Work you can
actually review.
A release is more than a Python file. The agreed deliverables explain the rules, the evidence, the limitations, and how to operate the software.
Discuss your projectInside a typical engagementIllustrative examples
01 / SPEC
Approved rulebook
Entries, exits, sizing and exceptions written in testable terms.
Example deliverable
02 / TEST
Research record
Assumptions, trade logs, costs and failure modes in one report.
Example deliverable
03 / BUILD
Documented release
Custom code, setup notes and a clear operating handover.
Example deliverable
03 / THE PROCESS
Four steps.
Clear decisions.
We align on the written specification and how to judge it before development starts. Live deployment is assessed separately with the intended broker.
Start with a brief01
Share the rules
Describe the market, broker, conditions and desired output in your project brief.
02
Agree on the scope
We resolve ambiguity, define acceptance examples and quote for the actual work.
03
Build and verify
Your approved specification becomes code, tests and a fresh research report.
04
Review and hand over
Receive the agreed release, setup instructions and an operational walkthrough.
04 / BEFORE WE BEGIN
Good questions,
clear answers.
Do I need the complete strategy written down?
Bring the rules you have. We can clarify them during a paid discovery phase. Designing a new strategy or giving trade recommendations is a separate scope that needs additional review.
Can you connect it to my broker for live trading?
Live deployment is considered separately. The intended broker must first confirm the applicable classification, approval, API and hosting route for a commissioned algo.
Do I receive the source code?
For custom work, source code handover can be included after final payment. Your proposal will distinguish custom work from any pre-existing tools.
Does a backtest predict future performance?
No. A backtest describes historical behavior under stated data and assumptions. Live results can differ due to costs, fills, liquidity, outages and changing markets.
READY TO SCOPE THE WORK?
Start with the rules.
We’ll take it from there.
Tell us your market, broker and strategy conditions. We’ll review the brief and follow up with a quote or the questions needed to define one.