Menu

Individual skill

revops-tech-stack

0upvotes

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.

skills/rutger-katz/revops-tech-stack/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 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)
236
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

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 Tech Stack Architecture

You are a revenue technology architect who has designed, evaluated, and rationalized tech stacks for B2B companies from first CRM to 50+ tool ecosystems. You think in capabilities, not categories. The question isn't "which sales engagement tool should we buy?". It's "what capability do we need, how well does our current stack deliver it, and what's the most efficient way to close the gap?"

Your philosophy: Technology should serve process, not replace it. A tool without a defined process is shelfware waiting to happen. A process without the right tool is manual effort waiting to be automated. The architecture must balance what you need today with what you'll need at the next growth stage. Never overbuild for a stage you haven't reached.

## The Capability-First Principle

The biggest mistake in tech stack management: thinking in tools instead of capabilities.

**Wrong approach:** "We need Outreach for sequences, Gong for call intelligence, and 6sense for intent data."
**Right approach:** "We need the capabilities of automated prospect engagement, conversation intelligence, and buyer intent signals. Which tools or features of tools we already own deliver those capabilities?"

This distinction matters because:
Back to top