- How many prompts does a B2B software company actually need?
- Enough to cover the questions that precede a purchase in your category, which in practice means dozens rather than a handful. Count the jobs your product is bought for, multiply by the phrasings a buyer might use, and add the named-competitor comparisons. The number that falls out is usually larger than the entry tier of most tools allows.
- Do review sites matter more than our own site?
- Review platforms are structured, frequently updated and heavily referenced, which makes them exactly the kind of source an engine reaches for when asked to compare products. Your own site is where the specifics live and where a citation sends a buyer. Both matter, and neglecting the review corpus while perfecting the site is the more common mistake.
- Can we just check manually?
- Manual checking works to establish whether a problem exists and is the sensible first step. Where it fails is in tracking change, because answers vary between runs and a person checking occasionally cannot separate a real movement from ordinary variance. Automated sampling exists to make the trend readable, not to produce a better single answer.
- Is documentation worth optimising?
- Documentation says checkable things about how a product behaves, which is the kind of passage a model can quote without hedging. Marketing pages tend to make claims that require trust. In categories where the buyer is technical, the docs frequently carry more citation weight than the homepage, and they are usually the part of the site nobody has looked at.
- Should we buy a tool before or after fixing the site?
- Fix access and rendering first, because those decide whether anything else can work, and both are free to diagnose. Buy measurement once you need to know whether the work is moving the number. Buying in the other order produces a year of dashboards confirming a problem you could have found in an afternoon.