NEON-Rutger/B2B-revops-skills

38 skills

• abm-engagement-scoring

  Account-level engagement scoring, buying group/DMU measurement, and marketing-to-sales handover triggers for account-based marketing programs (50-500 named accounts). Use when the user mentions account engagement score, ABM measurement, buying committee, DMU coverage, account stage progression, engagement triggering sales handover, multiple stakeholder tracking, account qualification, or ABM program measurement. Also trigger on 'how do we measure ABM success,' 'which accounts are hot,' 'do we have the buying group,' 'when do we hand this to sales,' 'account engagement scoring model,' or 'we run ABM but can't prove ROI.' BOUNDARY: Covers account-level engagement scoring, buying group measurement, and handover-to-sales triggers in ABM contexts. For lead-level scoring (fit + engagement dual-axis), see marketing-operations. For account selection and ICP methodology, see icp-builder. For sales speed-to-lead and routing, see lead-routing.

  Reaches the webInstructions only4,579 words
• closed-lost-revival

  Run a quarterly revival sweep over the pipeline you already paid for: closed-lost deals, proposals that went quiet, champions who changed jobs, and engaged contacts who went silent. Triggers on 'closed-lost,' 'win-back,' 'revive dead deals,' 'they ghosted us,' 'gone quiet,' 'lost the deal, what now,' 'reactivation campaign,' 're-engage old pipeline,' 'proposal never answered,' 'dormant accounts,' or any situation where a team is buying new leads while a warehouse of once-interested accounts sits untouched. The skill gates hard: it revives accounts that engaged and then went quiet, never cold contacts that ignored you from day one. BOUNDARY: closed-won- replication-play covers the WON side of the same idea (turning wins into lookalikes); champion-move-detection covers movers as a standing monitoring signal, while this skill only consumes verified moves inside a quarterly campaign; stage-aware-follow-up owns live threads still inside an active cadence (under 60 days of silence), which are patience, not revival.

  Self-containedInstructions only1,636 words
• crm-migration-consolidation

  CRM migration, instance consolidation, and post-merger integration for B2B revenue teams; system-of-record design; deduplication and identity resolution; data harmonization before cutover; historical data strategy; adoption and change management; PE portfolio integration playbooks. Use when the user describes merging two CRM instances, consolidating after acquisition, post-merger CRM integration, handling dual CRM coexistence, managing CRM data quality before migration, defining which system of record wins for which object, planning a CRM cutover, multi-entity or multi-currency CRM challenges, or running a 100-day integration plan with CRM elements. Trigger phrases: "merge our CRMs", "consolidate two HubSpot portals", "HubSpot and Salesforce together", "post-merger CRM", "CRM integration plan", "deduplication before migration", "which CRM wins", "cutover", "consolidation strategy", or "100-day CRM plan". BOUNDARY: Use this skill for CRM architecture decisions, data strategy, and integration planning. For detailed Salesforce configuration, see revops-salesforce. For detailed HubSpot configuration, see revops-hubspot. For handoff design across the revenue bow tie, see revops-handoffs. For broader PMI strategy, see revops-change-management. For data governance and master data management, see revops-data-governance. See also: revops-diagnostic, revops-tech-stack.

  Reaches the webInstructions only5,673 words
• cs-operations

  Customer success operations for B2B SaaS. The post-sale revenue engine that prevents churn, drives expansion, and compounds customer value. Use when the user mentions customer success, CS ops, health scoring, renewal management, churn prevention, expansion playbook, expansion signals, onboarding orchestration, time to first value, QBR, customer segmentation, coverage model, high-touch, low-touch, tech-touch, CSM ratios, NPS, CSAT, save plays, red accounts, CS-Sales handoff, churn autopsy, renewal discount governance, discount sunset, renewal pricing, or save plays with pricing components. Also trigger when someone says "we keep losing customers" or "our CS team is reactive" or "we have no idea which accounts will churn" or "discounts are expiring and customers are pushing back" or "renewal price increase resistance."

  Reaches the webInstructions only3,138 words
