Product

6B. PRODUCT

Authoritative Resources:

Core Frameworks:

1. Product-Market Fit (PMF) — First Round's "Paths to PMF": find wedge → iterate on feedback → triple down on what works. No single formula, but pattern: solve an urgent problem for a narrow audience.
2. Positioning (April Dunford) — 10 steps: competitive alternatives → unique attributes → value → target customer → market category → positioning statement. "If you can't position it, you can't sell it."
3. RICE Scoring (Reach × Impact × Confidence / Effort) — prioritization at product/feature level
4. Opportunity Solution Trees — Map desired outcomes → opportunities → solutions. Avoid build traps.
5. Jobs to Be Done (JTBD) — Customers "hire" products for jobs. Drives strategy, not features.
6. Shape Up — 6-week cycles, shaped vs unshaped work, appetite over estimates

How AI Changes Product:

• AI-native PMF: Gamma found PMF after pivoting to AI-native product (First Round case study). AI-first startups don't "add AI" — they rebuild from scratch around AI.
• AI user research synthesis: 10,000 support tickets → themes → opportunities in minutes
• AI spec generation: PM describes the problem; AI drafts user stories, acceptance criteria, edge cases
• AI prototyping: PMs wireframe, mock, and generate working front-end — the PM expands into rapid prototyping
• Role shift: from "feature delivery" → "outcome ownership." AI handles execution; PM focuses on strategy, psychology, business outcomes.

Product & Monetization Operating Rules

• Wedge first: validate one narrow, painful job and a reachable buyer before expanding into a platform or suite.
• Shared core, modular surface: when multiple products share tenancy, identity, billing, data, or workflow primitives, build those once and expose modules behind clear boundaries.
• Value-aligned pricing: keep entry pricing predictable, then align expansion to measurable usage or value. Cap or explain overage so customers can forecast.
• Paid discovery beats speculative breadth: a customer-funded implementation is strategically useful only when the contract protects reusable platform IP, isolates customer data/configuration, and creates a path to recurring support or resale.
• Impact still needs a payer: a real social problem is not automatically a viable business. Define the beneficiary, user, economic buyer, distribution path, and sustainable funding model separately.
• Price on countable activity: prefer transactions, invoices, payments collected, API calls, credits, SKUs, or completed workflow actions over unverifiable profit or revenue shares.
• Variable pricing is a trust system: show usage before payment, provide a grace buffer, cap or explain overage, and make the maximum plausible bill legible.
• Productize consulting before forcing SaaS: paid setup → repeatable workflow templates → managed service → multi-client platform → SaaS control plane. Productize only workflows that repeat across customers and retain.
• The moat is workflow depth and distribution: customer trust, local integrations, operating data, repeatable templates, and embedded workflows matter more than a specific agent runtime or model brand.

---