When the field survives and keeps its names

Research question

In a mature, feature-saturated category, does the recommendation field survive with its original members, and does the opening leader keep its position?

Why it mattered

A fifth kind of category for the survivability runs: a mature, saturated one. It was chosen as a contrast to the churn seen in E-041, to see whether a settled market survives by keeping its members rather than replacing them. The contrast carries a confound, noted below.

Method

Evaluator: Google AI Mode, single surface, logged out. Three draws, each a fresh conversation. The requirements were capability-framed rather than priced: an unqualified category recommendation, then a two-hundred-person distributed company running internal and external webinars, then real-time in-meeting speech translation, then external participants joining in the browser with no install. Instrument details and scoring are retained internally.

Direct observations

• The field survived in every draw, and the vendors that survived to the end were the same major platforms that opened it, Zoom, Google Meet, and Microsoft Teams, rather than new entrants.
• Specialist translation tools appeared only briefly and never became the recommended platform.
• The opening leader, Zoom, led through the first three turns in all three draws and lost first place at the browser-join requirement every time, the first requirement it structurally could not meet.
• Zoom survived demoted in two draws and was eliminated in one. Google Meet was dropped mid-sequence in all three draws and returned to first place at the browser-join requirement each time.
• Pricing was volunteered without being asked in every draw.

Interpretation (not established)

In this category and on this surface, the field survived by keeping its members and reordering them, rather than by replacing them. The leader lost its lead at the first requirement it could not satisfy, which is consistent with the position-based pattern seen elsewhere, here as demotion rather than elimination. This run cannot separate market maturity from the kind of requirement used, because the requirements here were capability-framed while the churn run they contrast with used pricing-framed requirements. The two move together, so maturity is not shown to be the cause.

Outcome and remaining uncertainty

Supported: the field survived with stable membership and the leader was moved out of first place at a specific requirement, both in all three draws, which is what the run was built to detect. The scope is narrow. One evaluator, one surface, three draws, no removal test, nothing causal. The stable-versus-churn contrast with the CRM run is confounded with requirement framing and is registered as a candidate observation carrying that confound, not as an established cause.