ON THIS PAGE 7 sections
The AI Recommendation Index tracks which software brands AI assistants place on a buyer’s shortlist and which one they recommend first.
The current edition combines four category studies run in June 2026. Each study used six buying prompts and the same six-model panel, producing 36 answers per category and 144 answers in total.
This is not a global brand ranking. It is a transparent collection of category snapshots. A CRM answer and a Finnish ecommerce answer do not share the same buyer, language, or competitive set, so collapsing them into one proprietary score would create confidence the data does not support.
The Current Index
| Category | Market | Answers | Share-of-voice leader | Leader SoV | First-pick signal |
|---|---|---|---|---|---|
| Ecommerce platforms | Finland, Finnish prompts | 36 | Shopify | 97% | Category page reports model and local-platform variation |
| Accounting software | US-framed, English prompts | 36 | QuickBooks, Wave, Xero | 86% each | QuickBooks led 24 of 36 answers |
| CRM software | English buying prompts | 36 | HubSpot, Zoho CRM | 97% each | HubSpot led 24 of 36 answers |
| Project management software | English buying prompts | 36 | Jira | 92% | Jira led 8 of 36 answers |
The table exposes the central pattern: mention rate alone is not enough. Accounting and CRM both produced ties at the top of share of voice, while the first-pick distribution separated a clear leader.
Download the Q2 2026 dataset
The response-level archive is published under CC BY 4.0. It contains the 144 message outputs, exact prompts, model identifiers, run timestamps, normalized mentions, first-pick proxies, and citations. Provider reasoning, API task IDs, token use, and costs are deliberately excluded.
| File | Use |
|---|---|
| Responses · JSON | Full nested dataset for analysis and applications |
| Responses · CSV | Spreadsheet, warehouse, and notebook import |
| Category summary · JSON | Aggregated mention and first-pick counts |
| Q2 manifest · JSON | Version, coverage, license, and distribution metadata |
| All waves · JSON | Stable machine-readable index for every quarterly release |
| GitHub repository | Version history, citation metadata, and source files |
| Zenodo · DOI 10.5281/zenodo.21420271 | Immutable Q2 2026 archive and scholarly citation |
Required attribution: AI Recommendation Index by Niko Alho, linked to this page. The files are versioned by wave instead of being silently overwritten.
The Method
Each category follows the same high-level design:
- Define six buying questions covering generic, budget, use-case, and comparison intent.
- Send the same six prompts to six models with web search enabled.
- Record every named product, the opening recommendation, and the cited sources.
- Normalize obvious product-name variants into one brand.
- Calculate share of voice as answers naming the brand divided by 36.
- Report the model panel, prompt framing, run month, results, and caveats on the category page.
The panel reported in the category studies was GPT-5.5, GPT-5-nano, Claude Opus 4-8, Claude Haiku 4-5, Gemini 3.1 Pro, and Perplexity Sonar Pro. The point of listing versions is not permanence. It is the opposite: model versions are part of the observation and must be recorded because the next wave may differ.
The downloadable response archive publishes all 24 prompts verbatim and keeps each answer attached to its category, model, market, language, and run timestamp.
Share of Voice Is Not Recommendation Position
AI share of voice answers: was the brand present?
First-pick rate answers: did the answer lead with it?
Those are different commercial positions. A product named in 30 of 36 answers but placed fourth each time has strong shortlist coverage and weak recommendation priority. A product named in 18 answers and placed first in 12 may own a narrower use case more convincingly.
This distinction is why the index does not publish a single blended score yet. Any weighting between coverage and position would be a business judgment, not a fact. The raw components are more useful.
What the Four Studies Already Show
1. High visibility can hide weak positioning
Xero reached 86% share of voice in accounting but opened zero of the 36 answers. Zoho CRM matched HubSpot at 97% share of voice while HubSpot dominated first-pick position. “Mentioned everywhere” and “recommended first” are not synonyms.
2. Prompt design changes the category
Wave’s accounting visibility benefits from the free-software prompt. Linear appears more strongly in project-management prompts aimed at software teams. Notion enters the PM category even though it is not a traditional project-management product. The prompt set defines the market the model is being asked to construct.
3. Language and geography matter
The Finnish ecommerce study surfaced domestic platforms and a Finnish source graph that would not be captured by an English global prompt set. It should not be compared directly with the US-framed accounting study.
4. Cited intermediaries matter
The category studies repeatedly find comparison publishers and specialist editorial sites in the citations. Vendor pages are part of the source graph, but they do not control it. This is where entity authority and digital PR meet LLM SEO.
Limitations
The index is designed to be inspectable, not infallible.
- Small prompt panels. Six prompts can expose a positioning pattern, but they do not represent every buyer question.
- Non-deterministic answers. Live web search and generated output can change between identical runs.
- Model drift. A dated model panel becomes historical as providers update routing and versions.
- Unequal markets. The ecommerce study is Finnish; the others use different framing. Cross-category ranking would be misleading.
- Mention normalization. Product aliases and parent brands require judgment. The public generator contains the normalization patterns, while the export keeps the unedited message text for re-analysis.
- First mention is only a proxy. The first normalized brand mention can be context rather than a positive recommendation. Treat it as a reproducible positional signal, not sentiment analysis.
The dataset makes the classification inspectable, but it does not make a non-deterministic model deterministic. A rerun can verify the method and still produce a different answer.
The Quarterly Protocol
A useful index must show change, not just one snapshot.
For each new wave:
- Freeze the core prompt set before the run.
- Keep a small exploratory prompt set separate from the trend panel.
- Record the exact model identifiers and run dates.
- Run all brands through the same normalization rules.
- Publish deltas in share of voice, first-pick rate, and cited-source concentration.
- Keep old waves available so model drift is visible rather than overwritten.
Do not edit a June result into an August result. Publish a new wave and preserve the baseline.
The stable all-waves manifest points to Q2 2026 now. Q3 and later releases will receive their own directory, response files, summary, and manifest under the same URL structure.
How to Use the Index
If a brand has low share of voice, audit category coverage and the sources retrieved for the missing prompts.
If it has high share of voice but low first-pick rate, the problem is positioning: the web recognizes the brand but consistently frames it as an alternative.
If performance varies heavily by model, inspect which sources each system retrieves and which category language appears around the brand.
Then rerun the same panel after a meaningful release. The measurement loop is detailed in how to measure AI share of voice and tracking AI citations.
The job is not to win a proprietary score. It is to understand where AI-mediated buying research includes the brand, how it positions it, and which source graph creates that answer.
Q01 How is AI share of voice calculated? +
Q02 What is first-pick rate? +
Q03 Can I compare a CRM score directly with an ecommerce score? +
Q04 Is the index reproducible? +
Q05 What should a brand do with the result? +
- [01] documentation
- [02] documentation



