| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Revenue recognition | Accounting and close | 8% | 4 of 77 | 32% | 19 | criticized challenger | ▲+3Since September 2026: 4% → 7%, +3 points. Inside the 10-point floor: within noise. Read over the models both editions asked. |
| SaaS metrics and analytics | Planning and analysis | 0% | 63 of 78 | 0% | 1 | under 10 labels · led by ChartMogul at 49% | newNew since September 2026: not ranked then, 0% now. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Revenue recognition | 4% | 7% | ▲+3Since September 2026: 4% → 7%, +3 points. Inside the 10-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 9 → 4 of 77 |
| SaaS metrics | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 63 of 78, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 10 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 1 | 1 |
| Gemini 3.5 Flash | 1 | 0 | 2 | 1 | 4 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 1 | 1 | 1 | 1 | 4 |
| Mistral Small | 0 | 1 | 0 | 0 | 1 |
| DeepSeek V4 Flash | 1 | 1 | 0 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 1 | 1 |
| Kimi K2 | 0 | 0 | 0 | 1 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 0 | 0 | 1 |
| MiniMax M2.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-6 Luna | 1 | 0 | 0 | 1 | 2 |
| Muse Glimmer 30B | 0 | 0 | 1 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“For a limited budget, Stripe Revenue Recognition is my first pick—if most of your revenue runs through Stripe.” GPT-6 Luna · Revenue recognition · budget prompt · first choice
“For most small businesses on a tight budget, Stripe Revenue Recognition at $25/month (if you use Stripe)” DeepSeek V4 Flash · Revenue recognition · budget prompt · first choice
“If you are already on Stripe: Turn on Stripe Revenue Recognition.” Gemini 3.5 Flash · Revenue recognition · budget prompt · first choice
“Stripe Revenue Recognition stands out as one of the best options” Grok 4.1 Fast · Revenue recognition · budget prompt · first choice
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“it lacks advanced features needed for complex B2B contracts... If you have complex contracts (e.g., mixed products): Avoid Stripe.” Qwen 3.7 Flash · Revenue recognition · comparative prompt · soft negative
“Easy entry point but leaves gaps—recognition data doesn't automatically flow into your GL; best as a baseline tool” Kimi K2 · Revenue recognition · comparative prompt · soft negative
“check whether its handling of your full contract and accounting workflow is sufficient” GPT-6 Luna · Revenue recognition · comparative prompt · soft negative
“you should be highly cautious of them as you scale” Gemini 3.5 Flash · Revenue recognition · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 50 of the 50 answers that named Stripe Revenue Recognition and are not a share of its labels.
188 of the 209 domain citations in answers naming Stripe Revenue Recognition came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Stripe Revenue Recognition's own pages state, read September 28, 2026: docs.stripe.com/revenue-recognition, stripe.com/revenue-recognition/pricing, docs.stripe.com/revenue-recognition/api, docs.stripe.com/revenue-recognition/rules, docs.stripe.com/revenue-recognition/reports. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Stripe Revenue Recognition's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Stripe Revenue Recognition, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Stripe Revenue Recognition by email, built from the raw record of the edition. It shows: