Mike: Your CRM has forty reports. Maybe fifty. Dashboards, scorecards, performance summaries — you could spend all day in there.
Chris: You could.
Mike: And your shop is still leaking money in the same three places it was leaking last month.
Chris: Because you're not looking at the right seven numbers. You're looking at all of them.
Mike: All of them. Or none of them. Those are the two modes I see. Either the owner's drowning in data and can't find the signal, or they stopped opening the reports tab in February and they're flying blind into summer.
Chris: And here's the contradiction — the shops with the best numbers? They're not the ones with the fanciest dashboards. They're the ones reading seven lines on a single page every Tuesday morning.
Mike: Seven lines.
Chris: Seven lines. One page. Fifteen minutes a week with your dispatcher and your lead tech. That's the whole read.
Mike: And you think that's enough to run a shop.
Chris: I think it's more than enough. I think it's better than what ninety percent of owners are doing right now — which is either everything or nothing.
Chris: Summer's about to hit. Demand spikes, the board fills up, and the margin you should be banking disappears into problems you can't see because you're not measuring the right things weekly. Not monthly. Not quarterly. Weekly.
Mike: Today we're building the seven-line scorecard — CSR booking rate, speed-to-lead, schedule utilization, first-time fix rate, estimate close rate, average ticket, revenue per crew day. Seven numbers you pull every Friday in ten minutes, review every Tuesday in fifteen. I'm Mike.
Chris: I'm Chris. And by the end of this one, you'll know exactly which report to export from ServiceTitan, Jobber, or Housecall Pro for each line — and what to do when a number turns red.
Mike: So here's what I want to start with. I talked to a guy last month — runs a seven-tech plumbing shop outside of Indianapolis. He's on ServiceTitan. Paying for it. Has been for two years. And when I asked him what his CSR booking rate was last week, he said — and I'm quoting — "I think it's pretty good."
Chris: Pretty good.
Mike: Pretty good. No number. No trend. Just a feeling.
Chris: And that's the gap. He's got the data. It's sitting right there in his system. But he's not pulling it into anything he actually reads every week. So he's making decisions based on gut.
Mike: Which works until it doesn't.
Chris: Which works until June, when the phone's ringing forty times a day and your CSRs are booking — what? ServiceTitan pulled data from over three thousand shops and found the average booking rate across all calls was forty-two percent.
Mike: Forty-two percent. So more than half the calls don't turn into jobs.
Chris: Now, that's all calls — including spam, vendors, wrong numbers. When you filter to just legitimate lead calls, ServiceTitan's KPI guide puts the average at seventy percent. But shops like Black Diamond Plumbing up in Chicago were hitting seventy-seven percent with weekly CSR coaching. And ServiceTitan's own advisors say ninety percent is attainable with discipline.
Mike: Ninety.
Chris: Ninety. So the difference between a shop that books at forty-two percent of all calls and one that books at seventy-seven percent of lead calls — that's not a small gap. On a seven-tech shop running forty calls a day, that's potentially ten to fifteen more booked jobs a week. At three hundred, four hundred dollars a ticket? You're talking four to six thousand dollars a week sitting on the table.
Mike: And nobody's looking at it.
Chris: Nobody's looking at it weekly. That's the problem. They check it once a quarter, or when the accountant asks, or never.
Mike: Okay. So that's the front door — calls coming in. What about the other end? Speed-to-lead.
Chris: Same story, bigger stakes. The original research on this — Harvard Business Review covered it, MIT and InsideSales ran the study — found that if you respond to a new lead within five minutes versus thirty minutes, your odds of making contact go up roughly a hundred times.
Mike: A hundred times.
Chris: A hundred times more likely to reach them. And twenty-one times more likely to qualify the lead. Five minutes versus thirty. That's the difference between your CSR calling back during the commercial break and calling back after lunch.
Mike: After lunch, they've already called somebody else.
Chris: They've already booked somebody else. So those two lines alone — CSR booking rate and speed-to-lead — are the front door of your business. And most shops don't measure either one weekly.
Mike: Alright, so walk me through all seven. Because I know some guys are going to hear "seven KPIs" and think this is a corporate exercise.
Chris: It's not. Every line ties to either booking, schedule, or cash. That's it. If a number doesn't connect to one of those three, it doesn't belong on the page.
Mike: So what's the order?
Chris: First two we just covered. CSR booking rate — booked jobs divided by eligible lead calls. Not total calls. You strip out the spam, the vendor calls, the wrong numbers. Just the real leads. What percentage turned into a job on the board?
Mike: And the target?
Chris: Good is seventy percent. Better is eighty. Best is eighty-eight or above. If you're below seventy on lead calls, you've got a coaching problem at the front desk.
Mike: We had a stretch where our booking rate dropped to about sixty and I couldn't figure out why. Turned out one of our CSRs was quoting prices on the phone instead of booking the call. Just giving away the number and letting people shop.
Chris: And you wouldn't have caught that without tracking the line weekly.
Mike: Took us three weeks to notice. Three weeks of leaked calls.
Chris: Right. Second line — speed-to-lead. Median minutes from new lead to first human response. Call or text. Good is under fifteen minutes. Better is under five. Best is under two.
Mike: Under two minutes. That's fast.
Chris: That's fast. But if you've got a CSR on the phones during business hours and your web leads are pinging their screen, two minutes is doable. The shops that struggle here are the ones where web leads sit in an inbox until someone remembers to check.
Mike: Okay. Third line.
Chris: Schedule utilization. Billable hours divided by total paid hours for your field staff. This is the board number. How much of your techs' paid time is actually on a job?
Mike: And you don't want a hundred percent.
Chris: You do not want a hundred percent. Seventy is good. Eighty is better. Eighty-five is the ceiling. Above that, you're squeezing out travel time, lunch, quality — and your callbacks start climbing. Skedulo's field service research is clear on this. You plan for seventy to eighty-five, not a hundred.
Mike: I've seen owners push for ninety-five and then wonder why their guys are burning out by July.
Chris: And why their callback rate doubles. Which brings us to line four — first-time fix rate. Jobs resolved on the first visit divided by total jobs. Aquant's twenty twenty-six benchmark puts the industry median at seventy-seven percent. Top performers hit eighty-eight.
Mike: So if you're below seventy-five, what's usually going wrong?
Chris: Two things. Truck stock and diagnosis. Either the tech doesn't have the part, or the tech didn't diagnose it right the first time. Both are coachable. Both show up in this number before they show up in your callback complaints.
Mike: Good is seventy-five. Better is eighty-two. Best is eighty-eight.
Chris: Right. Line five — estimate close rate. Accepted estimates divided by sent estimates. This one's directional — the vendor data says forty to sixty percent is healthy for residential trades, but that range comes mostly from case studies, not large-scale neutral research. So use your own baseline. If you're at thirty-five percent and you move to forty-five, that's real money.
Mike: Service Labs Group ran a recovery program on unsold estimates for an HVAC and plumbing portfolio and pulled in eight hundred and fifty thousand dollars. Just from following up on estimates that were already out there.
Chris: From estimates already sent. Not new leads. Not new marketing spend. Just follow-up on work they'd already quoted.
Mike: That's the line that makes owners' eyes go wide.
Chris: Because it's the cheapest revenue you'll ever find. Line six — average ticket. Completed revenue on opportunity jobs divided by the count of those jobs. ServiceTitan defines this as the Opportunity Job Average. For HVAC service, their benchmark starts at three-fifty. Plumbing, four-fifty. But your number depends on your market, your mix, and your pricing.
Mike: So don't compare yourself to a shop in Phoenix if you're running calls in Ohio.
Chris: Compare yourself to yourself four weeks ago. That's what the trend line is for. And line seven — revenue per crew day. Total revenue divided by crew days. One tech working a full day equals one crew day. A two-tech crew for a full day equals two crew days.
Mike: So it's basically — how much did each tech-day produce?
Chris: That's it. And it rolls up everything above it. If your booking rate is high, your utilization is tight, your close rate is solid, and your average ticket is healthy — revenue per crew day reflects all of that. It's the summary line.
Mike: What's a good number?
Chris: Depends on trade and market. Twelve hundred is a reasonable floor for a lot of residential shops. Sixteen hundred is better. Two thousand is strong. But again — trend matters more than the absolute number. You want to see it climbing week over week, not bouncing around.
Mike: Okay. Seven lines. I get what they measure. Now — how do I actually get these numbers every week without it becoming a second job?
Chris: Friday. Ten minutes. You open your CRM, pull the exports, and drop seven numbers into a sheet. That's it.
Mike: Walk me through the pulls. Because this is where guys get stuck — they open the reports tab, see forty options, and close the laptop.
Chris: So the good news is all three major platforms — ServiceTitan, Jobber, Housecall Pro — have the data. The reports are just labeled differently. For booking rate and speed-to-lead, you need your call data. ServiceTitan has that in the Call Center summary. Jobber and Housecall Pro — if you're running CallRail, the call data syncs in. If not, you're pulling from your phone system or sampling twenty web leads and time-stamping the callbacks manually.
Mike: Not perfect, but better than guessing.
Chris: Way better than guessing. For utilization and first-time fix rate, you need tech hours and job completion data. ServiceTitan — Technician Performance report or Timesheets. Jobber — Time Sheets paired with job data. Housecall Pro — same idea, time tracking against your jobs list.
Mike: And estimate close rate?
Chris: Estimates by status. ServiceTitan — Business Unit Performance report, look for the Sold Rate column. Jobber — Insights, Reports, Quotes, export the CSV. Housecall Pro — Estimates list, Actions, Export. Approved divided by sent. Done.
Mike: So the data's there. In all three platforms. Just sitting in different drawers.
Chris: Different drawers, same kitchen. Average ticket and revenue per crew day come from the same revenue sources — pair them with your timesheets for crew days. And once you've done the pull twice, it takes ten minutes. Maybe less.
Mike: We actually built this sheet for you. It's on the Resources page — the Seven-Line Weekly Scorecard. Google Sheet you can copy. The KPI rows are set up, the target bands are in there with starter numbers you can adjust for your trade, and column F tells you exactly which report to open in ServiceTitan, Jobber, or Housecall Pro for each line. So you're not hunting through menus every week.
Chris: And the twelve-week trend tab feeds the sparklines automatically. Drop in your Friday numbers and you can see the shape of the last three months at a glance.
Mike: Alright. So Friday you pull the numbers. Then what?
Chris: Tuesday morning. Fifteen minutes. You, your dispatcher, and your lead tech — or techs, if you've got more than one crew lead. You pull up the sheet. Seven lines. Each line has a color — green, amber, red — based on the target bands you set.
Mike: And you don't try to fix everything at once.
Chris: No. You read each line. You note the trend — is it climbing, flat, or dropping over the last twelve weeks? And for each line, you agree on one behavior to coach that week. Not a project. Not a system overhaul. One behavior.
Mike: Give me an example.
Chris: Say your estimate close rate dropped from forty-eight to forty-one percent over three weeks. You don't redesign your estimate process. You say — this week, every estimate gets a same-day text, a next-day call, and a day-four options text. Three touches. And you assign that to whoever owns estimates. Next Tuesday, you check — did the touches happen? Did the number move?
Mike: One line, one behavior, one week.
Chris: That's the whole ritual. Chris Hunter — he's a former owner-operator, now a principal advisor at ServiceTitan — has been saying this for years. Track KPIs to coach behaviors, not to manage by statistics. The number tells you where to look. The behavior is what you actually change.
Mike: Okay, I want to push on something. Because I've seen this go wrong.
Chris: Go ahead.
Mike: You put a number in front of a tech — say, average ticket — and suddenly every call gets an upsell pitch whether it needs one or not. Customer came in for a forty-dollar capacitor and walks out with a quote for a full system replacement they didn't ask for. Your average ticket looks great. Your customer satisfaction tanks. Your Google reviews start mentioning "pushy."
Chris: Yeah. That's real. And it's the strongest argument against a scorecard like this.
Mike: It's not hypothetical. I've watched it happen.
Chris: I know. And the answer isn't to stop measuring average ticket. The answer is to pair it with a health check. When average ticket goes up, you watch callbacks and customer complaints in the same week. If ticket rises and callbacks stay flat and reviews stay clean — you're offering better options and customers are saying yes. If ticket rises and callbacks spike or you get a one-star review mentioning pressure — you've got a coaching problem, not a KPI win.
Mike: So every line gets a buddy metric.
Chris: Every line gets a sanity check. Utilization goes up? Watch overtime hours and callbacks. If utilization hits eighty-five and overtime doubles, you're over-booking the board. Estimate close rate jumps? Make sure it's not because your estimator is lowballing to close. The number alone doesn't tell you if you're winning. The number plus the health check does.
Mike: And that's what the Tuesday huddle is for.
Chris: That's exactly what it's for. You're not just reading seven numbers. You're reading seven numbers and asking — is this number moving for the right reason? Skedulo's field service team makes this point explicitly. Utilization has to be balanced with quality and technician well-being. You can't just chase the number.
Mike: Okay. So the scorecard isn't a leaderboard. It's a coaching tool.
Chris: It's a coaching tool. The moment it becomes a leaderboard — the moment you're posting it on the wall and ranking techs by average ticket — you've lost the plot. The Tuesday huddle is a conversation, not a performance review.
Mike: That distinction matters.
Chris: It's the whole thing.
Mike: One more piece. You mentioned a twelve-week trend. Why twelve?
Chris: Because one week is noise. Two weeks might be a coincidence. But if your first-time fix rate has been sliding for six straight weeks, that's a pattern. Twelve weeks gives you enough data to see the trend without drowning in history. And it fits on a sparkline — one little line chart next to each KPI that shows you the shape of the last three months.
Mike: So you're not reacting to one bad week.
Chris: You're coaching the trend. If utilization dipped this week because you had a tech out sick, that's not a problem. If it's been dipping for four weeks, something changed in how you're dispatching or how the board is getting filled.
Mike: And every Friday you add one row to the trend tab. Seven numbers, one row.
Chris: One row. Delete the oldest week if you want to keep it clean, or just let it scroll. The sparkline on the scorecard tab pulls from the last twelve entries automatically.
Mike: So — forty reports in your CRM. And the answer was seven lines.
Chris: Seven lines, one page, two rituals. Friday you pull the numbers. Tuesday you coach the behaviors. That's the whole system. You don't need a data team. You don't need a custom dashboard. You need a sheet, ten minutes on Friday, and fifteen minutes on Tuesday with the people who actually touch the work.
Mike: And the question for this week — the one I want you sitting with before your next Tuesday morning —
Chris: Yeah.
Mike: Which single line on that scorecard is the cheapest to move by Friday? Not the hardest. Not the most important. The cheapest. The one where one conversation, one small change in how your team handles the next call or the next estimate, actually shows up in the number this week.
Chris: And what exact behavior are you going to coach to move it? That's the question. Not "what number do I want to improve." What behavior am I going to change this week to make it move?
Mike: Pick the line. Name the behavior. Run the huddle. That's it.
Chris: That's it. I'm Chris.
Mike: I'm Mike. We'll see you next Tuesday.