RevOps1,071
Ido Goldberg
Co-Founder & CPO
Skillify
Turns useful work from the current conversation into a reusable org skill. Captures the trigger, outcome, procedure, and judgment so the play can be rerun.
RevOps
59 skills in RevOps.
RevOps1,067
Ido Goldberg
Co-Founder & CPO
Clear my desk
Triages pending Swan work for a user. Use to prioritize review items, sequence approvals, alerts, and suggestions into act-now, bulk-approve, acknowledge, or investigate buckets.
RevOps1,066
Ido Goldberg
Co-Founder & CPO
Audit Swan
Checks whether a Swan workspace is structurally healthy. Use for configuration audits that surface missing knowledge, disconnected integrations, exhausted senders, broken triggers, sparse CRM data, and credit or subscription issues.
RevOps785
Ido Goldberg
Co-Founder & CPO
Inbox zero
Triage a user inbox across email, Slack, LinkedIn, and Swan. Use for inbox sweeps where the agent should archive obvious noise, draft replies, and return a single summary of items needing attention.
RevOps27
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps26
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Expansion revenue architecture
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.
RevOps26
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
GTM compensation design
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.
RevOps26
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
GTM planning and org design
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.
RevOps24
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps24
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Partner ecosystem architect
Design and install partner ecosystem strategies for B2B SaaS clients using ecosystem-led growth (ELG) and nearbound methodology. Use when someone mentions 'partner strategy,' 'ecosystem-led growth,' 'nearbound,' 'partner ecosystem,' 'build a partner programme,' 'co-selling strategy,' 'account mapping,' 'Crossbeam,' 'Reveal,' 'partner motion,' 'referral programme,' or 'partner revenue.' Also trigger on 'we need partners to grow,' 'partner programme 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.
RevOps24
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Revenue performance 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.
RevOps24
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps24
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
CRM migration and consolidation
CRM migration, instance consolidation, and post-merger integration for B2B revenue teams; system-of-record design; deduplication and identity resolution; data harmonisation 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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Forecast accuracy recovery
Use this skill when the forecast is consistently wrong: over-forecasting, missed quarter-ends, deals slipping unexpectedly. Installs category-based forecasting (Commit, Best Case, Upside), multi-method triangulation combining stage-weighted and historical views, and forecast accuracy diagnostics with benchmarks. Produces a repeatable forecast cadence, the red flags to inspect in forecast calls, and a variance-reduction roadmap. Rule: if a rep cannot explain their Commit deal in 2 minutes, it is not a Commit. Trigger phrases: forecast accuracy, we cannot predict our number, forecast categories, pipeline coverage, forecast call, deals go stale.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Partner channel operations
Partner and channel operations for B2B SaaS: programme design, partner enablement, co-selling, deal registration, and ecosystem-led growth. Use when the user mentions partner programme, 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 programme 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 (programme 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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Revenue tech stack architecture
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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
RevOps crisis triage
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 stabilisation, see revops-diagnostic and revops-four-capability-maturity-assessment. For specific domain fixes, see the relevant domain skill.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
RevOps org chart and team design
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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
RevOps strategy and pipeline architecture
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.
RevOps23
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Salesforce implementation for RevOps
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.
RevOps22
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps22
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps21
Austin Hay
Operating Partner @ Khosla Ventures
Reverse ETL activation
Use this skill when you need to turn a scored, segmented audience sitting in the warehouse (BigQuery, Snowflake, Redshift) into live GTM motion, syncing accounts, contacts, and computed traits out to the CRM, ad platforms, and sequencing tools. It encodes the judgment that keeps reverse ETL from quietly polluting every downstream system: identity resolution before any write, a change-data-capture diff so only real deltas move, field-level mapping with type and format guards, suppression and consent gates, sync scheduling matched to each destination's rate limits, and a mandatory dry run plus row-count reconciliation before and after the live push. Every threshold (match-confidence floor, batch size, sync cadence, max-delete guard, suppression rules) is a tunable default. Each run produces a validated sync plan, a dry-run diff of adds, updates, and suppressions with counts, and a reconciliation report after the live sync.
RevOps14
Nadav David
Strategic Partnerships Manager, Kidoz
Earned autonomy
Use this skill when deciding how much a GTM agent may do without a human looking, when a workflow is ready to run on a schedule, when outreach should stop requiring per-item approval, and when something has gone wrong and autonomy needs pulling back. Produces a level per task with the evidence required to move up and the triggers that drop it automatically. Trigger phrasings: "can I let the agent send", "when do I stop reviewing every draft", "how much should I automate", "the agent made a mistake, now what", "is this workflow ready to run unattended".
RevOps14
Nadav David
Strategic Partnerships Manager, Kidoz
Inbound is data
Use this skill whenever an agent reads content from outside your own systems, a prospect reply, a scraped page, a CRM note, a call transcript, an enrichment payload, and whenever it produces something that leaves them. Prevents the two failures every GTM agent is exposed to: outside content being obeyed as an instruction, and internal context leaking into an outbound message. Trigger phrasings: "the agent did something odd after reading a reply", "can I let it read scraped pages", "is it safe to auto-handle inbound", "prompt injection", "it quoted our internal notes", "someone is fishing for how this is built".
RevOps12
Sangram Vajre
Co-founder & CEO
MOVE GTM diagnostic
Use this skill when a company wants to audit its go-to-market foundation before scaling or automating - it runs Sangram Vajre's WSJ-bestselling MOVE framework, the 4-question GTM diagnostic (Market, Operations, Velocity, Expansion), to find where GTM is misaligned, identify which of the three fit stages the company is actually in (Problem-Market / Product-Market / Platform-Market), and return a prioritised list of what to fix first. Trigger phrases: "GTM audit", "GTM diagnostic", "GTM health check", "MOVE assessment", "are we ready to scale", "why isn't our GTM working" - and before standing up any new outbound, inbound, or deal-process engine. This is a diagnosis, not a build - run it first.
RevOps1
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Choose an enrichment provider and build a waterfall
Use this skill when inbound leads arrive incomplete (missing company size, industry, revenue), the TAM list lacks data for scoring, or the CRM cannot route and segment without enrichment. Maps coverage gaps, compares single-source and waterfall provider strategies, and builds an integration roadmap with cost guardrails and quality gates. Produces a provider recommendation matrix, a waterfall architecture, and a go or no-go checklist. Rule: no single provider has full coverage; a waterfall across two or more providers in sequence beats any one source on match rate. Trigger phrases: data enrichment, leads come in with no company info, enrichment coverage, firmographic data, which enrichment tool, data freshness.
RevOps1
Gali Firon
Sales & Marketing Coordinator, Kidoz Inc.
GTM command center
Use this skill when a GTM operator is losing time hopping between tools to see their own work - the task board in one tab, the outreach queue in another, research in a third, the content calendar in a fourth. Produces one personal operating surface that aggregates those lanes, plus a single daily "what needs me now" roll-up. Reach for it when someone says "I'm drowning in tabs", "I need one place to work from", "build me a dashboard", "a command center", "a morning operating view", or "I keep missing things across my tools".
RevOps1
Sam Jacobs
Founder & CEO @ Pavilion
Profitable efficient growth
Use this skill when a founder, revenue leader, CFO, or RevOps team is heading into annual planning, a board meeting, or a fundraise; is debating whether to pour more fuel on acquisition or fix the model first; needs a reality check on a 'growth at any cost' reflex; or asks anything about unit economics, CAC payback, NRR, burn multiple, Rule of 40, magic number, growth efficiency, or GTM budget allocation — even if they never say the word 'scorecard'. Builds a board-ready Profitable Efficient Growth (PEG) scorecard: computes the unit-economics picture from the company's own numbers, grades each metric against Sam Jacobs' PEG benchmarks, diagnoses whether the engine is scale-ready or leaking into a cash trap, and recommends how to allocate the next dollar of GTM spend using the 60/30/10 tranche strategy.
RevOps1
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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 DETECT risk across the base; this skill executes the intervention on one flagged account, starting where their output ends. Expansion analysis is the offense on healthy accounts; the two are mutually exclusive on the same account at the same time, and an expansion attempt blocked on inactivity 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.
RevOps0
Gerrit Kesten
Co-Founder, job.rocks
Acquired-brand GTM integration
Use this skill immediately after acquiring a product or brand, before combining websites, customer data, pipelines, messaging, analytics, or campaigns. Produces a staged GTM integration plan that preserves active demand and customer access while defining what to retain, endorse, consolidate, or retire.
RevOps0
Roman Palii
Founder
Audit the base, not the rate
Use this skill when a percentage in a commercial term is being set, questioned, or is producing a number nobody expected — sales commission, revenue share, affiliate and creator payouts, channel margin, agency fees, referral fees, rebates. Triggers: "reps are hitting quota but margin isn't moving", "what does this promo actually cost us", "our partner payouts are higher than the model", "is 15% a fair rate", "we're renegotiating the split", "the comp plan is paying out on deals we lost money on". It finds what the percentage multiplies, identifies the condition under which that choice starts to matter, quantifies the gap at that condition, and identifies the clause to revisit.
RevOps0
Tanyo Gochev
Co-Founder & Head of GTM, The Demand Department
Campaign benchmarking
Use this skill when someone needs to know whether a campaign's numbers are actually good — before setting targets for a launch, when reporting performance to someone who needs context rather than raw figures, or when comparing across clients, segments, and time periods. Produces a verdict with the comparison layer named, plus what to do about it. Trigger phrasings: "is this reply rate good", "what should we expect", "set targets for this campaign", "how do we compare", "benchmark this", "our numbers dropped", "is 3% good", "what's a normal reply rate".
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Consumption billing and revenue operations
Use this skill when bill shock is killing renewal cohorts, a consumption model breaks revenue recognition, or metering and billing are out of sync. Builds the operational layers: metering (ingestion, deduplication, customer mapping), rating and pricing engines (tiers, overages, minimums, credits), invoicing with audit trails, collections logic, and revenue reconciliation for variable contracts. Produces a data-quality audit of metering leaks, a quote-to-cash integration map, a per-seat-to-usage migration plan that does not break revenue reporting, and an ASC 606 compliance checklist. Rule: consumption pricing is only as good as its metering, billing and reconciliation plumbing; one broken layer breaks them all. Trigger phrases: usage billing, bill shock, metering, price migration, overages, billing reconciliation, variable revenue.
RevOps0
Udi Cohen
Director of Revenue Operations
Data quality
Verify, enrich, and clean any contact or account list against Lusha's verified B2B database. Checks emails, refreshes titles, fills missing direct dials, enriches firmographics, and flags duplicates and unverifiable records. Returns a clean list with a data quality summary showing exactly what was fixed and why. Requires a Lusha connection.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Design HubSpot for revenue operations
Use this skill when CRM architecture breaks revenue clarity: lifecycle stages that do not match the funnel, unmaintainable properties, reporting that needs three spreadsheets. Covers object model design, lifecycle architecture, property governance, pipeline configuration, automation patterns, and reporting structure for HubSpot. Produces a documented architecture with stage definitions, property naming standards, workflow specs, and a revenue-decision-focused dashboard roadmap. Rule: design for reporting first; if you cannot name the report a property feeds, do not create it. Trigger phrases: HubSpot setup, lifecycle stages, messy HubSpot instance, deal pipelines, HubSpot reporting, CRM architecture.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Design revenue handoffs
Use this skill when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns what sales committed. Designs handoff protocols across the full revenue bow-tie (marketing to sales, sales to customer, customer to expansion) with speed-to-lead SLAs, context-packet architecture, ownership models, and leading indicators of failure. Produces handoff playbooks per transition, context templates, SLAs with measurement dashboards, and detection rules for leaking revenue. Rule: handoffs are where revenue leaks. Trigger phrases: leads fall through the cracks, closed-won handoff, CS-to-sales handback, speed-to-lead, SLA between teams, nobody owns expansion.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Discount governance and approval system
Use this skill when reps hold too much pricing authority, discounts spiral by region, or approval bottlenecks stall deals. Builds the approval matrix by discount depth and deal size, SLA-backed quote workflows, and strategic override lanes that separate noise from genuine exceptions. Produces a matrix routing small discounts to reps, large discounts to leadership and non-standard terms to the deal desk, a three-stage quote process with 24 to 48 hour SLAs, and a 30-day audit loop on exceptions. Rule: if a rep can approve a discount without understanding the margin impact, the approval matrix is too loose. Trigger phrases: discount governance, approval matrix, pricing exceptions, deals stalled in approval, margin erosion, quote SLAs.
RevOps0
Tanyo Gochev
Co-Founder & Head of GTM, The Demand Department
Email sequence
Use this skill when designing or fixing an automated multi-email flow for people who already know you — welcome and onboarding series, lead nurture, trial conversion, re-engagement, post-purchase, or any behaviour-triggered drip. Produces the sequence spec: entry trigger, touch count, timing, per-email job, exit conditions, and what to measure. Trigger phrasings: "email sequence", "drip campaign", "nurture flow", "welcome series", "onboarding emails", "re-engagement emails", "lifecycle emails", "what emails should we send", "our nurture isn't converting".
RevOps0
Nylan Richard
AI Expert in Residence @ FullEnrich
Enrich a contact file without corrupting it
Use this skill when a user uploads a CSV or spreadsheet of contacts and wants verified work emails, phone numbers, or professional fields appended at scale. Produces a cleaned input, confirmed field mapping, bounded enrichment run, non-destructive merge, quality report, and export that preserves every original row and value.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Fix your CRM data chaos
Use this skill when CRM reports do not match, fields are a mess, hundreds of properties sit unused, or nobody trusts the data. Builds a data model mapped to the customer journey, designs field naming conventions and governance, sets up quality scorecards (completeness, accuracy, consistency, timeliness), and audits integrations to stop data rot. Produces a data dictionary, a field governance process with create and deprecate workflows, and quarterly quality targets. Rule: if a field has no documented owner and no documented use case, delete it. Trigger phrases: our reports do not match, our CRM is a mess, data quality, system of record, deduplication, field governance.
RevOps0
Ryan Iyengar
CEO & Founder, Full Stack GTM
Governed CRM cleanup
Use this skill when CRM data is unreliable, a cleanup is overdue, or a team is considering a bulk correction. Produces an evidence-backed audit, a reviewable change plan, approved corrections, and controls that prevent the same defects from returning.
RevOps0
Udi Cohen
Director of Revenue Operations
ICP score and route
Score any lead or account against your ICP criteria, verify key contacts via Lusha, and return a routing recommendation — AE, SDR, or nurture — with a confidence level and the specific data points that drove the decision. Runs on a single lead or across a full list in one pass. Requires a Lusha connection.
RevOps0
Eliezer Cohen
Head of Global Sales & Partnerships, GoPerfect
Leaked demand recovery
Use this skill when demand may have leaked between systems: a chat or form lead who never completed a booking, a demo request with no meeting, a call held with no follow-up sent, an inbound reply never answered, a trial that ended quietly, a deal closed lost on a blocker that has since changed. Produces a list of confirmed drops with the evidence attached and one drafted recovery message each, queued for a human to send. Fires on "did they ever book", "who fell through the cracks", "what did we drop", "who never got a follow-up", "unworked inbound", "leads that went nowhere", "recover lost inbound", and before any re-engagement send.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Onboarding to first value
Design customer onboarding as an activation system. Use when customers sign and stall, go-live takes months, or the gap between signed and successful is where accounts quietly die. Carries the why-they-bought evidence across the signature, drives to first realized value on a clock, detects stalls while they are cheap, and graduates accounts into steady state with a value baseline installed. Produces an activation definition, a milestone plan with a stall protocol, and the value baseline every later business review measures against. Rule: onboarding ends at first realized value, not at go-live. Trigger phrases: customer onboarding, time to value, activation, implementation drags, customers sign and stall, onboarding handoff.
RevOps0
Tanyo Gochev
Co-Founder & Head of GTM, The Demand Department
Outbound performance diagnosis
Use this skill when an outbound campaign is underperforming and the cause isn't obvious — replies dropped, meetings dried up, a sequence that worked stopped working, or the numbers look fine but nothing closes. Works through the funnel in fixed order so the real leak gets fixed instead of the most visible one. Produces the diagnosis, the evidence for it, and the single next fix. Trigger phrasings: "why did our reply rate drop", "campaign isn't working", "diagnose this campaign", "opens are fine but no replies", "replies but no meetings", "should we change the copy", "our sequence stopped working".
RevOps0
Udi Cohen
Director of Revenue Operations
Pipeline signal review
Run a full signal check across every open deal in a pipeline. Takes a deal list with account names and stages. Returns a risk-ranked brief — stale contacts, missing buying group coverage, signal gaps, and a recommended next action for every deal that needs attention. Requires a Lusha connection.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
QBR and 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 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 owns 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.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Red account rescue
Save churning customers through proactive health scoring and recovery plays. Use when red accounts pile up unpredictably, renewal conversations turn contentious, or expansion-ready accounts slip away. Builds a 5-dimension health score (product usage, relationship quality, support friction, commercial trends, outcomes) updated weekly, triages red accounts into rescue mode or renewal-risk mode, and activates save plays with executive sponsorship, backed by the full post-sale operating model (onboarding, QBRs, CS-Sales handoffs, renewal governance). Produces a weekly red-account triage list and recovery playbooks by churn cause. Rule: a customer does not turn red on one signal; red means 3 or more health dimensions breaking at once. Trigger phrases: we keep losing customers, red accounts, health scoring, save play, churn autopsy, renewal price increase resistance.
RevOps0
Ryan Iyengar
CEO & Founder, Full Stack GTM
Resolve before creating CRM records
Use this skill before importing, enriching, or manually creating contacts and accounts in a CRM. Produces a create, link, review, or reject decision that prevents duplicates while preserving uncertain matches for human resolution.
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
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.
RevOps0
Tanyo Gochev
Co-Founder & Head of GTM, The Demand Department
SaaS lifecycle programs
Use this skill when a subscription product's messaging needs to be designed, audited, or rebuilt across the whole customer journey — activation, onboarding, trial conversion, adoption, retention, expansion, failed-payment recovery, and win-back. Produces either a findings report ranked by leverage, or a staged build roadmap with the trigger, touches, and data prerequisites for each program. Trigger phrasings: "design our lifecycle", "why are we churning", "review our lifecycle emails", "trial conversion is low", "build a win-back flow", "dunning", "onboarding emails", "our activation rate is bad", "where do we start with lifecycle".
RevOps0
Rutger Katz
Founder @ Neon Triforce — AI-Ready Revenue Systems
Sales cycle compression
Compress sales cycles through stage-gate enforcement and pipeline deflation. Use when deals stall at specific stages, cycles exceed segment benchmarks, or zombie deals inflate the pipeline. Diagnoses the binding constraint (qualification, stage progression, or volume), builds stage exit criteria mapped to buyer actions rather than seller activities, and establishes zombie detection to deflate stale deals. Produces a velocity diagnostic with benchmarked targets and a stage-gate implementation blueprint. Rule: if a deal cannot advance without meeting stage exit criteria, the system is the constraint, not the rep. Trigger phrases: deal velocity, sales cycle too long, deals stalling, zombie deals, stage exit criteria, pipeline is bloated but nothing closes.
RevOps0
Ryan Iyengar
CEO & Founder, Full Stack GTM
Score CRM health over time
Use this skill when leaders need a repeatable measure of CRM reliability, its trend, and the defects driving it. Produces a deterministic health score, object- and rule-level diagnostics, a confidence statement, and a prioritized remediation queue.
RevOps0
Nylan Richard
AI Expert in Residence @ FullEnrich
Sync enriched contacts into a CRM safely
Use this skill when a user has an approved set of enriched contacts and wants to create or update CRM records without duplicates, silent overwrites, or ambiguous writes. Produces a schema-aware field map, duplicate decisions, an exact create-update-skip plan, an approval gate, and a reconciliation receipt for every attempted record.
RevOps0
Erwann Lefevre
Growth & GTM Engineer, La Growth Machine
Weekly performance advisor
Use this skill for the recurring review of a running outbound book — the Monday question of what needs attention this week. Produces a triaged list of replies waiting on an answer, the campaigns that are genuinely underperforming with the one step to fix on each, and week-over-week movement on the metrics that matter. Trigger phrasings: "how are my campaigns doing this week", "weekly outbound review", "my Monday cockpit", "campaign health at a glance", "who do I need to reply to", "which campaigns should I fix", "is my outbound trending up or down".