Praelor / Services / Intelligence & Fusion Managed · Analyst led · On call
Intelligence & Fusion

The picture is a job,
not a subscription.

Most organizations can buy a feed. Fewer can keep an analyst on the question long enough for the answer to be worth acting on. This service puts Praelor analysts on your standing requirements, working on AETHOS, reporting to the people who have to decide.

A feed tells you what happened somewhere. This service is for the harder question: what it means for your estate, and who in your building needs to know before the next decision.
02
What you get

An analyst on your
requirement, continuously.

The engagement is scoped around what your leadership actually has to decide, then run against that, not against a generic sector watchlist.

Standing watch

Monitoring against your requirements

Cyber, physical, geopolitical and operational reporting worked against requirements you agreed, by analysts who know what your estate is made of.

Reporting

Situation reports on your schedule

Written on the cadence you set, in the format your leadership already reads, with the sourcing attached so a claim can be checked rather than taken.

Reporting

Risk reporting for your footprint

Geopolitical and operational reporting scoped to your sector, your geography and the sites you actually run, rather than a regional summary you have to translate.

Access

A named analyst you can call

Direct access for questions that will not wait for the next report: a deep dive on a single actor, a read on an emerging situation, a second opinion before a decision.

Incident support

Analysts alongside your team

While an incident runs, Praelor analysts work the intelligence line so your own people can stay on response, with the record of what was known and when kept as it goes.

Surge

Capacity agreed in advance

Terms for additional analyst capacity settled before an elevated period, a major event or a transition, so the arrangement is not being negotiated during one.

03
How it runs

Requirements first,
then the watch.

What follows is the order of the work rather than a calendar. Cadence is set with you at the start, because a reporting rhythm that suits one leadership team suits another badly.

Requirements

We write down what the organization needs to know, which assets and decisions it supports, and who receives it. Unwritten requirements are the reason most intelligence arrives at the wrong desk.

Before anything runs
Access and sourcing

Reporting sources, platform access and points of contact are connected. What is not connected is stated plainly rather than quietly left out of the picture.

Start of engagement
Standing watch

Analysts work the requirements across domains, and route anything that crosses a threshold you set to the person who owns that decision.

Continuous
Scheduled reporting

Situation reports and risk reporting are delivered on the agreed cadence, each one carrying its sourcing and what remained uncertain.

On your cadence
Direct tasking

Deep dives, rapid assessments and direct questions are handled against the same requirements, by the analysts already carrying the account.

On request
Review

Requirements are revisited with you: what changed in the estate, what was asked for that nobody had written down, what should be dropped.

By agreement
04
What you leave with

A record, not just
a set of briefings.

Everything this service produces is retained in a form you can audit, reuse and hand to someone who was not in the room.

  • Standing intelligence requirements written, agreed and reviewed with named recipients
  • Situation reports delivered on your cadence, in your format, with sourcing attached
  • Risk reporting scoped to your sector, geography and site list
  • Assessments on request deep dives and rapid reads, retained with the reporting behind them
  • Incident intelligence record what was known, when it was known, and who was told
  • Coverage statement the sources this picture rests on, and the ones it does not

The engagement is run so that it can be handed over.

Requirements, sourcing and product templates belong to you. If you later build the capability internally, or move it to another provider, the written requirements and the product record go with you rather than staying with us.

Where a source does not exist or access was refused, that gap is stated on the product instead of being absorbed into a confident sentence.

In the first meeting

We walk one question your leadership asked recently, and name what it would have taken to answer it properly: which sources, which access, and how long.

Request a briefing →