2. What prompts should we track for AI search visibility?

Demand a documented buying-question library, not an unexplained list generated by the monitoring tool.

Put to: Aleyda Solís, with an in-house demand-generation leader.

Why it matters to buyers: Solís’s prompt-library framework organises coverage around journey stage, offering, audience, market and business priority. It distinguishes a purposeful sampling system from an exhaustive collection of possible questions. (aleydasolis.com)

Ask: “How would you build a B2B SaaS AI-search prompt list from our actual sales process, and which parts would you admit are inferred rather than observed?”

A good answer should cover:

• Provenance labels: customer-supplied AI conversations, interview-derived needs, sales objections, search-derived questions and analyst-generated tests.
• Separate discovery, requirements, comparison, alternatives, validation and branded-reputation groups.
• Realistic constraints, such as implementation capacity, integrations, company size and security requirements.
• A fixed core for trend reporting and a separately labelled exploratory set.
• A process for challenging irrelevant or artificially favourable prompts before collection begins.

Illustrative question—not observed demand: “Which customer-support platforms suit a US software company with 200 employees, Salesforce integration and a small implementation team?”

Press for: the five prompts the expert would remove from the buyer’s existing tracker, with reasons. Ask what evidence would change their weighting of the remaining groups.

Expert quote — pending: ____________________