Startup & Founder, in order.

Open questions 50 open

• Agentic Technical Debt3 open
  • SourceHow long does a CLAUDE.md remain accurate as a codebase evolves? The playbook gestures at session-by-session updates; no data on rot rate. (Partially answered — not answered — by Khatri 2026: rot rate is still unmeasured, but the question's stakes move. If a Good/Excellent-rated file buys no correctness over having none, then a stale file costs correspondingly little correctness too, and the rot that matters is in the environment-fact content (test cost, deployment invariants) that carried the one measured effect. The measurement still owed is a longitudinal one: does a file's accuracy decay track anything observable in agent behaviour?) (Repair cadence, not rot rate, measured 2026-09-22 by who maintains agent skills longitudinal on the sibling artefact: actively maintained public SKILL.md files are touched every 5 days at the median and 38% of substantive edits are corrections — factual corrections and fixes from observed failures — with concrete failure evidence on 24% of edits under the primary coding pass and 63% under a cross-family recode. That is how often maintained skills get repaired, not how fast unmaintained ones decay, and the same paper's transfer-task null (latest version −0.09 vs earliest, CI [−0.28, +0.10]) says the repairs bought nothing measurable — Khatri's stakes-deflation from the other side.)
  • NoteThe 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. (Deflated, not resolved, by Khatri 2026 — if the file doesn't move correctness, the founder's inability to write a good one costs less than this bullet assumes; see Founder as Agent Orchestrator.)
  • NoteAnthropic's harness-shrinkage thesis suggests CLAUDE.md may eventually be inferred by the model itself. Until then, the discipline is load-bearing.
