revops

Name: revops
Availability: InStock
Author: felarmouche

Implement end-to-end RevOps practices to unify marketing, sales, and customer success.

Updated Oct 16, 2025

Search Tags:#automation #routing #crm #pipeline #scoring #lifecycle #revops

Ready to run

npx skills add https://github.com/felarmouche/elaesthetics-nextjs --skill revops-felarmouche

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: revops
Source: https://github.com/felarmouche/elaesthetics-nextjs/tree/main/.agents/skills/revops
Command: npx skills add https://github.com/felarmouche/elaesthetics-nextjs --skill revops-felarmouche

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

RevOps unifies and optimizes the systems that connect marketing, sales, and customer success into a single revenue engine, reducing handoff leaks and misaligned incentives that slow growth.

Core Features & Use Cases

Single Source of Truth: Establish one canonical CRM source of truth for leads and accounts.
Define Before Automate: Capture stage definitions, scoring, and routing on paper before automating.
Measure Every Handoff: Include SLAs and ownership for MQL<->SQL, SDR<->AE, and CS handoffs.
Revenue Team Alignment: Align definitions and governance across teams to prevent misfires.

Quick Start

Design your initial RevOps playbook and implement core stage definitions, scoring models, routing rules, and CRM automation to start closing gaps.

Frequently Asked Questions about revops

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

FAQPage Schema

How do I prevent revenue leaks between marketing, sales, and customer success teams?▼

RevOps prevents revenue leaks by unifying marketing, sales, and customer success into a single revenue engine, establishing a canonical CRM source of truth, and measuring every handoff with clear SLAs to prevent misaligned incentives and handoff gaps.

How do I set up lead scoring and routing rules in my CRM?▼

You set up lead scoring and routing by capturing stage definitions and models on paper first, then applying cross-tool automation with HubSpot, Salesforce, Calendly, and enrichment tools to route leads through defined lifecycle stages.

What is the best way to establish a single source of truth for B2B SaaS pipeline hygiene?▼

Establishing a single source of truth for pipeline hygiene requires a canonical CRM source that defines lifecycle stages from Subscriber to Evangelist, applies lead scoring models, and measures handoffs to maintain data quality across GTM teams.

Can I use this RevOps approach to align SDR, AE, and CS handoffs with SLAs?▼

Yes, this RevOps approach aligns SDR, AE, and CS handoffs by defining governance and SLAs across teams, ensuring every handoff including MQL to SQL transitions has clear ownership to prevent misfires and revenue leaks.

Do I need to define lifecycle stages before automating my revenue pipeline?▼

Yes, you must define lifecycle stages on paper before automating, as RevOps practices require capturing stage definitions, scoring models, and routing trees prior to implementing cross-tool CRM automation to prevent misaligned incentives.