Proof in production

StreamGist from 0 → 1.

StreamGist helps streamers pick games to play and turns their choices into a demand read for game studios, live in production.

StreamGist bar chart of save rate by game quality against a 21.4% baseline, with 95% confidence ranges. Chat-interactive games are saved at 29.7% and horror at 26.6%, above baseline; deep or study-heavy, MMO-scale, and aggressive monetization fall below, down to 16.3%.
Streamer Demand Report, August 2026 edition. Save rate by game quality against a 21.4% baseline, with 95% confidence ranges.

Demand read

Every save and skip becomes a demand signal.

Streamers save or skip each recommendation. In aggregate, those choices show game studios which qualities pull saves, measured against a baseline with confidence ranges. It is a demand read, not a forecast.

Read the demand reportOpen the live product
26×go-live rate for saved vs. skipped games, in backtest
3,000+games scored each week
Dailyrankings for smaller channels, from competition, viewer spread, and saves

Why it matters

The company runs on its own execution system.

Early on I directed contract engineers, designers, and SEO help. Now I run the company alone: agents do research, monitoring, and engineering, a second model reviews every change, and I approve it.

The customer-facing core is plain, testable code, so a model failure can't take down the product.

Representative agents

Each agent has a different job and the same controls.

Three of the agents that run StreamGist. Each has defined inputs, code-enforced controls, and reviewable outputs.

Selected production agents
Research

Game enrichment agent

Public game sources become a structured research record after required-field and completeness checks.

Monitor

Recommendation quality agent

User choices and stream results are checked against preset quality and alert rules to produce a daily quality read.

Brief

Operations monitor agent

Daily checks on infrastructure, product health, and revenue. AI writes the briefing, and a person decides what to act on.

Public documentation

Inspect how StreamGist operates.

Two public pages go deeper.

The operating model

See how recurring signals become reviewable decisions, who owns the call, and what happens afterward.

See the operating model

Want this kind of discipline on your own AI work?

StreamGist is how I know the method holds. I bring the same controls to client work.