• AI Investment Story, Not Efficiency Story5 open
  • SourceIs the classification driving the result? "AI company" is Emergence's label. If AI companies are disproportionately younger (more likely pre-revenue-inflection) than the non-AI cohort at the same revenue band, some of the RPE gap is an age/stage artifact, not an AI effect. The report doesn't publish a stage-matched comparison. (Partially answered on a different outcome, 2026-08-11: OECD AI Papers No. 62 runs exactly this test on market share instead of RPE, with adoption measured by a compulsory national statistical survey rather than a label. The raw gap is enormous — AI users hold 7.5× (France) and 3.2× (Portugal) the average market share of non-users — and it dies under controls: the AI user coefficient on market-share decile goes 0.0657\\\ → 0.0530\\ → 0.0266 ns in France and 0.0681\\\ → 0.0283 ns → 0.0199 ns in Portugal, killed mainly by lagged productivity (0.18–0.19, 7–9× the AI coefficient it displaces). So on the closest available analogue, the answer is yes, selection is doing the work — but note the direction: there the selection inflates the AI cohort's apparent advantage, whereas here the suspicion is that stage/age composition deflates it. The RPE half is untouched; a stage-matched financial comparison is still what would settle it.)
  • WaitWhen does the crossover happen? AI-native RPE is growing faster and already leads on growth; at $100M+ top decile it grew +58% vs −6%. Does the level gap close within a year or two, and does it invert (AI companies more efficient per head) — the point at which "efficiency story" becomes true? (Partially answered — no inversion visible as of Q2 2026, on an instrument that cannot see a trend (2026-09-22). iconiq pacesetter index 2026 supplies a measured level two to three quarters after Emergence's Q4-2025 snapshot, on the most favourable AI cohort anyone has published: top-quartile-growth AI-forward companies at $100M+ run $655K median / $890K top-quartile revenue per FTE. Both sit below Emergence's AI top-decile $960K and far below its non-AI top-decile $1.3M, so nothing in the newer reading looks like an inversion. Three reasons this is weak evidence and does not retire the bullet: the ICONIQ figure is a pooled 2024–Q2 2026 cross-section with no year-over-year series, so it measures a level and the question is about a rate; the percentiles are not comparable (a top quartile of a selected cohort is not a population top decile); and ICONIQ publishes no non-AI comparator at all, which is the entire object of the crossover. The trigger event is unchanged — a matched AI-vs-non-AI RPE series with at least two readings on the same instrument.) Extended — a series finally exists, and it turns down (2026-09-22). iconiq 2026 state of scaling, the full report the index excerpts, publishes the year-by-year ARR-per-FTE the index could not: top quartile by band, 2022-23 / 2024 / 2025 / 2026, at $315K / $398K / $488K / $478K ($100M+), $201K / $229K / $265K / $290K ($25-100M) and $139K / $196K / $203K / $149K ($10-25M). Two things follow for this bullet. The rate question it asks can at last be addressed on operating data, and the answer in 2026 is that per-head productivity stopped rising outside the $25-100M band - the largest band posted its first decline in the series and the smallest fell 26%. An inversion is therefore further away than the trajectory readings implied, not closer. But the bullet is about AI versus non-AI, and this series is cut by ARR band and by revenue-growth cohort, never by AI status - ICONIQ does not publish the split anywhere in 52 pages. It also thins hard (n falls 403 -> 120 company-quarters) and mixes composition effects into every band as companies graduate. So: the missing time axis is supplied, the missing comparator is not, and the trigger event stands exactly as written.)*
  • SourceTail vs. mean gap. No data here on the deliberately-lean solo-founder tail's RPE specifically — the lean-unicorn claim lives in that tail, which the population medians can't isolate. (Partly informed: Emergent, a celebrated lean-tail exhibit, checks in at ~$600K/head at $120M ARR — below this cohort's $100M+ top-decile AI figure ($960K), suggesting the tail's scaled RPE is less exceptional than the low-headcount snapshots imply. One vendor-claim datapoint, not a cohort.) Checked against Carta's own 2026 follow-up and still not answered (2026-09-22): carta founder ownership report 2026 splits founder ownership by founding-team size, sector and AI-vs-non-AI, and publishes no revenue figure of any kind. The gap is structural to the instrument — cap tables do not contain revenue — so no Carta publication will close this; it needs a financials source (Standard Metrics-class portfolio data) cut on founding-team size.
  • SourceWhich instrument is right for the frontier AI-native subset? Two empirical-tagged sources disagree in direction — cap-table financials say AI companies earn ~39% less per head, a founder survey says AI-natives clear $400K/head at 55% and grow 156%. The disagreement is confounded by instrument (measured vs self-reported) and reference class (matched-band AI-vs-non-AI vs AI-native-vs-all-startups). Only a matched-segment, financial-data RPE study of the deliberately-lean AI-native frontier specifically — not the broad "AI company" label — would settle whether the survey optimism or the cap-table pessimism describes that tail. (ICONIQ's fourth reading adds a forward trajectory — RPE projected +84% by 2027 — but it too is self-report, and projected, so it deepens the survey-side optimism rather than adjudicating it.) (Partially answered, and the partial is precisely half (2026-09-22). iconiq pacesetter index 2026 is the vault's fifth reading and the first to satisfy the instrument half of what this bullet demands: operating financials rather than self-report — quarterly data 2024–Q2 2026 from public software companies plus the publisher's own portfolio — applied to an explicitly AI-forward frontier cohort rather than to a broad "AI company" label. At $100M+ its median is $655K/FTE, top quartile $890K. That lands between the two disagreeing readings: comfortably above Emergence's $394K all-company median for the band, comfortably above the $400K threshold AWS's survey has 55% of AI-natives clearing, and still below Emergence's AI top-decile $960K. It fails the comparison half completely, and the failure is structural, not incidental: a Pacesetter is selected on top-quartile three-year growth plus ICONIQ's own AI-Native/AI-Driven label, and there is no non-Pacesetter and no non-AI control group anywhere in the publication. A selected cohort's median is not a population median, so this cannot say whether AI companies out-earn matched non-AI peers — it adds a third reference class rather than collapsing the two. A calibration worth keeping from it: ICONIQ's top-quartile Pacesetter, $890K, clears Emergence's all-company top quartile of $827K by only ~8%, which prices what the double selection is actually worth. What would still settle the bullet is unchanged — a matched-segment financial-data comparison carrying a non-AI control.) Extended, and the comparison half is now half-satisfied (2026-09-22). The claim that ICONIQ publishes no comparator was true of the index page and false of the report it excerpts: iconiq 2026 state of scaling plots an explicit "Others" bar beside the Pacesetter bar on six metrics. That is a real control group and it changes the reading materially - at $100M+ Pacesetters run less OpEx than Others (53% vs 75%) and a better burn multiple (0.8x vs 1.4x), having run 284% vs 124% and an FCF margin 5.6x more negative below $100M. What it still is not is the control this bullet specifies: "Others" is the non-Pacesetter remainder of ICONIQ's own 137 companies (portfolio plus 11 publics themselves selected on IPO performance), it is defined by failing the growth-or-AI test jointly so no figure separates an AI effect from a growth effect, and the Pacesetter cells carry n = 4-12 company-quarters. And the one metric it is never cut on is revenue per FTE - there is no Pacesetter-vs-Others RPE bar anywhere. So the bullet keeps its tag: a within-sample winners-vs-winners comparator on cost metrics is progress on the comparison demand without touching the AI-vs-non-AI proposition.)*
  • WaitMargin question (report's own): are the fastest-growers' 6–16pp-lower gross margins a temporary AI-infra-cost absorption or a permanent repricing of software's economic quality? (Partially answered on direction, untouched on the actual question (2026-09-22). iconiq pacesetter index 2026 measures company-level gross margin across a top-quartile-growth AI-forward cohort by ARR band: 55% → 60% → 80% → 75% median (top quartile 80% / 70% / 85% / 85%). The depressed margins are located entirely in the two smallest and fastest-growing bands, and $25M+ Pacesetters already sit at conventional software levels — which is the shape "temporary absorption" predicts. But this is a stage series, not a time series, and the distinction is the whole bullet: these are different companies at different sizes observed in one pooled 2024–Q2 2026 window, so the identical ladder is produced by margins recovering within each company as it scales and by a vintage effect in which the newest, most inference-heavy entrants happen to be the small ones. Two further cautions: the ladder is non-monotone — median margin falls 80% → 75% from $25–100M into $100M+ — and the sub-$10M band's 25pp median-to-top-quartile spread (55% vs 80%) says early AI-forward companies do not share one margin structure at all. Settling this needs the same companies measured across years; the trigger event is unchanged.)