• data-enrichment

  B2B data enrichment strategy, provider evaluation, integration patterns, and quality management for revenue operations teams. Use when the user mentions data enrichment, lead enrichment, account enrichment, contact enrichment, ZoomInfo, HubSpot Data Platform, Apollo, Clay, Cognism, Lusha, enrichment automation, enrichment workflows, firmographic data, technographic data, intent data, data append, enrichment API, enrichment coverage, data freshness, enrichment quality, or third-party data providers. Also trigger on 'our data is incomplete,' 'leads come in with no company info,' 'we need better data on our accounts,' 'enrichment isn't working,' or 'which enrichment tool should we use.' BOUNDARY: Covers enrichment STRATEGY, PROVIDER SELECTION, and INTEGRATION. For CRM-specific implementation, see revops-hubspot or revops-salesforce. For data governance, see revops-data-governance. For lead scoring that uses enriched data, see marketing-operations.

  Reaches the webInstructions only2,507 words
• deal-desk-operations

  Deal desk as a RevOps-owned function: when to stand one up, approval matrix design, discount governance and non-standard terms, quote review workflows, pricing economics for consumption and outcome-based deals, renewal negotiation governance, and maturity progression from ad-hoc approvals to strategic desk. Use when the user mentions deal desk, approval matrix, discount governance, quote SLAs, non-standard terms, pricing exceptions, deal desk ROI, approval velocity, discount leakage, or centralizing deal approval authority. Also trigger on "our reps have too much authority", "discounts are all over the place", "deals are stalled in approval", "we need guardrails on pricing", "custom pricing is a bottleneck", or "how do we control margin erosion".

  Reaches the webInstructions only2,803 words
• deal-qualification-gates

  Install evidence-gated qualification on a live pipeline: score the QUALITY of evidence behind every deal (1-5 per qualification dimension), set minimum scores per stage, and enforce qualify-or-kill at each gate. Triggers on 'zombie deals,' 'pipeline is full of junk,' 'is this deal real,' 'qualify or kill,' 'deals stall at proposal,' 'forecast built on hope,' 'reps say every deal is closing,' 'stage criteria,' 'exit criteria,' 'MEDDIC scoring,' 'SPICED scoring,' 'qualification framework rollout,' or any situation where deals advance on rep optimism instead of buyer evidence. Works with SPICED by default and maps to MEDDICC or BANT. BOUNDARY: icp-builder owns ACCOUNT-level fit (is this the right company) and carries a summary of these gates as its pipeline-enforcement step; this skill is the full deal-level operating system (is this deal real). deal-velocity-engineer treats slow deals as a speed problem; this skill treats false deals as a truth problem, and it runs first, because accelerating an unqualified deal just produces a faster loss. Weekly pipeline reviews (e.g. pipeline-review) consume the scores this skill produces; they read the dashboard, this skill builds the engine under it.

  Self-containedInstructions only1,122 words
• deal-velocity-engineer

  Diagnose and fix deal velocity problems. Sales cycle diagnostics, stage exit criteria, pipeline deflation, zombie deal elimination, multi-threading, mutual action plans, AI-driven deal scoring, revenue intelligence integration (Gong/Chorus), and compression tactics with sourced benchmarks. Trigger on 'deal velocity,' 'sales cycle too long,' 'deals stalling,' 'pipeline velocity,' 'stage exit criteria,' 'zombie deals,' 'pipeline deflation,' 'deals stuck,' 'multi-threading,' 'mutual action plan,' 'deal inspection,' 'pipeline hygiene,' 'cycle time,' 'stage conversion,' 'deals die in negotiation,' 'we keep slipping deals,' 'reps can't close,' or 'pipeline is bloated but nothing closes.' Connects stage gates, deal scoring, inspection cadence, and pipeline deflation into the operating cadence. Includes modern AI/automation patterns (HubSpot Breeze, Salesforce Agentforce, predictive pipeline management). BOUNDARY: For forecast methodology see revops-forecasting. For pipeline visibility and dashboards see pipeline-visibility. For sales methodology (SPICED/MEDDPICC) see sales-methodology. For operating cadence see revenue-operating-cadence.

  Reaches the webInstructions only3,749 words
