Optimize Revenue Operations

This skill acts as a revenue operations expert, helping design and optimize the systems connecting marketing, sales, and customer success into a unified revenue engine. It first gathers GTM context (motion type, ACV range, sales cycle length, current tool stack, current lead-management state, goals), checking for a product-marketing-context.md file first before asking. It then applies core principles - single source of truth (one canonical CRM), define-before-automate, measuring every cross-team handoff with SLAs, and revenue-team definition alignment - across a full lead lifecycle framework (Subscriber through Lead, MQL, SQL, Opportunity, Customer, Evangelist, each with entry/exit criteria and an owner), a two-dimensional lead scoring model (explicit fit score plus implicit engagement score, with negative disqualifying signals), lead routing methods (round-robin, territory-based, account-based, skill-based) with a speed-to-lead framework (contact within 5 minutes = 21x more likely to qualify per Lead Connect), pipeline stage management with required fields and stale-deal/stage-skip detection, CRM automation workflows for marketing-to-sales handoffs and calendar scheduling, deal desk approval tiers for non-standard deals, data hygiene/deduplication and enrichment tooling, and a RevOps metrics dashboard spanning marketing/sales/executive views (lead-to-MQL rate, pipeline velocity, CAC, LTV:CAC).

Use it when the user needs lead scoring, routing, handoffs, or lifecycle definitions; when CRM process design and revenue-team coordination are the core problem; or when marketing, sales, and customer success systems need operational alignment.

Don't block on missing inputs - work with whatever context the user gives and note what would strengthen the solution rather than stalling. Treat its output as a set of recommendation documents (lifecycle stages, scoring spec, routing rules, pipeline configuration, metrics dashboard spec) to implement and validate against your actual CRM platform, not a substitute for environment-specific configuration or expert review - stop to ask for clarification if required inputs, permissions, or success criteria are missing.

Input: GTM motion, ACV, sales cycle length, current CRM/tooling stack, and the specific RevOps problem (scoring, routing, handoffs, lifecycle). Output: five standalone implementation documents - a lifecycle stage document, a scoring specification, a routing rules decision tree, a pipeline configuration, and a metrics dashboard spec - with platform-specific guidance when the CRM is known.

MQL-to-SQL Handoff SLA:
- MQL alert sent to assigned rep
- Rep contacts within 4 hours (business hours)
- Rep qualifies or rejects within 48 hours
- Rejected MQLs go to recycling nurture with reason code

References CRM and RevOps tooling including HubSpot, Salesforce, Calendly, SavvyCal, Clearbit, Apollo, ZoomInfo, ActiveCampaign, and Zapier for cross-tool automation. Chains with cold-email, email-sequence, pricing-strategy, analytics-tracking, launch-strategy, and sales-enablement skills.

RevOps, marketing ops, and sales ops professionals designing or fixing the systems connecting marketing, sales, and customer success - lead scoring, routing, lifecycle stages, pipeline hygiene, and cross-team SLAs - who want concrete, implementable specs rather than generic RevOps advice.