Decision Intelligence· Build, monitor, detect, diagnose

Build the KPI. Watch it. Know why it moved.

Decision Intelligence runs the whole life of a KPI. An agent builds it from your question and proves it on your data, Pulse watches it month by month, alert rules catch the change, and root-cause analysis finds where it moved and why — then what-ifs show what would change it.

In the product: Decision Lab · Pulse

New KPI · Regretted attritiondry run · nothing saved
Measure
Regretted voluntary exits ÷ average headcount
Population
Permanent employees
Breakdown
Department
Period
Rolling 12 months, read monthly

Dry run · regretted attrition, last 12 months

9.80%14.60%11.20%7.40%
Create KPIWatch in PulseAlert above 10%Sample data
Modules

6 modules, one suite.

  • KPI builderAn agent designs the KPI from your question and proves it on your data.
  • PulseWatchlists that track your KPIs month by month, with notes and comparisons.
  • AlertsRules on a level, the previous period or the same period last year, in your inbox.
  • Root cause analysisWhere a KPI moved and why — hypotheses tested on the graph.
  • What-ifs & scenariosExact, projected or estimated — and the change that would reach a goal.
  • Decision LabThe AI analyst, in plain English, with every figure checked.
What it does

Decision Intelligence, part by part.

  • 01

    Built from the question

    The definition — measure, population, breakdown, period — is written by code from the question itself, not retyped into a form.

  • 02

    Proven before it is saved

    Every new KPI runs as a dry run on your data first, so you approve figures, not a description. It is created only on your go-ahead.

  • 03

    Diagnosed, not guessed

    A change is split into parts that add up exactly to it, then candidate causes are searched in your graph and each one is tested.

  • 04

    Decided with what-ifs

    Change an assumption and see the answer worked out again — exact on an answer, projected on a forecast, estimated on a model.

How it works

Build, Monitor, Detect, Diagnose, Decide.

  1. Step 1

    Build

    The agent designs the KPI and proves it on your data.

  2. Step 2

    Monitor

    Pulse watches it month by month, in watchlists.

  3. Step 3

    Detect

    Alert rules catch a level or a change, in your inbox.

  4. Step 4

    Diagnose

    Root-cause analysis finds where it moved, and why.

  5. Step 5

    Decide

    What-ifs show what would change it.

Root cause, step by step

How a change is diagnosed

Findings are worded by the strength of the evidence — correlated, contributing, or a likely root cause under stated assumptions — and never presented as proven.

StepWhat happens
Moved
The KPI's change, and the periods compared.
Where
The change split into parts that add up exactly to it; the largest are kept until they explain 80% of it.
Discover
Candidate causes searched across the graph's own signals: HR events, features and record properties.
Test
Each hypothesis is a condition found in the graph, shown as a measure and classed a likely root cause, contributing, correlated or unrelated.
Why, again
The analysis asks why again of its own findings, up to four levels below the first.
Keep
The finding is kept with every step and the graph queries behind it.
Ask it

Questions it answers, in your words.

  • “Turn this answer into a KPI I can watch.”
  • “Alert me when regretted attrition in Engineering crosses 10%.”
  • “Why did headcount drop between January and February?”
Works with

On the same model and graph

Your next people decision, with the why attached.

Request a demo. We'll email you a two-minute walkthrough today, then set up a time that suits you.

We'll use your email to set up your demo. Remove it any time. Privacy Policy