← All posts
Business operationsReportingMay 11, 2026Clint Research Team

The Weekly Business Review for Home Service Owners: 6 Numbers in 15 Minutes

Most home service owners skip the weekly business review or spend 45 minutes pulling reports for it. Here is a lean 15-minute process built around 6 numbers you can pull in under 5 minutes from any major CRM.

10 min read

Key takeaways

  • Six numbers cover the health of revenue, pipeline, production, cash flow, and reputation. More than six and the review stops being a review and becomes a reporting exercise.
  • Open estimates older than 5 days with no follow-up are recoverable pipeline. Most businesses have 10–30% of their monthly revenue sitting in this category unanswered.
  • Cash in bank versus invoices over 30 days outstanding is the single most important number for a business under $5M. The P&L can look healthy while the bank account is draining.
  • Text Clint 'give me my 6 weekly business numbers' and all six return in a single response.
Contents
  1. 01Why 6 Numbers Is the Right Number
  2. 02The 6-Number Weekly Review
  3. 03How to Run a 15-Minute Team Check-In With These Numbers
  4. 04What to Do When a Number Is Off
  5. 05How Clint Runs the 6-Number Weekly Review
  6. 06Sources
  7. 07Frequently Asked Questions

Most home service owners do not have a weekly business review. The ones who do spend 45 minutes pulling exports before the meeting even starts. Both outcomes leave the owner flying on feel rather than data. The business is running, but the directional signals that should prompt action are invisible until a problem becomes obvious.

The fix is not a more elaborate reporting system. It is six specific numbers, run in 15 minutes, reviewed with enough context to act when one is off.

Why 6 Numbers Is the Right Number

Business reporting for a $1M to $5M home service company has one job: tell the owner what changed this week and whether any change requires action before next week. That requires breadth, not depth. Depth is what you add after a number signals a problem.

Six numbers cover five domains: revenue direction, pipeline health, production quality, recoverable pipeline, reputation, and cash position. Together they give a complete picture of the business state in a single sitting. For the broader framework on which metrics to track at all, see home service dashboard metrics and the complete KPI playbook.

Fewer than six and you miss a domain. Seven or more and the review becomes an analysis session rather than a check-in. The goal is to be in and out in 15 minutes with a clear sense of whether the business is on track and one or two specific actions to address what is not.

Each number below includes what to look for, what a good versus concerning result looks like, and the single action to take if it is off.

The 6-Number Weekly Review

Number 1: Revenue Booked This Week vs. Last Week vs. Same Week Last Year

Revenue booked is the total value of jobs confirmed this week, not invoiced. This is a leading indicator, not a trailing one. Invoiced revenue lags the actual pace of business by 1 to 3 weeks. Booked revenue tells you what is coming.

What to look for: compare this week's booked revenue to last week and to the same week last year. Three data points give context. A slow week against last week might be a scheduling anomaly. A slow week against the same week last year is a trend.

Good: within 10 to 15% of same-week prior year, up from last week. Concerning: more than 20% below same-week prior year for a second consecutive week.

Action if off: identify whether the gap is in new customer volume or repeat customer volume. New customer gap means marketing or visibility. Repeat customer gap means service quality or retention.

Text Clint: "what was my total revenue booked this week versus last week versus the same week last year?"

Number 2: New Estimates Sent vs. Accepted

New estimates sent this week tells you pipeline input. Estimates accepted tells you close rate and pipeline conversion. The ratio between them is close rate.

What to look for: the absolute volume of estimates sent should be consistent with your average weekly activity. If estimates sent drops, sales activity has dropped. If estimates sent is normal but acceptance rate drops, pricing, presentation, or follow-up has a problem.

Good: close rate above 60% on estimates sent this week, consistent with your trailing average. Concerning: close rate below 45% for two consecutive weeks, or estimates sent volume down more than 25% from prior week.

