Skip to main content

About John Yu

I'm building Kam so bettors see the market before they fire.

I'm John Yu, founder of Kam AI. I build the product, the systems, the writing, and the workflows behind Kam. The idea is simple: pick your spots, let Kam read the market shape, and get a clear read before you fire.

Product

Market intelligence, not another picks feed

Kam is built to watch the games, sportsbooks, prediction markets, schedules, and saved reads a user cares about, then show what moved, where markets disagree, what is missing, and what to verify next.

Engineering

Web, mobile, backend, data, and AI in one loop

The work spans Next.js, React Native, backend APIs, source checks, admin review, evals, saved reads, and chat. The point is one product that feels connected.

Taste

Simple words beat fancy systems talk

Users should not need architecture vocabulary. They should know what moved, what is stale, and what to check before they fire.

Who I am

A founder who builds the whole loop.

I care about products where the words, design, data, and backend all point at the same job. For Kam, that job is helping a bettor get a better read before acting.

That means I am not only building screens. I am building the source checks, admin tools, saved reads, chat behavior, blog education, and test gates that keep the product honest.

I want Kam to feel like a sharp second opinion. Straight talk. No fake locks. No magic claims. Just the source, the market shape, the missing info, and the next useful step.

What I've built

Kam is already more than a landing page.

A Next.js web product with public pages, docs, blog, pricing, and admin surfaces.

A React Native product direction for sports-market research and AI chat workflows.

Backend proxy and admin auth flows that protect operational tools with Cognito and Google Workspace.

Manual Data Ops tools for staged batches, validation, review, import, rollback, and audit history.

A blog and docs system that explains Kam in plain English instead of hype.

Agent persona rules so the sports betting assistant sounds like a market-intelligence layer, not a generic chatbot.

What Kam stands for

A better bet starts before the bet.

Catch moves. Don't chase.

Kam should help users see the market shape before they take a worse number.

No fake locks.

The product should never promise winners, sure things, or risk-free bets.

Show the missing info.

If the sportsbook line, prediction-market context, schedule, source, score, or injury context is stale or missing, say it clearly.

Keep the final call human.

Kam can organize the read. The user still owns the bet, the wait, the pass, and the review.