• expansion-revenue-architect

  Design and install expansion revenue systems improving NRR and GRR for B2B SaaS. GRR/NRR diagnostic, expansion motion architecture, whitespace analysis, CS-Sales handback, renewal pricing, and 90-day NRR programs. Trigger on 'NRR improvement,' 'GRR strategy,' 'expansion revenue,' 'upsell cross-sell,' 'whitespace analysis,' 'CS expansion,' 'net revenue retention,' 'right side of the bowtie,' 'land and expand,' 'expansion is accidental,' 'CS doesn't own revenue,' 'we keep discounting renewals,' 'health score,' 'time to value,' 'customer advocacy,' 'usage-based pricing NRR,' 'account penetration,' 'second-order revenue,' or 'CSM coverage model.' Also use when NRR below 110% or GRR below 90%. Designs full expansion engine connecting health scoring, signals, whitespace, CS-Sales handbacks, and dashboard tiles. BOUNDARY: For CS operations, see cs-operations. For pricing and consumption billing operations, see pricing-monetization-ops. For handoffs, see revops-handoffs.

  Reaches the webInstructions only2,989 words
• gtm-compensation

  GTM compensation plan design, quota setting, OTE structures, and benchmarking for B2B revenue teams. Use when the user mentions comp plans, OTE, on-target earnings, variable pay, commission structure, quota setting, accelerators, decelerators, SPIFs, clawbacks, sales compensation, SDR comp, AE comp, CSM comp, pay mix, commission rates, ramp periods, or comp plan modeling. Also trigger when someone asks about benchmarking GTM salaries, designing incentive structures, or fixing misaligned compensation. If someone says "how should I pay my reps" or "what's a fair OTE" or "our comp plan isn't working," activate this skill. BOUNDARY: Covers how to PAY people. For org design and capacity, see gtm-planning.

  Reaches the webInstructions only3,752 words
• gtm-data-architecture

  GTM data architecture for revenue operators who are not data engineers; warehouse-native and zero-copy patterns that have won in the market. Use when designing GTM data stacks, planning data transformation layers, evaluating CDP vendors, building identity resolution and unified customer intelligence, implementing reverse ETL (Hightouch or Census), or assessing data readiness for AI agents. Also trigger on "data architecture", "ELT vs ETL", "warehouse-native CDP", "composable CDP", "reverse ETL implementation", "dbt for RevOps", "unified health scores", "customer data platform strategy", or "data mesh for GTM". BOUNDARY: Covers architecture and transformation layers only. Handoff to revops-data-governance for CRM data quality and governance; to revops-tech-stack for vendor selection frameworks; to gtm-planning for strategy implications. This skill addresses the data layer for a RevOps team scaling AI adoption.

  Reaches the webInstructions only3,255 words
• gtm-planning

  Go-to-market planning, org design, territory design, and capacity planning for B2B revenue teams. Use when the user mentions GTM planning, go-to-market, GTM motion, territory design, org design, sales org, team structure, capacity planning, headcount model, hiring plan, ICP definition, PLG, product-led growth, sales-led, partner-led, channel strategy, named accounts, team ratios, SDR-to-AE ratio, or scaling the sales team. Also trigger when someone asks about entering a new market, redesigning territories, or planning next year's revenue org. If someone says "how should I structure my sales team" or "our territories don't make sense," activate this skill. BOUNDARY: Covers team STRUCTURE, territories, and capacity. For comp plans and quotas, see gtm-compensation. For ICP BUILDING methodology (GAP method, interviews, thresholds), see icp-builder.

  Reaches the webInstructions only3,829 words
• icp-builder

  Build, validate, or expand your ICP (Ideal Customer Profile) using the GAP method, SPICED framework, and customer interview pipeline. Triggers on 'build your ICP,' 'check your ICP,' 'ICP validation,' 'ICP quality,' 'you don't have an ICP,' 'ICP is too broad,' 'who should we sell to,' 'segment our market,' 'ICP workshop,' 'customer interviews for ICP,' 'GAP method,' 'ICP expansion,' 'Goldilocks zone,' 'tier our customers,' 'A/B/C segmentation,' 'are we targeting the right customers,' 'segmentation check,' 'ICP review,' 'who are we actually selling to,' 'score our accounts,' 'ICP scoring,' 'fit score,' 'TAM list,' 'target list,' 'build our market list,' or any situation where your ICP is missing, broken, or needs validation. This skill covers the full ICP lifecycle: validate what exists, build from scratch, score every company 0-100 on fit, produce and maintain the TAM list, refine with interviews, and plan expansion. BOUNDARY: For positioning/messaging (step AFTER ICP), see positioning-messaging-designer.

  Reaches the webInstructions only2,453 words
