KPI examples for a Maltese business, department by department

A key performance indicator is simply a number you have agreed to steer by. The list below gives examples for each part of a business, with the one thing each KPI needs before it is worth tracking: a definition written down once. Use it to pick a short set, not all of them.

Three tests before a number becomes a KPI

1. It is tied to money. If the number moves, you can say what it changes in revenue, margin or cash. If you cannot, it is a metric worth watching, not a KPI worth steering by.

2. Someone owns it. One named person answers for it and knows what to do when it drifts.

3. It can be produced without rebuilding it. If it takes a day of exports every month, it will be late, argued over and eventually dropped.

Sales KPIs

Revenue by customer. Agree whether revenue means the order or the invoice. Sales often counts one, finance the other, and both are right by their own definition.

Pipeline value by stage. Agree what “qualified” means, so the pipeline is not everyone's optimism added together.

Win rate. Deals won divided by deals decided. Agree whether a deal that goes quiet counts as lost, and after how long.

Average order value. Agree whether discounts and returns are taken off.

Finance KPIs

Gross margin by product or service. The total margin hides which work pays for the rest. Agree which costs sit inside the margin and which sit below it.

Cash conversion. How long it takes for work delivered to become cash in the bank. Agree the start point: the order, the delivery or the invoice.

Debtor days. Agree whether it is measured from the invoice date or the due date.

Budget against actual. Only useful if actuals are built from the same definitions as the budget.

Operations KPIs

On-time delivery. Agree what “on time” is measured against: the date promised or the date requested.

Capacity used. Hours, rooms, tables or machines in use, against what was available.

Stock cover. How long current stock lasts at the current rate of sale. Agree which sales period sets the rate.

Rework or returns. Work or goods that came back. Agree what counts as a return.

Customer KPIs

Repeat rate. Customers who bought again within a set period. Agree the period.

Revenue per customer. Useful beside the cost to serve, not instead of it.

Cost to serve. What it costs to look after a customer once they have bought, including the hours nobody bills. This is often the number no single system holds.

Complaints or tickets per order. Agree what counts as a complaint.

People KPIs

Utilisation. Billable or productive hours against hours available. Agree what counts as productive.

Overtime. Hours beyond contract, by team, beside the work they produced.

Staff turnover. Leavers against average headcount. Agree the period.

People cost as a share of revenue. Only meaningful when revenue and people cost come from the same period and the same definitions.

Marketing KPIs

Cost per enquiry. Spend against enquiries, by channel.

Cost per booked meeting or sale. Closer to the money than cost per enquiry, and harder to game.

Enquiry to customer rate. Agree when an enquiry becomes a customer: the first order or the first payment.

Examples by sector

Hospitality: occupancy, average rate, revenue per available room, and margin by event or menu once staff hours and supplier costs are counted.

Retail and distribution: margin by category and branch, stock turn, and sales per channel after discounts and returns.

Professional services: utilisation, realisation (what was billed against the time recorded), work in progress, and margin by client.

Why the same KPI shows two different numbers

Two reports can show different figures for the same KPI when each pulls from its own system, at a different moment, with its own definition. We wrote about this in why two departments never agree on the number. The fix is not a better spreadsheet. It is agreeing each definition once and building every report from the same source.

From a list of KPIs to a Command Centre

A KPI list only helps if the numbers arrive on their own. That usually means three things:

1. One source. The systems the business already runs load into one data warehouse the business owns, on a schedule, so nobody exports anything.

2. One definition per KPI. Written down with the people who use it, and inherited by every report.

3. One view per role. The owner sees the whole business; a department head sees what their role needs.

Put together, that is a Command Centre: one data ecosystem the business owns, the whole business on one screen, one set of numbers. A KPI dashboard is the last step of that work, not the first.

Frequently asked questions

How many KPIs should a business track?
Fewer than most businesses start with. A handful per role that pass the three tests above will do more than a long list nobody owns.

What is the difference between a KPI and a metric?
A metric is any number you can measure. A KPI is a metric you have chosen to steer by, with an owner and an agreed definition.

How often should KPIs be updated?
As often as the decision they support is made. Most operational KPIs are worth seeing daily; most financial ones weekly or monthly. What matters is that updating them takes no manual work.

Who should own a KPI?
The person who can act on it. If nobody can change the number, it should not be a KPI.

Do we need new systems to track KPIs?
Usually not. The data normally already exists in the accounting, sales, operations and payroll systems a business runs. What is missing is the connection between them and the agreed definitions, and that is what a Command Centre adds on top of the systems you keep.