The Contractor Financial Dashboard: 7 Numbers Owners Check Every Monday (How to Make It Stick)

Why Most Contractor Dashboards Fail

In contractor finance reviews, one pattern to look for is an owner who built a dashboard but abandoned it, or kept it nominally alive while ignoring it within the first few weeks. The useful test is whether each number has an owner, a reliable input and an action when it crosses a threshold.

Four failure conditions to check:

Too many metrics. The owner or their consultant built a 30-row spreadsheet covering every conceivable KPI. Nobody updates it consistently. Nobody knows what to do when a metric is off. It becomes a data collection exercise, not a decision-making tool.

Wrong cadence. The dashboard updates monthly, using data that's already 15-30 days stale by the time the month closes. By the time you see a problem, you've got 2 weeks of the next month behind you too.

No accountability structure. The dashboard is something the owner reviews privately. Nobody else is responsible for the numbers on it. So nothing changes when numbers are off.

Wrong data sources. The contractor has data in QuickBooks, a field service management platform, a payroll system, and maybe a CRM. Getting them to talk to each other can look like a BI implementation that nobody has time to build. $50K is an illustrative scale for that kind of project, not a quoted price.

Here's how to build one that doesn't fail.

Layer 1: The Weekly 7 (An Illustrative 20-30 Minute Update Budget)

Your dashboard has three layers. The first layer, the one that runs weekly with an illustrative 20-30 minute update budget, is the foundation.

The 7 numbers every $5M contractor should check weekly covers this in detail, but here they are in summary:

1. Cash position + collectible AR
2. Backlog, committed vs. pipeline
3. Revenue per truck this week vs. trailing 4-week average
4. Gross margin on completed jobs this week
5. Open quotes aging (flag anything over 7 days)
6. Technician utilization this week
7. Overhead spend rate vs. monthly budget

These 7 numbers should live at the top of your dashboard in a single table. Color-coded green/yellow/red. Updated every Monday morning. The entire team sees it.

This weekly layer can catch problems before the monthly close. By the time your month closes, you've seen four weekly views of each metric and had four chances to act on red flags.

Layer 2: The Monthly Deep-Dives (60-90 Minutes, Once a Month)

The second layer runs monthly, within 15 business days of month-end close. This is where you do the deeper analysis that can't be done weekly.

P&L by Service Line

Not just your blended P&L, broken down by business unit. The typical commercial contractor I've reviewed has 3-5 meaningful service lines: HVAC service/repair, HVAC maintenance, HVAC install/replacement, maybe electrical or plumbing as secondary trades.

Each service line needs its own gross margin review:

• Actual margin vs. target margin for the month
• Month-over-month trend (is margin expanding or compressing?)
• Volume trend (is revenue growing, flat, declining?)

If your HVAC service margin is compressing 2-3 points per month for 4 months in a row, that's a pricing or labor cost problem, and you want to know at month 4, not month 8. The how to read a contractor P&L post covers the service line breakdown setup.

Customer Profitability

Your top 10-15 customers should appear on your monthly dashboard with their revenue and estimated gross margin for the month. In our operating and diligence experience, this is an often overlooked analysis that can reveal costs hidden by a blended margin.

A simple test shows whether this applies to you. Rank your top 15 customers by gross margin, not by revenue, using the same cost allocation for each. If your largest customer sits near the bottom of that list, your other customers may be subsidizing it. Fictional example: a largest customer at $1.0M revenue and 14% gross margin produces $140K of gross profit, while a $400K mid-tier customer at 44% produces $176K. Owners often assume their biggest customers are their best ones; the ranking tests that assumption.

The customer profitability post covers the full analysis setup. For the monthly dashboard: you don't need exact margin, a relative ranking (which customers are profitable vs. which are pulling down your average) is enough to have the right conversations.

WIP Schedule (For Commercial Work)

If you're doing commercial projects with progress billing, your WIP schedule belongs in the monthly review. This is the formal schedule of:

• Estimated total contract value for each open job
• Costs incurred to date vs. estimated costs to complete
• Revenue recognized to date vs. billings to date
• Over/under-billing status, are you overbilled (you've billed more than you've earned) or underbilled (you've earned more than you've billed)?

Without a reconciled WIP schedule, you cannot explain earned revenue, estimated cost to complete and over/under billings on contracts recognized over time. Missing the schedule does not itself prove the GL is wrong. Underbillings can reflect a billing cutoff or a genuine missed invoice; overbillings are contract liabilities, not automatic losses. Confirm the financial-statement and WIP requirements in your actual surety and lending agreements, then tie the schedule to the GL and contract records.

For the dashboard: a simple WIP table showing total jobs, total contract value, percent complete, and aggregate over/under-billing status. Once job costing and cost-to-complete estimates are maintained, populating the summary can be quick. Time it on your first two closes. The job costing in QuickBooks post covers the setup. If your WIP problem sits between field software and the ERP, start with the integration data-layer map.

