Metrics That Matter: Core Work

Why this matters

Founders almost always track too many numbers or the wrong ones. Both lead to the same place: decisions made on gut feel while a spreadsheet collects dust.

A service business with 10-80 people generates hundreds of data points every month. Revenue, hours billed, proposals sent, social media reach, employee satisfaction, pipeline value. The instinct is to track all of them. The result is a dashboard nobody opens after week two.

The real job is choosing 5-7 metrics that tell you whether money is coming in, work is getting done, and cash is actually reaching your account. Everything else is noise until those numbers are healthy. This chapter gives you the selection logic, the structure to cascade those metrics to your teams, and a scoreboard your people will actually use.

This maps directly to the Leads, Conversion, and Revenue Model audits in your ARCAS diagnosis. If those audits flagged gaps, this is where you close them.

A founder you might recognise

Two years back, the founder of a 35 person facilities management business in Abu Dhabi was running AED 14.2M (USD 3.9M) on maintenance contracts for commercial buildings. The dashboard had 23 metrics. The operations lead had built it in Excel over two years. It tracked everything from Instagram engagement to vehicle fuel costs to average response time per maintenance ticket.

Every Sunday, the operations lead spent three hours updating it. Every Monday, the founder glanced at the revenue line, ignored the rest, and asked on WhatsApp: "How many new contracts did we close this month?"

The dashboard told the founder everything except what he needed to know. He could not answer three questions. Are we winning enough new work? Are we collecting cash fast enough? Is each worker producing enough revenue to keep margins healthy?

He did not have a data problem. He had a selection problem.

Leading vs lagging: know what you are looking at

A lagging metric tells you what already happened. Revenue last month. Contracts lost this quarter. Cash collected in January. These are important, but by the time you read them, the outcome is fixed.

A leading metric tells you what is likely to happen. Proposals sent this week. Site visits booked. Renewal conversations started 90 days before contract end. These are the numbers you can still influence.

It is common to track only lagging metrics. The founder knows revenue dropped but cannot explain why until they dig through emails and WhatsApp threads. The fix is simple: pair every lagging metric with one or two leading metrics that predict it.

Revenue (lagging) pairs with qualified leads per week and proposals sent (leading). If leads drop in March, revenue drops in May. You see it coming.

Cash collected (lagging) pairs with invoices sent within 48 hours of job completion (leading). If your team delays invoicing, your collection days stretch. You see it before the bank balance tells you.

Client retention (lagging) pairs with renewal conversations started 90 days out (leading). If nobody starts those conversations, you find out clients left when the contract simply expires.

The 5-7 metric rule

Here is the hard truth: if you track more than seven metrics at company level, nobody tracks any of them. The number is the limit of what a team can hold in working memory during a weekly meeting, not an arbitrary choice.

Pick five to seven. No more. If someone argues for an eighth, ask them which of the current seven they want to drop. This forcing function is the entire point.

For a UAE service business, these five usually cover it:

1. Revenue per worker per month (connects to Part 1, Chapter 4). Take monthly revenue, divide by headcount. If this number is flat or falling while you add people, you are scaling costs faster than income.
2. Qualified leads generated per week. Not followers. Not website visits. People who fit your client profile and have expressed interest.
3. Proposal-to-win rate. Proposals sent vs proposals signed. If you send 20 proposals and win 2, your sales process has a conversion leak.
4. Cash collection days. Average number of days between invoice date and payment received. In the UAE, this is survival arithmetic. Anything above 60 days in a service business means you are funding your clients' cash flow.
5. Billable rate. Billable hours divided by available hours. For a facilities management or consulting firm, the difference between 65% and 80% on this metric is the difference between breaking even and a healthy margin.

Add a sixth or seventh only if your business model demands it. A recruitment firm might add "placements per recruiter per month." An architecture practice might add "project margin at completion vs estimate." But five is a strong starting point.

The metrics cascade

Company-level metrics belong to the founder and leadership team. But they only move if teams and individuals know which piece they own. This is the cascade.

Company level (3-5 metrics). These are the numbers you review every Sunday or Monday. Revenue per worker. Qualified leads. Proposal-to-win rate. Cash collection days. Billable rate.

Team level (2-3 metrics per team). Each team owns the inputs to one or two company metrics. Your sales team owns qualified leads and proposal-to-win rate. Your operations team owns billable rate and project delivery margin. Your finance and admin team owns cash collection days and invoicing speed.

Individual level (1-2 metrics per person). Each person owns one or two numbers that feed their team metric. A sales coordinator tracks "discovery calls booked this week." A project manager tracks "jobs completed on schedule." An accounts receivable clerk tracks "invoices sent within 48 hours."

The cascade makes accountability specific. When the founder asked the operations lead why leads had dropped, she could point to the sales coordinator's number: discovery calls booked fell from 12 per week to 4. The coordinator had been pulled onto a proposal for three weeks. The leading indicator showed the problem. The cascade showed who could fix it.

The weekly scoreboard

A scoreboard works when it fits on one screen and updates weekly. No scrolling. No tabs. No login required.

Build it in Excel or Google Sheets. One row per metric. Six columns:

Share it in the team WhatsApp group every Monday morning. Review it in a 20-minute standup. Ask three questions per metric: Is it on target? If not, why? What will we do this week to move it?

That is the entire meeting. Twenty minutes. Five metrics. Fifteen questions. Done.

Vanity metrics vs revenue-connected metrics

