Quod Financial has put Qanvas into general availability, offering buy-side and sell-side trading desks a way to specify changes to their front-end workflows in natural language. The London announcement, dated 28 October in the release itself, concerns the interface and workflow framework used with Quod's order management, execution management and smart order routing products. It does not describe an artificial-intelligence system making autonomous order-routing decisions.[1]
The separation is the critical engineering detail. Quod says the AI-led development process generates and tests new displays and workflow features, while execution, routing and risk calculations remain within a deterministic and auditable underlying core. A trading desk may be able to modify the way orders and positions appear without altering the engine that decides how a valid instruction is handled.[1]
As evidence of deployment speed, Quod reports one request progressing to validated and merged code in four hours and 33 minutes. The firm also says it rebuilt its own trading front end in six weeks, replacing a conventional development effort that had taken two years. Those are vendor-supplied examples, not independently benchmarked delivery times across customer installations.[1]
Quod also reports about 950 features delivered over five months by staffing equivalent to 1.4 engineers. Those inputs imply roughly 136 features per engineer-month. They do not substantiate the same release's separate claim of about 50 features per engineer-week: a five-month period is roughly 22 weeks, giving about 31 features per engineer-week on the stated totals. The release does not explain that difference or provide a standard definition of a feature, so the figures should be treated as supplier examples rather than a comparable productivity benchmark.[1]
Where a broker must still perform due diligence
How to read Quod’s published performance figures
| Metric | Reported scope or limitation |
|---|---|
| 4 hours 33 minutes | One feature, request to validated and merged code |
| Six weeks | Vendor’s own replacement front-end build |
| About 950 features | Vendor-reported delivery over five months |
| 1.4 engineers | Vendor-stated equivalent staffing for that period |
| Execution decisions | Remain in Quod’s deterministic core, according to the vendor |
The claimed advantage is most straightforward for user interfaces: adding blotter fields, changing sales-trading views or normalising display across equities, FX, listed derivatives and digital assets. Operationally, a broker would still need to test permissions, latency, audit trails, order validation and any interactions between the revised interface and the unchanged execution engine. A fast merge is not equivalent to approval for production use by a regulated customer.[1]
Quod says it now has a unified interface across those asset classes. That is a vendor description of product capability, not evidence that every client has deployed each connection or replaced a legacy platform. Equally, the core/front-end distinction should not be mistaken for a blanket assertion that AI-generated front-end code is risk-free: incorrectly presented order size, currency or price information could create an operational problem even where the routing engine is deterministic.[1]
For procurement teams, the most useful questions now are how changes are tested and signed off, what version and rollback controls are available, and whether the supplier can show comparable demonstrations using the customer's own workflows. The release confirms availability and describes Quod's internal results; independent customer-wide deployment metrics were not supplied.[1]
Sources & further reading
- Qanvas launch and general-availability announcement Quod Financial · 28 Oct 2026 · Accessed 30 Oct 2026
- The collapse of the capital-markets software vendor and the rise of the trading desk Quod Financial · 1 Oct 2026 · Accessed 30 Oct 2026