SA Renewal Rate and Pull-Through

Service agreement metrics deserve their own monthly slot:

• SAs up for renewal this month, how many renewed vs. didn't?
• Pull-through revenue as a percentage of total SA revenue
• SA book size (total active agreements) vs. prior month

SA renewal rate is one signal of customer retention. Pull-through reflects follow-on work from agreement customers, including relationship-driven projects, rather than isolating technician training. Both move slowly enough for a monthly review with annual comparison, you won't see week-to-week signal, but monthly trends are meaningful. For reference, the Level Index annual pull-through (additional repair, replacement and project revenue from agreement customers divided by annual agreement revenue) has a median of 8.7% across 386 eligible companies, with a wide spread (25th percentile 1.5%, 75th percentile 29.6%). Compare on an annual basis, since a single month is noisy. The overhead rate benchmarks and SA posts provide context for how these numbers compare to industry.

Layer 3: Quarterly Strategic Metrics (30 Minutes, Once a Quarter)

The third layer runs quarterly. This is the 30,000-foot view, trends and trajectories that don't show up in weekly or monthly snapshots.

Revenue Mix Trend

What percentage of your revenue came from service/maintenance vs. install/project this quarter, compared to the prior 4 quarters? Is the mix moving in the direction you want?

In our judgment, mix is one of the larger drivers of how buyers view a contractor, because recurring service revenue is often valued differently from project revenue. A business trending from 35% to 55% service revenue may be building enterprise value, and one trending the other way may see buyers apply a lower multiple. The effect depends on margins, agreement retention and the buyer's method. An SDE multiple, an EBITDA multiple and a cash-flow valuation are not interchangeable. The maintenance vs. install valuation post has the math on what a 10-point mix shift is worth.

Overhead Rate Trend

Your overhead as a percentage of revenue, trended across 8 quarters. Is it stable? Compressing (getting more efficient as you scale)? Expanding (a warning sign)?

Overhead rate compression is one of the clearest signals that a business is scaling efficiently. If your revenue grew 20% last year and overhead grew 8%, your overhead rate improved, and if gross margin held, that improvement flows to EBITDA. If revenue grew 20% and overhead grew 28%, you have a cost discipline problem.

Backlog Pipeline Health

Your rolling pipeline coverage, the ratio of your total quoted pipeline to your trailing 12-month revenue. As an illustrative starting point, not a measured benchmark, 1.5-2.0x unweighted pipeline means 1.5-2 years of trailing revenue only if every quoted dollar closes. Estimate expected dollars using your own value-weighted conversion by job type and the likely start dates. Fictional sensitivity: 2.0x pipeline at an assumed 38% dollar conversion yields 0.76x trailing revenue before timing. Level's 38.1% all-quote median is a count ratio, so it cannot supply this dollar-weighted probability. Above 3.0x is an editorial review trigger, not proof of poor qualification. Check quote ages, value mix and actual decisions before changing the sales process.

Also worth reviewing quarterly: your average quote to close cycle time, which determines how far ahead you need to be selling.

The Data Source Reality

Here's the problem every contractor faces: your data lives in 3-5 systems that don't talk to each other.

A full BI implementation that integrates all five usually isn't the first answer for a $5-15M contractor. The answer is simpler: a weekly Google Sheet that gets manually updated with the key numbers from each source.

This sounds low-tech. It is. That's why it works.

Here's the architecture that works in practice:

1. The source systems stay as-is. You're not replacing QuickBooks or ServiceTitan. You're pulling numbers from them.

2. A weekly update doc gets filled in every Monday morning. An illustrative 20-30 minute budget. The numbers come from 3 browser tabs, QuickBooks reports, your FSM dashboard, your bank.

3. One person owns each section. The owner owns cash and reviews overhead. The ops manager owns utilization, backlog, revenue per truck and completed-job gross margin. The office manager owns AR aging and overhead spend. Quote status belongs to the sales lead where one exists, otherwise to the office manager.

4. The dashboard is shared. Everyone who owns a section sees everyone else's section. That's the accountability mechanism.

The single biggest mistake contractors make with dashboards is treating it as a private tool for the owner. The dashboard's value is creating shared visibility and shared accountability. If the ops manager can see that utilization is 58% and knows the owner sees it too, behavior changes.

The Red/Yellow/Green Framework

Every metric on your dashboard should have predefined thresholds. Not just "is this good?" but a specific number that triggers each color.

Here's the framework for the 7 weekly metrics:

The thresholds in this table are starting points, calibrate them to your specific business. Two definition checks apply. First, the utilization green band matches Level's 65-80% working range, which divides billable hours by total paid hours, including drive, admin, training and idle time; the yellow and red bands are illustrative. Do not substitute billing capture (hours invoiced divided by hours logged on jobs, Level Index median 97.1%), which is a different ratio. Second, for cash plus collectible AR, divide by gross weekly operating outflow (payroll, materials, rent, debt service), not by a net burn figure that already subtracts expected collections. Dividing cash plus AR by net burn counts the same collections twice. Count only AR you expect to collect within the window. A seasonal contractor has different cash thresholds in June vs. January. The seasonal cash flow post has the seasonal adjustment framework.

