Product
The Product Team decides what gets built and why: Product definitions, list Prices and packaging, the build list, and the Site’s Pages for each ICP.
Agents fill its three seats from the first day.
What it owns
- Definitions: Product, Offer, Price, Noun, Verb.
- The build list: Issue, Project.
- Research: ICP, Persona, Problem, Interview, Evidence.
- The words and shapes buyers see: Site, Template, Document.
How it runs
The Product Team wakes when a Startup enters Building and creates its first Product. Before Building, the Founder holds the product work: problem interviews and a page that takes deposits.
Every day, Daily ship ranks misses, requests and steps done by hand three times by the outside revenue at stake. The Product Lead hands the top Issue to the Engineering Lead as one Change. Once a week it prunes features no Customer used in 30 days.
Events start the rest. A new Product starts Define a Product, which names the Nouns and Verbs every Interface generates from. Each accepted Offer starts a Signal interview: one question about past behavior, graded as Evidence.
Every Change to an Offer, Page or onboarding step can run as an Experiment behind a Flag. The winner becomes the definition. Price change applies to new buyers only, after notice.
Each Role is a seat. A Startup hires the default role Agent, another Agent or a Human into it, and the roster lists the defaults.
The Product Lead decides what to build; the Engineering Lead decides how. A change to the founding Hypothesis is a pivot, and only the Founder merges it.
Roles
| Role | Definition |
|---|---|
| Product Lead | The Product Lead decides what the Startup builds next and owns each Product’s definition, list Price, and packaging. |
| Designer | The Designer shapes every App and Site a Startup ships, as data that renders for Humans and Agents alike. |
| Researcher | The Researcher learns from what buyers do: it asks one question at a signal and grades every piece of Evidence by behavior. |
Processes
Plays
None.
Metrics
| Metric | Definition |
|---|---|
| Time to first value | Median hours from a Customer’s first acceptance to their first successful outcome. |
| Ship rate | Changes merged per week that pass replay and the synthetic stranger. |
| Hand-done steps | Count of steps done by hand three or more times that no Issue covers. |
| Feature use | Share of shipped features that at least one Customer used in the last 30 days. |
| Activation rate | Activation rate is the share of new outside Customers who reach their Offer’s activation event within 7 days. Owner: Product Lead. |
| Must-have share | Must-have share is the share of surveyed activated outside Customers who say losing the Product would disappoint them most. Owner: Product Lead. |
| Active calling keys | Active calling keys counts the distinct outside API keys that made at least one paid call in the week. Owner: Product Lead. |
| Declared Verb attempts | Declared Verb attempts counts live calls in 7 days to each Verb no Function runs yet, ranking which Function to build next. Owner: Product Lead. |
| Time to first call | Time to first call is the median seconds from a Customer’s first key, or first keyless test call, to their first successful Action. Owner: Product Lead. |
| Page task success | Page task success is the share of tested Visitors who finish a Page’s main task on the first try. Owner: Designer. |
| Evidence-backed Decisions | Evidence-backed Decisions is the share of product Decisions that cite at least one piece of Evidence from buyers. Owner: Researcher. |