A 45-person consulting firm I know built a beautiful Looker dashboard in 2023. Twelve tiles, color-coded, refreshed nightly from three spreadsheets someone stitched together every evening. Leadership loved it in the kickoff meeting. By month two, the ops manager was still updating it, but nobody else was looking. The dashboard wasn't wrong. It was just built for the person who made it, not for the three people in the room who needed to make a staffing call in the next ten minutes. That gap is the whole problem this post is about.
In this guide
Why most ops dashboards stop getting opened The five numbers worth putting in front of leadership Wiring it so nobody has to rebuild it every Monday Turning the dashboard into a habit, not a project Frequently asked questions
Why Most Ops Dashboards Stop Getting Opened
Three things kill a dashboard, and it's almost never the tool. First, too many numbers. A dashboard with 20 tiles asks the reader to do triage every single time, and most people would rather skip the whole thing than figure out which four of the 20 actually matter this week. Second, stale data. If utilization was last updated Thursday and it's now Tuesday, leadership stops trusting the number, and once trust goes, so does the habit of checking. Third, and this is the one people underestimate, a dashboard built by ops for ops doesn't answer the questions a CEO or a head of delivery is actually asking, which are usually blunt: are we going to hit margin this month, can we take on the next deal, and is any client about to walk.
The fix for all three is the same discipline: fewer numbers, live numbers, and numbers picked for the questions leadership actually asks out loud in a meeting, not the ones ops finds interesting to compute.
The Five Numbers Worth Putting in Front of Leadership
Pick five. Not eight, not twelve. If a sixth number feels essential, it probably belongs one click deeper on a drill-down screen, not on the summary view a VP glances at between meetings. Here's the set that covers delivery, money, and growth without overlap.
- Utilization rate, this week, not a trailing 90-day average. A trailing average hides the fact that three consultants sat idle since Monday.
- Project gross margin, by active project, ranked worst to best, so the two projects bleeding money surface first instead of getting buried under the ten that are fine.
- Pipeline coverage ratio, open pipeline value divided by the revenue target for the next quarter. Below roughly 3x and there's a real chance of a revenue gap nobody flagged in time.
- Days sales outstanding (DSO), because a firm can be fully booked and profitable on paper and still run out of cash if invoices sit unpaid for 60 days.
- Capacity headroom over the next four weeks, the one forward-looking number on the list, since it answers "can we say yes" before the sales call, not after.
Notice what's missing: no vanity metrics like total hours logged, no metric that only ops cares about, nothing that requires a footnote to explain. If a leadership team can't understand a tile in under five seconds, cut it.
Wiring It So Nobody Has to Rebuild It Every Monday
Here's the part most teams get wrong, and it's not a metrics problem, it's a plumbing problem. Utilization lives in the time-tracking tool. Margin lives in a spreadsheet someone builds from invoicing and payroll exports. Pipeline coverage lives in the CRM. DSO lives in accounting software. Capacity headroom lives in someone's head, or a scheduling spreadsheet that's two weeks out of date. Five numbers, four or five separate systems, and one person stitching them together by hand every week. That person eventually goes on vacation, or leaves, and the dashboard quietly dies.
The way around this is to stop treating the dashboard as a report and start treating it as a view into data that's already connected. If time entries, invoices, the pipeline, and project budgets already live in the same system, utilization and margin and pipeline coverage aren't calculations someone runs on Friday, they're just numbers that are already correct because the underlying activity updated them in real time. That's the actual argument for a platform built specifically for professional services rather than a general project tool bolted to a general CRM. If you want the fuller picture of what that category covers and why it's different from stitching tools together yourself, this guide to PSA software walks through it. Autovella's own features page shows how time, projects, invoicing, and the CRM share one dataset, which is the piece that makes a five-number dashboard actually stay current without a human in the loop.
Turning the Dashboard Into a Habit, Not a Project
A dashboard nobody schedules time to look at is just a webpage. Pick a fixed slot, the first ten minutes of Monday's leadership meeting works well, and make checking it the literal first agenda item, before status updates, before anyone starts talking about what they did last week. The order matters. Numbers first, narrative second, so the conversation is anchored to what's actually happening rather than to whoever speaks first.
The dashboard should change what happens in the meeting, not just get glanced at. If utilization is down 12 points and nobody reassigns anyone by the end of that Monday meeting, the dashboard isn't driving decisions, it's decoration. A useful test: after six weeks, can you point to one staffing call, one collections call, or one go/no-go deal decision that happened because of a number on that screen? If the answer is no, the numbers are wrong, or the meeting habit isn't real yet.
One more thing worth saying plainly: don't build this for 20 people. Build it for the three or four who actually make weekly calls on staffing, cash, and pipeline. Everyone else can get a monthly summary. A dashboard trying to serve the whole company ends up serving no one particularly well, and that's usually the moment it turns back into the twelve-tile Looker report nobody opens.
See utilization, margin, and pipeline on one live screen
Get a walkthrough of how Autovella keeps your operations dashboard current automatically, and check current plans and pricing while you're at it.
Frequently asked
Five is a good ceiling for the view leadership sees first. Utilization, project margin, pipeline coverage, DSO, and capacity headroom cover delivery, money, and growth without forcing anyone to scroll. Everything else belongs one click deeper, not on the summary screen.
A spreadsheet works for the first version while you're figuring out which numbers matter, but it breaks down once the data has to be pulled from time tracking, invoicing, and the CRM separately every week. At that point a connected system that already holds all three keeps the numbers current without anyone maintaining a pull-and-paste routine.
Weekly, at a fixed time, ideally the same 15 minutes at the start of a Monday leadership meeting. Monthly reviews are too slow to catch a utilization dip or a slipping project before it turns into a missed margin target, and daily checks usually just create noise without enough new data to act on.