Revenue OS

From code to customers to cash — The monetization operating system for developers

Revenue OS is a powerful Claude Code plugin that transforms the journey from building a product to generating revenue. It analyzes your codebase, identifies ideal customers, polishes your value proposition, and generates everything you need to start making money.

Perfect for: Indie hackers, solo founders, startup developers, SaaS builders, and anyone who builds great products but struggles to monetize them.

Why Revenue OS?

Developers are great at building products but often struggle with:

Revenue OS provides a systematic, engineering-minded approach to monetization — because revenue is just another system to be designed and optimized.

Features

• Codebase Analysis — Understands YOUR specific product, not generic advice
• ICP Discovery — Find exactly who will pay for your product
• Value Proposition — Multiple proven frameworks (JTBD, PAS, Before/After)
• Pricing Psychology — Research-backed tier design with competitor analysis
• Outreach Generation — Cold email, LinkedIn, and Twitter sequences
• Landing Page Copy — Conversion-optimized page structure
• Objection Handling — Proven responses to common sales objections
• Revenue Audit — Score your monetization readiness with action plan

Installation

Revenue OS is distributed from the belkins Claude Code marketplace. Adding the marketplace registers its catalog; it does not install the plugin by itself.

# Run these inside Claude Code
/plugin marketplace add Belkins/revenue-os
/plugin install revenue-os@belkins

Run /reload-plugins if Claude Code asks you to activate the newly installed plugin. The commands are namespaced as /revenue-os:ros-*.

For non-interactive installation, use the equivalent CLI commands:

claude plugin marketplace add Belkins/revenue-os
claude plugin install revenue-os@belkins

Update or Uninstall

Refresh the marketplace before updating so Claude Code sees the latest release:

# Run these inside Claude Code
/plugin marketplace update belkins
/plugin update revenue-os@belkins

To remove Revenue OS from the current scope:

/plugin uninstall revenue-os@belkins

Because this marketplace currently contains only Revenue OS, you can also remove the catalog afterward with /plugin marketplace remove belkins.

The default uninstall also removes plugin-managed data when this is the final installed scope. To preserve that data with the CLI, use claude plugin uninstall revenue-os@belkins --keep-data. The old ~/.claude/revenue-os/ directory from versions before 1.0.1 is separate from Claude's managed plugin data and is never deleted by Revenue OS.

Cloning this repository alone does not install or auto-detect the plugin. For local development, run ./scripts/validate-repository.sh. The marketplace points directly at the dedicated plugin/ package, and validation installs that exact directory into temporary HOME and CLAUDE_CONFIG_DIR paths without changing your normal Claude configuration. Preflight rejects __pycache__ directories, .pyc files, symlinks, and special filesystem entries anywhere in the package. Install smoke compares every source and installed path, entry type, permission mode, and regular-file hash. Release validation requires Claude Code 2.1.221, the same version pinned in CI; Python 3 is required by the packaged storage boundary.

Quick Start

# 1. See your revenue readiness score
/revenue-os:ros

# 2. Discover who will pay for your product
/revenue-os:ros-icp

# 3. Polish your value proposition
/revenue-os:ros-value-prop

# 4. Design your pricing
/revenue-os:ros-pricing

# 5. Generate outreach sequences
/revenue-os:ros-outreach

# 6. Get a full audit with action plan
/revenue-os:ros-audit

Commands

How It Works

1. Analyzes Your Code

Revenue OS scans your codebase to understand:

• What problem your product solves
• Key features and capabilities
• Technology stack
• Potential use cases

2. Finds Your Customers

Using AI analysis and web research:

• Generates ICP (Ideal Customer Profile) hypotheses
• Finds communities where they gather
• Validates pain points exist
• Identifies buying triggers

3. Polishes Your Pitch

Creates compelling messaging using proven frameworks:

• Jobs-to-be-Done (JTBD)
• Problem-Agitate-Solution (PAS)
• Before/After Transformation
• Unique Mechanism

4. Designs Pricing

Research-backed pricing architecture:

• Competitor analysis via web search
• Psychology-based tier design (charm pricing, anchoring, decoy effect)
• Revenue projections
• Stripe integration code

5. Generates Assets

Ready-to-use marketing materials:

