# Bezos Flywheel Prover MCP > Bezos Flywheel Prover evaluates business strategies against five rigorous axes derived from Amazon's founding principles. Your agent forces you to think like Bezos, checking for customer obsession, self-accelerating flywheel loops, infrastructure plays, Day 1 team culture, and long-term compounding theses. It quickly flags if your strategy is merely a project list or a true growth engine. ## Overview - **Category:** business - **Price:** Free - **Tags:** bezos, flywheel, customer-obsession, infrastructure, day-1, long-term, compounding ## Description This MCP validates complex business strategies by forcing you to meet five tough standards: customer obsession, flywheel design, identifying core infrastructure assets, maintaining Day 1 speed, and committing to decades-long goals. When you run an evaluation through this tool, it doesn't just give suggestions; it points out exactly where your plan fails—whether you're optimizing too much for a single quarter or building something that only works in theory. It forces the agent to work backward from actual customer pain, design continuous growth loops, and map out infrastructure plays that become platforms for others. If your strategy falls short of these five axes, it flags the failure (like being competitor-obsessed or too focused on surface products). Users find this MCP cataloged in Vinkius because it moves past basic planning models to deliver true strategic rigor. ## Tools ### validate_bezos_flywheel Analyzes a full business strategy by checking for customer obsession, flywheel loops, infrastructure plays, Day 1 culture, and seven-year compounding theses. ## Prompt Examples **Prompt:** ``` Beat the competition, launch a standalone project, build an app, form a committee, optimize quarterly results. ``` **Response:** ``` COMPETITOR_OBSESSED — Five fatal gaps: competitor benchmarking, linear initiatives, surface building, Day 2 bureaucracy, short-term focus. ``` **Prompt:** ``` Customer: SMBs, 4hrs/week manual invoicing, 12% error rate. Flywheel: faster invoicing → more SMBs → more data → better credit scoring → faster payments → supplier referrals → more SMBs. Infrastructure: payment engine offered as a service, 2,400 transactions/day from 12 partners. Day 1: two-pizza teams, 70% decisions, weekly delivery cadence, no committees. Long-term: Year 1-2 infrastructure, Year 3-4 $1M revenue, Year 5-6 platform standard $12M revenue, Year 7 $40M revenue 65% margin. ``` **Response:** ``` FLYWHEEL_PROVEN — Flywheel strategy validated. All five axes pass. Execute. ``` **Prompt:** ``` We built internal payment processing that handles 2,400 transactions/day from 12 partners. But customer discovery shows SMBs want mobile-first invoicing, not desktop. Do we pivot the infrastructure to mobile? ``` **Response:** ``` Partial validation — infrastructure axis passes (platform serves partners). But customer obsession demands the pivot: start from the customer pain, not the infrastructure you already built. Rebuild the press release for mobile SMBs. ``` ## Capabilities ### Validate Strategic Viability Forces your agent to analyze a business plan against five rigorous, foundational axes of sustainable growth. ### Identify Customer Pain Points Shifts focus from technology capabilities to the core pain points that drive customer behavior and purchasing decisions. ### Design Flywheel Loops Checks if every element in your business model accelerates every other, creating a self-reinforcing cycle of growth. ### Map Platform Infrastructure Plays Determines the core internal infrastructure layer that can be productized and used by multiple paying customers. ### Enforce Day 1 Operational Culture Validates organizational speed, team size (two-pizza teams), and decision-making processes over bureaucratic committee structures. ### Commit to Long-Term Thesis Requires mapping milestones across a full seven-year time horizon instead of just focusing on quarterly gains. ## Use Cases ### The 'Beat the Competition' Trap A marketing team suggests launching a feature to directly beat a rival. The agent uses validate_bezos_flywheel and flags it as COMPETITOR_OBSESSED, forcing the team to redefine success based on unique customer pain points instead. ### From App Idea to Platform Strategy A founder has built a successful end-user application. The MCP analysis identifies that the true growth lies not in the app itself, but in building an underlying payment processing infrastructure that can be sold as a service to other businesses. ### The Committee Paralysis A product roadmap is stalled by departmental committees. Running it through validate_bezos_flywheel highlights the DAY2_BUREAUCRACY failure, forcing the team to restructure into smaller, empowered two-pizza teams. ### The Short-Sighted Budget A department proposes a budget focused entirely on hitting next quarter's revenue targets. The MCP flags SHORT_TERM_FOCUS, compelling leadership to adjust the plan toward investments that pay off in years five through seven. ## Benefits - Stop confusing a project list with a growth engine. This tool forces you to map out self-accelerating loops, ensuring every feature links back to the core value proposition. - It shifts focus from current market benchmarks to foundational customer pain. You'll know exactly what problem your product solves by working backward from the user's deepest frustration. - You identify true moats. Instead of building a standalone user-facing app, this MCP helps you determine if your core internal processes can become a valuable platform for partners and other services. - It prevents bureaucracy creep. By forcing Day 1 thinking, you test whether your operational plan relies on quick decisions by small teams rather than committees and endless approval flows. - You secure long-term funding narratives. The tool requires mapping milestones across a full seven-year time horizon, anchoring your strategy in compounding growth instead of quarterly vanity metrics. ## How It Works The bottom line is that you get an objective, multi-axis assessment of your strategy to ensure it’s built for sustainable, compounding growth. 1. You provide your full business plan, including details about the customer pain, proposed growth loops, core infrastructure assets, team structure, and long-term goals. 2. The MCP processes this data by running five distinct strategic checks against the input, forcing it to look for failures in areas like linear thinking or surface building. 3. Your agent returns a verdict: either 'FLYWHEEL_PROVEN' if all axes pass, or a specific failure code (e.g., COMPETITOR_OBSESSED) detailing exactly which strategic pillar is missing. ## Frequently Asked Questions **How does the Bezos Flywheel Prover MCP work?** This MCP forces your agent to validate strategies across five specific axes: customer pain, flywheel loops, infrastructure plays, Day 1 culture, and long-term goals. It doesn't offer advice; it checks for structural failures. **Can the Bezos Flywheel Prover MCP tell me what my competitors are doing?** No. The tool is designed to prevent competitor obsession by forcing you to start with your own customer pain points and work backward, rather than benchmarking rivals. **What happens if the validation fails on Day 2 Bureaucracy?** The MCP flags DAY2_BUREAUCRACY failure. This tells you that your plan relies too heavily on committees or slow approval workflows, signaling a need for smaller, autonomous teams. **Is this better than just doing strategic brainstorming?** Yes. Brainstorming is subjective; the MCP runs an objective check against five rigorous standards that mimic deep operational experience across decades of business cycles. **Do I need to have a 7-year plan to use the Bezos Flywheel Prover MCP?** While it requires mapping out milestones for years 1 through 7+ to pass, you only need a clear vision of your long-term commitment, not a fully detailed document. **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.