RevOps Vault

The operational GTM system of record

RevOps Vault scaffolds a fully structured Obsidian vault pre-configured for B2B revenue operations. Every Claude Code conversation starts with your business context loaded automatically: ICPs, personas, deal history, call transcripts, campaign data, and more.

MIT License Claude Code Obsidian 28 Slash Commands
28
Commands
18
Views
3
Agents
26
Templates
8
Hubs
2
Skills
GET STARTED VIEW ON GITHUB

THE PROBLEM

Why your GTM knowledge is broken

  • GTM knowledge lives in scattered docs, Slack threads, and people's heads. There is no single source of truth.
  • Every Claude conversation starts from scratch with zero business context, so you re-explain your ICP, deal stages, and processes every time.
  • Sales calls get logged but never connected to deals, personas, or pipeline. Insights stay trapped in individual notes.
  • RevOps teams spend more time finding information than acting on it. Context switching kills execution speed.

RevOps Vault turns Obsidian into a structured system of record for your entire revenue operation. Every document links to related documents through wiki-links, creating a navigable knowledge graph. Every AI interaction draws on your accumulated business context. Every command auto-links new content to what already exists.

WHAT YOU GET

Four pillars of revenue operations

01

Sales Intelligence

  • Call logging with auto-linking to deals, personas, and pipeline
  • Deal tracking with stale alerts and missing-info flags
  • Pipeline reports, win/loss analysis, and objection detection
  • Outbound sequence generation by persona and segment
  • Pre-call briefings assembled from accumulated vault context
02

Customer Success

  • Account health tracking with renewal timelines and risk scoring
  • Interaction logging for QBRs, onboarding, and support calls
  • Escalation tracking by severity, category, and resolution
  • Expansion pipeline for upsell and cross-sell opportunities
  • Sales-to-CS handoff with full context transfer
03

Marketing Operations

  • Campaign tracking across channels with performance metrics
  • Lead tracking with MQL/SQL qualification scoring
  • A/B test experiment tracking and statistical analysis
  • Event management with ROI tracking
  • Attribution analysis connecting campaigns to pipeline revenue
04

Cross-Functional

  • Full-funnel view from lead capture to closed-won to expansion
  • Vault health diagnostics with scoring and remediation
  • Weekly recaps aggregating all activity across departments
  • Draft/review/publish workflow for document governance
  • Lead qualification framework with configurable scoring

ALL 28 COMMANDS

Every slash command installed by /setup

01

Sales

/log-call Log a sales call with auto-linking to deals, personas, and pipeline
/prep-call Generate a pre-call briefing from accumulated vault context
/pipeline-report Pipeline summary with stale deal alerts and missing-info flags
/analyze-objections Cross-call objection pattern analysis with frequency and responses
/draft-sequence Generate persona-targeted outbound email sequences
/draft-content Draft LinkedIn posts or blog outlines from vault knowledge
/win-loss Closed deal pattern analysis across wins and losses
02

Customer Success

/log-interaction Log a CS interaction (QBR, onboarding, check-in, support)
/portfolio-report Account portfolio health summary with risk indicators
/prep-qbr Prepare QBR materials from account history and health metrics
/churn-analysis Identify churn risk patterns across the customer portfolio
/log-escalation Log a customer escalation with severity, category, and owner
/expansion-report Upsell and cross-sell pipeline with expansion opportunity scoring
/handoff-to-cs Sales-to-CS handoff with full context transfer and checklist
/feedback-analysis Analyze customer feedback for sentiment trends and themes
03

Marketing

/log-campaign Log a marketing campaign with channel, targeting, and budget
/campaign-report Campaign performance report with ROI and conversion metrics
/content-calendar Content pipeline and publishing calendar overview
/attribution-analysis Connect campaigns to pipeline revenue with attribution modeling
/log-lead Log a new lead with source, qualification criteria, and scoring
/analyze-tests A/B test analysis with statistical significance and recommendations
04

Cross-Functional

/new-draft Create a new draft document in the staging workflow
/submit-for-review Move a draft to the review queue for approval
/publish Promote a reviewed document to its canonical location
/weekly-recap Generate a weekly activity summary across all departments
/vault-health Diagnostic health check with scoring and remediation suggestions
/onboard Guided walkthrough for new team members learning the vault
/qualify-lead Score a lead against your ICP using configurable qualification criteria

Plus /setup, the interactive wizard that creates everything above.