• AI Product Economics Maturation4 open
  • WaitICONIQ's respondents project gross margins expanding to ~59% by 2027, while Emergence's cap-table data measures the fastest-growers running 6–16pp below peers today. Does the projected margin expansion materialize, or is it survey optimism that regresses toward the measured growth-margin tradeoff as these companies scale? Checked against the same publisher's own measured benchmark and still not answered (2026-09-22): iconiq pacesetter index 2026 is measured rather than projected, which is the upgrade this bullet wants — but it is measured by ARR band, not by year (55% / 60% / 80% / 75% median across <$10M / $10–25M / $25–100M / $100M+), on a different cohort (top-quartile-growth AI-forward companies, no control group) and at a different level (company gross margin, not gross margin on AI products). A cross-section of different companies at different sizes cannot falsify a forecast about one panel across time, and this one is not even monotone — median margin falls 80% → 75% entering the largest band. It does confirm, on receipts rather than self-report, that the growth-margin tradeoff the bullet's other half asserts is real and is concentrated in the smallest, fastest-growing bands. The trigger event is unchanged: 2027 actuals for the surveyed panel, or any same-companies-across-years margin series. Extended, and the missing comparator arrived without helping (2026-09-22): the full report the index excerpts, iconiq 2026 state of scaling, plots gross margin by year and against a non-Pacesetter comparator — the two things the index lacked. Company-level medians: under $100M, 72% / 74% / 70% / 70% (2022-23 → 2026), with Pacesetters at 71% against Others' 70%; above $100M, 78% / 79% / 79% / 78%, with Pacesetters at 73% against Others' 78%. So a time axis now exists and it is flat — no aggregate margin expansion anywhere in four years — and the only real gap is the ~5pp ICONIQ attributes to Pacesetters' 'higher inference, infrastructure, and deployment costs' at scale. This is still not the quantity the bullet asks about: 70-78% is company gross margin, and the 45%→53%→59% projection is margin on AI products specifically, a sub-line that a blended company margin can hide entirely. What it does add is the direction of the drag — at the top of the ladder AI-forward companies give up margin rather than gaining it, which is the opposite of the projection's slope. n = 4-12 company-quarters on the Pacesetter cells. Trigger event unchanged.
  • SourceFDEs are monetized fragmentedly (bundled / separate PS fees / hybrid) and comped on retention. Does a dominant FDE monetization model emerge, and does the "Revenue Driver" self-framing (38%) survive a margin analysis — i.e. are FDEs actually accretive, or a services drag reclassified as growth? (Still open, and pointedly so: the corpus's most prominent July-2026 coverage of the role discusses supply, scarcity, and vendor structure at length and says nothing about pricing, bundling, or margin. The answer will come from a filing or an operator's P&L, not from role coverage.) A third staffing model appeared with no price attached, which adds a column and no evidence (2026-09-22). accenture google cloud gemini fde business group (Accenture newsroom press release, 2026-09-08, vendor-claim) announces a global systems integrator staffing a 1,000-person FDE workforce on a model vendor's platform — neither the vendor-side delivery arm nor the customer-internal team this page's other bullets track. Accenture and Google Cloud state the workforce is built on "nearly 50,000 Google Cloud-skilled professionals" and that Google Cloud will train them; the release states no billing model, no employer for the FDEs, no timeline and no margin. So the count of plausible monetization models goes from three (bundled / separate PS fees / hybrid) to four (an SI's own services contract, where the platform vendor books consumption and the integrator books time), while the evidence on which dominates stays at zero — and the largest single FDE commitment in the corpus is the one that discloses least. The nearest thing to an economic test arrived from a different source and is a hurdle rate, not a result: ICONIQ's operators in iconiq 2026 state of scaling state FDE economics "typically only makes sense when deployed against opportunities that can drive a 5–10x return on fully loaded cost," with capacity scaling "linearly with headcount" and viability only "at meaningful ACV levels." That cuts against the Revenue-Driver self-framing in a specific way the bullet should keep: if the motion only clears its cost against large accounts, then 38% "Revenue Driver" is a statement about the accounts FDEs are assigned to, not about the motion's margin, and the two are separable. Demand-side, the same report's n=132 buyer survey has 73% viewing FDEs positively — the layer is wanted, which is not the same as accretive. Trigger unchanged, with one new candidate: an SI segment disclosure that breaks out agentic-deployment services.
  • SourceEnterprises are building internal FDE teams specifically to avoid exposing proprietary business processes to their model vendor (C&T via TechCrunch, vendor-claim, motive documented via one recruiter and one vendor CEO; the behaviour mostly not yet observed — Ode reports no client asking it to build such a team). Does that in-housing actually happen at scale, and if it does, does it cap the FDE-as-revenue-driver motion at exactly the accounts worth the most — i.e. is the labs' delivery-layer integration self-limiting? Falsifiable from job-postings data (internal FDE-titled roles at non-vendor enterprises) against vendor-services revenue disclosures. A genuinely new axis, and it does not dissolve the concern (2026-09-22): accenture google cloud gemini fde business group (vendor-claim) puts a fourth party in the frame. A global systems integrator staffing 1,000 FDEs on Google Cloud's Gemini Enterprise is neither of the two options this bullet contrasts: the FDE relationship, and with it the encoded process knowledge, is owned by a firm that sells no competing software and whose interest in the account outlives the platform choice. Taken literally that answers the stated fear — the model vendor does not get the processes. It does not answer the fear's actual content, and the release says so in its own words: the group's second priority is "building repeatable, industry-specific solutions," i.e. process knowledge acquired at one client and resold to its competitors, by a firm serving ~9,000 clients. So in-housing and the SI route are not substitutes, and a buyer holding this concern has no reason to be reassured by the third model. Two further caveats keep this from being progress on the bullet's falsifiable half: it is a vendor-claim announcement with no timeline and no employer named for the 1,000 engineers, so no behaviour has yet been observed; and it says nothing about whether enterprises are building internal teams, which is still the quantity the bullet asks about. What it does change is the job-postings test named above — an internal-FDE count is now ambiguous between in-housing and SI-supplied staff placed on client sites, so the instrument needs to separate employer from work location.
  • WaitInternal AI spend jumped from 1–3% to a projected 16% of revenue with respondents calling true cost hard to predict. Is 16% a transient enablement bulge that falls as tooling matures, or a durable new cost line for software companies? (Partially answered on the price leg, untouched on the spend leg (2026-09-22). iconiq 2026 state of scaling is the same publisher's operating-data report and it measures the input price, not the spend: the Silicon Data blended token-expenditure index runs $1.02 → $1.79 → $1.26 → $2.07 (Jun'26) → $1.05 (Aug'26), roughly halving from peak, with ICONIQ attributing the fall to model routing across providers rather than to list-price cuts. A halving unit price is a necessary condition for the bulge deflating and nowhere near a sufficient one — spend is price × volume, and the same report's agentic-workflow evidence has volume rising fast. The one company-level datum is an anecdote and is in the wrong unit: a $500M+ ARR fintech CFO says token spend went 'from near zero to ~5-10% of payroll' before mid-tier defaults and caching took it 'well below that even as usage climbed' — one unnamed firm, a payroll denominator, and a figure the speaker cut himself, but it is a direct observation of a cost line first inflating and then being engineered down, which is what 'transient bulge' predicts. Public-company earnings calls corroborate the line becoming salient without sizing it: compute/infrastructure-cost mentions doubled 3% → 6% of substantive AI commentary Q2'25 → Q2'26. The trigger event is unchanged and now sharper: the same panel re-surveyed on AI spend as a share of revenue for 2026 actuals — ICONIQ publishes no such figure in 52 pages, so this cannot be settled from the operating-data side.)
• AI-Native Startup Lifecycle3 open
  • 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. (Partially answered: Emergence Capital, June 2026 now supplies headcount-at-round medians — Seed 6.2 (−39% from the 2021 peak of 10.3), Series A 16.8, Series B 48.2 — plus days-to-first-hire 214→284 and capital concentration (44% of venture to AI). Still missing: median time-to-PMF, headcount-at-PMF specifically, and failure-rate data; and the Carta cohort is market-wide, not the lean-AI-native subset. See AI Investment Story, Not Efficiency Story for the efficiency counter-signal in the same data.) Extended with an ARR-band ladder, and it points against the claim (2026-09-22): iconiq pacesetter index 2026 benchmarks a top-quartile-growth AI-forward cohort on quarterly operating financials, and its revenue-per-FTE row inverts into implied headcount at a given ARR — ~65 people at ~$5M ARR on a $75K median, rising through $115K and $225K before revenue per FTE nearly triples to $655K at $100M+. So the compression the playbook promises is visible only in the largest band, and implied headcount grows through every stage below it; the ladder is evidence against "headcount can stay flat through Scale" rather than for it. Three limits keep the bullet open and none of them is minor: band medians are not per-company ratios and break at band edges, the cohort is selected by its own investor with no control group, and ICONIQ publishes no time-to-PMF, no headcount-at-PMF and no failure rate — the three things this bullet actually asks for. What it substitutes is headcount-at-scale, which is adjacent, not the same. Extended again, with the first direct headcount series and a time-to-scale figure (2026-09-22): iconiq 2026 state of scaling, the full report the index excerpts, adds the two closest population data yet. Time-to-scale: Pacesetters reach $100M ARR from $1M in ~14 quarters against ~22 for other software companies (~2-4 years on average; ICONIQ's outlier subset "just 1-3 years"), which is the first comparator-backed version of the compression this bullet asks about — but it is modeled, not measured: the curve assumes 24 months from founding to $1M where undisclosed, assumes exponential growth between two press-released endpoints, and is drawn only over companies that reached $100M, so it cannot carry a failure rate. Headcount: median headcount growth by revenue-growth cohort, 2022-23 through 2026, runs 119/65/115/146% for 100%+ growers against 47/38/46/34%, 17/12/18/6% and (6%)/(5%)/4/2% for the slower bands (n=390/200/197/76 company-quarters). That is a direct measurement with a time axis, and it points against the compression claim harder than the index's cross-section did: the fastest growers hire hardest and the gap is widening. Still not answered, and by now the reason is structural rather than incidental: no time-to-PMF, no headcount-at-PMF, and above all no failure rate - a living cohort re-selected each period on top-quartile growth, plotted through companies that already reached $100M, is the one instrument that can never produce one. Closing this needs a source that follows a fixed cohort forward, including its casualties.
  • NoteFounder 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.
  • SourceThe 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.
  • ResolvedTension with HBR's accountability findings (above) is unresolved. The playbook's orchestration framing reads as the exact framing HBR's experimental conditions tested against. Answered: Orchestration vs Employee Framing: Reconciling the Founder's Playbook with HBR's Accountability Evidence resolved this operationally in May 2026 — orchestration as workflow design (agents, handoffs, review gates, decision rights) survives HBR's critique; orchestration as a coworker mental model (naming, delegation-without-scope) is what produces the −9pp/+44%/−18% effects, and the playbook's lifecycle needs only the former. The Orchestrator's Real Workload: Decision Burden, Framing Discipline, and Whether Taste Scales adds the July 2026 reinforcement: decision-rights gating now has measured backing (control-channel authorization 100% on safety-critical actions vs 51/54% for advisory channels), while the framing effect compounds with brain-fry in the same direction (felt control, decayed review). The residual — why Anthropic's founder marketing ignores its own framing-discipline work — is a question about Anthropic, tracked on Founder as Agent Orchestrator as #oq/source.
• Compounding Data Moat4 open
  • SourceIs the "two-year replication window" claim defensible empirically, or aspirational? The playbook does not cite measurement. (Partially answered, at the far end only: DroneDeploy is a ~decade accumulation whose value arrived discontinuously when vision models did, priced at $845M — one case, told by its own investor, with no counterfactual for how fast a late entrant could have caught up once the demand was legible. What it suggests is that "two years" is the wrong unit: the binding variable is whether accumulation started before the monetizing capability was foreseeable, not elapsed calendar time. A real answer still needs a matched pair — two vertical products, one with a pre-capability archive and one without, competing after the capability lands.)
  • WaitHow 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? (Reframed rather than answered (2026-09-22): iconiq 2026 state of scaling asserts the premise this bullet fears in a form that cuts the other way — 'as AI models become interchangeable, the edge is data and workflows rivals cannot copy' — i.e. rapid model improvement is read as commoditizing the model layer and therefore strengthening the data moat, not dissolving it. Both readings can be right and they apply to different things: commoditization of general capability raises the value of a proprietary corpus, while a model that internalizes a vertical's edge cases specifically destroys the corpus's marginal value. ICONIQ offers no evidence for either, only selected exhibits of scale (Samsara 25T datapoints, Shopify 20 years of commerce data, CrowdStrike's Threat Graph), all chosen because their owners are outperforming. The bullet's trigger is unchanged and is now stateable precisely: a vertical where a frontier release measurably eroded an incumbent's data advantage.)
  • SourceThe 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.
  • SourceThe "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?
• Forward-Deployed Engineering as a Delivery Layer3 open
  • SourceWhere do 1,000 FDEs come from? Accenture and Google Cloud state the workforce will be "built on" ~50,000 already-Google-Cloud-skilled Accenture professionals via training and certification, while the recruiting-side estimate in the corpus puts the entire US pool able to deliver at ~2,000. If the SI route converts consultants rather than hiring engineers, the scarcity framing collapses and the quality question replaces it. Falsifiable from Accenture's own job postings for FDE-titled roles against its certification disclosures, or from any Gemini Enterprise certification count published over the next year.
  • SourceDoes the layer ever scale sublinearly? ICONIQ's operators state capacity "scales linearly with headcount" — which is the constraint agentic delivery is supposed to remove. Does any vendor or SI report deployment count growing faster than FDE headcount, or is the layer a permanent linear tier? A vendor publishing deployments-per-FDE across two years would settle it; nothing in the corpus reports the ratio even once.
  • SourceIs an SI-staffed FDE a different product from a vendor-staffed one? Both satisfy ICONIQ's "consultant-trained, technically fluent" profile from opposite ends (a consultant taught the platform, versus a platform engineer taught the customer), and no source compares outcomes, retention or time-to-production between them. A buyer-side survey cutting satisfaction by who employed the embedded engineer would be the instrument.
• Founder as Agent Orchestrator4 open
  • SourceThe 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? (Partially answered — by deflation — Khatri 2026, arXiv 2607.27250, empirical: in a 288-run two-agent ablation, having a Good/Excellent-rated AGENTS.md produces no measurable correctness gain over having none (bounded <10–15pp), and the real file never converts a near-miss to a pass in a 36-cell probe. If the file the non-technical founder cannot write buys ~0 correctness, the recursion is a smaller tax than the playbook's own framing implies. Two reasons this doesn't close the question: the ablation measures single-session task correctness, not the cross-session architectural coherence this recursion is actually about, and the deficit it identifies as gating — implementation skill: feature design, pattern selection, exact wiring — is precisely the judgment a non-technical founder also lacks and cannot delegate to a file. The recursion may not run through the context file at all; it runs through review.)
  • 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. (Partially answered: Emergence Capital, June 2026 gives Carta round-medians with a 2020–2025 series — Series A 16.8 (down from the 2021 peak of 25.9), Seed 6.2 (from 10.3), Series B 48.2 — the prior-cohort comparison the playbook lacked, plus the AI-vs-all-tech headcount-allocation split (engineering-heavy, lean support). Still open: these are round-medians, not headcount-at-PMF; and the Carta cohort is market-wide, not split AI vs non-AI at Seed/A.)
  • SourceHow 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). Partially answered: The Orchestrator's Real Workload: Decision Burden, Framing Discipline, and Whether Taste Scales — higher and reshaped: execution load is exchanged for oversight load at an unfavorable rate, because the incoming work is the error-prone kind (+39% major errors under fatigue), the invisible kind (rubber-stamped planning decisions are transcript-indistinguishable from judgment), and non-monotonic in value (HAS-Bench's returns-curve peak — over-intervention breaks tasks). The load is bounded only by deliberate structure: bounded parallelism, sampled review, high-stakes gates. Still unmeasured: founder-side oversight load directly — concurrency telemetry sums agent-hours, not human attention. Partially answered (2026-10-01): Harness Patterns Under Scale and Domain Shift: Context Routing, Other Domains, Large Action Spaces, and the Overseer — the mechanism is sharper. The verification tax (Alami et al.) is levied by retained accountability, not by agent throughput: "if we weren't responsible for the code it produced, it would be a lot faster." A founder is the last accountable party, so orchestration puts them at the top rate unless accountability is delegated to people or deterministic gates. Faros's September 2026 report finds the strain changing shape (parallelism pressure easing, restarts +66.7%) rather than easing. Both studies are of engineers, not founders, and neither measures attention, so net load still needs a direct measurement. Retagged #oq/now → #oq/source.
  • SourceAnthropic 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 Orchestration vs Employee Framing: Reconciling the Founder's Playbook with HBR's Accountability Evidence 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 Discipline2 open
  • SourceWhere 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.
  • SourceDoes 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 Market2 open
  • WaitA 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?
  • SourceThe 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 Democratization3 open
  • SourceIs 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. (Partially answered: Anthropic's 400K-session study finds non-software occupations reach verified success in code-producing sessions within ~7pp of software engineers — the strongest evidence yet that the claim holds, at least within Claude Code's user base. Market-scale corroboration: Emergent reports 200K+ non-technical paying customers — trucking companies, factories, and construction businesses building their own ERPs, property managers building CRM tools (TechCrunch, July 2026, vendor-claim) — Boris's "the accountant writes the accounting software" observed as a paying market, not just inside one vendor's telemetry.) Further advanced: Is Breadth Cheap Now? Specialist Ramp Speed and Domain-Expert-as-Builder at Scale sorts all the evidence into three tiers — capability parity (measured: within-7pp), market existence (demonstrated, vendor-claimed: Emergent's 200K+ non-technical builders; AI responsibilities in 28–40% of business job descriptions), and primary-job building as population-level practice (still unshown: every measured population is selection-biased toward adopters, complements gate realized value, and the ATLAS composition shows experts pointing AI at their own inexpert tasks rather than non-experts becoming builders). The gating variable is now complements + retained understanding, not capability. A practitioner case (2026-08-28): Andrew Ng describes an organization where the practice is the norm — "All of my marketers know how to code," a marketer's self-built desktop app, a CFO's document-checking scripts, and "what they've built" as the interview question for marketers (andrew ng biggest opportunities in ai arent where you think, practitioner-opinion). Tier-two evidence at best — one firm, selected for it by its founder ("my team's probably… somewhat ahead of the curve"), no outcome measure — but the first primary-job building by non-engineers the vault holds from inside a firm rather than from a vendor's customer count. Retagged 2026-10-05: every measured population is adopter-selected; needs a population-level survey of primary-job software building by non-engineers.
  • WaitWhat'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?
  • SourceBoris's "accountant writes accounting software" — does that result in 10K narrow tools that don't interoperate? What's the integration story?
• Problem-Solution Fit Discipline2 open
  • SourceDoes 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.
  • SourceHas anyone measured 2026 startup failure rates with AI-built products? The "42% will climb" claim is asserted without measurement.
  • ResolvedThe 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 character training (sycophancy resistance, devil's-advocate willingness)? Answered: Playbook Boundary Conditions: the Devil's-Advocate Substrate and the Prototype's Edge — complementary, not conflicting: the prompted moves are framing-compliance tasks that work on any instruction-follower (none requires disagreeing with the founder), while character training supplies the unprompted pushback the prompts can't manufacture — portable technique, vendor-specific safety net, and the residual gap (framing bias within the assigned adversarial task) is the sibling #oq/source above.
• Product Velocity as Moat2 open
  • WaitVelocity-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? (Checked against the cohort's own answer and still open (2026-09-22). iconiq 2026 state of scaling asked five of the fastest-growing AI-forward companies in its portfolio the same question, and their answer is the conversion this bullet asks for: velocity keeps a workflow moat ahead of copying — 'defensibility is moving from the model to the specific workflow the product solves' — with AI-generated code pushing customer learnings back into the product 'fast enough that the gap widens with every release.' That is a structural claim (velocity feeding an accumulating asset, not velocity alone), and it is the right shape of answer. It is also unfalsifiable as offered: no competitor pace, no convergence measurement, no case where the gap failed to widen — five self-selected winners describing their own moat in an investor's report. The bullet's trigger is unchanged: it needs a losing case, a company that shipped fast and was caught anyway.)
  • Source"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 AI3 open
  • SourceIs "switching cost" really collapsing in practice, or just in narrative? Anthropic's own retention numbers, Salesforce churn, etc. would test this. Partially answered (2026-09-22) by techcrunch startup arr less secure madrona (practitioner-opinion), and the partial is precise about which half it touches. It supplies the first buyer-side behavioural datum the bullet asks for: 77% of 150 surveyed enterprise IT professionals re-evaluate their AI vendors every six months or on a rolling basis, and Madrona states the conclusion outright — "switching costs are lower and the re-evaluation cadence is relentless." So the collapse is not only narrative; a measurable share of buyers have institutionalised a procurement cadence that presumes it. What the bullet actually asked for is still missing, and the gap is the whole distance between re-evaluating and leaving: no churn, renewal, retention or NRR figure appears anywhere in the source — a 77% re-evaluation rate is compatible with a 5% switch rate and with a 50% one, and the Emergence receipts (6–8 vendors held all year) suggest the low end. Three further discounts: it is a VC's survey reaching the wiki through a news article with the primary report unread, n=150 self-reporting IT professionals with no sampling frame published, and it measures stated process, not observed behaviour. The instrument that would close this is unchanged — a vendor-side retention series (the Anthropic/Salesforce churn numbers named in the bullet) or a receipts panel tracking vendor exits rather than vendor counts. Extended (2026-09-22) — the retention numbers arrived, and they answer a different question than the one asked. iconiq pacesetter index 2026 (empirical, quarterly operating financials 2024 – Q2 2026, not a survey) publishes the corpus's first measured retention figures: median gross dollar retention 100% / 95% / 95% / 90% and net dollar retention 105% / 125% / 130% / 115% across the <$10M / $10–25M / $25–100M / $100M+ ARR bands. Two things follow. The apparatus change is the real evidence: ICONIQ added gross retention to its benchmark as a new metric and said why — "switching tools has become significantly easier… contracts are shorter, and POCs have become the default entry point… putting existing revenue at risk in ways NDR can miss" — which is a third, disinterested party re-tooling its measurement around the erosion this bullet asks about. The levels do not show a collapse: at $100M+ a ~10% annual gross loss is more than covered by 115% net retention. But the bullet is about change, and this is a pooled cross-section with no time series, so it cannot show retention falling; it is measured on a cohort selected for top-quartile growth with no control group, i.e. the population least likely to exhibit the collapse; and it is cohort-wide operating data rather than the named-vendor churn disclosure the bullet specifies. Closing it now needs the same metric across years — two or more editions of this index, or a vendor's own retention series. Extended a second time, and the two additions point in opposite directions (2026-09-22). iconiq 2026 state of scaling, the full report the index excerpts, adds the comparator the previous extension said was missing: at $100M+ in 2026, non-Pacesetter median NDR is 99% — expansion exactly cancelling churn — against 130% for the AI-forward cohort (n=32 vs n=4 company-quarters). So revenue durability has deteriorated for the median software vendor in ICONIQ's own dataset, which is the first evidence on this page that the erosion is visible in money rather than in intent. But the same report's cohort figures, compared against the index's pooled 2024–Q2 2026 window, suggest Pacesetter retention is rising (115%→130% median at $100M+ as the window narrows to 2026), and it supplies the strongest behavioural datum yet on the buyer side: 65% of 132 enterprise buyers prefer contracts of one year or less — a commitment actually made, not a process self-reported, and a harder reading than Madrona's 77% re-evaluation cadence. What is still missing is exactly what it was: a named vendor's churn or gross-retention series across years. ICONIQ publishes gross retention only in the index's pooled cross-section and never cuts it against Others, so even the comparator does not reach the metric the bullet names. Two editions of this report is now a concrete, dated trigger.)*
  • WaitWhat does Boris's "cornered resource" look like for foundation-model labs that are themselves trying to commoditize? Internal contradiction or transient phase?
  • SourceCounter-positioning — explicitly the "incumbent can't follow" power — should amplify under AI. Is anyone running this play deliberately?
• The 1% Rule for Wedge Selection2 open
  • SourceDoes the rule hold empirically? Nothing here tests whether markets where models scored ~20% in 2025 were absorbed faster than markets where they scored ~0%. The data to check it (benchmark-era capability snapshots against startup outcomes) exists in principle.
  • SourceWhat is the 2026 cost of a defensible niche model? Dean asserts "maybe it doesn't take that much compute"; a founder needs the number, and the corpus doesn't have it.
• The AI-Native Safe-Choice Inversion2 open
  • WaitThe 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?
  • WaitHow long until incumbents bolt on credible AI and neutralize the counter-positioning — and does the custom-foundation-model claim actually defend against that?
• The Solo-Founder Shift3 open
  • SourceIs the employee-equity null a real population fact or a median artifact? Carta reports near-identical medians; the publisher claims 2–5× among founders in his own program. A distributional cut — variance or upper decile of first-five grants, split by founding-team size — would settle it, and neither party publishes one. Checked against Carta's own follow-up and still not answered (2026-09-22): carta founder ownership report 2026 publishes employee equity only as a pool aggregate by stage (12.1% at seed, 16.8% at Series C) and never splits grants by founding-team size. The check did sharpen the question, though: the same report publishes a distribution for founder-to-founder splits (equal-split rates by team size, both rising), so the missing cut is an editorial choice rather than a dataset limit — worth asking the Data Desk for directly rather than waiting for it to appear.
  • SourceDoes the solo-founded tail differ from co-founded companies on revenue per head? This dataset cannot say — it holds cap tables, not revenue — and it is the missing half of AI Investment Story, Not Efficiency Story's tail question. Checked (2026-09-22): carta founder ownership report 2026 is again cap tables only; it adds ownership-by-stage and sector splits and not a single revenue figure. The gap is structural to the instrument, so no Carta publication will close it — this needs a financials source.
  • SourceIs the solo share of funded companies rising in step with the solo share of formed companies, or is the trend stalling at the financing gate? Carta publishes solo share of formations (~36% in 2025) and two-founder share of round-closers (36%, 40% SaaS) but not solo share of round-closers — the one number that would say whether the funnel is narrowing on solo teams. Any Carta cut of founding-team size among companies that closed a round, or the gated full report, would settle it.
  • ResolvedDoes the H1 2025 jump to 36.3% survive a full-year datapoint, or is it a half-year artifact? Every prior step is 0.6–2.7pp and this one is 5.8pp. Trigger: Carta's 2025 full-year or 2026 update to this series. Answered (2026-09-22): the trigger fired — carta founder ownership report 2026 (Carta Data Desk, 2026-03-12, empirical) reports about 36% of startups founded on Carta in 2025 were solo-led, up from 31% in 2024. Same instrument, same denominator phrase, consistent 2024 anchor and a consistent ten-year doubling. The jump survived: it is a full-year step of roughly +5pp, still by far the steepest in the series. Graded as a prediction, in three parts. Right: the methodological objection — a half-year point is not comparable to six full years, and the anomalous step size warranted a hold rather than a headline — was correct, and the trigger was named precisely enough that a single follow-up publication settled it. Wrong: the substantive prediction underneath it. "If H1 2025 behaved like any prior year it would read ~32%" is falsified by about 4pp; regression toward the historical step size did not happen, and the half-year-artifact hypothesis is dead. Right for the wrong reason: the suspicion that the series is not fixed between publications was vindicated — the 2024 point did move, 30.5% → 31% — but by the publisher's own restatement or rounding, not by the sampling artifact the question hypothesized. Residual, which is a rounding limit and not a reason to keep the question open: the follow-up gives "about 36%" with no decimal and no H2-only cut, so the size of any second-half reversion is unknowable from it (bounded at roughly 34.7–36.5% for H2 under an equal-halves assumption). And the second caveat this page raised — platform-composition drift in the on Carta denominator — is entirely untouched by a full-year datapoint; it is tracked in the body, not as an open question, because no Carta publication can address it.
• Zero-Friction Scope Creep3 open
  • SourceThe 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?
  • SourceIs there a measurable threshold where scope creep crosses into outright pivot territory? The playbook gestures at "losing direction" without a metric.
  • SourceHow does this interact with 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?