Ethan Brooks leads Sales and Partnerships at PeakIntent, where he helps high-ticket service businesses, from personal injury and tax resolution firms to cosmetic surgery, dental, restoration, and roofing companies, buy exclusive leads that actually convert. He writes about lead economics, why cost per signed case beats cost per lead, and how to scale acquisition without wasting budget.
The dashboard most service operators actually look at every Monday morning is called their bank balance. That is not a dashboard; that is a lagging indicator with a four-week delay. This piece is the one-page dashboard that catches pipeline problems while they are still fixable, built around a single honest metric: cost per signed case.
Closes out the week's operator series on lead-generation ops. See also the first-five-minute rotation piece, the two-question intake filter, the four-bottleneck diagnostic, the quality-vs-volume margin math, and the 14-day leak plus two-touch cadence. This piece is the tool that catches all of those problems in weekly cadence.
Why Weekly Beats Daily
Daily metrics are noise. A slow Wednesday does not mean the pipeline is broken; it usually just means it was a slow Wednesday. But four slow weeks in a row is a signal, and the only way to see the signal is to review at weekly cadence with the same six metrics every time.
Monday morning is the correct cadence hour because the prior week is closed (all leads, closes, and spend are countable) and the next week's decisions (ad budget, staffing, follow-up prioritization) can be made from the data. Reviewing on Friday afternoon guarantees the decisions get pushed to Monday anyway.
The Six Metrics That Belong on the Page
- Leads received last week (count, by source)
- Signed jobs closed last week (count, by source of the originating lead)
- Cost per signed case (spend by source divided by signed jobs from that source)
- Median time from form submit to first human contact
- Close rate by response-time bucket (under 10 min, 10-60 min, 1-24 hours, over 24 hours)
- Estimates outstanding past day 10 without a response (the two-touch cadence backlog)
These six catch every one of the four bottlenecks in the diagnostic piece. Volume shows up in metric 1. Quality shows up in metric 3. Intake speed shows up in metrics 4 and 5. Case value shows up implicitly in metric 3 when compared to average ticket over time. The two-touch cadence backlog in metric 6 is the leak-detection layer.
Cost per Signed Case: The Only Honest Metric
Cost per lead is what the vendor sells. Cost per signed case is what the operator lives on. The difference is close rate, and close rate is not something the vendor controls.
The math is straightforward. For each lead source in a given week:
Cost per signed case = (spend on that source) / (signed jobs originated from that source)
A $30 shared marketplace lead source that closed 2 out of 40 leads last week produced a cost per signed case of ($30 × 40) / 2 = $600. A $175 PeakIntent exclusive lead source that closed 4 out of 20 produced a cost per signed case of ($175 × 20) / 4 = $875 at first glance, but if the intake team spent one third the time per exclusive lead (because vetted leads pre-fill the discovery), the real all-in per signed case usually inverts the ranking. For the full margin math see the quality-vs-volume piece.
The dashboard should show cost per signed case per source, updated weekly, with a rolling 90-day trend line. Any source that drifts up more than 20 percent for three consecutive weeks is a source that either needs a fix (tighter intake filter, better response speed) or needs to be cut.
Response-Time Bucket Breakdown
The response-time close-rate table is the single most valuable diagnostic on the page. It looks like this:
| Response time bucket | Leads worked | Signed jobs | Close rate |
|---|---|---|---|
| Under 10 minutes | 18 | 7 | 39% |
| 10 to 60 minutes | 22 | 5 | 23% |
| 1 to 24 hours | 34 | 4 | 12% |
| Over 24 hours | 28 | 1 | 4% |
Every operator sees roughly this shape once they measure it. The bar chart alone builds the case for the rotation and SMS bridge from the first-five-minute piece. The dashboard makes the case visible weekly, which is what turns it into an operating decision instead of a nice-to-know statistic.
Source Attribution
Metric 3 (cost per signed case by source) only works if you know which source each closed job came from. Attribution is the boring plumbing that makes everything else on the dashboard useful. Three practical patterns:
- Call tracking per source. Unique phone numbers per lead source, routed to the same intake destination. CallRail and similar tools charge $10 to $50 per month for the numbers.
- UTM tags on every landing page link. Every ad, email, LinkedIn post, and organic listing gets a utm_source, utm_medium, and utm_campaign so the form submit carries the attribution automatically. See the PeakIntent resources hub for the full UTM convention.
- CRM source field on every lead record. Populated automatically from UTM or call-tracking, filled in manually on the rare walk-in or referral. The source field is the join column that makes the whole dashboard queryable.
Without these three, cost per signed case per source is a spreadsheet you cannot fill in, and the dashboard collapses back into "how did we do this week overall," which is not actionable.
Building the Sheet
The dashboard is one page. Not one spreadsheet with fifteen tabs. Not a BI tool with drill-downs. One page with the six metrics, updated weekly, taking under thirty minutes to compile.
Rough layout:
- Top row: this-week versus last-week comparison for metrics 1, 2, 3 (three cells side by side)
- Middle row: the response-time close-rate table (metric 5) plus the median time chart (metric 4)
- Bottom row: the two-touch cadence backlog (metric 6) with a count of leads that need follow-up this week
Print it every Monday morning or paste it into the same document. Do not build a "real-time dashboard" that nobody reads because it updates too fast. Weekly is the cadence; discipline beats sophistication.
How to Read It in Ten Minutes
The Monday review has one job: identify which of the four bottlenecks (volume, quality, intake speed, case value) is the current one, and decide what to do about it this week. Ten minutes with the dashboard, using the diagnostic questions from the four-bottleneck piece:
- Did total lead volume drop more than 20 percent versus prior week? (Metric 1)
- Did close rate on any single source drop more than 5 points? (Metric 3, per source)
- Did median response time drift above 10 minutes? (Metric 4)
- Did any source's cost per signed case drift more than 20 percent up? (Metric 3, trend)
The first "yes" is what you fix this week. Everything else is optionality that follows. If all four are "no," look at the two-touch cadence backlog and work down whichever leads are past day 10 without a response.
Frequently Asked Questions
What if some sources have too few leads per week to be meaningful?
Use a rolling 30-day view for small sources. Weekly is the cadence for the whole dashboard, but the per-source cells can smooth over 30 days so a source with 3 leads per week is not judged on 1 or 2 close events.
Should this dashboard replace the CRM's built-in reports?
Complement, not replace. The CRM report tells you what happened; this dashboard tells you what to do about it. Most CRM reports are structured for accounting, not weekly operational decisions.
What if we sell services with different ticket sizes and margins?
Add a "revenue per source" column alongside cost per signed case. Two sources with identical cost per signed case can produce very different revenue if one drives $12,000 HVAC installs and the other drives $400 service calls.
How often should the dashboard structure itself change?
Rarely. If the six metrics change every quarter, nobody trusts the trend line. Set the structure at launch and only revisit annually or when a genuinely new bottleneck emerges (new market, new service line, new lead channel).
Does this work for firms buying only shared marketplace leads?
Yes, with one caveat: metric 5 (response-time close-rate) matters even more for shared marketplace leads because the whole model rewards fastest-to-contact. Any shared source with median response time above 5 minutes is burning most of what you paid for.
Ten Minutes That Runs the Business
The Monday dashboard is not sophisticated. It is disciplined. Six metrics, one page, thirty minutes to compile, ten minutes to read, one decision per week about which bottleneck to fix. Over a year, the compounding effect of catching problems while they are still fixable beats every other operational habit in a small service business.
Once the dashboard is running, the case for exclusive high-intent leads becomes empirical rather than argumentative: your own cost-per-signed-case numbers, per source, tell the story. To see PeakIntent exclusive-lead pricing for your service area, run the two-minute PeakIntent matching wizard. Full library of operator playbooks at the PeakIntent resources hub.