1. Client problem
[[The situation before the project: manual execution, missed signals, an approach that could not be tested, or a component that did not exist yet.]]
Case Studies
Case studies
TimeXtrade case studies focus on the software: the problem, the requirements, the technical challenge, the architecture, the implementation, the testing and the outcome as a software result.
Publishing policy
Case studies are published only with the client's written permission and only after the facts have been checked. They describe software outcomes — for example, fewer manual steps, a repeatable testing process, or a monitored deployment — and never investment returns. Figures appear only when they have been verified.
Verified client case studies will appear here as they are approved for publication. The outline below shows the format each one follows.
Format
Custom strategy automation case study — outline
2. Strategy requirements
[[The documented rules in scope: market and instruments, timeframe, entries, exits, stops, sizing, re-entry and risk limits.]]
3. Technical challenge
[[What made it non-trivial: data handling, timing, a tricky conditional, an API constraint, or reconciliation.]]
4. Architecture
[[The modules used — strategy engine, rule processing, risk engine, execution, monitoring, logging — and how data flowed between them.]]
5. Implementation
[[How the rules were built and organised; key decisions; how configuration and credentials were handled.]]
6. Testing
[[How the implementation was validated against the specification: historical replay, sensitivity checks, and cautious live testing with small size.]]
7. Result (software outcome)
[[Stated as a software outcome only — e.g. "reduced manual execution steps by X" — and only if verified. No investment-return claims.]]
Want your project documented this way?
We can agree upfront whether, and how, a case study is published.