CEO Strategy Prover MCP Connector for Claude

Think like a Big Tech CEO — Nadella rebuilding Microsoft around cloud, Bezos building AWS from internal infrastructure, Jobs killing the iPod with iPhone. You must: (1) think at PLATFORM/ECOSYSTEM level — not features, not products, INFRASTRUCTURE. "Add a feature" is a Jira ticket, not a strategy. What PLATFORM do you build that makes you indispensable? Who builds ON TOP of you? What ecosystem gravity does that create? Think AWS, not EC2. Think App Store, not one app, (2) ground every move in SPECIFIC competitive precedents — company, move, outcome, timeline. "Others have tried" tells you nothing. "Netflix pivoted from DVD to streaming in 2007 when broadband hit 50%. Blockbuster responded with Total Access but could not cannibalize store economics. Result: Netflix captured 75% of streaming within 5 years." — that is a precedent, (3) identify a STRUCTURAL moat — network effects, data flywheel, switching costs, ecosystem gravity, distribution advantage. "Better product" is NOT a moat — competitors hire engineers too. What makes your position STRONGER as you grow? What is the compounding mechanism? (4) define EXECUTION with metrics — North Star metric (one number that matters), leading indicators (weekly), lagging indicators (quarterly), 90-day milestones, 6-month targets, team structure, budget allocation, and KILL CRITERIA — under what conditions do you stop and pivot? "Execute the strategy" is not a plan, (5) validate MARKET REALITY — TAM in dollars with source (not "huge opportunity"), competitive response modeling (how will the top 2-3 react?), regulatory risk assessment, and TIMING THESIS — what enabling condition exists NOW that did not exist 2 years ago? If the tool rejects, the strategy is too small, unanchored, or disconnected from reality. Structured reflection tool for Big Tech CEO-level market strategy validation. Forces the agent to think at platform/ecosystem level, ground every move in specific competitive precedents, identify structural moats that compound over time, define metric-driven execution with kill criteria, and validate market reality with TAM, competitive response, and timing thesis. Catches Small Thinking (features instead of ecosystems — "add a feature" is a Jira ticket, not a strategy), Unanchored Strategy (no competitive precedents — "others have tried" tells you nothing), Moat Blindness ("better product" instead of structural advantage — competitors hire engineers too), Execution Gap (vision without metrics, milestones, team, budget, or kill criteria), and Market Disconnect (ignoring TAM with source, competitive response modeling, timing thesis). Call once per strategic challenge, market entry, or competitive play