deal-velocity-engineer

Diagnose B2B SaaS pipeline velocity issues and produce an actionable blueprint with stage gate criteria.

40|18|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/NEON-Rutger/B2B-revops-skills --skill deal-velocity-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deal-velocity-engineer
Source: https://github.com/NEON-Rutger/B2B-revops-skills/tree/main/deal-velocity-engineer
Command: npx skills add https://github.com/NEON-Rutger/B2B-revops-skills --skill deal-velocity-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you diagnose why deals move slowly, stall, or die, and then redesign the revenue system so pipeline velocity improves through measurable process changes.

Core Features & Use Cases

  • Velocity diagnostics: Produces a deal velocity scorecard (cycle length, win rate, slippage, zombie %, multi-threading, stage drop-off) and identifies the binding constraint using symptom patterns.
  • Pipeline deflation & zombie elimination: Defines zombie criteria, triage decisions (revive/push/close), and prevention routines to remove inflated, unproductive pipeline without “just adding more leads.”
  • Stage gates & enforcement: Designs buyer-action-based stage exit criteria, deal health scoring dimensions, and operating-cadence “velocity rules” to prevent seller activity from masquerading as progress.
  • Multi-threading & MAP installation: Improves deal resilience by enforcing stakeholder engagement targets and mutual action plans for decision acceleration.

Quick Start

Ask the skill to run a deal-velocity diagnostic for your last 12 months of CRM pipeline and return the single highest-priority system constraint to fix first.

Frequently Asked Questions about deal-velocity-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose slow deal velocity in my B2B pipeline?

To diagnose slow deal velocity, measure pipeline cycle length, win rate, conversion drop-offs, slippage, and zombie deal prevalence across stages to identify the binding constraint. This produces a scorecard isolating the specific bottleneck restricting deal progression.

What is the best way to eliminate zombie deals and deflate an inflated pipeline?

Eliminating zombie deals requires defining specific zombie criteria and applying triage decisions to revive, push, or close them. This removes unproductive pipeline volume without needing to add more leads, preventing pipeline inflation.

How do I create stage exit criteria based on buyer actions?

Creating buyer-action-based stage exit criteria involves setting deal health scoring dimensions and operating-cadence velocity rules. This enforces strict stage gates that prevent seller activity from masquerading as actual deal progress.

When do I need mutual action plans to improve multi-threading in sales negotiations?

You need mutual action plans to improve multi-threading when deals lack stakeholder engagement and stall during negotiations. Enforcing these plans with specific engagement targets accelerates decision-making and builds deal resilience.

Can I use pipeline diagnostics to fix inaccurate forecast inputs?

Yes, pipeline diagnostics fix inaccurate forecast inputs by analyzing multi-threading performance and stage progression to establish signal-based velocity rules. This ensures forecasting relies on measurable buyer actions rather than seller optimism.

What is a deal velocity scorecard and what does it measure?

A deal velocity scorecard measures pipeline cycle length, win rate, slippage, zombie percentage, multi-threading, and stage drop-off rates. It identifies symptom patterns to pinpoint the highest-priority system constraint limiting revenue generation.