• lead-routing

  Lead routing strategy, assignment logic, round-robin patterns, territory design, speed-to-lead SLA frameworks, and routing automation for B2B revenue teams. Use when the user mentions lead routing, lead assignment, round-robin, territory assignment, lead distribution, speed-to-lead, lead SLA, lead queue, routing rules, routing logic, account-based routing, geographic routing, skills-based routing, load balancing, lead handoff, inbound lead routing, outbound lead routing, routing tools (LeanData, Chili Piper, Default), or lead cherry-picking. Also trigger on 'leads aren't getting to the right rep,' 'our routing is broken,' 'leads sit in a queue,' 'reps cherry-pick,' 'speed-to-lead is too slow,' or 'we need to redesign territories.' BOUNDARY: Covers routing STRATEGY and LOGIC (CRM-agnostic). For CRM-specific implementation, see revops-hubspot or revops-salesforce. For enrichment that feeds routing, see data-enrichment. For lead scoring, see marketing-operations.

  Reaches the webInstructions only2,800 words
• marketing-operations

  Marketing operations for B2B revenue teams: lead scoring, attribution, campaign tracking, and handoff protocols. Use when the user mentions marketing operations, marops, lead scoring, MQL definition, MQL to SQL handoff, lead routing, attribution modeling, multi-touch attribution, W-shaped attribution, marketing sourced pipeline, campaign operations, UTM taxonomy, demand gen ops, channel mix, marketing SLA, speed to lead, ICP fit scoring, SPICED lead scoring, ICP fit matrix, selection fit, urgency fit, qualification tier scoring, T1 T2 T3 leads, or ICP fit scoring. Also trigger when someone says "sales says our leads are garbage" or "we can't attribute revenue to campaigns." BOUNDARY: Covers marketing OPERATIONS (lead management, attribution, campaign ops). For HubSpot, see revops-hubspot. For funnel math, see revops-metrics. For ICP BUILDING methodology (GAP method, customer interviews), see icp-builder.

  Reaches the webInstructions only3,745 words
• operating-cadence-designer

  Design and install the operating cadence for your organization: the calendar that makes the revenue operating system real. Connects the strategy scorecard (strategy), the revenue dashboard (visibility), and weekly/monthly rituals (execution). Use whenever the user mentions 'operating cadence,' 'cadence design,' 'meeting architecture,' 'install the cadence,' 'ritual design,' 'revenue meetings,' '5P meetings,' 'breach rhythm,' 'WIP limits,' 'decision cadence,' 'signal trigger action,' 'decision rules,' or any engagement where meetings need restructuring. Also trigger on 'our meetings are status updates,' 'nobody makes decisions,' 'nothing gets done,' 'the board keeps getting surprised,' or 'we need a rhythm.' Also trigger on 'forecast calls,' 'pipeline review,' 'QBR,' 'board meeting,' 'board deck,' 'monthly business review,' 'sales standup,' or 'deal review.' BOUNDARY: For the revenue dashboard build itself, see pipeline-visibility.

  Reaches the webInstructions only3,929 words
• partner-channel-operations

  Partner and channel operations for B2B SaaS: program design, partner enablement, co-selling, deal registration, and ecosystem-led growth. Use when the user mentions partner program, channel strategy, partner enablement, co-sell, deal registration, partner onboarding, partner tiers, ecosystem-led growth, partner-sourced pipeline, partner health scoring, partner QBR, ideal partner profile, IPP, referral partners, resellers, VARs, implementation partners, GSIs, MSPs, partner portal, MDF, partner attribution, partner revenue, or partner operations. Also trigger when someone says 'we need partners to scale,' 'our partner program isn't producing,' 'how do we structure partner tiers,' 'partners aren't bringing deals,' or 'we want to build an ecosystem.' BOUNDARY: covers partner OPERATIONS (program design, enablement, pipeline, reporting). For GTM org design and capacity, see gtm-planning. For handoff design between partner and direct, see revops-handoffs. For HubSpot implementation, see revops-hubspot.

  Reaches the webInstructions only3,622 words
