Selected Work Case Study 02
OTC Pricing & Market Intelligence — From Fragmented Data to Execution Decisions
A dealing-desk design for comparing market observations, judging visible liquidity and deciding whether a reference price is useful for an OTC quote.
A price from one venue and a price from another may describe different instruments, settlement obligations or moments in time. Even when the prices are comparable, the better offer can be available for too little size to inform the requested quote.
Project context
The public project description concerns market observation and decision support: interpret fragmented inputs, assess spread and liquidity, and provide context for pricing decisions. The workflow below describes a read-only analytical view. It establishes no supported venue list, live-feed guarantee, order-routing capability or hedge automation.
Conceptual workflow
From market observation to desk review
Observe the market
Keep venue observations distinct. Identify the instrument, quote currency, bid, offer and any available size and timing context.
Check comparability
Align units and settlement terms. Flag observations with missing or stale timing, uncertain instrument mapping or unusable depth.
Assess liquidity for size
Compare spread and visible depth. Estimate a size-specific price only if the relevant side of the observed book has enough quantity.
Review the quote
Show the benchmark and its limits to the desk. Separate the reference observation from a price the desk is prepared to quote.
Design decisions
Preserve meaning before averaging prices
A last trade, a midpoint and a best offer answer different questions. Preserve instrument type, pricing currency and supported size before comparing like observations. A different settlement obligation can make an apparent price difference economically meaningless.
Separate spread from size-dependent cost
The best bid and offer define the quoted spread. A volume-weighted price for a hypothetical book sweep uses the quantities actually available at each level. If available depth cannot fill the intended quantity, report the shortfall instead of supplying a full-order estimate.
Show what makes a reference usable
A decision-support view can distinguish fresh, comparable observations from stale, incomplete or non-comparable ones. Show the reason for exclusion and the size to which an estimate applies. A single price without that context invites comparisons the data cannot support.
Operational risk and reliability
Source event time and local receipt time describe different things. A recent response may contain an old observation, and a quiet book is not automatically stale. A book snapshot can also change before any order arrives. Use any static estimate as an analytical reference; an OTC commitment additionally depends on fees, access, quote validity, settlement terms and counterparty exposure.
Contribution
Seyed Iman Hosseini’s documented focus is pricing intelligence, market-data interpretation and dealing-desk workflows for execution decision support. The public project description does not allocate component-level implementation responsibility.
What the design teaches
A useful reference price carries its instrument, side, size and assumptions with it. The public simulator demonstrates the book arithmetic, and the independent pilot illustrates the limits of observed data. They are separate work, not evidence of this project’s deployment or performance.
Related insights
- Liquidity in Fragmented Markets
Learn why available depth depends on access and where inventory is held.
- Trading Infrastructure & AI
Distinguish feed liveness, freshness and integrity.
- Order Book Execution Simulator
Test the effect of order size on an editable synthetic book.
- Iran Digital Asset Liquidity & Execution Pilot
Read the 30-minute observational study and its limits on interpreting estimated execution costs.
Discuss the work
For professional conversations on execution, financial operations and market infrastructure.