The important thing is that the thresholds exist and are agreed upon before you start tracking. "Is this good?" is a judgment call. "This is red because it triggered the 20% threshold" is a fact.

Accountability Structure

The dashboard doesn't create accountability by existing. It creates accountability by being seen by the right people, in a shared format, on a consistent schedule.

The structure that works:

Owner: Reviews all 7 metrics every Monday. Asks one question per red metric: "What's the cause and what's the action?" Holds the team accountable for the answers, not the numbers.

Operations manager: Owns utilization, backlog, and revenue per truck. Responsible for explaining red numbers and presenting a fix. If two consecutive Mondays show red utilization, the ops manager comes to Monday's review with a scheduling change already in motion.

Office manager/admin: Owns AR aging and overhead spend. Responsible for the follow-up calls that move AR from yellow to green and for flagging overhead variances before the month is over.

Sales lead (if you have one): Owns open quote aging and pipeline coverage. Responsible for follow-up on every quote over 7 days. The quote conversion rate post has the full follow-up process.

This isn't a weekly meeting, it's a shared document. Each person updates their section, reads everyone else's, and acts on their red metrics. If you need a 60-minute meeting every week to go through the dashboard, the dashboard is too complex.

What to Build It In

For most $3-20M contractors: Google Sheets. Not Looker, not Tableau, not a custom BI tool. Google Sheets is accessible from any device, shareable with the team, easy to color-code with conditional formatting, and doesn't require IT support.

Build one tab per layer:

• Tab 1: Weekly 7 (current week + 12-week history for trends)
• Tab 2: Monthly deep-dives (P&L by service line, customer profitability, WIP)
• Tab 3: Quarterly strategic view (mix trend, overhead rate trend, backlog health)

As complexity grows across service lines and locations, a more sophisticated tool may justify itself. The $20M revenue point is an editorial heuristic, not a validated product threshold. Before that, check whether a BI tool solves a real reconciliation and decision problem or adds maintenance without a better decision. The contractors I've seen build elaborate BI dashboards before their financial processes were clean ended up with beautifully formatted wrong numbers.

Get the numbers right first. Then make them pretty.

The Minimum Viable Version

If you're reading this and you don't have any dashboard right now, here's the minimum viable version to start this week:

1. Open a Google Sheet.
2. Put the 7 metrics as rows, dates as columns.
3. Fill it in this Monday morning from QuickBooks, your FSM, and your bank.
4. Share it with your ops manager.
5. Do it again next Monday.

You don't need to build all three layers this week. You need to build the habit. As an illustrative planning range, Layers 2 and 3 can take one to three monthly closes to add, depending on cleaner source-system extraction and validated closes.

But the weekly 7 can start Monday. And starting Monday with an imperfect list of 7 numbers beats starting in six months with a perfect 30-metric dashboard.

---

The Bottom Line

The dashboard that gets used is the one with 7 weekly metrics, clear ownership, defined thresholds, and a Monday sharing ritual. The dashboard that dies is the one with 30 metrics, monthly updates, and no accountability structure.

If you've built dashboards before and watched them die, the failure wasn't the numbers, it was the structure around the numbers. Fix the structure, and the same metrics work.

Q: Can Level build and maintain a financial dashboard for my contracting business? A: Where the signed engagement includes reporting, Level can set up extraction for your system stack, define thresholds with you and integrate the dashboard with your monthly close. Ongoing maintenance and training follow the engagement tier and signed scope. Where training is in scope, we also work with your team on ownership of each section so the accountability structure holds after setup.

Q: How long does it take to build a working dashboard? A: As a planning example, the weekly 7 might be running in a week if the required QuickBooks and FSM inputs already exist. Time depends on access, edition, data quality and a reliable tie-out. The full three-layer version, including monthly P&L by service line, WIP schedule, and customer profitability, might take an illustrative one to three monthly closes, depending on cleaner source-system extraction and validated closes.

Q: What if my data is in different systems that don't connect? A: For a small, stable source set, a Google Sheet can be enough. Budget an illustrative 20-30 minutes for weekly pulls from three browser tabs, then measure your actual time and exception load. Manual and automated feeds fail in different ways. Manual entry fails through typos, stale tabs and skipped weeks. Automated feeds fail when a source system changes a field or a sync silently stops. Whichever you use, run a weekly tie-out: the sheet's cash equals the bank balance on the same date, and the sheet's AR equals the AR aging total in your accounting system. Automate a field once its definition is stable and you can detect a failed sync. Choose automation based on source volume, stable definitions, exception rates and the team's ability to maintain it, rather than a universal revenue cutoff.