The moments that trigger the question
B2B software moments arrive in roles: the practitioner hitting a wall in the current tool, the founder consolidating spend, the ops lead with a migration deadline, security clearing a vendor, procurement asking who else uses it. Each role phrases differently and pulls different evidence, and products routinely win the practitioner conversation while losing the economic-buyer one about the same purchase.
The sources the answers lean on
For software recommendations, assistants lean on review platforms and their structured ratings, comparison articles and category listicles, community threads where users speak plainly, documentation and changelogs as proof of substance, and vendor pages that state pricing, limits and fit honestly. Refusing to publish pricing has a specific cost here: the assistant fills the gap from third parties, accurately or not.
Why the same software products keep winning
The products that keep getting named supply comparable facts, real pricing, honest fit statements, named alternatives, and their review and community record corroborates the claims. Category incumbents dominate generic asks through sheer citation depth, but focused tools win the specific moments, this team size, this stack, this compliance need, whenever their evidence matches tighter than the incumbent's.
Run the test yourself, and what software products can do about it
The test costs nothing: ask ChatGPT, Gemini, Claude and Perplexity the questions above, phrased the way a real person would say them, and write down who gets named and what sources appear. Run each question twice on different days, since answers vary and patterns matter more than single runs.
For SaaS teams, the fixes: publish pricing and honest comparison pages, keep review profiles active, and show up in the community threads your buyers read, as named people with disclosure. For software products that want the systematic version, the free Aethon audit runs your real buyer questions across all four assistants with screenshots, and the SaaS playbook turns the gaps into a work plan.