Founding Product Lead

What You Will Own

• Product law. The locked specs agents build from, across chat, web, extension, mobile, and personalization.
• A consumer quality bar. The standard for everything a shopper touches, held as evidence tests for four to six product outcomes — each falsifiable, each with a test a stranger could run.
• The decision-shaped UX standard. With our Founding Designer, you'll define what a verdict looks like: interfaces shaped around the decision the user is making — buy, wait, walk away — rather than around the content we happen to have.
• Outcomes, personally. One or two falsifiable product outcomes a quarter that you run end-to-end yourself.
• Operator contract. This is the model we run: in your first quarter you co-sign a seat charter — one machine-checkable number that proves the seat works, plus a written split of what you decide freely and what you bring to the founder.

The System

• Three knowledge graphs, one answer. A Commerce Graph (what exists, prices, availability), a Truth Graph (product claims that survive our verification research and carry citations), and a Preference Graph (what each user actually cares about).
• A chat product whose edge is structural. General assistants average the internet confidently. Ours answers with verified truth and citations — including "don't buy this."
• Agent-era distribution. The product has to be a named capability inside ChatGPT, Apple App Intents, Gemini, and Claude — surfaces where an AI agent, not a human, decides whether to call us.
• The build pipeline. Intent becomes a visual mockup, then a locked spec, then agents build, then separate verifier agents check the build against the spec.
• The verifier is the load-bearing part: it's a test the building agent can't author or grade, so the system can't quietly approve its own work. Your spec is what those checks run against.

Who You Are

• You independently form working models of complex systems, notice where your model is wrong, and update fast — including killing your own ideas when the evidence says so.
• You write clearly because clear writing is evidence of clear thought, and here your writing is executable.
• You move between strategy and locked spec without getting stuck at either altitude — from "what should chat do when the evidence conflicts?" to a spec agents can build from, same day.
• You treat the agent's output as something you check, not something you accept on faith.