• partner-ecosystem-architect

  Design and install partner ecosystem strategies for your company using ecosystem-led growth (ELG) and nearbound methodology. Use when someone mentions 'partner strategy,' 'ecosystem-led growth,' 'nearbound,' 'partner ecosystem,' 'build a partner program,' 'co-selling strategy,' 'account mapping,' 'Crossbeam,' 'Reveal,' 'partner motion,' 'referral program,' or 'partner revenue.' Also trigger on 'we need partners to grow,' 'partner program isn't working,' or 'partners should be our next GTM motion.' Also trigger on 'Crossbeam Reveal,' 'Introw,' 'PRM tools,' 'partner tools,' 'cloud marketplace strategy,' 'partner benchmark,' or 'partner economics.' Designs partner strategy and architecture: why this partner type, why now, how it fits the system. BOUNDARY: For partner operational plumbing (deal registration, health scoring, CRM properties), see partner-channel-operations. For handoffs see revops-handoffs.

  Reaches the webInstructions only3,685 words
• pipeline-visibility

  Pipeline visibility, reporting architecture, dashboard design, pipeline hygiene, and forecast reporting for B2B revenue teams. CRM-agnostic patterns for any platform. Use when the user mentions pipeline visibility, pipeline reporting, sales dashboards, pipeline hygiene, stale deals, pipeline coverage, pipeline health, deal inspection, pipeline review, win rate reporting, conversion funnels, pipeline cleanup, pipeline scrub, forecast reporting, forecast accuracy tracking, big deal alerts, or pipeline quality score. Also trigger on 'we can't see our pipeline,' 'deals go stale,' 'pipeline reports are wrong,' 'we need better dashboards,' or 'how do we track pipeline health.' BOUNDARY: Covers pipeline VISIBILITY and REPORTING (CRM-agnostic). For CRM-specific implementation, see revops-hubspot or revops-salesforce. For forecast methodology, see revops-forecasting. For metrics, see revops-metrics.

  Reaches the webInstructions only3,219 words
• positioning-messaging-designer

  Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method. Use whenever you need to define your positioning, build a messaging framework, create a Use Case Canvas, or bridge the gap between ICP and copy. Triggers include 'position yourself,' 'messaging framework,' 'Use Case Canvas,' 'how should we position,' 'our messaging is all over the place,' 'we skip straight to copy,' 'Opposites method,' 'Old Way vs New Way,' 'positioning workshop,' 'value prop,' 'one-liner,' 'elevator pitch,' 'positioning line,' or any situation where you have an ICP but your messaging is missing or inconsistent. BOUNDARY: This skill designs POSITIONING and MESSAGING frameworks. For ICP building (the step BEFORE), see icp-builder. For writing actual LinkedIn copy, see a LinkedIn posting skill. For proposals, see a proposal generator skill.

  Reaches the webInstructions only2,951 words
• pricing-monetization-ops

  Pricing and monetization operations for B2B SaaS: designing, implementing, and operating consumption-based and outcome-based pricing models; metering architecture with deduplication and customer mapping; billing system integration for usage, overages, and variable revenue; hybrid contract structures (minimums, ramps, credits); monthly reconciliation and drift detection; revenue recognition for variable contracts; pricing-tier migrations from per-seat to usage without breaking revenue reporting; packaging changes and price increases across renewal cohorts; CPQ and billing platform selection; billing data quality audits. Use when discussing metering infrastructure, consumption billing, hybrid pricing models, variable revenue, price migrations, quote-to-cash consolidation, billing-grade data quality, or revenue reconciliation. Trigger phrases: metering, deduplication, usage billing, consumption pricing, hybrid pricing, price migration, overages, minimums, CPQ platform, billing reconciliation, variable revenue, outcome-based pricing. Also triggers on "we need to move from per-seat to usage," "our billing system can't handle variable revenue," "revenue recognition is a nightmare," or "we're losing customers on bill shock."

  Reaches the webInstructions only4,789 words
