A requirements gap is not always obvious from the stakeholder conversation alone.
A Business Analyst may recognise that a requirement is incomplete, unusually broad or missing important context, while still having no credible external reference point against which to examine it.
Industry Benchmark Intelligence is Antozoe's approach to providing that context: sourced reference information for the project's industry, surfaced during requirements gap analysis without generating benchmark figures simply to fill the screen.
Where benchmark intelligence sits in FLOW
Industry Benchmark Intelligence appears during the Optimise stage of the FLOW methodology.
That placement is deliberate.
By this point, the stakeholder evidence has already been captured and the relevant requirements, decisions, business rules, risks and questions have been identified.
The BA is now examining what may be missing, unclear or in conflict.
Industry context can be useful here because it remains separate from the stakeholder evidence.
A benchmark does not become a stakeholder requirement simply because it exists. It is an external reference point that the BA can decide whether — and how — to use.
What the benchmark panel shows
Where sourced benchmark information is available, the panel is designed to make its provenance visible alongside the figure itself.
A benchmark entry can identify the metric being considered, its typical reference value, the source from which it was obtained and the date or period against which that information was current.
Those details matter as much as the number.
A figure without provenance can look authoritative while giving the analyst very little basis for deciding whether it applies to the organisation, market or problem in front of them.
Industry data can also age, differ between markets and depend heavily on how a metric was defined.
The source and date therefore remain part of the analysis rather than disappearing behind the benchmark value.
What happens when there is no benchmark
Antozoe does not generate or estimate benchmark figures on demand merely because the panel exists.
Benchmark material is added from sourced reference information.
If no sourced benchmark has been added for the relevant industry or metric, the correct result is an empty state explaining that no benchmark data is currently available.
There is no synthetic average, illustrative percentage or placeholder dressed up as industry evidence.
That constraint is intentional.
In a client conversation, "we do not currently have a defensible reference point for this" is a more useful answer than presenting an invented one.
A benchmark is context, not truth
Even properly sourced benchmark data should not replace analysis.
A typical industry value does not establish what an individual organisation must do, and it does not automatically make a stakeholder requirement correct or incorrect.
The BA still needs to consider the organisation's operating model, scale, regulation, objectives, constraints and the definition behind the metric itself.
Industry Benchmark Intelligence is therefore best understood as additional evidence for examination rather than an answer engine.
It gives the analyst another question to ask:
How does what we have heard compare with credible external context?
Why sourcing matters
The practical test of a benchmark is what happens when a stakeholder asks:
Where did that figure come from?
If the source, context and date cannot be examined, the number becomes difficult to defend.
Keeping provenance attached allows the BA to decide whether the benchmark is appropriate before carrying it into a requirement discussion or client recommendation.
It also creates an important boundary inside the product.
Stakeholder evidence remains stakeholder evidence.
Industry reference material remains external context.
And when external context is not available, Antozoe says so.
That separation is a small design decision with a larger governance consequence: the system does not need to pretend to know something simply because a useful answer would be convenient.