GitHub Contribute

Back to the library

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

78% of companies are using AI. Only 5% see substantial returns. The gap is the foundation. Rutger helps B2B scale-ups (€15–150M) build AI-ready revenue systems — diagnostics first, then the operating system: forecasting, pipeline architecture, handoffs, and the tooling to run it.

28 skills · 0 installs

Skills by Rutger

RevOps0

Customer success 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."

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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, Clearbit, 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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Deal velocity engineering

Diagnose and fix deal velocity problems. Sales cycle diagnostics, stage exit criteria, pipeline deflation, zombie deal elimination, multi-threading, mutual action plans, 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. 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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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 programmes. 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, see pricing-strategy. For handoffs, see revops-handoffs.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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 neon-icp.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

HubSpot implementation for RevOps

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

ICP builder

Build, validate, or expand a client's ICP (Ideal Customer Profile) using the GAP method, SPICED framework, and customer interview pipeline. Triggers on 'build their ICP,' 'check their ICP,' 'ICP validation,' 'ICP quality,' 'they don't have an ICP,' 'ICP is too broad,' 'who should they sell to,' 'segment their market,' 'ICP workshop,' 'customer interviews for ICP,' 'GAP method,' 'ICP expansion,' 'Goldilocks zone,' 'tier their customers,' 'A/B/C segmentation,' 'are they targeting the right customers,' 'segmentation check,' 'ICP review,' 'who are they actually selling to,' or any client engagement where the ICP is missing, broken, or needs validation. This skill covers the full ICP lifecycle: validate what exists, build from scratch, refine with interviews, and plan expansion. BOUNDARY: For positioning/messaging (step AFTER ICP), see positioning-messaging-designer.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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 neon-icp.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Operating cadence designer

Design and install the operating cadence for a client — 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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Positioning and messaging designer

Design positioning and messaging frameworks for clients using the Use Case Messaging Canvas and Opposites method. Use whenever helping a client define their positioning, build a messaging framework, create a Use Case Canvas, or bridge the gap between ICP and copy. Triggers include 'position them,' 'messaging framework,' 'Use Case Canvas,' 'how should they position,' 'their messaging is all over the place,' 'they skip straight to copy,' 'Opposites method,' 'Old Way vs New Way,' 'positioning workshop,' 'value prop,' 'one-liner,' 'elevator pitch,' 'positioning line,' or any client engagement where ICP exists but 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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Revenue 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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Revenue 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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Revenue handoff operations

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," or "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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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, behaviour change, coaching programme, 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. For AI Readiness Day, see neon-ai-readiness-day.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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 3x and falling, NRR crashed below 90%, multiple simultaneous system failures, loss of trust between functions, data that can't be trusted, or scenarios like "everything is broken," "forecast is ±30% wrong," "we're losing deals we should win," "I can't 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're 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-maturity. For specific domain fixes, see the relevant domain skill.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

RevOps org chart and team design

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

RevOps strategy and pipeline architecture

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

Sales methodology implementation

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

RevOps0

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.

Rutger Katz

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems