Skip to content

Case study

Bet Collector

Prediction market data was spread across venues and tabs. Bet Collector pulls venues like Polymarket and Kalshi into one table first workspace for people who check odds often.

Visit project →

The problem

Most market people do not lack information. They lack one place that still makes sense on Friday afternoon.

The product had to be fast to scan, easy to return to, and clear that it is a workspace, not a crystal ball.

The challenge

The scope sounds small until you account for messy sources, duplicates, and the fact that people quit anything that feels like extra admin.

We also wanted a tone that felt professional without cosplaying a bank terminal.

What we did

We started with discovery and comparison: what moved, where it trades, how you find it again without building a taxonomy science project.

We kept the UI spare, biased toward repeat use over first visit fireworks, and labeled sources clearly when data came from more than one venue.

When integrations failed, we treated that as normal: visible errors, retries, no silent drops.

Outcome

Sessions got lighter cognitively. The app stayed out of the way unless it was helping someone resume where they stopped.

The win is modest on purpose: fewer lost threads and less duplicate work during a noisy week.

Technologies used

  • TypeScript
  • Responsive web app
  • Authentication and account boundaries
  • Multi venue market data (Polymarket, Kalshi, and similar)
  • Search and dense tables