Build a KPI dashboard by defining the decisions a service business needs to make, selecting a small set of measures, and reconciling the underlying data before choosing software. For a $5M business, connect cash, sales, delivery, margin, and quality with named owners and review actions. Revenue is context, not a formula for the number of metrics required.
Start with the decisions and the source records
A dashboard should help someone decide what to do. Write five questions first: Can we meet upcoming cash commitments? Is demand converting into deliverable work? Can capacity meet those commitments? Are completed jobs contributing as expected? Are service quality problems creating additional cost or customer risk? Change the questions to match your operating model.
Map each question to a source record and owner. Cash may come from reconciled banking and the forecast; work commitments from scheduling; job margin from accounting and job costing; quality from service records. If systems disagree, resolve the definition before creating a chart. A polished display built on inconsistent dates or statuses can make uncertainty harder to see.
Write a metric dictionary before automating
For each metric, document its purpose, formula, unit, reporting period, source, refresh time, exclusions, and responsible person. Define what counts as a completed job, a qualified opportunity, or an on-time commitment. State whether a financial measure includes overhead and how credits or adjustments are handled. Make the definition accessible to the people who use the report.
Distinguish snapshots from period measures. Open receivables at Friday's close is a snapshot; receipts during the week is a flow. Mixing them without explanation creates misleading comparisons. Show the latest refresh date and flag incomplete data. Keep a record of definition changes so a process improvement is not confused with a reporting change.
Connect each indicator to an action
Choose measures that expose a decision, such as the lowest projected cash balance, work overdue against an agreed commitment, completed-job contribution, and unresolved quality exceptions. A target must come from your business's needs and evidence. A red indicator should trigger an investigation or action, not automatic blame or a demand to change the number.
Illustrative example: a $5M service company displays 25 overdue jobs. Managers discover that 15 await customer approval and 10 lack an internal resource assignment. One total concealed two different actions. Adding a reason breakdown lets account owners address approvals while operations resolves staffing. The improvement comes from the decision and follow-through, not the visual alone.
Use a summary view for leadership and a drill-down for process owners. Limit access where customer, employee, or financial information requires it. Avoid publishing sensitive detail simply because the reporting tool can display it. NIST's Baldrige tools provide resources for organizational self-assessment; they do not prescribe a universal dashboard or KPI target.
Sources: NIST Baldrige improvement tools.
Pilot the review before buying more software
Run the dashboard manually for several review cycles if that is the fastest way to test definitions. At each meeting, record the decision, owner, due date, and expected evidence. Remove measures nobody uses and investigate unexpected changes. Compare key totals with source systems before relying on automated refreshes for important commitments.
Once the review works, automate stable data transfers and define who maintains them. Document refresh failures, access permissions, and backup ownership. A spreadsheet can be sufficient for an early version; a reporting platform may be justified when integration or access needs grow. This guide covers building the dashboard system. HPG's existing weekly scorecard guide addresses what leadership should review, so the two resources serve related but different decisions.
HPG describes its advisory work in operational performance, financial visibility, growth execution, and strategic advisory for founder led businesses. Discuss the specific scope and responsibilities before engaging support.
Sources: HPG advisory services.
Relevant HPG support
Common Questions
How many KPIs should a service business track?
Use the smallest set that supports the decisions your team must make. There is no universal number determined by revenue.
Do we need dashboard software first?
No. Test definitions, source reconciliation, and the management review before buying or expanding software.
Who should own the dashboard?
Assign both a reporting owner and a business owner for each measure. A technician maintaining the report cannot own every operating decision.
Related reading
Learn about HPG advisory services or contact Horizon Path Group to discuss your business.
You may also find these useful: How to Measure AI ROI in a Small Service Business, How to Scale a Service Business From $3M to $10M Without Operational Chaos, and Sales Forecast Accuracy: Explain What Changed Before Resetting the Number.
This article provides general business information. Decisions depend on your circumstances and may require qualified professional advice.