The five dashboards every operator should have

Most owner-operators are not short of reports. The phone system produces one, the CRM produces another, the field service software produces a third, and the marketing agency sends a fourth every month. What is missing is a single place where those numbers agree with each other and point at a decision.

That is the difference between reporting and business intelligence. Reporting tells you what happened in one system. Intelligence tells you what to do next across the whole operation. In practice, the second requires far fewer screens than most people expect — five dashboards cover nearly every recurring question a growing home services business has.

One: the demand dashboard

The first question every morning is the same: how much work is coming in, and from where?

What belongs on it:

• Inbound volume by channel — calls, web forms, chat, referrals — for the current period against the prior one.
• Answer rate and missed calls, broken out by hour of day and day of week.
• New leads created, with the source attached to each.
• Booked appointments against capacity for the coming two weeks.

The purpose of this dashboard is early warning. Demand problems show up here days before they show up in revenue, and hourly detail is what makes it actionable — a healthy weekly total can easily conceal a Saturday morning where nobody answers the phone.

Two: the speed-to-lead dashboard

The second dashboard measures how fast the business responds to the demand the first one counts.

• Median time from lead creation to first contact, split by source.
• The same measure split by hour and day, so evenings and weekends are visible on their own.
• The share of leads contacted inside your target window.
• Leads with no contact attempt at all, listed individually rather than summarized.

That last item is the one that changes behavior. An average is a discussion; a list of specific requests nobody followed up is a task queue. Keep the definition honest — the clock starts when the customer acts, not when someone in the office notices.

Three: the sales conversion dashboard

Once leads are being answered, the question becomes how many turn into work and where the drop-off happens.

• Conversion from lead to appointment, appointment to quote, and quote to sold job.
• Average job value, tracked as a trend rather than a single figure.
• Aging of open quotes, so follow-up happens before the customer decides elsewhere.
• Conversion by source, which frequently reorders how you think about your marketing.

Stage-by-stage conversion is what makes this useful. A single overall close rate tells you the outcome; the stage view tells you which conversation to fix. A business losing deals at the quote stage has a pricing or follow-up problem. One losing them before the appointment has a scheduling or trust problem. Those are different projects.

Four: the operations dashboard

This is the dashboard that protects margin after the sale is made.

• Jobs scheduled, completed, rescheduled and canceled.
• No-show rate for both customers and crews.
• First-visit completion — how often the work finishes without a return trip.
• Technician or crew utilization, and the gap between scheduled and actual duration.

Rescheduling and return visits are where profit quietly disappears in field operations. Both are measurable, both respond to better confirmation and dispatch design, and neither shows up anywhere in a revenue report.

Five: the marketing return dashboard

The last dashboard connects spend to booked work rather than to activity.

• Spend by channel and campaign for the period.
• Leads, booked jobs and revenue attributed to each, using consistent rules.
• Cost per lead and cost per booked job, side by side — they often disagree.
• The share of leads that could not be attributed at all, shown honestly.

That final line matters more than it looks. Every attribution model has gaps, and a dashboard that hides them invites decisions based on false precision. Showing the unattributed share keeps the conversation credible.

Agree on definitions before you build anything

Nearly every argument about a dashboard is actually an argument about a definition. Is a lead created when the form is submitted or when it is qualified? Is a job counted when it is scheduled, completed or invoiced? Does a rescheduled appointment count as a no-show?

Write the definitions down before building. Store them where the dashboard lives. Change them deliberately and note when they changed, because a metric that silently redefines itself destroys trust in every other number on the screen.

This is also why the reporting layer should sit on top of a data platform rather than inside any single application. When the phone system, the CRM and the field service software each report their own version of the truth, the discussion becomes about whose number is right instead of what to do.

Give every dashboard an owner and a decision

A dashboard with no owner becomes wallpaper within a month. Each of the five should have one person accountable, one review cadence and one defined action when the number moves the wrong way.

• Demand: reviewed daily by whoever manages the front office.
• Speed-to-lead: reviewed weekly, with the no-contact list worked immediately.
• Sales conversion: reviewed weekly with the sales or estimating team.
• Operations: reviewed daily by dispatch, weekly by the owner.
• Marketing return: reviewed monthly, before any spend decision.

Push the decision back into the operation

The final step is the one most reporting projects skip. A dashboard that identifies a problem and requires a human to remember to act on it will only work while someone is paying attention.

The stronger pattern is to route the insight back into the systems that run the business: an alert when response time crosses a threshold, a routing change when a queue backs up, an automatic follow-up when a quote ages past a week. That is where reporting stops being a rear-view mirror and becomes part of the operation.

Five dashboards, clear definitions, named owners and a path from the number back into the workflow. That is a reporting layer an operator can actually run a business on.