# Gates Platform Prover MCP

> Gates Platform Prover diagnoses if your business model relies on a sustainable platform or just standalone products. It forces you to test five critical axes of market dominance, checking for structural flaws in standard ownership, developer ecosystems, bundling strategy, threat modeling, and product feedback loops.

## Overview
- **Category:** strategy
- **Price:** Free
- **Tags:** gates, platform, standard, developer-ecosystem, bundling, competitive-intelligence, feedback-loops

## Description

Building 'the next big thing' is hard because most companies make the same strategic mistake: they focus on building a better product instead of owning the underlying platform. This MCP forces you to think like a market monopolist who understands that true power comes from standards, not features. You run it through your agent and feed in your current strategy—whether you’re launching a new service or evaluating an existing line of tools. The output doesn't tell you what to build; it tells you where the foundational gaps are. Does your product rely on proprietary data formats that lock people in? Are you ignoring the network effect created by third-party builders? By forcing evaluation across five key axes, this MCP gives you a rigorous check against common strategic failures like silo thinking or anti-bundling mistakes. Use it to move beyond feature parity and establish true market dominance, starting your deep analysis directly from Vinkius.

## Tools

### validate_gates_platform
Evaluates your entire business strategy against five pillars of platform dominance: standard ownership, ecosystem growth, competitive bundling, threat modeling, and internal data loops.

## Prompt Examples

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

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

**Prompt:** 
```
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.
```

**Response:** 
```
PLATFORM_PROVEN — Platform dominance validated. All five axes pass. Execute.
```

**Prompt:** 
```
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?
```

**Response:** 
```
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.
```

## Capabilities

### Assess platform structural viability
Runs a comprehensive diagnostic check against five critical axes of market strategy to determine if your business is built on an indispensable standard or just isolated products.

## Use Cases

### The new SaaS offering isn't sticking
A startup launches a slick product but sees low retention. They run `validate_gates_platform`, which flags 'Ecosystem Neglect.' The diagnosis shows the company is focused on consumer-first marketing when they should be instead building tools that make third-party developers build *for* their platform, creating an organic moat.

### The market leader assumption is dangerous
A large corporation assumes its market position is safe. Running the MCP reveals 'Complacency,' forcing them to model a specific threat—say, a new open-source alternative gaining traction in 18 months—and build immediate parity plans.

### Product lines are fighting each other
A company has multiple departments with separate software. The MCP points out 'Silo Thinking,' showing how data from the marketing platform isn't flowing back to improve the product development models, which is crucial for true cross-product dominance.

### Competitors are copying our features
Instead of raising prices or adding a minor feature, the MCP suggests using 'Anti-Bundling.' They identify a key free utility they already offer and reposition it as a competitive weapon to eliminate adjacent market entrants.

## Benefits

- You stop thinking about 'better features' and start focusing on standards. The tool forces you to identify the infrastructure others must depend on, making it harder for competitors to bypass you.
- It helps you build indispensable moats by designing free features as weapons against rivals. This moves revenue generation from just subscriptions to platform necessity.
- By modeling specific competitive threats with timelines, you move past generic 'we are leaders' statements. You get a concrete 18-month plan for defending your market position.
- It ensures that every product component feeds data into the others. Instead of having independent revenue streams, all tools reinforce each other, making them essential to use together.
- You avoid building siloed departments or products. The framework mandates cross-product feedback loops, ensuring that improvements in one area automatically benefit the whole platform.

## How It Works

The bottom line is that it translates vague business goals into concrete structural requirements for market success.

1. Input a detailed description of your current product line, its partners, and its revenue model into the MCP.
2. The tool processes this data against five established platform axes: standard ownership, ecosystem depth, bundling approach, threat modeling, and cross-product feedback loops.
3. It returns a structured assessment, identifying which strategic axis fails—for example, flagging 'Ecosystem Neglect' or 'Silo Thinking'—and suggesting the required pivot.

## Frequently Asked Questions

**What is the Gates Platform Prover MCP for?**
This MCP assesses if your business strategy relies on owning a foundational standard, which is more powerful than simply having the best product. It diagnoses five structural gaps that stop companies from achieving market dominance.

**Can I use Gates Platform Prover to check my current competitors?**
The MCP requires you to input your own strategy and data, forcing you to self-diagnose vulnerabilities. While the results inform how you must structure your defense against others, it doesn't analyze external companies directly.

**Does Gates Platform Prover help with product roadmaps?**
Yes. It forces a pivot from listing 'better features' to mapping required infrastructure ownership. You use its diagnosis to restructure your roadmap around standards and ecosystem growth instead of standalone improvements.

**What happens if I get flagged for Anti-Bundling?**
It means you are treating free utilities as nice extras, not weapons. The MCP guides you on how to strategically bundle those tools to make competitors' offerings non-viable without directly attacking them.

**How many times should I run validate_gates_platform?**
You should run it every time there is a major strategic pivot, such as entering a new market vertical or launching an entirely new product line. It's designed for periodic structural audits.