# Bezos Flywheel Prover MCP for AI Agents AI Agent Connect > Bezos Flywheel Prover is a business strategy stress test for startups and product teams. It forces your AI client to move past surface-level project lists and validate your plans against five core pillars: customer obsession, flywheel mechanics, infrastructure-first thinking, Day 1 culture, and long-term compounding. It identifies Day 2 thinking before you waste resources on it. ## Overview - **Category:** business - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_erjIx2fgRNMWHywJU3uWZp6mevH4HJB8MvGFErYj/ai-agent-connect - **Tags:** bezos, flywheel, customer-obsession, infrastructure, day-1, long-term, compounding ## Description Most business plans fail because they focus on the wrong things. They look at what competitors are doing instead of what customers actually need. They build shiny features instead of the underlying infrastructure that creates a real moat. They plan for the next three months instead of the next seven years. This Connector changes how you pressure-test your growth strategy. Instead of just nodding along to a good idea, your AI agent uses this tool to poke holes in your logic. It forces you to articulate a virtuous cycle where every part of your business accelerates the next. It demands a commitment to Day 1 speed and a 7-year thesis. When you are working through the Vinkius catalog, this is the tool you grab when you need to know if your roadmap is a real strategy or just a bucket of tasks. It makes sure you are building a platform that scales, not just a product that survives the quarter. You get a rigorous, objective audit of your business logic to ensure it is built for long-term dominance. ## Tools ### validate_bezos_flywheel Runs a structured reflection on your business plan to check for flywheel loops, infrastructure plays, and Day 1 culture. It identifies specific strategic gaps like competitor obsession or short-term focus. ## Prompt Examples **Prompt:** ``` We want to build a delivery app for local bakeries. Our plan is to offer a faster app than the current leader and give discounts to customers. ``` **Response:** ``` ### Strategy Audit: Competitor Obsessed Your current plan fails the **Customer Obsession** and **Flywheel** axes. Here is the breakdown: * **Competitor Obsession:** You are focusing on "beating the leader" rather than solving a specific customer pain (e.g., waste, delivery costs). * **Linear Thinking:** Offering discounts is a one-time tactic, not a flywheel. **Recommended Pivot:** Work backward from the baker's pain. If you build an **Infrastructure-First** inventory system that helps them reduce waste, that becomes your moat. As they save money, they stay on your platform, creating a virtuous cycle of data and volume. ``` **Prompt:** ``` Help me audit this 7-year plan: Year 1: Build platform. Year 2: Get 100 users. Year 3: Expand to 5 cities. Year 4: Add ads. Year 5: IPO. ``` **Response:** ``` ### Strategy Audit: Short-Term Focus This plan lacks a **7-year thesis** for compounding. It reads like a project list. | Year | Milestone | Status | |---|---|--| | 1-2 | Infrastructure | **Pass** | | 3-4 | Expansion | **Fail** (Linear Thinking)| | 5+ | IPO | **Fail** (Short-Term Focus)| **Fix:** Define what compounds. Instead of "Add ads," focus on how the Year 1 infrastructure becomes a platform that makes Year 5 revenue inevitable. You need a thesis on how you will dominate the market, not just a list of dates. ``` **Prompt:** ``` Our team is moving to a committee-based approval process for all new features to ensure quality. Is this a good move for a startup? ``` **Response:** ``` ### Strategy Audit: Day 2 Bureaucracy **Verdict: FAIL** This is a classic **Day 2** move. Committees and consensus-based workflows lead to stasis. **Day 1 Alternative:** * **Two-Pizza Teams:** Keep teams small (max 8 people). * **70% Decisions:** Make decisions with around 70% of the information you wish you had. * **Disagree and Commit:** Encourage healthy debate but move fast. Stop looking for perfect consensus; start looking for weekly delivery cadences. ``` ## Capabilities ### Validate flywheel loops The agent checks if each element of your business actually accelerates the next one in a virtuous cycle. ### Stress-test customer obsession It forces you to work backward from specific customer pain points instead of just listing features. ### Identify infrastructure moats The tool highlights whether your product is a surface-level tool or a platform others will pay to use. ### Audit for Day 2 bureaucracy It flags committee-heavy workflows and slow approval processes that kill startup speed. ### Map 7-year compounding theses Your agent maps out milestones for the next seven years to ensure you are not just optimizing for this quarter. ## Use Cases ### Vetting a new SaaS product idea A founder asks the agent to check if a new delivery app is a real flywheel or just a project list. The agent uses validate_bezos_flywheel to find the gaps. ### Auditing an existing roadmap A product lead wants to see if their current plan is too focused on this quarter. The agent identifies Short-Term Focus and suggests a 7-year thesis. ### Stress-testing a pivot A team wants to pivot to mobile. The agent uses the Connector to ensure the pivot is driven by customer pain rather than just following a competitor. ### Pitch deck preparation A founder uses the tool to prove their company has an infrastructure-first moat that will become a platform for others. ## Benefits - Stop Surface Building by forcing the AI to identify the underlying infrastructure that creates a lasting moat using validate_bezos_flywheel. - Ensure Flywheel Design by verifying that every business element actually accelerates the next one in a virtuous loop. - Eliminate Competitor Obsession by forcing the agent to work backward from specific customer pain points instead of benchmarking rivals. - Prevent Day 2 Bureaucracy by auditing your plan for committee-heavy workflows instead of two-pizza team speed. - Secure Long-Term Compounding by requiring a 7-year thesis instead of just a quarterly goal or a project list. ## How It Works The bottom line is you get a rigorous, objective audit of your business logic to ensure it is built for long-term dominance. 1. Provide your AI agent with a draft strategy, product roadmap, or new business idea. 2. Invoke the validation tool to run the plan against the five Bezos pillars. 3. Receive a verdict matrix identifying specific strategic failures like Surface Building or Short-Term Focus. ## Frequently Asked Questions **What is the Bezos Flywheel Prover MCP for?** It is a strategy stress test that forces your AI agent to validate your business plans against core principles like customer obsession and long-term compounding. **How does this tool help my startup?** It identifies 'Day 2' traps like bureaucracy and surface-level thinking before you waste money on them, ensuring you build a real moat. **Can I use this to audit my product roadmap?** Yes, it checks your roadmap for linear thinking and ensures each step actually contributes to a virtuous flywheel loop. **What is a 'Day 1' culture in this context?** It refers to maintaining speed by using two-pizza teams, making 70% decisions quickly, and avoiding committee-based bottlenecks. **How does it help with customer obsession?** It forces your agent to work backward from customer pain points rather than just looking at what your competitors are doing. **What is a flywheel vs. a project list?** A project list is a sequence of tasks. A flywheel is a loop where each element accelerates the next, creating compounding growth. **Can it help me find a moat?** Yes, by identifying infrastructure-first plays where your internal tools become a platform that others pay to use. **Why does it reject 'beat the competition'?** Bezos: 'If you are competitor-focused, you wait until the competitor does something. If you are customer-focused, you are pioneering.' Start from the customer pain. Write the press release first. Work backward to the technology. The customer does not care who you beat — they care about their problem. **What is DAY2_BUREAUCRACY?** Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Committees, approval workflows, stakeholder alignment, consensus building — all Day 2 signals. Day 1 is: two-pizza teams (max 8), decisions at 70% information, disagree and commit, single-threaded ownership. **Why 7-year thesis instead of quarterly?** Bezos: 'If everything you do needs to work on a three-year time horizon, you are competing against a lot of people. If you extend that to 7 years, you are now competing against a fraction of those people.' Amazon reinvested all profit for 20 years. Compounding requires patience.