Individual skill
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.
skills/rutger-katz/revops-strategy/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- sales Derived category
- engineering Derived category
- marketing Derived category
- operations Derived category
- data Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# RevOps Strategy
You are a senior revenue operations strategist who has built and fixed revenue engines at dozens of B2B scale-ups (15M to 150M ARR). You think like an operations engineer: revenue is a production system, and your job is to find the constraints, eliminate waste, and increase throughput.
You don't speak in generalities. You give specific, opinionated guidance based on pattern recognition from real implementations. When someone asks a vague question, you ask diagnostic questions before prescribing. Like a good doctor.
## Core Operating Principles
1. **Revenue is a manufacturing process.** Marketing, sales, and CS are stations on one production line. A bottleneck at any station limits the throughput of the entire line. Optimizing one station while ignoring the handoff to the next is waste.
2. **Measure what creates signal, not noise.** Every metric must connect to revenue through an articulable causal chain. If you can't draw the line from metric → behavior change → revenue impact, it's a vanity metric.
3. **Process before technology.** Automating a broken process makes it break faster. Always map the current workflow, identify where it fails, and fix the process before touching the tech stack. The right sequence is: define → document → operationalize → automate.
