MCP For Claude Marketplace
Gates Platform Prover

Gates Platform Prover MCP Connector for Claude

A+

A team built a product while competitors owned the standard. It says 'better product' instead of naming a structural moat. It sells standalone tools instead of bundling. It assumes market position is safe. That is not a platform strategy — that is a slide deck for a product no one will remember. This tool forces five Gates-level platform axes: standard ownership, developer ecosystem, bundling strategy, paranoid execution, and cross-product feedback loops.

1 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

The Problem

Every LLM commits five platform reasoning failures:

  1. Product Thinking — builds products instead of owning standards.
  2. Ecosystem Neglect — builds for end-users, ignores participant ecosystem.
  3. Anti-Bundling — sells standalone products instead of bundling.
  4. Complacency — assumes market position is safe.
  5. Silo Thinking — independent products without feedback loops.

The 5 Platform Axes

Axis Pivot Rule
Standard Owned Others build on YOUR platform/protocols.
Ecosystem Self-Reinforcing More builders → more solutions → more users.
Bundling Deployed Free features eliminate adjacent competitors.
Paranoia Threats Modeled 18-month threat response plans.
Loops Established Product A data improves product B.

Verdict Matrix

Axis 1 fails → PRODUCT_THINKING
Axis 2 fails → ECOSYSTEM_NEGLECTED
Axis 3 fails → UNBUNDLED
Axis 4 fails → COMPLACENT
Axis 5 fails → SILO_THINKING
All pass     → PLATFORM_PROVEN
gatesplatformstandarddeveloper-ecosystembundlingcompetitive-intelligencefeedback-loops

1 tools expose this connector's capabilities to your AI agent.

validate_gates_platform

Think like Bill Gates — the person who understood that owning the standard is more powerful than owning the best product. You must: (1) OWN THE STANDARD — not the product, the infrastructure others depend on. Windows is a standard. Word is a product running on that standard. "Better product" is a feature, not a platform, (2) BUILD THE ECOSYSTEM — control participants who create solutions that make you essential. More developers → more software → more users → more developers. "Consumer-first" misses the flywheel that makes the platform indispensable, (3) BUNDLE — use free features as weapons to eliminate adjacent competitors. IE was free to kill Netscape. Teams was free to kill Slack. The platform subscription is the revenue — the free feature is the weapon, (4) STAY PARANOID — assume competitors are 18 months from killing your standard. "We are the leader" is what IBM said. Model specific threats with specific timelines, (5) CREATE LOOPS — each product must make the others essential. Data flows between products. Proprietary format lock-in. "Independent products" are a portfolio, not a platform. If rejected, the strategy builds a product, not a platform monopoly.Send ALL parameters in ONE call — the analyses above plus YOUR OWN verdict: every PIVOT boolean, verdict and clarification. The engine cross-checks the pivots against the verdict and rejects incomplete or self-contradictory calls. Structured reflection tool for Bill Gates-level platform dominance strategy — forces evaluation of standard ownership, ecosystem building, competitive bundling, paranoid threat modeling, and cross-product feedback loops. Catches Product Thinking (building a better product instead of owning the standard others depend on — Lotus 1-2-3 was a better spreadsheet. Excel won because Windows owned the platform. The product is a vehicle for the standard, not the standard itself), Ecosystem Neglect (ignoring the participant ecosystem that makes the platform essential — "consumer-first" misses the flywheel. Windows won because 70,000 developers wrote software for it. Developers wrote for it because users were there. Users were there because developers wrote for it. The ecosystem IS the moat), Anti-Bundling (selling standalone products instead of bundling to eliminate adjacent competitors — Internet Explorer was free because the browser was a weapon against Netscape, not a revenue source. The platform subscription is the revenue. Free features are competitive weapons), Complacency ("we are the market leader" without modeling specific threats with timelines — IBM said that before losing the PC standard to Microsoft. Microsoft said that before nearly losing the internet to Netscape. Only the paranoid survive. Name the threat and its timeline to feature parity), and Silo Thinking (independent products without cross-product feedback loops — a portfolio is not a platform. Office documents link to Outlook email, OneDrive storage, Teams collaboration, SharePoint publishing. Each product makes the others essential. Independent products are SKUs, not a platform). Call once per platform strategy or ecosystem evaluation

See how to talk to your AI agent using Gates Platform Prover.

Build a better product, focus on end users, standalone offering, we are the leader, independent products with separate roadmaps.

PRODUCT_THINKING — Five fatal gaps: product-level thinking, end-user only, standalone, complacency, silo thinking.

Standard: our protocol is the industry standard for logistics, 340 integrations. Ecosystem: 12K active participants/mo, 45 certified partners, satisfaction 94%. Bundling: analytics (free) eliminates CompetitorA/B, $200M market captured. Paranoid: OpenSourceX 18-month parity — 3 community leads, free tier, proprietary format extensions. Loops: data from product A improves product B, product B trains product A models, export loses 40% metadata.

PLATFORM_PROVEN — Platform dominance validated. All five axes pass. Execute.

Our platform has 340 integrations but no single partner exceeds 3% of total activity. We control the portal but not the runtime. Should we enforce stricter protocol versioning to increase lock-in?

Distribution breadth without dependency depth. 340 integrations at 3% each means no partner is committed. Versioning alone adds friction without value. Instead: create tiered access where premium features require deeper integration. Make the platform MORE valuable at higher integration depth.

Gates did not build a better word processor — he owned the operating system every application required. 'Better product' is a feature. The standard is the monopoly. Own the platform that others build on.

Related Connectors

Venture Platform Services Value Engine

Venture Platform Services Value Engine MCP

4 tools Official

Quantify the economic impact and ROI of platform services across your venture portfolio.

A+ View details →
Pitch Deck Prover

Pitch Deck Prover MCP

1 tools Official

An AI built a pitch deck that claimed a '$4.2B TAM' with no source, described the problem as 'everyone struggles with this,' showed '15K downloads' as traction with 3% D30 retention, and asked for 'funding to accelerate growth' — no amount, no use of funds, no milestones. The deck got rejected in 8 minutes. This tool forces problem validation with evidence, sourced market sizing, defined unit economics, retention-based traction, and a specific fundraising ask.

A+ View details →
Platform Sizing & Economics

Platform Sizing & Economics MCP

4 tools Official

Optimize offshore platform selection and physical dimensions based on production and environment.

A+ View details →
Migration Strategy Prover

Migration Strategy Prover MCP

1 tools Official

An AI recommended a big-bang database migration over the weekend. No dependency map — 7 services read from that database. No rollback plan — 'just restore from backup.' No data validation — 2.3 million records with timezone-dependent timestamps. The migration ran Saturday at 2 AM. By 4 AM, 3 downstream services were returning stale data, the backup was 6 hours old, and 14,000 customer records had corrupted timestamps. Monday morning: 72-hour incident. This tool forces risk assessment, rollback definition, data integrity verification, cutover planning, and stakeholder alignment.

A+ View details →