MMRs, Neutralizers and Differentiators

Every feature in your product is one of three things. Getting the category right — and, more importantly, spending roadmap time in proportion to the category — is one of the highest-leverage product decisions you'll make.

The three categories

• MMRs (Minimum Market Requirements): Table-stakes features every serious product in the category must have. Customers don't pick you because you have them; they eliminate you if you don't.
• Neutralizers: Features that cancel out a competitor's advantage. They don't win deals, but their absence loses deals to a specific competitor.
• Differentiators: Features that are the reason customers pick you over everyone else. Your moat.

Concretely, for a B2B SaaS project-management tool in 2026:

Category	Example	Why
MMR	User authentication, role-based access control, a REST API	Every buyer screening in this category expects these. Missing any = disqualified.
Neutralizer	Gantt view	Not unique, but Asana has it, so if you're pitching against Asana, you need it.
Differentiator	AI-native task decomposition that generates sub-tasks from a one-line brief	Novel; the reason a buyer picks you.

The customer-feedback trap

Customers often provide feedback on MMRs and neutralizers. ==The product management team must take responsibility for reinforcing the startup's differentiator.==

This is the most important line in the original Tom Tunguz post and it deserves expansion. Customers give you feedback based on what they compared you against. A prospect evaluating you against Jira will tell you about missing Jira features. A prospect evaluating against Linear will tell you about Linear features. Neither prospect will tell you to double down on your differentiator — because your differentiator is exactly what they lacked context on until they met you.

If you build your roadmap by counting customer feature requests, you will end up with a product that is 90% MMRs and neutralizers and 10% differentiator. That's a product indistinguishable from any competitor in the category. The roadmap that wins looks inverted: a small, stable MMR base, strategic neutralizers against your one or two sharpest competitors, and heavy investment in the differentiator.

The feature lifecycle

Features migrate across categories over time, always in the same direction:

Differentiator → Neutralizer → MMR → (eventually) deprecated

Salesforce's custom objects were a differentiator in 2001, a neutralizer by 2008, and are a pure MMR today — every enterprise CRM has them. Stripe's developer-first API was a differentiator in 2011 and is now baseline for payments infrastructure. Zoom's one-click join was a differentiator in 2015 and is MMR for every video conferencing product in 2026.

The strategic implication: a differentiator has a shelf life. Once the market recognizes your advantage, competitors race to replicate it. If your only advantage is one differentiator, you have maybe 2-5 years before it drifts down the stack. Sustaining a market lead requires either:

1. A continuous pipeline of new differentiators (Apple's approach — new novel capabilities every 2-3 product cycles).
2. A compounding moat — a differentiator that becomes harder to copy over time, not easier (network effects, data advantages, switching costs, brand trust).

Neither is automatic; both require explicit roadmap investment.

Roadmap allocation heuristic

A rough rule that's held up in my experience:

• Early stage (pre-PMF to early traction): 70% differentiator, 20% MMRs, 10% neutralizers. You lose deals you shouldn't win yet; you win the deals that care about the one thing you're actually great at.
• Growth stage (post-PMF, expanding into new segments): 40% differentiator, 30% MMRs (you're expanding into segments with stricter requirements), 30% neutralizers.
• Scale stage (enterprise, multiple competitors): 30% differentiator, 40% MMRs, 30% neutralizers. At scale you're playing on enterprise RFPs where MMR checklists matter.

If you find yourself spending 70% of the roadmap on MMRs at the early stage, you've misread the category — either the MMR list is smaller than you think, or you're trying to play scale-stage GTM with a seed-stage product.

Common failure modes

• MMR gold-plating. Building the "best-in-class SSO implementation" when a basic Okta integration would pass the RFP. MMRs should be adequate, not excellent; spending excellence on MMRs is a tax on your differentiator.
• Neutralizer whack-a-mole. Adding a feature every time a competitor ships one. This is how you end up with a bloated product with no identity. Neutralize only the competitors you lose deals to, and only the features that actually matter in the buying decision.
• Mistaking a neutralizer for a differentiator. A feature you shipped first but that a competitor can ship in a quarter isn't a differentiator — it's a neutralizer with a lead time. Treating it as a differentiator (and resting on it) is how market leads evaporate.
• Under-investing in the differentiator. The most common failure. The customer feedback pipeline doesn't request it, so the team quietly stops shipping to it. Six quarters later, the differentiator hasn't evolved and the competition has caught up.

Practical application

Before each quarterly planning cycle:

1. List every roadmap item on the table.
2. Classify each as MMR / Neutralizer / Differentiator. Force the classification — no "all of the above."
3. Calculate the percentage of engineering time that falls in each category.
4. Compare against the stage-appropriate allocation above.
5. If the differentiator share is below target, ask: why did no one propose more? Usually the answer is "no customer asked for it" — which is exactly the trap.

See also

• What is a Market? — the buyer-reference definition that underlies this framework.
• 9x Effect — why differentiators need to be dramatically better, not incrementally better, to matter.
• Competition Demystified — on moats and sustainable advantage (related framing).