DGrid OTC
Designing a token OTC marketplace from scratch — transforming fragmented community-based trading into a structured marketplace with batch buying.
Project Intro
DGrid OTC Marketplace is a 0-to-1 product design for tDGAI token trading. In the early stage, buyers and sellers relied on manual community matchmaking — low efficiency, scattered information, and no standardized market for browsing, comparing, and completing trades.
This case focuses on how I transformed unstructured OTC trading needs into a Marketplace experience with seller listing aggregation and buyer batch buying.
My Role
Product Designer
Responsible for the 0-to-1 product experience design of the OTC Marketplace.
Separated seller listing, single-purchase, and Batch Buy paths.
Designed order lists, purchase confirmation, batch buying, and transaction status pages.
Aligned with the engineering team on order, transaction, failure, and status feedback rules.
Background & Problem
tDGAI had trading demand, but early OTC trades relied on community communication. Sellers had to post listings, buyers had to find suitable orders on their own, and the process lacked a unified interface and status feedback.
Key Problems:
Short development window required reaching preliminary consensus with marketing and ops to adopt this order-book listing method.
Seller listings were scattered, making it hard for buyers to compare prices and quantities.
Single-purchase efficiency was low; large purchases required repeatedly selecting multiple orders.
Transaction status was unclear — users couldn't tell if a trade was completed.
OTC trading lacked a marketplace experience, failing to clearly present supply and demand.
Design Goal
Aggregate seller listings into a browsable trading market.
Support both single-purchase and Batch Buy sweeping.
Help users understand price, quantity, total, and expected outcomes before purchasing.
Reduce uncertainty in OTC trading through clear status feedback.
Design Process
Step 1 · Separating Trading Paths by Role
I split the trading flow into two core User Flows:
Seller Path:
Buyer Path:
Role separation allows each interface to focus on its core tasks rather than mixing all operations into one flow.
Step 2 · Transforming Listings into a Marketplace
Seller listings were organized into a browsable list where buyers could quickly see:
Available quantity
Unit price
Total amount
Seller order status
Whether it can be added to Batch Buy
Users no longer relied on community information — they could discover and compare within the product.
Step 3 · Designing the Batch Buy Mechanism
For users needing to purchase multiple orders, single-buying was inefficient. So I designed Batch Buy:
Multi-select seller listings
Show combined quantity and total
Unified transaction confirmation
Display each order's transaction status
Key Design Solution
Marketplace Listing View
Aggregated scattered seller orders into a market view, enabling buyers to browse, compare, and filter.
Single Purchase
Preserved a simple, direct purchase path for users who want to quickly complete a specific order.
Batch Buy Sweep
Enabled buyers to select multiple listings at once, reducing repetitive operations for large purchases.
Transaction Status Feedback
Visualized order status, transaction status, and failure states so users know whether a trade is submitted, processing, completed, or failed.
Result & Impact
Completed the 0-to-1 design delivery of DGrid OTC Marketplace.
Transformed community-based OTC trading into a seller listing aggregation and buyer sweep experience.
Improved buyer efficiency in finding, comparing, and completing orders.
Achieved $500,000+ trading volume in the first week of launch, validating the market demand for a standardized Marketplace.