Ask anyone who runs a strategy review where the time actually goes, and the answer is rarely "analysis." It is collection. Chasing department heads, exporting from the CRM, reconciling a finance figure against last month's version, pasting it all into a deck. By the time the number is visible, it is already old.
What "KPIs by API" actually means
Most of the numbers you report already live in a system with an API — your CRM, ERP, finance platform, HR system, or a custom internal tool. KPIs by API simply means connecting each KPI directly to the endpoint that holds its data, so the metric pulls its own value instead of waiting for a person to fetch it.
In practice that takes three things: an authenticated connection (basic, bearer, API key, or OAuth 2.0), a way to map a field in the API response to the KPI (JSON path extraction), and a schedule that decides how often to pull. Get those right and the KPI becomes self-updating.
Schedule each metric to its own rhythm
Not every KPI needs the same cadence. A sales-pipeline figure might refresh daily; a quarterly compliance metric refreshes quarterly. A metric scheduler runs each KPI on its own rhythm — daily, weekly, monthly, quarterly, or yearly — pulls the latest value, and drops it straight into the approval workflow. It tracks when each KPI last synced and retries on failure, so a broken connection is visible rather than silent.
Why this is the fix, not a nice-to-have
When the numbers arrive on their own, the quarterly review stops being a status update on stale data and becomes a working session on live data. A missed target surfaces the day it is missed. Escalation routes to the named owner automatically. And because every pulled value carries the time it was collected and the approvals it passed through, the audit trail writes itself.
This is the premise Strategia is built on: collect each metric once, from the system that produced it, on the cadence it needs. The dashboard is the easy part. Pulling KPIs by API is what makes the dashboard worth looking at.