Startup & Founder, in order.

Open questions 35 open

• Agentic Technical Debt
  • How long does a CLAUDE.md remain accurate as a codebase evolves? The playbook gestures at session-by-session updates; no data on rot rate.
  • The remedy assumes the founder is *able* to articulate architecture in plain language. Non-technical founders (the playbook's headline beneficiary group) may have neither the vocabulary nor the intuition to do this well — a recursion failure the playbook doesn't address.
  • Anthropic's [[harness-shrinkage-as-models-improve|harness-shrinkage]] thesis suggests CLAUDE.md may eventually be inferred by the model itself. Until then, the discipline is load-bearing.
• AI-Native Startup Lifecycle
  • The playbook gives no quantitative evidence for the headcount/capital compression claims (no median time-to-PMF, no headcount-at-PMF numbers, no failure-rate data). The "lean 10-person unicorn" is asserted as deliberate target without case-study evidence in the doc itself.
  • Founder stories in the resources section (Carta Healthcare, Anything, Cogent, Airtree, Duvo, Zingage, Kindora, Wordsmith) are short callouts — none have published outcomes or comparable-baseline data.
  • The 42% "built-something-nobody-wanted" CB Insights figure is from a pre-AI era; the playbook predicts the rate will climb but doesn't cite a 2026 measurement.
  • Tension with HBR's accountability findings (above) is unresolved. The playbook's orchestration framing reads as the exact framing HBR's experimental conditions tested *against*.
• Compounding Data Moat
  • Is the "two-year replication window" claim defensible empirically, or aspirational? The playbook does not cite measurement.
  • How does this moat hold up when foundation models themselves continue improving rapidly? If a generalist model in 2027 has internalized enough vertical context to handle 340B drug claims natively, does the vertical-edge-case moat erode?
  • The data-flywheel argument has been made for SaaS for 15 years. What's actually different in the AI-native version? Probably: the data improves the *model* in addition to the product, but the playbook doesn't make this distinction precisely.
  • The "customers build APIs on top of you" lock-in is structurally similar to platform plays (Salesforce AppExchange, Shopify apps). Is the moat type really new, or just newly accessible to lean startups?
• Founder as Agent Orchestrator
  • The playbook claims non-technical founders can now build production software, but it does not address the architectural-judgment recursion problem ([[agentic-technical-debt]]): non-technical founders may not have the vocabulary to write effective CLAUDE.md. How does that scale?
  • The "lean 10-person unicorn" is asserted; no quantitative data in the playbook on actual headcount-at-PMF or headcount-at-Series-A medians for AI-native startups vs. the prior cohort.
  • How does the orchestration role change the founder's *decision* burden? Fewer hands-on tasks but more parallel agent oversight; net cognitive load is unclear and may be higher (see [[ai-brain-fry]]).
  • Anthropic publishes both the playbook's anthropomorphic framing *and* HBR-aware accountability work (auto-mode, alignment) simultaneously without engaging the framing literature directly. The synthesis in [[wiki/derived/orchestration-vs-employee-framing-reconciliation]] reconciles the tension at the operational level — *orchestration as workflow design* preserves accountability; *orchestration as mental model of agents-as-coworkers* does not — but the open question of why the playbook's marketing language doesn't reflect Anthropic's own framing-discipline work remains.
• Founder-Led Sales Discipline
  • Where exactly does "until PMF" end, and what's the first thing a founder *should* hand off (AE? agent? both)? Glasgow still does it post-Series-B, suggesting the boundary is fuzzy.
  • Does Glasgow's anti-offload stance generalize, or is it specific to high-trust, mission-critical enterprise sales (ERP) where "they're buying *you*" — would a PLG/SMB motion delegate to agents far earlier?
• Narrow Wedge into a Legacy Market
  • A wedge works going in; does it constrain going out? Campfire now serves public companies — at what point does "narrow-but-best" require becoming the broad incumbent it displaced, re-incurring NetSuite's complexity?
  • The wedge-flip shows the first wedge can be wrong. What's the fastest signal that a wedge converts to the core vs. merely sells — Campfire took ~3 months; can it be read sooner?
• Printing Press Software Democratization
  • Is domain-expert-as-builder actually happening at scale in 2026? Anecdotes (shop owners, microcontroller hobbyists) yes; primary-job software building by non-engineers, less clear.
  • What's the equivalent of compulsory schooling for universal coding literacy? Or does that not happen and we get a long tail of self-taught builders?
  • Boris's "accountant writes accounting software" — does that result in 10K narrow tools that don't interoperate? What's the integration story?
• Problem-Solution Fit Discipline
  • Does asking an AI to argue against an idea actually produce disconfirming evidence at the same rigor as confirming evidence, or does the model still bias toward the framing the founder presents? Worth measuring.
  • The playbook recommends "ask Claude to make the most compelling argument for why a competitor would succeed while you do not." How does this interact with Anthropic's published [[claude-character-as-product|character training]] (sycophancy resistance, devil's-advocate willingness)?
  • Has anyone measured 2026 startup failure rates with AI-built products? The "42% will climb" claim is asserted without measurement.
• Product Velocity as Moat
  • Velocity-as-moat is a treadmill: it evaporates the moment a competitor matches pace. What converts Campfire's velocity lead into a *structural* moat before the AI-native cohort's pace converges?
  • "Never had anyone outgrow Campfire" — is that survivorship (they haven't hit true enterprise scale yet) or a real claim that velocity closes the breadth gap faster than customers grow into it?
• Seven Powers Applied to AI
  • Is "switching cost" really collapsing in practice, or just in narrative? Anthropic's own retention numbers, Salesforce churn, etc. would test this.
  • What does Boris's "cornered resource" look like for foundation-model labs that are themselves trying to commoditize? Internal contradiction or transient phase?
  • Counter-positioning — explicitly the "incumbent can't follow" power — should *amplify* under AI. Is anyone running this play deliberately?
• The AI-Native Safe-Choice Inversion
  • The inversion is a one-time repricing of "safe." Once several AI-native ERPs exist, does "safe" re-stabilize around the *largest* AI-native vendor — and does Campfire's "we're now the largest of the new cohort" claim reflect a land-grab for that position?
  • How long until incumbents bolt on credible AI and neutralize the counter-positioning — and does the custom-foundation-model claim actually defend against that?
• Zero-Friction Scope Creep
  • The playbook recommends written scope but offers no template or worked example. How specific does "what we deliberately don't do" need to be to actually block requests?
  • Is there a measurable threshold where scope creep crosses into outright pivot territory? The playbook gestures at "losing direction" without a metric.
  • How does this interact with [[ai-native-product-cadence|Cat Wu's]] 1-day shipping cadence? Anthropic's internal practice ships fast but with strong product judgment; how does that judgment translate for a first-time founder?