Action if off: if close rate is low, look at the estimates that did not convert. Were they price objections? No response? Pull the jobs by tech or estimator and see if the gap is concentrated on one person. If estimates sent is low, check whether the team is booking fewer diagnostic calls or follow-up visits.

Number 3: Jobs Completed On Time vs. Jobs That Ran Late

Production discipline (whether the schedule ran as planned) is a leading indicator of customer satisfaction. Completed on time means the job was closed within the scheduled window. Jobs that ran late required reschedule, overtime, or customer notification.

What to look for: late job rate above 15% signals a scheduling or capacity problem. A spike in one week may be weather or a single difficult job. Two consecutive weeks above 15% is a trend.

Good: 90% or more of jobs completed within scheduled window. Concerning: more than 15% of jobs late for two or more consecutive weeks.

Action if off: look at the specific jobs that ran late. Were they concentrated on one tech, one service type, or one part of the week? Late jobs in the morning cascade into late jobs in the afternoon. If the pattern is consistent Tuesday afternoons, the Tuesday schedule is too tight. If the pattern is concentrated on one tech, their job estimates are off.

Text Clint: "how many jobs were completed on time this week versus ran late, broken out by technician?"

Number 4: Open Estimates Older Than 5 Days With No Follow-Up

Open estimates that have not been followed up in 5 or more days are recoverable pipeline that is decaying. Most home service businesses have 10 to 30% of their estimated monthly revenue sitting in open estimates that have not been contacted. This number is the easiest win in the weekly review.

What to look for: any estimate that went out more than 5 days ago with no follow-up call or message. These are warm leads. The customer requested a quote. They have not said no. They have not been asked again.

Good: fewer than 5 open estimates older than 5 days with no follow-up activity. Concerning: more than 10 open estimates in this category, or any estimate over $2,000 older than 7 days with no follow-up.

Action if off: this is the one number with an immediate action every time it is off. Pull the list. Call or text each customer today. A simple follow-up message ("checking in on the estimate we sent, any questions?") converts at 20 to 35% in most service businesses. The revenue is there. It just needs to be asked for. For the full cadence, see how to follow up on estimates without being pushy.

Text Clint: "list all open estimates older than 5 days with no follow-up activity, sorted by value"

Number 5: Customer Reviews Received This Week

Reviews received is a proxy for customer satisfaction and a direct driver of inbound call volume. Most home service businesses receive 1 review for every 10 to 25 customers served, depending on how actively they request them. The absolute number matters less than the trend and the content.

What to look for: how many reviews came in this week, what the average rating was, and whether any specific theme appeared in negative reviews.

Good: at least 2 to 3 new reviews per week for a business doing 25 to 50 jobs per week, averaging 4.5 stars or above. Concerning: zero reviews two weeks in a row (the request process has broken down), or any 1-star or 2-star review that references the same issue two weeks running.

Action if off: if review volume is low, check whether the automated review request (sent after job completion via CRM) is firing correctly. If review requests are sending but response rate is low, the timing may be off. Most reviews are written within 2 hours of job close. If a negative review theme is repeating, it is an operational signal, not a reputation problem.

Number 6: Cash in Bank vs. Outstanding Invoices Over 30 Days

This is the cash flow check. Cash in bank at the start of the week versus the total value of invoices that are 30 or more days past due.

What to look for: the ratio of cash available to overdue receivables. If overdue receivables exceed cash on hand, the business is funding customer delays with owner capital.

Good: overdue receivables under 10% of trailing 30-day revenue, cash in bank covering at least 3 weeks of operating expenses. Concerning: overdue receivables above 20% of trailing 30-day revenue, or cash in bank below 2 weeks of expenses.

Action if off: pull the overdue invoice list sorted by age and value. Call the top 5 by value today. Send a written notice to anything over 60 days with a payment deadline. Consider a 2% early payment discount for anything over 45 days if cash position is tight. For chronic late payers, require payment on completion before the next service. See also how to collect invoices faster for the broader receivables process.

