accelerating-pipeline

Use when pipeline velocity is flat or declining, win rates are below 20 percent, sales cycles are lengthening, deals are single-threaded, or lead routing is slow. Use when MQL volume is prioritized over pipeline quality, when marketing and sales define funnel stages differently, or when signal-based engagement has not replaced linear nurture drips.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "accelerating-pipeline" with this command: npx skills add amogha-dalvi/marketing_gtm/amogha-dalvi-marketing-gtm-accelerating-pipeline

Pipeline Accelerator

Overview

Pipeline velocity is four levers operating together: deal volume, win rate, deal size, and cycle time. A 15% improvement across all four produces a 75% velocity increase. This skill identifies the highest-leverage lever and applies AI-powered signal-based approaches to move all four.

When to Use

  • Pipeline velocity is flat or declining quarter over quarter
  • Win rate is below 20% overall
  • Sales cycle length is increasing or exceeds 60 days
  • Deals are single-threaded (one champion per opportunity)
  • Lead response time exceeds 5 minutes for high-intent signals
  • MQL volume is the primary marketing success metric
  • Marketing and sales define pipeline stages differently
  • No formal pipeline velocity measurement exists
  • Lead scoring is manual, static, or nonexistent

Don't use when: You have fewer than 30 closed deals to analyze, or when the constraint is product-market fit rather than GTM execution.

Quick Reference

PhaseDurationOutput
Pipeline velocity auditDay 1-2Velocity, lever analysis
Intent-based ABM designDay 3-5Account tiers, sequences
Signal-based engagementDay 6-8Signal taxonomy, routing
Buying group orchestrationDay 9-10Coverage maps, playbook
Predictive lead scoringDay 11-13Scoring model
Win rate improvementDay 14-16Win/loss system
RevOps alignmentDay 17-19Dashboard, SLAs
AI agent deploymentDay 20-22Agent specs, metrics

Core Deliverables

  • Pipeline Velocity Audit -- Velocity calculation, lever analysis, conversion map
  • ABM Program Design -- Account tiers, buying group maps, engagement sequences
  • Signal Engagement System -- Signal taxonomy, scoring model, routing rules
  • Buying Group Orchestration -- Coverage maps, role-based content, gap-filling playbook
  • Lead Scoring Model -- Fit, intent, engagement layers with composite scoring
  • Win Rate Playbook -- Win/loss analysis, personalization, deal acceleration
  • RevOps Dashboard -- Pipeline, funnel, signal, attribution views

Common Mistakes

  • Optimizing only top-of-funnel volume while ignoring other velocity levers
  • Using MQL volume as success metric instead of pipeline created
  • Building linear nurture drips that ignore buyer context and signal strength
  • Routing all leads the same way regardless of intent level
  • Single-threading deals instead of orchestrating the buying group
  • Deploying AI agents without measuring baseline performance first

Integration

Feeds into: tracking-marketing-metrics, managing-marketing-ops

Refresh: Velocity weekly. Lever analysis monthly. ABM list quarterly. Lead scoring quarterly. Full system audit every 6 months.

See workflow.md for detailed phase-by-phase execution, velocity calculators, ABM templates, signal workflows, scoring architecture, and AI agent deployment plans.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Web3

defining-icp-segmentation

No summary provided by upstream source.

Repository SourceNeeds Review
General

reducing-cac

No summary provided by upstream source.

Repository SourceNeeds Review
General

planning-marketing-budget

No summary provided by upstream source.

Repository SourceNeeds Review
General

running-content-engine

No summary provided by upstream source.

Repository SourceNeeds Review