A SaaS platform for high-volume commodity trading on blockchain — built to serve traders, market-makers, and ecosystem partners with a single auditable settlement layer. At 3i Infotech I led the end-to-end UX. I owned UX strategy, the design system, and the trader-desk experience — the highest-stakes surface in the product.
Traditional commodity trading runs on bilateral phone calls, paper LCs, multi-day settlements, and trust relationships built over decades. For a Dubai-based commodity house targeting global supply chains, that model was no longer scalable. They needed a SaaS platform that brought institutional-grade trading UX to commodities — with blockchain settlement to remove the multi-day clearing and counterparty risk.
The platform's success was contingent on a second, equally hard problem: building partnerships across the commodities ecosystem. A trading platform with no counterparties is a brochure. From day one, the product had to onboard market-makers, exporters, banks, and clearing partners — each with their own KYC requirements, compliance regimes, and operational rhythms. Onboarding had to be fast enough that a partner's compliance team would say yes, and rigorous enough that the platform's compliance team would let them on.
"Our customers shouldn't have to choose between Bloomberg-grade UX and counterparty trust. We have to deliver both — a settlement layer they can audit, and a partner ecosystem they can rely on." — Client product head, kickoff
Core problems:
Trading-floor UX is unforgiving. Get one trade ticket layout wrong and you've taught 100 traders to make mistakes 1,000 times a day. We started with deep contextual interviews with 8 commodity traders across two desks, and a parallel sync with the smart-contract / settlement engineering team to map what state the UI could and couldn't show.
Depth on the left, chart and settlement in the middle, positions and risk on the right. Tickets sit at the bottom of the depth pane — where the trader's hand already is.
Eye-tracking proxy from interviews: traders never look more than 1.5s away from depth+chart. Every secondary surface had to fit the periphery, not steal the centre.
We borrowed institutional trading conventions where users were already trained — green = bid, red = ask, monospaced numerals, no animations on price ticks — and added a custom layer for blockchain settlement that didn't exist in our reference set.
No auto-execution. AI is purely advisory — flagging weird trades, drift on settlement, and compliance risk. The trader or compliance officer always decides.
Flags orders > 3σ from the trader's 30-day median size or > X% from VWAP. Surfaces as a modal-blocking confirm with a one-line reason.
Predicts settlement-time outliers based on network conditions and chain mempool depth. Alerts ops before SLA breach instead of after.
Detects circular trade patterns across counterparties; routes to compliance with the full trail. Compliance officer is the decision-maker.
Pre-classifies KYC documents, extracts fields, flags inconsistencies. Cuts onboarding time from days to hours; humans verify before signing off.
Illustrative numbers — I'll swap in verified figures before publishing.
Co-design the state machine with engineering on day one. Settlement statuses were a UX problem disguised as a backend problem; treating them as one made every later decision easier.
Let convention do the heavy lifting. Borrowing from institutional terminals meant traders trusted the platform on day one. Novelty for novelty's sake would have killed adoption.
Fat-finger guards as a system primitive. Once we stopped treating them as a per-screen concern and made them a token-driven primitive, every order surface inherited the protection.
Treat partner onboarding as a product surface, not an admin form. Every counterparty we onboarded fast was a counterparty the traders trusted to trade against. Onboarding UX is liquidity UX — they're the same thing on different timescales.
Closed beta with traders earlier. We had a first cohort at week 14; week 8 would have caught two layout decisions before they got expensive.
Designed compliance & ops with equal weight from day one. Trader desk got 80% of attention early; ops/compliance had to play catch-up later.
Blockchain explainability is a UX surface, not a footnote. Showing chain hash + status + finality is the difference between users believing in the settlement layer and not.