Text Clint: "what is the total value of invoices over 30 days outstanding, and how many customers account for more than half of that balance?"

How to Run a 15-Minute Team Check-In With These Numbers

The weekly review does not require a team meeting. It is a solo owner process that takes 10 to 15 minutes with the right data. If you do include an office manager or dispatcher, the structure is:

Minutes 1 to 5: pull the six numbers. If you are using Clint, this is one question and one response.

Minutes 5 to 10: review each number against the threshold. Mark any that are off.

Minutes 10 to 15: assign one action per off number. Write it down with a name and a deadline. This is the only output that matters from the review.

Do this the same day and time every week. Monday morning at 7:30 am works well because you are setting direction before the first calls of the week. Tuesday morning works if your Monday is field-heavy. The consistency matters more than the specific day. For the full list of weekly reports worth running, see what reports to run every Monday.

The review fails when it turns into a discussion about why a number is off rather than a decision about what to do. Context is useful for 60 seconds per number. After that, it is delay.

What to Do When a Number Is Off

Two rules for the action that follows a number being off:

The action should be completable within 48 hours. If it is not, it is a project, not a weekly action item. Break it into a first step that is completable within 48 hours and schedule the project separately.

One person owns it. Not "the team." Not "we should." One name, one action, one deadline. Numbers that are owned collectively are not owned at all.

The most common failure mode in the weekly review is identifying a problem and deferring action until the "right time." There is no right time that is not this week. If a number is off and no action is taken by the next review, the number will still be off. The business has had one more week of drift.

How Clint Runs the 6-Number Weekly Review

Text Clint "give me my 6 weekly business numbers" and all six return in a single response. Revenue booked this week versus last week versus same-week prior year. Estimates sent and close rate. Jobs completed on time. Open estimates older than 5 days. Reviews received. Cash and overdue invoices.

Clint pulls each number from your connected CRM and financial data and formats the response so the owner can review it without opening a dashboard or pulling an export. The entire check-in happens in the texting interface, typically in 3 to 5 minutes including the time to text the question.

For the follow-up actions that come out of the review, Clint can drill into any number on command. "Show me the open estimates older than 5 days" returns the list with customer name, estimate value, and days since sent. "Which tech had the most late jobs this week?" returns the count and the jobs. The six-number review is the weekly check-in. Clint is the first-level diagnostic when something needs to be understood in more detail.

Sources

Frequently Asked Questions

4 questions home service owners actually ask about this.

  • 01How often should I review these numbers beyond weekly?

    Revenue booked and schedule fill rate are worth a daily 60-second check during busy season. The other four are weekly. Checking cash position more than weekly is a sign of a cash flow problem that needs a solution, not more frequent monitoring.

  • 02What if my CRM does not track all six of these natively?

    Most major CRMs (Jobber, Housecall Pro, ServiceTitan) track revenue booked, estimates, jobs completed, and overdue invoices natively. Open estimates without follow-up and reviews received may require pulling from a second source or CRM reporting add-on. If any of the six numbers requires more than 5 minutes to pull, the review process breaks down. Fix the data access before committing to the cadence.

  • 03Should I share these numbers with my office staff?

    Revenue direction and cash position are typically owner-only. Jobs completed on time, open estimates, and reviews are worth sharing with the dispatcher and office manager who can act on them. The framing matters: share numbers with the people who can change them. Numbers shared without an action pathway create anxiety without improvement.

  • 04What is the right time of week for this review?

    Monday morning before 8 am is the most common choice for owner-operators. You are setting direction for the week before it starts. If you are field-heavy on Mondays, Tuesday morning works. The worst time is Friday afternoon, when most of the actionable items require reaching customers or staff who are not available until Monday anyway.

See Clint in action

Clint is the pre-built AI for home service shops. Connect your CRM, email, and phone system in minutes and the agents run on your real data.