suede-revops

Defines lead scoring, routing rules, pipeline stages, and CRM automation workflows for revenue operations.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-revops-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-revops
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-revops-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Marketing, sales, and customer success teams often operate with misaligned lead definitions, leaky handoffs, stale pipelines, and messy CRM data. This Skill produces implementation-ready revenue operations logic — lifecycle stages, scoring models, routing rules, and automation workflows — so teams can align on definitions and fix funnel leaks before automating anything. ## Core Features & Use Cases - Lead Lifecycle & Scoring: Defines Subscriber-through-Evangelist stage criteria, MQL/SQL thresholds, and fit-plus-engagement scoring models with negative scoring and calibration guidance. - Routing & Pipeline Management: Builds routing decision trees (round-robin, territory, ABM), speed-to-lead SLAs, pipeline stage hygiene rules, and deal-desk approval tiers. - CRM Automation & Hygiene: Provides platform-specific workflow recipes for HubSpot and Salesforce, dedup strategies, required-field enforcement, and quarterly audit checklists. - Use Case: A B2B SaaS company whose marketing and sales teams disagree on what counts as an MQL uses this Skill to define shared lifecycle stages, a 4-hour MQL follow-up SLA, and a scoring model calibrated against closed-won data. ## Quick Start Use the suede-revops skill to define our lead lifecycle stages, MQL scoring model, and marketing-to-sales handoff SLA for our HubSpot CRM.

Frequently Asked Questions about suede-revops

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

FAQPage Schema
How do I define MQL and SQL criteria for my sales team?

An MQL requires both fit (company size, industry, role matching your ICP) and engagement (pricing page visits, demo requests) crossing a threshold, typically 50-80 points. An SQL requires a qualifying sales conversation confirming at least two of budget, authority, need, and timeline.

How do I set up lead scoring for enterprise sales?

For enterprise deals ($50K+ ACV), weight fit at 60% and engagement at 40%, emphasizing company size, VP+ titles, and budget authority. Set the MQL threshold around 75 points and recalibrate quarterly against closed-won data.

What lead routing method should I use: round-robin or territory?

Round-robin works for equal territories and similar deal sizes; territory routing fits regional teams or industry specialists. Route to the most specific match first (named accounts, then enterprise, then territory), with round-robin as the fallback and a queue for unassigned leads.

Does this skill work with HubSpot and Salesforce?

Yes, the references include platform-specific automation recipes: HubSpot workflows for MQL alerts, SLA escalation, and closed-won handoffs, plus equivalent Salesforce Flow configurations. Verify the live schema and permissions before implementing any workflow.

Can this skill write cold outreach emails or change my CRM directly?

No, writing outreach is deferred to a cold-email skill, and the skill never mutates production CRM fields, routing, or records without reading the live schema, previewing the effect, and receiving explicit approval. It produces recommendations and documents for human decision-makers.

How do I fix a messy CRM with duplicates and missing fields?

Use a dedup strategy with email domain, company name, and phone as match keys, enforce required fields per lifecycle stage, and run weekly automated dedup with manual review. Follow the quarterly audit checklist covering duplicates, stale contacts, and stage distribution.