A vanity metric feels good but does not connect to revenue. Instagram followers, website page views, LinkedIn post impressions, event attendance. These are activity metrics. They measure motion, not progress.

A revenue-connected metric traces a clear line to cash in your account. Leads generated from that Instagram account. Proposals that came from website inquiries. Clients acquired through that LinkedIn campaign. Contracts signed after that event.

The team posted on Instagram three times a week. They had 4,200 followers. The marketing coordinator reported "engagement is up 18% this month." The founder felt good about it. But when they traced it: zero of their 22 active contracts came from Instagram. Their actual lead sources were referrals (14 contracts), direct outreach (6), and a government portal (2).

The test is simple. For every metric someone wants to track, ask: "Can you draw a line from this number to revenue collected in the next 90 days?" If the answer is no, it is not one of your seven.

Emiratisation compliance as a metric

If your company has 20 or more employees in a targeted sector, Emiratisation belongs on your scoreboard. Non-compliance is a lagging indicator. Once MoHRE issues the fine, the problem already happened months ago. Track the leading indicators instead.

Three numbers to watch:

1. Emirati headcount vs MoHRE target. Know the current required count or percentage for your headcount band and where you stand against it. Update monthly as your total headcount changes.
2. Emirati employee retention rate. If Emirati hires leave within the first year, your compliance count resets and your recruiting cost doubles. A retention rate below 70% at the 12-month mark signals a role design or onboarding problem, not a hiring problem.
3. Time to productivity for Emirati hires. Measure how long it takes a new Emirati employee to perform their role independently. If the answer is "they never really got there," review the role card and SOP before concluding it was a hiring mistake.

For the 20 to 49 employee SME track, recent financial contributions were AED 96,000 (USD 26,140) for the missed 2024 UAE citizen target and AED 108,000 (USD 29,410) for the missed 2025 target. But the real cost is the cycle of hiring, losing, and rehiring without fixing the underlying structure. Put these three numbers on the scoreboard, assign an owner, and review them monthly alongside your other metrics.

Common mistakes

Tracking inputs instead of outcomes. "We sent 15 proposals" is an input. "We won 5 of 15 proposals" is an outcome. Track the ratio, not just the activity.

Changing metrics every quarter. Pick your five to seven and keep them for at least six months. You need trend data. A number in isolation means nothing. The same number compared to the last 12 weeks tells a story.

Making the scoreboard too complex. If someone needs training to read it, simplify it. If it requires more than 30 minutes to update, automate the data pull or reduce the metrics.

Ignoring cash collection days. In the UAE, this is not optional. Many service businesses have strong revenue on paper and weak cash positions because clients pay at 90 or 120 days. Track it weekly. Treat it like oxygen.

No individual ownership. If a metric has no name next to it, nobody owns it. Unowned metrics do not move.

When to move on

You are ready to move on when you can answer yes to all three:

• You have a scoreboard with 5-7 metrics, updated weekly, reviewed in a standup.
• Every metric has a named owner and a target.
• You have at least four weeks of trend data and your team can explain why each number moved.

If you cannot say yes to all three, stay here. The chapters ahead assume your team knows what to measure and is already measuring it.

Working prompts

People

• Who on your team currently owns each metric? If nobody does, who should?
• Does every team member know which 1-2 numbers they personally affect?
• When a metric drops, does the responsible person find out in the weekly standup or weeks later?

System

• Is your scoreboard updated in under 30 minutes each week?
• Do your leading metrics actually predict your lagging metrics? Check by comparing three months of data.
• Is your cascade documented, or does it only exist in your head?

AI

• Could a simple Zoho or Excel formula auto-pull data from your invoicing system into the scoreboard?
• Are there manual data entry steps that a scheduled report could replace?
• Once you have 12 weeks of data, could a trendline alert you when a leading metric drops below threshold?

Founder exercise

Part A: Select your metrics (30 minutes)

List every number your business currently tracks. Write them all down. Now cross out everything that fails the 90-day revenue connection test. From what remains, pick five to seven. Assign each one a named owner and a weekly target.

Part B: Build the scoreboard (45 minutes)

Open a new Excel or Google Sheets file. Create the six-column table from this chapter: Metric, Owner, Target, This Week, Last Week, Trend. Fill in this week's numbers. If you do not have the data, that gap is your first finding.

Part C: Run the first review (20 minutes)

Gather your team leads. Walk through each metric. For every number below target, ask: "Why?" and "What will we do this week?" Write the actions in the WhatsApp group. Next Monday, check if they moved the number.

ARCAS lens

Metrics are not a systems project. They are a people project with a systems wrapper. The cascade works because it gives each person a clear number to own. The scoreboard works because it is simple enough that your team will actually use it. Technology enters last: auto-pulling data, sending alerts, spotting trends. But none of that matters if the five metrics are wrong or if nobody reviews them weekly.

This is the pattern across the ARCAS model. People first: assign ownership, set expectations, create accountability. Systems second: build the scoreboard, define the review rhythm, document the cascade. AI third: automate the data, flag anomalies, predict trends. Skip the first two and the third is just an expensive notification system.

Start now: Quick self-assessment

Rate each statement from 1 (not true) to 5 (completely true):

Score 25-30: Your metrics system is working. Move to the next chapter. Score 16-24: The structure exists but has gaps. Use the founder exercise to tighten it. Score 6-15: Start with Part A of the founder exercise today. Pick five metrics and assign owners before your next Monday standup.