• qbr-ebr-builder

  Design and build customer business reviews that buyers actually attend: QBR (operational cadence) and EBR (executive cadence), with the value recap in the customer's own numbers as the load-bearing artifact. Triggers on 'QBR,' 'EBR,' 'business review,' 'executive business review,' 'quarterly review deck,' 'prove value to the customer,' 'renewal conversation prep,' 'customer stopped attending reviews,' 'our QBRs are a feature parade,' 'success plan review,' or any situation where post-sale value needs to be demonstrated to the people who pay, not just the people who use. BOUNDARY: account-health-audit and customer-health scanners produce the internal diagnostic BEFORE the review; this skill builds the customer-facing instrument itself and starts from their output. renewal-save-motion owns the intervention when a review surfaces risk; expansion-revenue-architect and expansion-opportunity-analysis own the motion when it surfaces headroom; this skill hands off to both and runs neither. revenue-operating-cadence owns INTERNAL meeting architecture; a business review is a customer-facing meeting and follows different rules: their agenda, their numbers, their next quarter.

  Self-containedInstructions only1,247 words
• renewal-save-motion

  Run the defensive counterpart to expansion: a structured save motion for at-risk customers and a renewal runbook that starts at T-120, not the week the contract ends. Triggers on 'renewal at risk,' 'customer went quiet,' 'churn save,' 'save play,' 'they stopped using the product,' 'champion left the account,' 'renewal coming up,' 'GRR is slipping,' 'downgrade request,' 'cancellation notice,' 'win the renewal,' or any situation where a health signal fired and the team's only play is a discount and a prayer. Entry condition: a risk flag already exists (from a health scan, usage drop, champion departure, or a blocked expansion attempt). BOUNDARY: customer-health scanners (e.g. customer-health, account-health-audit) DETECT risk across the base; this skill executes the intervention on one flagged account, starting where their output ends. expansion-opportunity- analysis is the offense on healthy accounts; the two are mutually exclusive on the same account at the same time, and its no-activity hard gate is precisely the handoff INTO this skill. cs-operations owns the full CS org design (segmentation, staffing, QBR cadence); this skill is one motion inside that system, not the system.

  Self-containedInstructions only1,129 words
• revenue-operating-cadence

  Revenue operating cadence: meeting architecture, data pyramid, and board reporting that turns strategy into execution. Use when the user mentions operating cadence, meeting cadence, forecast calls, pipeline review, QBR, board meeting, board deck, monthly business review, sales standup, deal review, meeting architecture, meeting agenda, revenue ceremonies, or structuring revenue meetings. Also trigger when someone asks about board deck structure, running forecast calls, fixing meetings that waste time, or getting accountability. If someone says "our meetings are status updates" or "the board keeps getting surprised" or "nothing gets done," activate this skill. BOUNDARY: Covers meeting structure and data inputs. For forecast methodology, see revops-forecasting. For metrics, see revops-metrics.

  Reaches the webInstructions only3,729 words
• revops-change-management

  Revenue change management: plan change, design enablement, make it stick, measure adoption. Trigger on change management, enablement design, adoption failure, rollout plan, communication plan, stakeholder management, training that doesn't stick, behavior change, coaching program, process change, system migration, comp plan change, territory change, Kotter, ADKAR, spaced repetition, forgetting curve, reverse salient, traffic light model, Bloom's taxonomy, "nobody follows the new process," "we trained them but nothing changed," "the tool is built but nobody uses it," "how do we get buy-in," "people are pushing back," AI change management, FOBO, shadow AI, AI adoption, works council AI, AI governance framework, AI rollout, or fear of becoming obsolete. BOUNDARY: For HubSpot adoption, see revops-hubspot. For GTM org change, see gtm-planning.

  Reaches the webInstructions only3,943 words
• revops-crisis

  Revenue crisis triage and emergency response when multiple systems break simultaneously. Use this skill when the user describes a CRISIS state: forecast missed for multiple quarters, win rate collapsing, pipeline coverage below 2.8x and falling, NRR crashed below 90%, multiple simultaneous system failures, loss of trust between functions, data that cannot be trusted, or scenarios like "everything is broken," "forecast is ±30% wrong," "we are losing deals we should win," "I cannot trust our data," "sales blames marketing blames product," "three quarters in a row we missed," "board is panicking," or "we need to save this quarter." Also trigger on "we need emergency triage," "nothing is working," "where do we even start," or "we are in firefighting mode." BOUNDARY: This is emergency response (what to fix FIRST when everything is broken). For detailed methodology after stabilization, see revops-diagnostic and revops-four-capability-maturity-assessment. For specific domain fixes, see the relevant domain skill.

  Reaches the webInstructions only3,179 words
