Speed to lead is the time a business takes to make its first touch on a new inbound lead. In the Sales Velocity Engine, the Inbound Response SLO requires every inbound lead touched within 10 minutes. The Follow-Up Cadence and SLO Activation playbook registers that standard as a KPI and routes breaches toward intervention.
What Speed to Lead Means for a Service Business
Speed to lead names a plain question that any owner or sales leader can ask about the sales desk. How long does a new inbound lead wait before someone on the team actually touches it? The Sales Velocity Engine answers that question with a written standard instead of a loose aspiration. That standard is the Inbound Response SLO, and it requires every inbound lead touched within 10 minutes.
The Sales Velocity Engine is a module of the VWCG OS, alongside modules such as the KPI Precision Grid and Core Execution. Inside that module, speed to lead belongs to a scored dimension called Follow-Up Speed and Cadence. The dimension sits beside Pipeline Hygiene Enforcement, Velocity Metric Integrity, Lead Scoring and AI Governance, and Downstream Routing Health. Each dimension carries an equal weight of 0.20 in the composite diagnostic score for the module.
Response time and follow-up cadence are related, yet they answer different questions for a service business owner. Response time asks how fast the first touch happens after a new inbound lead reaches the business. Cadence asks what the team does across the following touches when the first reply closes nothing. The focus here stays on response time, the 10-minute inbound SLO, and the routing of every breach.
Where Response Time Sits in the Diagnostic
The Sales Velocity Engine Diagnostic scores every dimension on a 0 to 5 scale against written anchors. Each anchor describes what a scorer should observe at a given level of the dimension. For Follow-Up Speed and Cadence, the dimension checks whether the cadence runs deployed and tracked per opportunity.
It checks whether the team measures the inbound SLO and reports it as a KPI in the KPI Precision Grid. The dimension also checks whether every sequence enforces the custom-line requirement that the cadence carries.
The written anchors make the difference between levels concrete for the person doing the scoring. At the low anchor, follow-up happens ad hoc, and inbound response takes hours or goes unmeasured entirely. The middle anchor describes a cadence that exists, uneven adherence, and an SLO that someone measures without routing breaches. At the top anchor, every inbound lead receives a touch inside 10 minutes, and breaches route through variance alerts to intervention.
Scorers read those anchors first, and then the composite bands decide what happens next for each dimension. A red reading on Follow-Up Speed and Cadence proposes the Follow-Up Cadence and SLO Activation playbook as the remedy. An amber reading sends the dimension to the Pipeline Monitoring and Amber Path playbook, which runs 30-day pulse checks. A green reading holds, and Core Execution continues to monitor the dimension from that point forward.
What Opens the Follow-Up Cadence and SLO Activation Playbook
The playbook carries a precise set of triggers, and any trigger on that list can start the path toward a run. A red reading on Follow-Up Speed and Cadence routes to this playbook as its owning remediation. A red reading on Lead Scoring and AI Governance routes to the same playbook through a separate line in the routing table. The trigger list adds an inbound SLO breached as the norm, and lead routing that still runs unscored.
Routes that fire from a scored dimension remain proposals until leadership confirms them in a formal review. Confirmation happens at the next monthly governance review or the Core Execution phase review, whichever comes first. The stated duration of the playbook starts at confirmation, not at the moment the red reading first appears.
A red Follow-Up Speed and Cadence reading also reaches the Change Enablement Sprint module through its own route. That module opens an inbound-response adoption sprint, subject to the materiality threshold it applies to change work. Its threshold reads more than 10 people, or any customer-facing process, before the sprint goes ahead.
The 10-Minute Inbound SLO as a Registered KPI
Speed to lead in this method rests on a written standard and a deliberate act of registration. Under the Inbound Response SLO, every inbound lead needs a touch within 10 minutes, and the word every carries real weight. The playbook registers the 10-minute inbound SLO as a KPI inside the KPI Precision Grid for ongoing tracking. The Downstream Routing Health dimension separately checks that the SLO appears among the registered KPIs of that module.
Registration gives the standard a home inside the KPI Precision Grid, where its variance alerts can carry breaches toward intervention. Consider an owner whose inbound leads currently land in a shared inbox that no named person watches closely. Under this method, that owner would register the 10-minute response window as a KPI and route its breaches toward intervention.
Routing Breaches Instead of Reporting Them
Measuring the SLO without routing breaches matches the middle anchor of the Follow-Up Speed and Cadence dimension. The top anchor requires breaches to route through KPI Precision Grid variance alerts to intervention. The playbook outcome sets its own expectation, namely every inbound lead inside the 10-minute SLO with breaches routed.
After the activation run finishes its work, the standing amber playbook keeps that discipline in view. Its stated outcome includes no unrouted breach older than two weeks across the whole sales operation. That playbook also checks SLO adherence and cadence adherence every week as part of its standing routine.
Not sure where the gap in your customer or sales process sits? See how an operations review works →
The Five-Touch Cadence in Summary
The playbook deploys the five-touch cadence as sequences inside the CRM, with each touch set to a scheduled day. Day 0 carries a recap, and Day 2 carries a resource tied to the pain point of the buyer. A voicemail plus email follows on Day 5, Day 8 brings social proof, and Day 14 delivers the break-up. The custom-line requirement applies to every sequence, and the diagnostic checks that each sequence enforces it.
The lead follow-up system guide covers that cadence in depth for readers who want the full treatment. Here, the cadence matters mainly as the work that follows the first touch inside the 10-minute window. The diagnostic reads cadence adherence per opportunity within the Follow-Up Speed and Cadence dimension, next to the SLO itself.
Scoring Tiers and the Override Cap
The same playbook activates lead scoring tiers, which decide where each inbound lead goes after it arrives. Scores of 80+ route straight to an account executive on the sales team. Leads scored 60 to 79 move to nurture, and leads scored below 60 move to marketing.
Account executives may override a score, but the cap limits each change to plus or minus 10 points. Each override requires a documented reason, and the override log enforces the cap across the whole team. The diagnostic tracks override reasons and override frequency within the Lead Scoring and AI Governance dimension. At its top anchor, that dimension describes an override log that drives retraining and bias audits that run quarterly.
A red Lead Scoring and AI Governance reading also routes to the AI Deployment Canvas module for registration work. That module registers the lead scoring model and the proposal generator with dual ownership and quarterly bias audits. Owners who think in unit economics may find the tiers useful for that outside analysis, though the lens sits outside the method.
Signals From Other Modules That Change Lead Priority
Several inbound routes from other modules land in the Follow-Up Cadence and SLO Activation playbook as well. When Client Success Loop expansion routing turns red, the Sales Velocity Engine stops taking expansion leads from that module. That pause holds until the expansion routing returns to amber, at which point the leads flow again.
A client expansion signal from the Client Success Loop normally makes that client a priority lead for the sales team. The exception applies when Client Success Loop routing is red or the client revenue share reaches the concentration threshold. When the Exit and Acquisition Layer raises a concentration flag, new-logo leads rank a tier higher in the queue. The concentrated client is excluded from expansion priority while that concentration flag stands in the record.
The AERI score from Intelligent Foundations can also change how the scoring tiers behave inside the sales operation. Below its threshold, lead scoring runs advisory only with human approval, and the proposal generator runs template-only. Routes that set AI mode count as safety routes, so they tighten on the first reading. They loosen only after an independent re-score clears the band edge for the relevant dimension.
Ownership, Duration, and How a Run Closes
The VP of Sales owns the playbook together with the Sales Ops Data Steward, and the stated duration is 4 weeks. Its outcome lists cadence adherence tracked, every inbound lead inside the 10-minute SLO with breaches routed, tiers enforced, and an override log running. Every playbook in the module follows a shared lifecycle, moving through open, running, met or missed, escalated, and closed.
Someone other than the owner re-scores the dimension, and that independent re-score decides whether the run closes. An outcome met, with an independent re-score at amber or better, closes the run for that dimension. A missed outcome at the end of the stated duration escalates to the manager of the owner and the next Core Execution quarter planning agenda. A trigger that arrives while the run remains open gets logged against that open run.
After the Run: Standing Checks on the Amber Path
When the outcome is met, any standing duty the run set up continues under the Pipeline Monitoring and Amber Path playbook. The Sales Ops Data Steward owns that standing playbook and runs a 30-day pulse check for each amber dimension. The routine checks SLO and cadence adherence weekly, reviews the override log monthly, and files quarterly bias audit results. Green maintenance then follows at the next Core Execution cycle, and module instruments return for scoring quarterly.
Leaders who already keep a balanced scorecard may place the SLO beside their financial measures for visibility. That framing stays an outside lens as well, while the method itself relies on the registered KPI and routed breaches.
Build the process your team should actually be measured against. Book a 30-minute operations review →
Frequently Asked Questions
What is speed to lead in the Sales Velocity Engine?
Speed to lead is the time a business takes to make its first touch on a new inbound lead. In the Sales Velocity Engine, that standard comes from the Inbound Response SLO, which requires every inbound lead touched within 10 minutes. The Follow-Up Speed and Cadence dimension reads how well the business meets that standard.
How does the 10-minute inbound SLO become a tracked KPI?
Under the Follow-Up Cadence and SLO Activation playbook, the 10-minute inbound SLO becomes a registered KPI inside the KPI Precision Grid. The Downstream Routing Health dimension also checks that the SLO appears among the registered KPIs. At the top anchor, breaches route through KPI Precision Grid variance alerts to intervention rather than sitting unrouted.
What triggers the Follow-Up Cadence and SLO Activation playbook?
A red reading on Follow-Up Speed and Cadence or on Lead Scoring and AI Governance routes to the playbook. The trigger list also covers an inbound SLO breached as the norm and lead routing that runs unscored. Leadership confirms a scored route at the next monthly governance review or the Core Execution phase review, whichever comes first.
How do the scoring tiers and the override cap work?
Scores of 80+ route to an account executive, leads scored 60 to 79 move to nurture, and leads scored below 60 move to marketing. Account executives may override a score by plus or minus 10 points at most. Each override needs a documented reason, and the override log enforces the cap across the team.
Who owns the playbook and how does a run close?
The VP of Sales owns the playbook with the Sales Ops Data Steward, and the stated duration is 4 weeks. Someone other than the owner re-scores the dimension. A met outcome with an independent re-score at amber or better closes the run. A missed outcome escalates to the manager of the owner.
How does a service business owner begin speed-to-lead and SLO work?
Service business owners can begin with a review of how the sales desk handles inbound leads. Sales Roadmaps helps owners implement the method through the VWCG OS service, starting with an engagement scoped around the Sales Velocity Engine. The engagement scores the Follow-Up Speed and Cadence dimension and plans the playbook from that reading.
