KPI page

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Subtractive by design — a page with fifteen tiles has no key indicators on it.

Every tile has an action attached, which is the test for whether it belongs.

Visible without running a report, which is the only way a daily number gets looked at daily.

How it works

1
Each tile names a source module and an aggregation — count of Orders, sum of Payments.
2
It recomputes on read, so there is no stored figure to go stale and no refresh to forget.
3
The trend compares against the previous period of equal length.
4
A tile whose source is empty shows a dash rather than a zero, because those mean different things.

Best for

The top of a dashboard, answering "is this going well".

Not the right choice for

Anything needing more than a glance.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Indicatorrequired	text	Named once when the tile is created, then left alone.
Nowrequired	text	Aggregated from the source module on read. Nobody writes this.
Target	text	The number that makes the current one good or bad.
Trend	choice	Up, Down or Flat against the previous period. Derived, never stated.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Four tiles is the practical maximum. A page with fifteen has no key indicators on it.
Aggregations are count, sum and average only. Anything conditional needs a Segment first.
No alerting or thresholds — it shows a number, it will not tell you the number is bad.
A partial current period always compares badly, and nothing corrects for that.

Before it works

What you have to provide, if anything.

Needs at least one other module holding data. This aggregates; it does not collect.
Set a target per tile, or the number has nothing to be read against.

In practice

A shop owner who checked figures once a month and reacted late.

“Orders today, unanswered messages, stock alerts, overdue invoices. Nothing else.”

What was said to the agent

What the agent built

Four tiles against targets, each aggregating a module already collecting.

What changed

Unanswered messages at four was the one nobody expected. It had been climbing for a week and nothing else would have shown it.

Better with

These do a different job on the same data. An agent can have all of them.

Metrics dashboardLive

Numbers move over time and the movement matters more than any single reading.

Revenue KPILive

Someone checks the business daily or weekly and needs the headline figures without opening a report.

Status pageLive

Customers depend on the service being available and, when it is not, they need somewhere to look that is not your inbox.

Questions

What data does the KPI page page use?

It reads metric records the agent has collected. Headline numbers. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a kpi the wrong choice?

Anything needing more than a glance. It is best for: the top of a dashboard, answering "is this going well".

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.