Product settings

Product Settings is configuration only — the operational money facts and the expense ledger live in Build → Economics and Build → Expenses; nothing here records evidence.

• Identity — the product's name, one-liner, description, URLs, and the declared framing (ICP, problem, desired outcome, wedge, channel, type). These are the Overview's identity fields — the same data, one copy.
• Integrations — the product's connection surface (founder 10/26): Build & research services — pick the research service the product research prompt uses (Mobbin by default; the workspace catalog can enable alternatives) and the build target(s) pre-selected in Build It's Prompts tab, plus founder prompt rules appended to every build prompt; Stripe pull (beta) — connect a restricted read-only Stripe key and SaaSFO pulls MRR, customers, and one-time sales daily (scheduled + Pull now), the same honest snapshots and provenance as the push webhook, key encrypted at rest; Live Data Feeds (push) — create Stripe or generic feeds, rotate secrets, pause/resume, and grab the copyable sample payloads that let you test the whole pipe in minutes. The service catalog itself is curated in Settings → Integrations — toggling a service off there hides it from every product.
• Template — save this product's structure (playbook answers, expense schedule, risk register shape) as a reusable template for the next product. Templates carry structure, never live data.
• Danger zone — delete the product. Isolated, named, and confirmed — destructive actions never sit beside configuration.