KPIs and Scaling
The KPI system: from a revenue goal to Tuesday's dial count
Work backward from a revenue goal to deals, appointments, conversations and daily dials, and read answer rates to spot a spam flagged number early.
Prep for Week 4: AI, live Tuesday, October 27Coming soonThis lesson is not recorded yet. Ty films it next. It will appear here, with its video and the written walkthrough, the day it goes live.
What this lesson will cover
- Leading vs lagging indicators: dials, correct numbers, conversations, appointments predict revenue; revenue and closed deals only confirm what happened 90 days ago. The three that matter most: dials m
- A dial is not a full attempt: one dial = one number; a full attempt = every number on the record plus voicemail plus text; a record can hold 3-5 numbers, which is why 150 dials is achievable
- Reverse-engineer the revenue goal: revenue divided by average deal profit gives deals, then walk the conversion ladder backward: ~5:1 conversations to appointment, 1.5:1 appointments to offer, 4:1 off
- The correct-numbers-to-deals ratio: 100 correct numbers is roughly 1 deal over 12 months (conservative; July guidance 50-100, some cohorts 30-50); the August refinement sharpens it to 1 in 20 RPC insi
- Diagnostic bands: answer rate below 50% = skip-trace or spam problem; ~70% is where Ty runs; a number at ~30% is spam-flagged, kill and replace it. Live triage examples: 1 correct per 34 dials is "not
- The kpi-engine skill is the packaged version: reads the per-record activity log (the only date-accurate, caller-attributed source), fixes the new_lead counting bug, grades against the benchmark catalo
- Ladder: 5:1 convo:appt, 1.5:1 appt:offer, 4:1 offer:contract; 100 correct numbers ~ 1 deal/12mo
- Visibility alone lifts dial counts 15-20%
- The stacked funnel with the August numbers: 1,457-record list, 261 RPC, 13 correct-number sellers inside 6 months, contracts
- The supersession timeline: 32:1 (2025), 10-15:1 (July), 13.5 blended (August) on one axis
- "A dial is not an attempt": one record exploding into 5 numbers + VM + text
- The anomaly tripwire: a flat KPI line dipping through a threshold and triggering a Slack bolt
- Manual KPI sheets, the Tally Counter and hand-built dashboards are retired: Claude builds the workbook on demand and watches for anomalies; the KPI Masterclass and the old manual system are historical.
‹ SOP creation: film it once, hand it to your hires and your AIThe dashboard shift: tracking KPIs with Claude, live ›
We build this with you live in Week 4: AI, Tuesday, October 27, 1 to 4 PM ET. Add it to your calendar.