QUICK START

From zero to a fully structured vault in minutes

Prerequisites

  • Claude Code CLI — npm install -g @anthropic-ai/claude-code
  • Obsidian — obsidian.md
  • Enable Bases core plugin in Obsidian (Settings > Core Plugins > Bases)
1

Create your vault folder

              $ mkdir ~/my-vault && cd ~/my-vault
2

Clone RevOps Vault

              $ git clone https://github.com/marawanaziz/revopsvault.git
3

Enter the directory

              $ cd revopsvault
4

Start Claude Code

              $ claude
5

Run the setup wizard

              > /setup

The wizard asks about your business, creates the full vault structure, installs all 28 commands, generates a CLAUDE.md tailored to your company, and deploys 18 database views.

6

Cleanup the clone

              $ cd .. && rm -rf revopsvault/
7

Start using your vault

              $ cd ~/my-vault && claude
> /log-call
> /pipeline-report
> /vault-health

HOW IT WORKS

Six building blocks that make the vault intelligent

CLAUDE.md

Every Claude Code session automatically reads CLAUDE.md from your vault root. This file contains your company profile, ICP definitions, deal stages, naming conventions, and folder structure. Claude starts every conversation already knowing your business.

Wiki-Links

Every document contains [[wiki-links]] to related documents. A call note links to its deal, the deal links to the persona, and the persona links to the ICP segment. Obsidian's Graph View renders these connections visually.

Commands

Slash commands do more than create files. They read existing vault content, auto-link new documents to related notes, enforce naming conventions, and maintain frontmatter consistency. The output is always a well-connected node in your knowledge graph.

Base Views

The 18 .base files are Obsidian Base configurations that query your vault via frontmatter properties. They render as filterable, sortable database views — like a CRM built from your markdown files.

Skills

Two skill modules teach Claude the vault's conventions (folder structure, naming patterns, frontmatter schemas) and GTM document standards (quality criteria, required sections, linking rules). Commands reference these skills to maintain consistency.

Agents

Three subagents handle structured data processing: transcripts become linked call notes, CS interactions become account-connected records, and campaign data becomes attributed pipeline entries.

VAULT STRUCTURE

What gets created when you run /setup 

your-vault/
├── CLAUDE.md                          # AI context, auto-loaded every session
├── HOME.md                            # Entry point with navigation to all hubs
│
├── hubs/                              # Dashboard notes linking everything
│   ├── business-context.md
│   ├── icp-and-personas.md
│   ├── sales-pipeline.md
│   ├── customer-success.md
│   ├── marketing.md
│   ├── automations.md
│   ├── deliverables.md
│   └── review-queue.md
│
├── company/                           # Business context and competitive intel
│   ├── overview.md
│   ├── team.md
│   ├── tech-stack.md
│   ├── pain-points.md
│   ├── metrics.md
│   └── competitors/
│
├── icp/                               # Customer profiles and segmentation
│   ├── personas/
│   └── segments/
│
├── sales/                             # Pipeline, calls, deals, sequences
│   ├── calls/
│   ├── deals/
│   └── sequences/
│
├── customer-success/                  # Post-sale operations
│   ├── accounts/
│   ├── interactions/
│   ├── playbooks/
│   ├── escalations/
│   ├── expansion/
│   └── feedback/
│
├── marketing/                         # Campaigns, content, leads, experiments
│   ├── campaigns/
│   ├── content/
│   ├── leads/
│   ├── experiments/
│   └── events/
│
├── automations/                       # Workflow specs
├── deliverables/                      # Reports, proposals
│   └── proposals/
├── meetings/                          # Internal sync notes
│
├── bases/                             # 18 Obsidian Base database views
│   ├── pipeline-tracker.base
│   ├── call-log.base
│   ├── account-health.base
│   └── ... (15 more)
│
├── _drafts/                           # Work in progress
├── _review/                           # Pending approval
├── archive/                           # Retired document versions
│
└── .claude/
    ├── commands/                      # 28 slash commands
    ├── skills/                        # Vault conventions + GTM standards
    └── agents/                        # Call, interaction, campaign processors

NEED HELP IMPLEMENTING THIS?

We'll build it for your team.

RevOps Vault is free and open source. If you want help tailoring it to your team's workflow, building custom commands, or operationalizing your entire GTM knowledge base, we can help.

SCHEDULE A CONSULTATION