fletchbuilds kodex pmm exercise · 2026

A take-home, taken seriously

One feature. Four hours. The whole workflow.

Kodex asked for a product page and the messaging behind it. Here's both — plus the part that usually stays invisible: exactly how an AI-native product marketer ships this much, this fast, without cutting corners on judgment.

The brief: watch the Kodex platform demo, pick one feature, build the page you'd ship for it, and show your work. Four-hour cap. Public information only. Assumptions labeled.

01 / the deliverable

The Page

Transparency Reporting — the product page Kodex doesn't have yet, built in their design system, with light and dark modes. The feature live sales demos rarely reach.

view the page→ 02 / the working doc

The Thinking

The positioning framework behind the page: why this feature beat everything else in the demo, who the buyer really is, and every claim labeled — found, assumed, or lived.

read the doc→ 03 / the system

The Build

The AI-native pipeline that made it: parallel research agents, a local video-intelligence pass on the demo, evidence-gated decisions, and a time ledger that kept the four-hour promise.

see the pipeline→
Why this feature

Their homepage names the pain — "you lack the data to generate transparency reports" — and their site never answers it with a page. Their demo covers it last, and live calls rarely reach it. That's not a feature gap. It's a distribution gap a page can fix.

Ground rules kept

The demo recording stayed on one machine. No demo-tenant data appears anywhere — every product depiction is a stylized recreation with invented values. Kodex's brand is used only inside the exercise, marked as concept work, and kept out of search indexes.

Who built this

Fletcher Stubblefield — full-stack, AI-native product marketer. Directed every judgment call; ran Claude Code as research team, video lab, and build partner. The split is documented, not hand-waved.