The Sales Velocity Engine tracks sales velocity as PV2: pipeline value times win rate, divided by cycle length.
The Sales Velocity Engine Diagnostic scores five dimensions of pipeline health on a 0 to 5 scale.
Red scores propose playbooks that enforce hygiene, speed, and governance.
What the Lowest Anchors Describe
The written anchors for this diagnostic describe the pipeline in terms of data, speed, and routing. A Porter lens on rivalry and buyer power can explain demand pressure, but these anchors look inward.
The lowest hygiene anchor describes rules that are absent or advisory and deals without close dates or next steps. At that level, the anchor records a forecast inflated 20 to 40%. The lowest velocity anchor adds metrics computed from dirty data or not at all, and surprises at quarter end. The lowest scoring anchor describes no scoring or unmanaged gut-feel routing, with AI deployed without governance.
Follow-Up, Hygiene, and Downstream Anchors
At the lowest follow-up anchor, follow-up is ad hoc and inbound response is measured in hours or never. The middle follow-up anchor describes a cadence that exists, with uneven adherence and SLO breaches that go unrouted.
The middle hygiene anchor describes documented rules, partial validation, and a Hygiene Score that is computed but unowned. At the lowest downstream anchor, sales metrics stay in sales, and capital decisions get made without PV2. The middle downstream anchor describes some routes that run live but stay manual or lagging.
An owner should ask which plans, such as inventory commitments, lean on the same forecast. At the top downstream anchor, all four routes run live and automatically.
Diagnose Sales Velocity Before Treating the Pipeline
The diagnostic measures the pipeline against written anchors.
An honest diagnosis classifies each dimension of the pipeline separately. Some weaknesses live in data entry and record ownership, while others live in response speed or metric computation.
The method notes that scorer agreement has not yet passed the reliability test. A route that fires from a scored dimension stays a proposal until leadership confirms it.
A fishbone diagram is a useful outside lens before a diagnosis, because it sorts possible causes into categories. The diagnostic itself produces scores, bands, and routes rather than a ranked list of fixes. An owner can use the fishbone lens to prepare questions for the scoring conversation.
The Sales Velocity Engine Diagnostic
The Sales Velocity Engine Diagnostic is one module instrument in the VWCG OS. It scores five dimensions of sales velocity on a 0 to 5 scale against written anchors. The composite is a weighted sum with equal weights of 0.20 per dimension.
Pipeline Hygiene Enforcement measures whether CRM validation that blocks saves enforces all four rules. It also checks the nightly stale-opportunity script and the weekly Hygiene Score audit by the Sales Ops Data Steward. Follow-Up Speed and Cadence measures cadence adherence, the inbound SLO, and the custom-line requirement in sequences.
Velocity Metric Integrity measures whether cycle length, win rate, and PV2 come from enforced-clean data. Lead Scoring and AI Governance measures scoring tiers, override tracking, registration of both AI deployments, and the AERI tier. Downstream Routing Health measures whether sales metrics reach the functions that depend on them.
Each dimension routes on its own reading, so a weak one still fires its own route. A theory of constraints lens suggests that a pipeline may move at the pace of its weakest dimension. That lens sits outside the method, but it helps an owner decide where to look first.
Calculating Sales Velocity and Scoring the Anchors
The written anchors define each level in advance for every dimension. For Pipeline Hygiene Enforcement, a score of one describes rules that are absent or advisory. A three describes documented rules with partial validation and an unowned Hygiene Score. A five requires validation that blocks saves on all four rules and a weekly audit.
The Hygiene Score is the weekly ratio of clean fields to total fields across active opportunities. Pipeline Value Velocity multiplies pipeline value by win rate and divides by cycle length. The Inbound Response SLO requires every inbound lead touched within 10 minutes. The Lead Score Override Rate caps account executive overrides at plus or minus 10 points with a documented reason.
These are standing page metrics with published rules behind them. PV2 is banded on the KPI Precision Grid directional scale rather than on the 0 to 5 scale. At the top velocity anchor, PV2 is trusted because hygiene is enforced.
A balanced scorecard lens fits here, because the instrument measures the process that produces revenue. A unit economics lens adds a separate question about what each stage of the pipeline costs to run. Both lenses connect revenue management consulting to the pipeline itself.
Reading the Bands and Routing Red Results
Composite scores fall into three bands with full coverage and no gaps between them. Red runs from 0.0 up to but not including 2.0. Amber runs from 2.0 to 3.5 inclusive, and green runs from above 3.5 up to and including 5.0.
A red dimension proposes the owning remediation playbook, and leadership confirms the proposal. Confirmation happens at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first. An amber dimension routes to monitoring with 30-day pulse checks. A green dimension holds under standing monitoring, and only the PV2 signal gets a daily digest.
A color changes only when a score clears the band edge by a margin, or holds for two consecutive scorings. The margin is 0.25 points on a 0 to 5 scale and 5 points on the AERI 0 to 100 scale. That rule keeps one reading near an edge from flipping a color on its own.
Safety routes behave differently from every other route. They tighten on the first reading and loosen only after an independent second scoring clears the edge. When two routes set the same parameter differently, the most restrictive value wins for safety routes. The owning module value wins for every other parameter.
Inbound Signals and Cross-Module Routes
Signals from other modules also change how this module runs. When Pipeline and Forecast Reliability scores red in the Intelligent Foundations module, CRM validation hardens. Stage aging tightens from 14 to 10 days, hygiene turns amber at 5% deviation, and follow-up cadences compress.
When the AERI overall score sits below 40, lead scoring runs advisory only with human approval. The proposal generator then works from templates only. When the Exit and Acquisition Layer module raises its revenue concentration flag on a client, new-logo leads rank one tier higher. That concentrated client drops out of expansion priority.
A red Follow-Up Speed and Cadence reading also routes to the Change Enablement Sprint module. That module opens an inbound-response adoption sprint when the change reaches more than 10 people or touches any customer-facing process. A red Lead Scoring and AI Governance reading routes to the AI Deployment Canvas module. There, lead scoring and the proposal generator register with dual ownership and quarterly bias audits.
The Pipeline Monitoring and Amber Path playbook runs the weekly Hygiene Score audit and reviews the daily PV2 digest. It pre-briefs the war-room when PV2 drifts toward red. The Sales Ops Data Steward owns it as a standing playbook, and no unrouted breach may sit older than two weeks.
Playbooks That Enforce Hygiene, Speed, and Governance
A red score produces a proposed route. The Pipeline Hygiene Enforcement playbook baselines the Hygiene Score, then implements CRM validation rules that block saves. Those rules cover a mandatory close date, a next step on stage change, and stage aging flags.
The flags publish at 14 days Discovery to Proposal and 21 days Proposal to Decision. A nightly stale-opportunity script, a 24-hour lost-reason code, and a legacy cleanup sprint complete the set.
The Follow-Up Cadence and SLO Activation playbook deploys the five-touch cadence as CRM sequences. Day 0 carries a recap, Day 2 a pain-point resource, and Day 5 a voicemail plus email. Day 8 brings social proof, and Day 14 a break-up. The custom-line requirement applies to every sequence, and the 10-minute inbound SLO registers as a KPI Precision Grid KPI.
Scoring tiers activate in the same playbook. Leads scoring 80+ route to an account executive, 60 to 79 to nurture, and below 60 to marketing. An override log enforces the plus or minus 10 point cap. The VP of Sales owns this playbook with the Sales Ops Data Steward for 4 weeks.
The PV2 War-Room and Gate Response playbook verifies its inputs first, because PV2 on dirty data is a false signal. Sales and customer success leadership decompose PV2 into pipeline volume, win rate, and cycle length. They name the dragging component and match the intervention to the diagnosis.
The VP of Sales owns it with the VP of Customer Success, with 1 week to activate. A RACI lens can help an owner check that each named role holds one clear responsibility.
How a Playbook Run Closes
A playbook run closes when its outcome is met and an independent second scoring reaches amber or better.
Consider a hypothetical firm whose Pipeline Hygiene Enforcement dimension scores red. The playbook installs a validation rule that blocks saves without a close date. The playbook runs 4 weeks under the Sales Ops Data Steward with the VP of Sales. Its outcome includes a Hygiene Score audited weekly and rising.
Imagine a founder-led operation where follow-up depends on individual memory. The mechanism is a CRM sequence that fires on schedule and requires a custom line. The design goal is that every inbound lead gets a touch within the SLO and every breach routes somewhere. An owner weighing business exit planning can ask whether that data would hold up under outside review.
Every owner runs at most three red playbooks at once, and further reds queue by how many modules they route into. A missed outcome at the end of its stated duration escalates to the manager of the owner.
Frequently Asked Questions
- What is the Sales Velocity Engine Diagnostic?
- It scores five dimensions of sales velocity on a 0 to 5 scale against written anchors. Red results propose playbooks that enforce hygiene, speed, and governance. Each dimension carries a weight of 0.20, so the composite is a weighted sum with equal weights.
- How does the diagnostic improve pipeline predictability?
- The diagnostic does not promise a result, so the honest answer is about mechanism. The diagnostic identifies weak dimensions and proposes targeted playbooks. Pipeline Hygiene Enforcement installs CRM validation that blocks saves. Follow-Up Cadence and SLO Activation enforces response speed, and PV2 War-Room and Gate Response verifies PV2 inputs first.
- What are the five dimensions scored?
- The five dimensions are Pipeline Hygiene Enforcement, Follow-Up Speed and Cadence, Velocity Metric Integrity, Lead Scoring and AI Governance, and Downstream Routing Health. Each carries a weight of 0.20. The scorer rates each on the same 0 to 5 scale against written anchors.
- What happens when a dimension scores red?
- A red score proposes a remediation playbook, which leadership confirms at the next scheduled review. Safety routes act on the first reading. Amber dimensions trigger monitoring with 30-day pulse checks. Green dimensions hold under standing monitoring, and the PV2 signal alone gets a daily digest.
- How does routing connect sales data to other business functions?
- Red hygiene routes to a parity and duplicate check on CRM opportunity data in the Integrated Tech Stack module. It also has the Agile Capital Allocation module flag PV2-dependent gate decisions as unverified for the next Forum until hygiene reaches amber. A red PV2 signal blocks Tier 2 to Tier 3 advancement for every revenue-dependent project until PV2 is green.
- How does World Consulting Group help an owner take the next step?
- World Consulting Group implements the Sales Velocity Engine Diagnostic as part of its VWCG OS service. The first step of the engagement is a scoring pass of the five dimensions against the written anchors. Leadership then confirms each proposed red route at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first.
