What's on the bench.
Build Model
Generates a modeling plan detailing transforms, tests, and deployment schedule for analytics use cases.
Success Planning Framework
Use to structure collaborative success plans with milestones, KPIs, and governance.
Expansion Playbook
Use to package upsell, cross-sell, and advocacy motions tied to customer outcomes.
Exec Briefing
Use to craft concise executive updates, agendas, and follow-up logs for QBR/EBR sessions.
Account Health Framework
Use to score accounts, flag risks, and standardize remediation triggers.
Run Account Review
Produces a structured account review packet with health signals, risks, and expansion plays.
Plan Qbr
Generates an executive-ready QBR/EBR agenda with data narratives, proof points, and follow-up actions.
Build Success Plan
Produces a joint success plan with milestones, KPIs, stakeholders, and expansion hooks.
Signal Intel
Use when consolidating intent, product usage, and third-party signals to prioritize ABM actions.
Personalization
Use when crafting tiered ABM messaging, offers, and creative variants.
Account Tiering
Use when defining ABM tiers, scoring logic, and coverage rules.
Target Accounts
Generates a prioritized ABM target list with tiering, buying committees, and activation triggers.
Plan Plays
Produces an ABM playbook roadmap with offers, channels, and timelines aligned to tiers.
Monitor Abm
Builds an ABM operations dashboard + action plan for engagement, pipeline, and experiment tracking.
Sales Methodology
Implement and operationalize proven sales methodologies across revenue teams, with deep SPICED qualification depth. Use when the user mentions SPICED, MEDDIC, MEDDPICC, BANT, Challenger, SPIN, Gap Selling, sales qualification, deal scoring, sales process design, pipeline qualification, discovery frameworks, deal review, sales coaching, rep onboarding, discount negotiation, discount objection handling, or pricing objections. SPICED depth includes full qualification scoring, buying committee mapping by persona, discovery call structure, pipeline stage gating, and canonical language patterns by customer cluster. Also trigger for structuring discovery calls, scoring deals, running deal reviews, handling discount requests, or operationalizing any sales framework. Covers methodology selection, CRM implementation, and discount negotiation playbooks. BOUNDARY: For change management see revops-change-management. For ICP building see neon-icp. For discount governance policy see pricing-strategy.
Revops Strategy
Revenue operations strategy, pipeline architecture, and strategic advisory for B2B companies. Use this skill when the user mentions RevOps, revenue operations, pipeline architecture, bow tie model, bowtie funnel, funnel stages, revenue leaks, KPI frameworks, sales-marketing alignment, GTM strategy, data hygiene, tech stack audit, revenue engine, or when they need help framing a strategic response to a client or stakeholder about revenue operations topics. Also trigger on pushing back on vanity metrics, translating problems into RevOps language, diagnosing pipeline problems, or building KPI frameworks. Even without "RevOps" — funnel conversion, pipeline velocity, lead handoffs, revenue alignment all trigger this. Also covers ICP-to-messaging alignment and operating system architecture. BOUNDARY: Covers strategic FRAMING and pipeline architecture. For ICP building, see revops-icp-building. For CRM implementation, see revops-hubspot. For operating system design, see revops-operating-system.
Revops Salesforce
Salesforce implementation patterns for revenue operations teams. Use when the user mentions Salesforce, SFDC, Salesforce setup, Salesforce object model, Salesforce Flows, record-triggered flows, Salesforce automation, Salesforce properties, Salesforce reporting, Salesforce dashboards, opportunity stages in Salesforce, Salesforce pipeline, collaborative forecasting, Einstein, CRM Analytics, Pipeline Inspection, Salesforce data model, Salesforce migration, Process Builder replacement, Salesforce field governance, Salesforce territory management, or Salesforce integrations. Also trigger on 'our Salesforce is a mess,' 'how should we set up Salesforce,' 'migrate from Process Builder to Flow,' or any CRM architecture question where the team uses Salesforce. BOUNDARY: Covers Salesforce-specific implementation. For CRM-agnostic strategy, see revops-strategy. For HubSpot, see revops-hubspot. For generic enrichment, see data-enrichment. For generic routing, see lead-routing.
Revops Org Chart
RevOps team org design, role structure, and hiring sequencing by company size and ARR stage. Use whenever a client asks about structuring their RevOps team, hiring order, business partner vs. center-of-excellence model, when to engage a Systems Architect (FTE, fractional, or advisory), evolving a CRM or automation team toward RevOps, who RevOps should report to, how to give RevOps a mandate or charter, centralized vs. embedded vs. hub-and-spoke model, multi-BU or multi-instance team design, or how to use agencies without creating dependency. Also trigger when a client has Business Partners and is theorizing about adding an Architect role. Includes frameworks from RevOps Co-op, Revenue Wizards, Hyperscayle, Go Nimbly, Maxio, Leanlayer, Stage2 Capital, and Rutger's own hiring guide.
Revops Metrics
Revenue performance measurement, funnel math, and unit economics for B2B teams. Use when the user mentions revenue metrics, conversion rates, pipeline velocity, unit economics, LTV, CAC, payback period, cohort analysis, NRR, GRR, churn rate, expansion revenue, ARR, MRR, funnel conversion, win rate, deal size, sales cycle, Rule of 40, burn multiple, T2D3, growth benchmarks, deal health scoring, deal health dimensions, conversational intelligence metrics, strategic initiative trackers, activity velocity, multi-threading score, or measuring revenue performance. Also trigger on "our numbers are off," "how do we stack up," "what should our conversion rate be," or "how healthy is this deal." BOUNDARY: This skill covers WHAT to measure. For forecasting, see revops-forecasting. For meeting cadence, see revenue-operating-cadence.
Revops Hubspot
HubSpot implementation patterns for revenue operations teams. Use this skill when the user mentions HubSpot, CRM setup, HubSpot properties, lifecycle stages, lead scoring in HubSpot, HubSpot workflows, HubSpot reporting, HubSpot dashboards, deal pipelines in HubSpot, HubSpot automation, contact/company/deal properties, HubSpot integrations, or asks about CRM architecture for B2B revenue teams using HubSpot. Also trigger when the user asks about mapping a bow tie or funnel model into HubSpot, building RevOps reporting in HubSpot, structuring HubSpot for multi-team revenue operations, cleaning up a messy HubSpot instance, HubSpot data hygiene, or migrating to HubSpot. If someone mentions CRM and they're in a B2B context, this skill is likely relevant even if they don't say "HubSpot" explicitly. BOUNDARY: This skill covers HubSpot-specific implementation. For strategic pipeline architecture and framework thinking, see revops-strategy. For ICP BUILDING methodology, see neon-icp.
Revops Handoffs
Revenue handoff design across the full bow-tie model — Marketing → Sales → Partner/Implementation → CS → Sales (expansion), plus lifecycle marketing and ABM loops. Use when the user mentions handoff, lead routing, speed-to-lead, MQL routing, closed-won handoff, partner handoff, CS-to-sales handback, expansion pipeline, cross-sell pipeline, upsell pipeline, renewal pipeline, territory routing, SLA between teams, transfer document, or AI handoff docs. Also trigger on "leads fall through the cracks," "CS never knows what sales promised," "we lose momentum after signature," "nobody owns expansion," or "cross-sell has a different buying group." BOUNDARY: covers handoff design and SLAs between bow-tie stages. For HubSpot implementation, also consult revops-hubspot. For CS operations, see cs-operations. For SPICED, see sales-methodology.
Revops Forecasting
Revenue forecasting methodology, forecast categories, pipeline analysis, and predictability for B2B revenue teams. Use when the user mentions forecasting, revenue forecast, sales forecast, forecast accuracy, forecast categories, commit, best case, upside, pipeline coverage, weighted pipeline, forecast cadence, capacity planning, quota modeling, forecast call, deal inspection, or forecast variance. Also trigger when someone says 'we can't predict our number,' 'our forecast is always wrong,' 'how much will we close this quarter,' 'we can't see our pipeline,' 'deals go stale,' or 'we need better dashboards.' Also trigger on pipeline visibility, pipeline reporting, sales dashboards, pipeline hygiene, stale deals, pipeline health, big deal alerts, or pipeline quality score. BOUNDARY: Covers forecast methodology, accuracy, and pipeline visibility/reporting. For CRM-specific dashboard implementation, see revops-hubspot. For metrics and benchmarks, see revops-metrics.
Revops Diagnostic
Revenue operations diagnostic frameworks for identifying system constraints and root causes in B2B GTM organizations. Use when the user mentions diagnosing revenue problems, finding the constraint, IFA diagnostic, six stages of check, system thinking, root cause analysis, A3 analysis, GTM health check, revenue system audit, or figuring out what's wrong with their revenue engine. Also trigger when someone describes symptoms like weak pipeline, wrong forecast, underperforming reps, or leadership chaos. If someone says "we keep missing plan" or "everyone is busy but nothing moves," activate this skill. This is the diagnostic skill — find the real constraint before recommending what to fix.
Revops Data Governance
Revenue data governance — the operational discipline every other RevOps skill depends on. Use when the user mentions data governance, data quality, data model, data architecture, field governance, property naming conventions, data hygiene, deduplication, integration data flows, system of record, sync rules, data enrichment, data definitions, one vision of truth, data spine, data quality scoring, validation rules, GDPR, field deprecation, or data audit. Also trigger when someone says "our reports don't match," "our CRM is a mess," "we have too many fields," or describes duplicate accounts, conflicting numbers, stale data. Fix data governance before building metrics or scaling. BOUNDARY: Covers data MODEL, QUALITY, and GOVERNANCE. For HubSpot setup, see revops-hubspot. For metrics, see revops-metrics.