• 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.

  Reaches the webInstructions only3,835 words
• 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.

  Reaches the webInstructions only5,034 words
• 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.

  Reaches the webInstructions only2,669 words
• 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.

  Reaches the webInstructions only1,869 words
• 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 icp-builder. For lead routing rules and assignment logic, see lead-routing (which defers to this skill for CRM-specific implementation). For reporting, dashboards, and pipeline visibility, see pipeline-visibility.

  Reaches the webInstructions only3,355 words
• 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.

  Reaches the webInstructions only4,792 words
• revops-org-chart

  RevOps team org design, role structure, and hiring sequencing by company size and ARR stage. Use this skill when you need to structure your RevOps team, determine hiring order, design a business partner vs. center-of-excellence model, decide when to engage a Systems Architect (FTE, fractional, or advisory), evolve a CRM or automation team toward RevOps, define who RevOps should report to, establish a mandate or charter, choose centralized vs. embedded vs. hub-and-spoke model, design multi-BU or multi-instance team structures, or build agencies into your RevOps strategy without creating dependency. Also use when you have Business Partners and are considering adding an Architect role. Includes frameworks from RevOps Co-op, Revenue Wizards, Hyperscayle, Go Nimbly, Maxio, Leanlayer, Stage2 Capital, and practice-based hiring guides.

  Reaches the webInstructions only2,943 words
• revops-revenue-planning

  Annual and quarterly revenue plan construction, top-down vs bottoms-up reconciliation, plan versioning, stretch goal handling, and FP&A-RevOps collaboration for B2B revenue teams. Use when the user mentions annual planning, revenue targets, capacity planning, planning calendar, stretch goals, plan versions, plan of record, reforecasting triggers, FP&A collaboration, or revenue reconciliation. Also trigger on "we need to build our plan", "our forecast and budget don't align", "how do we set targets", "what's our plan of record", "we got a stretch from finance", "when should we start planning", or "we need to reforecast". BOUNDARY: Covers plan construction, versioning, and reconciliation. For in-quarter/weekly forecasting mechanics, see revops-forecasting. For GTM structure and capacity mechanics, see gtm-planning. For compensation and quotas, see gtm-compensation.

  Reaches the webInstructions only3,746 words
• 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.

  Reaches the webInstructions only1,464 words
• revops-strategy

  Revenue operations strategy, pipeline architecture, and strategic advisory for building your B2B company's revenue engine. Use this skill when you mention 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 you need help framing a strategic response 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 icp-builder. For CRM implementation, see revops-hubspot.

  Reaches the webInstructions only4,217 words
• revops-tech-stack

  Revenue technology stack architecture, value engineering, platform evaluation, and capability mapping for B2B GTM teams. Use when the user mentions tech stack, martech stack, sales tech, CRM evaluation, platform selection, tool consolidation, stack audit, build vs buy, integration architecture, composability, iPaaS, CDP, MAP, sales engagement platform, AI tools for GTM, AI maturity, AI orchestration, AI agents, knowledge layer, semantic retrieval, RAG stack, vector database, EU AI stack, GDPR AI tools, knowledge management platform, Glean, Langdock, Weaviate, Qdrant, Pinecone, LlamaIndex, LangChain, Dust.tt, Guru, or Notion AI. Also trigger on "we have too many tools," "our tools don't talk to each other," "should we buy X or build it," "where should our knowledge live," or "how do we give AI access to our internal docs." BOUNDARY: Covers TECHNOLOGY evaluation and architecture. For strategy framing, see revops-strategy. For HubSpot, see revops-hubspot. For data governance, see revops-data-governance.

  Reaches the webInstructions only4,241 words
• 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 icp-builder. For discount governance policy see deal-desk-operations.

  Reaches the webInstructions only6,703 words