Business KPIs Explained: Sales, Marketing, Finance, HR and Operations
Define measures with clear denominators, periods and decision context.
Part of the Business Analytics track: modules, projects and first roles →
By the GullyMentor team · 5 min read · Published 2026-10-18 · Updated 2026-11-06 · Sources listed at the end. Not a promise about mentorship outcomes.
A key performance indicator (KPI) is a measure chosen to show progress toward a specific objective. A number only becomes a KPI when everyone agrees on its definition, its source and the decision it supports. The same word can mean different things in sales, finance, HR and operations, so write the definition down first.
What is the difference between a metric and a KPI?
A metric is any number you can calculate. A KPI is a metric tied to an objective that someone owns. Page views are a metric. "Share of visitors who place an order" is a KPI if the team is trying to improve ordering.
Ask one question of every number on a report: what would we do differently if it moved? If the answer is nothing, it is a metric, not a KPI.
Sales and marketing KPIs
Sales revenue measures value sold under a defined recognition rule. Conversion rate measures a selected outcome divided by an eligible starting population. If 40 of 1,000 fictional qualified visits become orders, that conversion rate is 4%.
Changing the denominator from visits to unique visitors changes the meaning. Cost per acquisition also depends on what counts as an acquired customer and which costs are included, such as ad spend only or ad spend plus tools and staff time.
Finance KPIs
Gross margin compares revenue with the direct costs included in its definition. If revenue is ₹10,000 and direct cost is ₹6,000, gross profit is ₹4,000 and gross margin is 40%.
This is not necessarily net profit: rent, salaries and other operating costs may be excluded. Cash collected also differs from revenue billed. Keep these distinctions visible in reports.
HR KPIs
Time-to-fill can track the duration between defined recruitment events. Choose the start and end explicitly, such as approved vacancy to accepted offer. Open vacancies require separate treatment; excluding them can make the process look faster.
Use aggregate or synthetic data in public projects. A report should not become an unsupported judgement about individual candidates or employees.
Operations KPIs
On-time completion rate requires a promised deadline and a completion definition. Average time may hide a long tail, so inspect delayed cases and variation. A median and a count of the slowest cases tell you more than one average.
How do you build a KPI step by step?
1. Write the objective in one sentence, for example "deliver orders when we promised". 2. Pick the measure that best reflects it and name the numerator and denominator. 3. Fix the period, such as a complete calendar week, so weeks are comparable. 4. Name the source table or file and the person who owns it. 5. Write down what the KPI leaves out and which cases are reported separately. 6. Agree who acts when it moves, and in which direction.
A usable KPI dictionary
| Field | Example |
|---|---|
| Objective | Understand order fulfilment reliability |
| Definition | Completed by promised time / eligible completed orders |
| Period | Complete calendar week |
| Source | Order and fulfilment records |
| Limitation | Cancelled and open orders reported separately |
What are the common mistakes?
- Mixing definitions between teams, so two reports show different conversion rates for the same week.
- Comparing a part-week with a full week.
- Reporting a ratio without its counts, which hides how small the sample is.
- Choosing a KPI because it is easy to pull, not because it reflects the objective.
- Letting one KPI drive behaviour that damages another, such as faster calls with unhappy customers.
How do you check you got it?
Hand your KPI dictionary to a classmate or colleague who has not seen the data. Ask them to recompute one value from the raw rows. If their answer differs from yours, the definition is not yet clear enough. Also describe a situation where the KPI improves while the underlying experience worsens. If you can, you understand its limits.
Worked scenario: a weekly review that went wrong
A fictional sweet shop reports "orders per day" and celebrates a rise. The owner then notices that complaints also rose. Checking the definition shows that split deliveries were being counted as two orders. The KPI went up because the counting rule changed, not because customers ordered more.
The fix is small. Count one order per customer basket, report split deliveries as a separate line and add the rule to the KPI dictionary with a date. The lesson is that a KPI change should always trigger a definition check before a celebration.
What should you build next?
Pick a fictional shop with orders, returns and ad spend. Define one KPI for each function above, state the numerator, denominator, period and owner, and put them in a one-page dictionary. Then turn them into a simple report using Build a Business Dashboard. The Business Analytics track shows where this fits in a wider learning path.
Avoid a dashboard full of unexplained green arrows. Measures should support a balanced decision, not encourage people to optimise a number at the expense of the objective.
Sources & further reading
Examples and practice recommendations are educational illustrations. Tool documentation and programme inclusions should be checked for your intended use.