Every founder we talk to says they track KPIs. Almost none of them are tracking the right things.
This isn't a criticism — it's a structural problem. The term "KPI" has been so thoroughly genericized that it has become almost meaningless. Finance software vendors sell dashboards full of KPIs. Consultants deliver decks full of KPIs. Boards ask for KPIs in the monthly package.
The result is that most leadership teams are watching the right numbers, and still making decisions slowly, reactively, or not at all.
The difference between a KPI and a CPF
A Key Performance Indicator is a metric that tells you how your business performed. A Critical Performance Factor is a metric that tells you why — and points to a specific action.
The distinction matters because performance metrics are inherently backward-looking. Revenue last month, gross margin last quarter, churn in the trailing twelve months — these tell you where you've been. They're necessary, but they're not sufficient for running a business at pace.
A CPF is a leading indicator with an owner, a threshold, and a defined response. It's not something you report. It's something you act on.
Most dashboards are full of KPIs. The businesses that compound year over year are running on CPFs.
The four CPFs that matter in every business
After 30 years and 1,000+ engagements across manufacturing, SaaS, defense contracting, professional services, and real estate, we've found that nearly every business has four underlying drivers that determine whether it grows, stalls, or fails — regardless of industry.
Building a dashboard you actually use
A useful financial dashboard has three properties: it's visible to the people who can act on it, it updates on a cadence that matches the decisions being made, and it has defined thresholds that trigger a response.
Most dashboards fail the third test. The numbers are accurate. They might even be beautiful. But no one has agreed on what it means when cash conversion drops below a certain threshold, or when a single customer reaches 35% of revenue.
Without that agreement, a dashboard is a report. With it, it's a management system.
A simple test: For each of your four CPFs, ask: "What number, if it moved 20% in the wrong direction, would change what I do this week?" If you can't answer that question, you don't have a dashboard problem. You have a clarity problem — and that's the more valuable thing to fix.
What this looks like in practice
We build CPF dashboards differently from standard reporting packages. Instead of organizing metrics by category (revenue, cost, headcount), we organize by decision: what does leadership need to see to make the five most important operating decisions in this business?
For a $15M professional services firm, those decisions might be: how to price new engagements, when to hire the next senior person, whether to take on a new client that increases concentration, how aggressively to invest in business development, and when to raise debt or equity for growth.
Every number on the dashboard is there because it informs one of those five decisions. Nothing else makes the cut.
- Utilization rate by practice area — informs pricing and hiring timing
- Revenue per senior headcount — signals when the next hire becomes accretive
- Client revenue concentration, rolling 90 days — flags concentration creep before it becomes a problem
- Gross margin by engagement type — separates high-value work from margin-dilutive volume
- Cash cycle length — drives A/R follow-up and credit terms decisions
None of these are exotic metrics. All of them are in standard accounting software. The difference is that someone has assigned an owner, set a threshold, and written down what happens when the threshold is breached.
The bottom line
The goal isn't a better dashboard. The goal is a management team that responds faster to what the business is actually telling them.
If your current reporting package is something you review at the monthly all-hands and then put away until next month, it isn't working. The numbers should be driving decisions between meetings, not summarizing what happened at them.