The intelligence cycle · 1 of 6

Direction

You decide what the platform cares about. Requirements come first, and everything downstream — collection, scoring, reporting — is answerable to them.


What you can do

  • Requirements in three tiers — Priority Intelligence Requirements at organisation, sector and global level. Collected items and generated reports are scored against them, not against a generic feed.
  • Industry sets, preloaded — Requirement cassettes for maritime, healthcare, financial services, energy and education load at onboarding, so your first week starts from a real collection plan.
  • Your wording, your ranking — Rewrite a requirement in your own language and it re-ranks what surfaces beneath it. The phrasing is not decoration — it drives retrieval.
  • Curate the stream — Choose sources, boost what matters with priority keywords, exclude what does not, and tag as you go so nothing becomes unfindable later.

0.93

Requirement classification

precision against a labelled golden set

1.00

Routing recall

feed-to-requirement routing, measured

3

Tiers

organisation, sector and global — nested, not parallel

What we deliberately do not make configurable

Severity is one shared rubric, not a per-tenant dial. Reports are generated once for everyone, so a tenant-tunable severity scale would mean the same threat carrying different severities in different accounts with nothing to reconcile them. Customisation belongs on routing and thresholds, which is where you will find it.

The rest of the cycle

See it against your own requirements

The fastest way to judge an intelligence platform is to point it at what you actually need to know.

Contact Sales