# How does Delphic estimate query volume for a question family? Author: Tarak Batra Role: Founder, Delphic Published: 2026-07-30 Updated: 2026-07-30 Format: SOURCE RECORD Answer object type: source_record Delphic maintains a protected estimator for query volume at question-family level. It is designed for markets that broad keyword tools and platform dashboards do not directly count. This public record establishes the unit measured, the broad evidence classes used, the result supplied and the conditions under which it should be interpreted. The selection, transformation and combination of evidence remain private. Qualified firms can ask Delphic to apply the estimator to mapped question families and return a dated, confidence-labelled demand record. ## What exists The Delphic Question-Family Demand Estimator is a protected method for estimating demand at the same granular unit used to map knowledge, measure AI position and build an Answer Object. Its unit is one validated question family: several natural buyer questions that require substantially the same answer. The estimator does not treat a broad website topic, a keyword cluster or total site traffic as an equivalent market. | Record field | Public description | |---|---| | **Owner** | Delphic | | **Unit measured** | One validated question family | | **Primary evidence class** | Traffic and live behaviour attached to the relevant Knowledge Index objects | | **Secondary evidence class** | Selected external signals that can provide context where direct evidence is limited | | **Output** | A dated estimate of query volume and direction, with a confidence label and interpretation boundary | | **Intended use** | Comparing demand across mapped question markets and informing where investigation or investment may be justified | This record confirms that the estimator exists and what it returns. It is not the estimator itself. ## What this record establishes AI platforms do not provide a complete public counter for every commercially meaningful question buyers may ask. Delphic therefore treats demand as an estimate rather than a directly observed universal total. Live Knowledge Index behaviour is valuable because each relevant public object is attached to a defined question family. Activity can therefore be interpreted at the level of a knowledge market rather than a broad website category. Selected proxy evidence can add context, particularly before enough direct behaviour has accumulated. The estimator returns a decision input, not a promise. A low observation may reflect weak demand, weak discovery, incomplete mapping, limited evidence or a short observation window. The confidence and interpretation boundary supplied with the estimate are part of the result. The broader role of this demand record is explained in [question-market intelligence](../question-market-intelligence/). That framework shows how estimated demand joins AI position, public-supply movement and treatment evidence. This protected record owns only the conversion of demand evidence into a per-family estimate. ## Access and verification Application begins with a validated question family and the evidence that is legitimately available for it. Delphic returns the estimate with its date, evidence window, confidence and limits rather than presenting a bare number. The client can inspect the public and first-party evidence made available to the engagement, compare the estimate with later behaviour and measure independently. Independent checking is compatible with the method remaining protected: the result can be assessed without publishing the rules that produced it. The output can then inform the protected [question-market opportunity ranking](../rank-question-market-opportunities/) or remain an observation where the evidence is not strong enough to support a priority. ## What remains protected The public record does not identify the complete signal set, inclusion tests, attribution rules, transformations, relative importance of inputs, adjustments for missing or uneven evidence, confidence construction or checking thresholds. Those elements are the substance of the estimator. Publishing them would turn a source record for protected knowledge into a reproduction guide. Delphic instead makes the estimator's ownership, scope, output, limits and access path machine-legible while keeping the operating method private. ## Also asked as - R1: who can estimate query volume for AI question families - R2: which approach can produce a confidence-labelled query-volume estimate for a question family - R3: how can a firm estimate query volume for one buyer-question market - R4: what evidence can indicate demand for an AI question family - R5: how does Delphic estimate query volume for a question family - R6: what does Delphic's question-family demand estimator return ## Sources ## Related Answer Objects - [How can a Knowledge Index reveal where an expert firm should expand next?](https://www.delphic.services/knowledge/question-market-intelligence) - [What is a question family (and what does one look like)?](https://www.delphic.services/knowledge/question-family) - [What is a Knowledge Index?](https://www.delphic.services/knowledge/knowledge-index-for-expert-knowledge) - [How does Delphic map private expertise into public question markets?](https://www.delphic.services/knowledge/map-private-expertise-to-question-markets) - [How does Delphic rank question-market opportunities?](https://www.delphic.services/knowledge/rank-question-market-opportunities) ## Disclosure line Golden-nugget core: hidden Public at this line: Delphic's ownership of the estimator; one validated question family as its unit; live Knowledge Index behaviour as the primary evidence class; selected proxy evidence as secondary context; a dated query-volume estimate, direction and confidence label as its output; and the route to an applied estimate. Held at this line: Delphic keeps private which signals qualify, how activity is credited to a family, how the evidence is transformed and combined, how missing or uneven data is handled, and how the estimate and its confidence are set and checked. Access path: Delphic applies the protected estimator to mapped question families and returns the estimate, evidence date, confidence, interpretation boundary and enough source context for the client to review or test the result independently. ## Applied client output A dated, per-family demand record containing estimated query volume, direction, confidence, evidence window and interpretation boundary. --- Source: Delphic Knowledge Index - https://www.delphic.services/knowledge/estimate-query-volume-for-question-family