Revops
Install when you need copy-paste HubSpot and Salesforce automation recipes for MQL routing, SLA escalation, and cross-tool revops without hiring a full RevOps team.
Overview
RevOps is an agent skill most often used in Grow (also Launch, Operate) that supplies HubSpot, Salesforce, and cross-tool revenue automation playbooks for MQL and lifecycle workflows.
Install
npx skills add https://github.com/infrasity-labs/dev-gtm-claude-skills --skill revopsWhat is this skill?
- HubSpot workflow recipes for MQL alert, round-robin assignment, and 4-hour follow-up tasks.
- MQL SLA escalation chain at 12h, 24h, and 48h with manager alerts and reassignment.
- Lead-scoring and lifecycle-stage automation patterns documented as platform-specific playbooks.
- Cross-tool recipes spanning scheduling, CRM, and Slack-style internal notifications.
- Each playbook lists trigger, ordered actions, outcome, and implementation notes for solo operators.
Adoption & trust: 1 installs on skills.sh; 24 GitHub stars; trending (+100% hot-view momentum).
What problem does it solve?
You have leads entering HubSpot but no consistent MQL assignment, SLA enforcement, or documented automation recipes your agent can implement.
Who is it for?
Indie SaaS founders automating HubSpot lifecycle stages, sales alerts, and handoffs from marketing to a tiny sales team.
Skip if: Builders with no CRM and no intent to run pipeline automation, or enterprises needing bespoke Salesforce Apex instead of playbook templates.
When should I use this skill?
The user asks for HubSpot workflows, MQL routing, SLA escalation, lead scoring automation, or RevOps playbooks across CRM and scheduling tools.
What do I get? / Deliverables
You get named workflows with triggers, actions, and outcomes ready to paste into HubSpot or adapt for Salesforce so every MQL gets worked within your SLA.
- Named workflow definitions with triggers and actions
- SLA escalation ladder documentation
- Implementation notes for enrollment exclusions
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Revenue operations automations compound after you have a product and pipeline—Grow is the canonical home for lifecycle and sales-motion tooling. MQL assignment, SLA breaches, and lead-scoring workflows are lifecycle operations that keep prospects moving through funnel stages.
Where it fits
Configure MQL notification, owner rotation, and a 4-hour follow-up task the moment lifecycle stage changes.
Turn on internal Slack and email alerts so your first outbound prospects do not sit unassigned after a campaign spike.
How it compares
Use structured RevOps playbooks instead of asking the agent for vague ‘set up HubSpot automation’ without triggers and escalation steps.
Common Questions / FAQ
Who is revops for?
It is for solo and indie builders who own CRM configuration and need agent-ready recipes for marketing-to-sales automation.
When should I use revops?
Use it in Grow when designing lifecycle workflows, at Launch when standing up first sales alerts, and in Operate when tightening SLA breach and reassignment rules.
Is revops safe to install?
The skill describes CRM workflow configuration only; review the Security Audits panel on this page and never paste production API keys into chat while following playbooks.
SKILL.md
READMESKILL.md - Revops
# Automation Playbooks Platform-specific workflow recipes for HubSpot, Salesforce, scheduling tools, and cross-tool automation. ## HubSpot Workflow Recipes ### 1. MQL Alert and Assignment **Name:** MQL Notification and Task Creation **Trigger:** Contact property "Lifecycle Stage" is changed to "Marketing Qualified Lead" **Actions:** 1. Rotate contact owner among sales team (round-robin) 2. Send internal email notification to contact owner with lead context 3. Create task: "Follow up with [Contact Name]" — due in 4 hours 4. Send Slack notification to #sales-alerts channel 5. Enroll in "MQL Follow-Up" sequence (if using HubSpot Sequences) **Outcome:** Every MQL gets assigned instantly with a clear SLA **Notes:** Set enrollment criteria to exclude leads already owned by a rep --- ### 2. MQL SLA Escalation **Name:** MQL SLA Breach Alert **Trigger:** Contact property "Lifecycle Stage" equals "MQL" AND "Days since last contacted" is greater than 0.5 (12 hours) **Actions:** 1. Send internal email to contact owner: "SLA warning: [Contact Name] has not been contacted" 2. If still no activity after 24 hours → send alert to sales manager 3. If still no activity after 48 hours → reassign contact owner via rotation 4. Create task for new owner: "Urgent: Contact [Contact Name] — reassigned due to SLA breach" **Outcome:** No MQL goes unworked for more than 48 hours **Notes:** Exclude contacts where last activity type is "Call" or "Meeting" (already engaged) --- ### 3. Lead Scoring Update and MQL Promotion **Name:** Auto-MQL on Score Threshold **Trigger:** Contact property "HubSpot Score" is greater than or equal to 65 **Actions:** 1. Set lifecycle stage to "Marketing Qualified Lead" 2. Set "MQL Date" to current date 3. Suppress from marketing nurture workflows 4. Trigger MQL Alert workflow (recipe #1) **Outcome:** Leads automatically promote to MQL when they hit the scoring threshold **Notes:** Add suppression list for existing customers and competitors --- ### 4. Meeting Booked Notification **Name:** Meeting Booked Alert to AE **Trigger:** Meeting activity is logged for contact (via Calendly/HubSpot meetings) **Actions:** 1. Send internal email to contact owner with meeting details 2. Update contact property "Last Meeting Booked" to current date 3. If lifecycle stage is "Lead" → update to "MQL" 4. Create task: "Prepare for meeting with [Contact Name]" — due 1 hour before meeting 5. Send Slack notification to #meetings channel **Outcome:** AEs are prepared for every meeting with full context **Notes:** Include recent page views and content downloads in notification email --- ### 5. Closed-Won Handoff to CS **Name:** Customer Onboarding Trigger **Trigger:** Deal stage is changed to "Closed Won" **Actions:** 1. Update associated contact lifecycle stage to "Customer" 2. Set "Customer Since" date to current date 3. Assign contact owner to CS team member (based on segment/territory) 4. Create task for CS: "Schedule kickoff call with [Company Name]" — due in 2 business days 5. Enroll contact in "Customer Onboarding" email sequence 6. Send internal notification to CS manager 7. Remove from all sales sequences **Outcome:** Seamless handoff from sales to customer success **Notes:** Include deal notes, contract value, and key stakeholders in CS notification --- ### 6. Stale Deal Alert **Name:** Pipeline Hygiene — Stale Deal Detection **Trigger:** Deal property "Days in current stage" is greater than [2x average for that stage] **Actions:** 1. Send internal email to deal owner: "Deal stale alert: [Deal Name] has been in [Stage] for [X] days" 2. Create task: "Update or close [Deal Name]" — due in 3 business days 3. If no update after 7 days → alert sales manager 4. Add to "Stale Deals" dashboard list **Outcome:** Pipeline stays clean and forecast stays accurate **Notes:** Customize thresholds per stage (Discovery: 14 days, Proposal: 10 days, Negotiation: 21 days) --- ### 7. Recycled Lead Nurture Re-Entry **Name:** MQL Recycling to