• Cold email sequences (4-email series)
• LinkedIn outreach templates
• Landing page copy
• Objection handling scripts

Example: 2-Week Revenue Sprint

Week 1: Foundation

# Day 1: Understand your product and customers
/revenue-os:ros-icp

# Day 2: Create compelling messaging
/revenue-os:ros-value-prop

# Day 3: Research the competition
/revenue-os:ros-competitors

# Day 4: Set your prices
/revenue-os:ros-pricing

# Day 5: Prepare for objections
/revenue-os:ros-objections

Week 2: Distribution

# Day 6-7: Build your landing page
/revenue-os:ros-landing-page full

# Day 8-9: Create outreach sequences
/revenue-os:ros-outreach cold-email
/revenue-os:ros-outreach linkedin

# Day 10-14: Execute and iterate
# Send outreach, track responses, refine

Data Persistence

Revenue OS stores working data in ${CLAUDE_PLUGIN_DATA}, the stable per-plugin directory supplied by Claude Code at runtime:

${CLAUDE_PLUGIN_DATA}/
├── product.json      # Product analysis
├── icp.json          # Ideal customer profiles
├── value-prop.json   # Value propositions
├── pricing.json      # Pricing strategy
└── outreach/         # Generated sequences

This managed directory persists across plugin updates and sessions, allowing commands to build on each other. On the first session after upgrading from an older release, Revenue OS copies legacy files from ~/.claude/revenue-os/ without overwriting canonical data or deleting the legacy source. Conflicts are left intact on both sides and retried after you resolve them.

All managed reads, writes, exports, outreach saves, migrations, and resets pass through a no-follow storage boundary. It requires an absolute data root, rejects symlinked or non-regular managed paths, restricts outreach names to safe basenames, and uses atomic sibling-file replacement. A reset fails before any deletion when the managed tree is unsafe. Successful reset removes exports, outreach, audits, and unknown regular artifacts as well as canonical JSON, then recreates clean defaults and a validated versioned migration tombstone so legacy data is not imported again. Canonical JSON must be a top-level object and known fields are type-checked on writes, reads, migration, scoring, and export.

Before the first reset deletion, Revenue OS takes and compares two complete tree snapshots, checks effective read/write/execute permissions and ACL results for every directory, and rejects immutable or append-only entries. This also proves the root can replace the tombstone/default files and recreate the managed directories. If a later subtree is not removable, reset leaves earlier data untouched.

On macOS, preflight additionally asks the Darwin kernel for _DELETE_OK on every file and directory through accessx_np. This evaluates effective delete and containing-directory delete_child ACL rules without changing the entry. The complete absolute ancestor chain remains pinned by open directory descriptors, and a fresh no-follow traversal must match every pinned device and inode plus the managed entry fingerprint both before and after the path-based ACL query. An ancestor rename, replacement, or indeterminate result therefore fails closed before reset deletes anything.

Command Reference

/revenue-os:ros-icp - Ideal Customer Profile

/revenue-os:ros-value-prop - Value Proposition

/revenue-os:ros-pricing - Pricing Strategy

/revenue-os:ros-outreach - Outreach Sequences

Use Cases

• Indie Hackers — Go from side project to paying customers
• SaaS Founders — Find product-market fit faster
• Developer Tools — Monetize your open source work
• Freelancers — Package your skills into products
• Agencies — Create productized services

Contributing

Contributions are welcome! Areas that could use help:

• Additional ICP templates for new industries
• More outreach templates and sequences
• Improved pricing psychology data
• Better Stripe integration examples
• Translations

See CLAUDE.md for development documentation.

GitHub Topics

When publishing this repo, add these topics for discoverability: claude-code, claude-plugin, monetization, saas, indie-hackers, pricing, sales, marketing, icp, value-proposition, outreach, developer-tools, startup, revenue

Author

Created by Vladyslav Podoliako

• Website: vladyslavpodoliako.com
• Newsletter: vladsnewsletter.com — Weekly insights on AI, development, and building products
• Twitter/X: @StBelkins

License

MIT License — see LICENSE for details.

Star History

If this plugin helps you make money, consider giving it a star!

Built for developers who deserve to get paid for their work.

Subscribe to the newsletter for more tools and insights.