The weekly numbers that matter for Service Autopilot owners

Six numbers, every Monday, twenty minutes: completion rate, revenue per crew-hour, cancel requests, cost per lead, lead-to-sold rate, and speed to lead. Three come from Service Autopilot, three from your marketing stack, and together they answer the only two weekly questions that matter: are we delivering what we sold, and is the pipeline paying for itself?

Why these six and not the forty in your reports menu?

Because weekly numbers exist to trigger action, and most metrics can't. Impressions, sessions, and follower counts move without meaning anything you'd act on by Thursday. The six below share two properties: each one degrades before the P&L shows the damage, and each one points at a specific fix. Everything else (CLV, churn rate, margin by service line) is real but monthly. (We covered the monthly money math in calculating CLV from your SA data and the marketing budget guide.)

What are the three ops numbers, and where do they live in SA?

Completion rate: visits completed ÷ visits scheduled, straight from SA's dispatch data. Healthy operations commonly run 95%+ outside weather weeks. A slipping completion rate is tomorrow's cancel and next month's bad review, visible today.

Revenue per crew-hour: invoiced revenue ÷ total crew hours including drive time. This is the number your route map controls (the density math is in the route density article). Ranges vary hugely by service mix (many residential operations land somewhere in $60–$120), so treat your own four-week baseline as the benchmark and manage the trend.

Cancel requests: the raw count, this week vs. your trailing average. Not churn rate (that's monthly); the weekly signal is the spike. Three extra cancels in a week is a crew problem, a billing surprise, or a competitor's postcard, all findable while the trail is warm, especially if each cancel gets a logged reason and a save sequence.

What are the three marketing numbers, and where do they live?

Cost per lead, by channel. Google Ads leads in residential services commonly run $25–$80 as of 2026, LSA often less; but the per-channel comparison on your own dashboard is the actionable part. One channel drifting 40% above its baseline is a Monday conversation with whoever runs it. (On our reporting dashboard this sits next to budget pacing and gets an AI anomaly flag before you'd spot it yourself.)

Lead-to-sold rate. Leads are vanity until they're sold work in SA. If sixty leads became nine customers, your marketing is fine and your follow-up is broken, a distinction cost-per-lead alone will never show you. This is also where call tracking earns its keep: recorded calls tell you why quoted jobs didn't close.

Speed to lead. Median minutes from inquiry to first response. Conversion commonly collapses after the first half hour, and this is the one number on the dashboard you can fix in a single week with an automated text-back. If you measure nothing else from this article, measure this once: the number is usually embarrassing and always profitable to fix.

What counts as "good"? (Hedged, because your market isn't ours)

Number	Where it lives	Commonly healthy	Act when…
Completion rate	Service Autopilot	95%+ (non-weather weeks)	Two weeks below baseline
Revenue per crew-hour	SA + timesheets	Your baseline, trending flat/up	Down 10%+ vs. trailing month
Cancel requests	SA status changes	Flat vs. trailing average	Any spike: investigate same week
Cost per lead	Ads/LSA reporting	~$25–$80 (Google Ads, resi, as of 2026)	Channel drifts 30–40% over baseline
Lead-to-sold	Pipeline + SA sold work	Many see 20–40% resi	Leads up but sold flat
Speed to lead	Call/form tracking	Under 5 minutes	Over 30 minutes: fix this first

Every range above is a planning range, not a promise: service mix, market, and season all move them. The discipline that actually pays is consistency: same definitions, same day, every week, so a drift of ten points means something.

What does the Monday ritual look like?

Twenty minutes, same agenda, no slides:

• Minutes 1–5: the six numbers vs. their four-week baselines. Green or red, no stories yet.
• Minutes 5–15: every red gets one owner and one action with a date. "Cancels spiked → office pulls the reasons by Wednesday." One action per red, not a task list.
• Minutes 15–20: last week's actions. Did they move the number? This step is the whole ritual; without it you're just reading numbers aloud.

The prerequisite is that the numbers assemble themselves. If Monday starts with 40 minutes of export-and-paste from SA, ad platforms, and a call log, the ritual dies by March. A synced dashboard (SA data via the Service Autopilot integration, ad and call data beside it) is what makes the habit survivable.

What should you stop tracking weekly?

Impressions, clicks without lead context, social followers, keyword rankings (monthly is plenty), and website sessions. None are worthless; all are noise at weekly resolution. The test for any metric that wants on the dashboard: what would we do differently on Thursday if this number were bad? No answer, no seat.

The takeaway: three ops numbers say whether you're keeping the promise, three marketing numbers say whether the pipeline earns its cost, and a 20-minute Monday with owners-and-actions turns them into a management system. Baselines over benchmarks, trends over snapshots.

Your dashboard setup checklist

1. Define the six numbers in writing, especially what counts as a "lead" and which hours go in crew-hours.
2. Automate the assembly: SA sync + ad accounts + call tracking into one view.
3. Run four weeks silently to build baselines before judging anything.
4. Book the recurring 20-minute Monday. Reds get one owner, one action, one date.
5. Review the review monthly: did fixed actions move numbers? Prune anything nobody acted on in a quarter.