sales-pipeline-revops

Designs revenue workflows aligning marketing, sales, and customer success for B2B SaaS.

Updated Jan 28, 2026

Search Tags:#sql #pipeline-management #lead-scoring #revops #lead-routing #crm-automation #mql

Ready to run

npx skills add https://github.com/scanady/nexus-agents --skill sales-pipeline-revops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sales-pipeline-revops
Source: https://github.com/scanady/nexus-agents/tree/main/skills/sales-pipeline-revops
Command: npx skills add https://github.com/scanady/nexus-agents --skill sales-pipeline-revops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Revenue operations teams often struggle to align marketing, sales, and customer success across the end-to-end revenue lifecycle. This Skill provides a comprehensive framework to design and optimize RevOps workflows, including lifecycle definitions, scoring, routing, pipeline hygiene, and automation.

Core Features & Use Cases

Lifecycle stage definitions, SLAs, owners, and recycling/rejection rules for Subscriber, Lead, MQL, SQL, Opportunity, Customer, and Evangelist.
Fit + engagement scoring models with calibration, negative signals, and MQL-to-SQL handoffs (with templates in references/).
Routing rules (round-robin, territory, ABM) with fallbacks and speed-to-lead optimizations; automation templates for common CRMs.

Quick Start

Begin by reviewing product-marketing-context.md and then define the lifecycle stages, scoring criteria, and routing rules on paper before automating.

Frequently Asked Questions about sales-pipeline-revops

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

FAQPage Schema

How do I optimize B2B SaaS RevOps workflows for MQL to SQL handoffs?▼

Optimizing RevOps workflows for MQL to SQL handoffs requires defining clear lifecycle stages, SLAs, and fit plus engagement scoring models. You establish specific MQL-to-SQL criteria with calibration and negative signals to align marketing and sales.

What is the best way to set up lead routing rules and speed-to-lead automation in a CRM?▼

Setting up lead routing rules involves configuring round-robin, territory, or ABM strategies with fallbacks. You can apply speed-to-lead optimizations and platform-agnostic automation templates to route MQLs efficiently across common CRM environments.

How do I build a lead scoring model that includes negative signals for pipeline management?▼

Building a lead scoring model with negative signals requires combining fit and engagement data calibration. You define specific criteria to deduct points for disqualifying behaviors, ensuring only qualified leads transition from MQL to SQL stages.

Can I use this pipeline management framework to define lifecycle stages for subscribers and evangelists?▼

Yes, you can use this pipeline management framework to define lifecycle stages for subscribers, leads, MQLs, SQLs, opportunities, customers, and evangelists. It provides specific owners, SLAs, and recycling or rejection rules for each stage.

Do I need product marketing context before implementing RevOps pipeline automation?▼

Yes, reviewing product marketing context is required before implementing RevOps pipeline automation. You should define lifecycle stages, scoring criteria, and routing rules on paper first, then apply platform-agnostic automation templates for CRM execution.

Why does my lead routing strategy need fallback rules for B2B SaaS pipeline hygiene?▼

Lead routing strategies need fallback rules to maintain pipeline hygiene when standard territory or ABM assignments fail. Fallbacks ensure no MQLs are dropped, supporting speed-to-lead optimizations and continuous revenue-operations workflow alignment.