Use Cases
A B2B SaaS company finds that many MQLs never reach sales and conversion is low. They invoke the RevOps skill to define lifecycle stages, build a fit+engagement scoring model, and set routing rules with 4-hour SLA. The skill delivers clear handoff SLAs and CRM automation recipes, reducing leaked leads and improving speed-to-lead, directly lifting pipeline conversion.
A scaling startup has no standard pipeline stages and reps skip stages arbitrarily. Using the RevOps skill, they get a pipeline stage table with required fields, stale-deal alerts, and deal desk tiers for non-standard terms. This brings discipline to forecasting and approvals, helps managers spot stalled deals, and aligns revenue team definitions across functions.
Skill File
Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When the user needs help with revenue operations, lead lifecycle management, marketing-to-sales handoff, lead scoring, routing, pipeline stages, CRM automation, or data hygiene. Typical triggers: 'RevOps', 'MQL', 'lead routing', 'pipeline management'.
.agents/product-marketing.md for context if present, then gathers GTM motion, ACV, stack, and goals.A unified revenue engine design: clear stage definitions, scoring thresholds, routing logic, SLA-bound handoffs, and automation recipes that reduce leaks and align marketing, sales, and CS.