Primary commercial product
TradeBroker
Collectibles intelligence, portfolio, trading, inventory, and marketplace infrastructure.
A connected product suite for collectors, stores, and market participants—built around real market data and the operational work that happens after a price lookup.

Public, sanitized project material.
The problem
Why it exists
Collectibles businesses and serious collectors rarely have one clean system of record. Catalogs, prices, binders, inventory, customer trades, and sales workflows tend to live in separate tools.
The hard part is not displaying a card. It is keeping identity, condition, ownership, valuation, and operational state coherent as an item moves through real workflows.
- Public material intentionally omits proprietary pricing and matching logic.
- No customer information, confidential data sources, or production topology is disclosed.
Architecture
Operating model
Capabilities
What it does
Security
Trust model
- Commercial data and proprietary logic stay behind explicit product boundaries.
- Public portfolio material is intentionally architectural rather than operational.
- User and store workflows are separated from administrative control surfaces.
Tradeoffs
Key decisions
A platform, not a feature pile
Portfolio, scanning, trading, and inventory share the same item identity and valuation model instead of becoming disconnected mini-products.
Operational truth over demo polish
The product is shaped by cycle counts, ambiguous scans, changing markets, and the messy edge cases of real collections.
Current state
Current state
- Multi-game catalog and collection surfaces
- Market pricing and valuation workflows
- Store inventory operations
- Scanning and AI-assisted identification
- Broader marketplace connectivity
- More store-side operational automation
- Deeper liquidity and portfolio intelligence
Lessons
What the work clarified
- A trustworthy product needs a coherent data model before it needs more screens.
- Market information becomes useful only when it is connected to a decision or workflow.
- Closed product logic and reusable infrastructure need deliberately different boundaries.