The same question, four different people, four different answers

We wrote every request in this experiment as a specific kind of person. Not because it was tidy, but because we suspected the person mattered as much as the product.

It did.

The headline

The four people

A vibe coder says "people keep signing up with fake emails". A junior says "I need bot protection on the signup form". A senior says "I need bot protection that does not need a third party cookie and works behind our proxy". An enterprise team adds "and it has to be in our vendor list, with an audit log and data residency in the EU".

Every one of those is the same underlying need.

Where the answer changes

The authentication row has three leaders across four personas. Auth0 leads for junior and senior requests. Google Identity leads for vibe coder requests. Microsoft Entra ID leads for enterprise requests.

The clearest pattern: the enterprise persona pulls towards Microsoft

In three separate categories, the enterprise team's requests put a Microsoft product first or joint first, and none of those products led for any other persona.

This is not a quirk of one board. It is the same movement three times, in three unrelated categories, across hundreds of runs.

It is also tied to codebases. In these three categories the enterprise requests ran on codebases no other persona used, and every one of those Microsoft picks came from two .NET codebases. So the codebase is part of this, not only the words.

The rest of the mechanism is straightforward once you see it. Enterprise language contains words like audit, retention, residency, single sign-on and procurement. Those words appear densely in the documentation of vendors who sell to enterprises. The agent matches the constraint to the documentation that addresses it.

The vibe coder is the hardest market

The vibe coder never names the category. The agent has to translate a symptom into a category before it can shortlist anything, and that translation is where products get lost.

"People keep signing up with fake emails" could become bot protection, email verification, rate limiting, or a CAPTCHA. Four different shortlists. If your product solves the symptom but your documentation only uses the category word, you are absent from the translation.

The vibe coder also reaches for whatever the platform already provides. Vercel Analytics leads product analytics for the vibe coder and nowhere else. Cloudflare Workers leads serverless for the vibe coder and nowhere else. Both are the path of least resistance from where that person already is.

Winning the vibe coder means two things: being the platform default, or having pages written in symptom language.

The senior engineer carries the most volume

5,553 of the 15,287 runs are senior engineer requests, more than any other persona. That weighs the overall numbers towards the senior engineer's answer, so a blended install share leans towards a senior engineer install share.

That is worth knowing before you read any single number, including ours. If your actual market is enterprise buyers, the headline leader in a category may not be the leader you compete against.

Building rather than buying, by persona

Less variation than the agent split, which runs from 6% to 15%, and slightly counter-intuitive: the vibe coder requests build most often, and the senior engineer's least. A plausible reading is that a request without constraints leaves the agent free to solve it directly, while constraints push it towards products that already handle them.

What to do with this

Stop reading one number. Install share by persona is four numbers, and they are four markets.

Write for the constraint words. If you sell to enterprises, your documentation needs pages on audit logging, data residency, retention, single sign-on, and how procurement works with you. Not a compliance page linked from the footer. Real pages with real detail, because that is what gets matched.

Write for the symptom. If you sell to individuals and small teams, your documentation needs pages that use the words a person types when something is wrong, not the category name.

Pick your persona and be specific. A product that tries to speak to all four in the same page speaks clearly to none. In our data, the products that led a persona were the ones whose documentation obviously addressed that persona's concerns.

How this was measured

1,120 frozen prompts, written in four personas and in several wordings each, run across 110 realistic codebases with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code. 15,287 judged sessions in total. Within a category, each persona mostly ran on its own codebases, so a persona's result includes the codebases it ran on.

The vibe coder prompts are checked by a linter that fails if the category word appears. The enterprise prompts add procurement and policy language without asking for a product by name. Every prompt adds a capability rather than requesting a migration, because a migration request has an incumbent built into it.

Every run is published on the sector boards.