Skip to main content
skill CX Codex

saas-replacement-planner — Claude Code skill: what it does

saas-replacement-planner analyzes your SaaS stack and produces a replacement plan with ROI calculations, implementation timeline, and risk assessment for switching to AI agents.

MIT 247 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill saas-replacement-planner -a claude-code
Open on GitHub

What saas-replacement-planner does

The skill takes a list of subscriptions with costs (from screenshots, CSVs, or statements), verifies current pricing via web search, and evaluates each tool through a six-step framework: classification, replacement feasibility, build cost estimation, Claude + MCP architecture design, risk scoring, and priority ranking. It outputs a saas-replacement-plan.md file with ROI analysis, sequenced rollout, timeline, and grouped replacements that share infrastructure.

It uses Read, Write, Edit, Glob, Grep, Bash, WebSearch, and WebFetch tools. Handles incomplete data: if seat counts, dependencies, or criticality are missing, it asks clarifying questions. Replacement patterns for common tool categories and estimation guidelines are stored in reference files inside the skill.

What it helps with

  • calculate economics of replacing SaaS with owned agents
  • prioritize replacements by impact versus effort
  • identify MCP servers and Claude architectures that cover existing subscription features
  • build a migration timeline accounting for dependencies and parallel running periods

Example prompts for the agent

  • Analyze our SaaS subscriptions from subscriptions.csv and draft a replacement plan
  • Take this screenshot of our software bill and suggest what can be replaced with Claude agents
  • Evaluate ROI for replacing Zapier, Notion, and Hubspot with Claude-powered solutions

How to install saas-replacement-planner

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill saas-replacement-planner -a claude-code

2Manually: put the files in place

~/.claude/skills/saas-replacement-planner/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/saas-replacement-planner/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about saas-replacement-planner

How to install saas-replacement-planner in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill saas-replacement-planner -a claude-code. The skill file will appear in ~/.claude/skills/saas-replacement-planner/SKILL.md.

What does saas-replacement-planner do?

The skill analyzes a company's SaaS subscriptions, assesses replacement feasibility and economics for each tool, builds a priority matrix, and writes an implementation plan with ROI, timeline, and risk breakdown.

What data is needed for SaaS replacement analysis?

A list of tools with monthly or annual costs, seat counts, and primary use cases. If critical parameters like integration dependencies, compliance requirements, or priority are missing, the skill will ask.

Source text

SKILL.md · MIT
---
name: saas-replacement-planner
description: Evaluates which SaaS tools can be replaced with AI agents. Takes a list of current SaaS subscriptions with costs, assesses replacement feasibility, estimates build vs buy economics, identifies Claude+MCP alternatives, and generates a comprehensive replacement plan with priority matrix, ROI analysis, implementation timeline, and risk assessment.
tools: Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch
model: inherit
---

# SaaS Replacement Planner

Evaluate a company's SaaS stack and produce a rigorous, actionable plan that quantifies the ROI of migrating from subscription software to AI-agent-powered alternatives. Bias toward replacement where the economics support it, but stay honest: not every tool can be replaced today.

## Contents

- `references/analysis-framework.md` -- the six-step per-tool analysis (classification, feasibility tiers, build-cost formulas, Claude+MCP architecture, risk scoring, priority matrix)
- `references/output-template.md` -- full `saas-replacement-plan.md` document structure
- `references/patterns.md` -- proven replacement patterns by category and edge-case handling
- `references/analysis-guidelines.md` -- estimation rigor, honesty rules, OneWave AI thesis, and output quality standards

## Workflow

1. **Gather input.** Collect the SaaS tool list. Parse screenshots, CSVs, or bank statements; organize informal lists into a structured format (tool, monthly/annual cost, seats, primary use case). Ask clarifying questions only when critical data is missing: seat counts, primary workflows, integration dependencies, mission-critical vs nice-to-have, and compliance requirements.
2. **Research current pricing.** For each tool, verify pricing with WebSearch when numbers are missing or look off. Check per-seat pricing, outdated plans, API access for the replacement, and data export capability.
3. **Analyze each tool.** Run the complete six-step framework in `references/analysis-framework.md` for every tool. Do not skip tools or give superficial analysis. Apply matching patterns from `references/patterns.md`.
4. **Build the priority matrix.** Plot all tools on the Impact vs Effort axes. Sequence replacements and group tools that share infrastructure (e.g., all needing Supabase) to reduce incremental build cost.
5. **Generate the timeline.** Create a realistic timeline accounting for engineering capacity, parallel running periods, dependencies between replacements, and quick wins that fund later investments.
6. **Write the plan.** Generate `saas-replacement-plan.md` in the current working directory using the structure in `references/output-template.md`. Follow the rigor and quality standards in `references/analysis-guidelines.md`.
7. **Present key findings.** After writing the file, summarize total potential savings, the top 3 quick wins, any surprising findings, and the recommended first action.

## Core Principle

Every SaaS subscription is a recurring tax on the business; every agent replacement is an investment in owned infrastructure that compounds over time. Make the numbers speak clearly and let the ROI make the argument. See `references/analysis-guidelines.md` for the full OneWave AI thesis and how to frame the analysis.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Notes, tasks and projects →

From the same set185

The whole set →
competitor-intel-agent competitor-intel-agent monitors competitor sites, pricing models, hiring shifts, and product releases while saving snapshot history. CX Codex +1 251installs okr-generator okr-generator builds a structured okr-plan.md file using the Google and Intel framework from your company targets and team baselines. CX Codex +1 250installs renewal-predictor The renewal-predictor skill analyzes seven account health dimensions—engagement, support, adoption, satisfaction, billing, stakeholder continuity. CX Codex +1 249installs utm-link-generator utm-link-generator builds UTM-tagged links under unified naming rules, tracks duplicates, and outputs variants for LinkedIn, email, social, and ads. CX Codex +1 249installs expansion-revenue-finder The expansion-revenue-finder skill for Claude Code finds upsell and cross-sell opportunities by analyzing product usage, team growth, and competitive pressure, then scores each by revenue potential, effort, and likelihood. CX Codex +1 247installs agent-swarm-deployer agent-swarm-deployer deploys parallel sub-agent swarms for heavy data jobs like bulk document summarization, dataset processing, and multi-record content generation. CX Codex +1 247installs churn-autopsy churn-autopsy — a skill for post-mortem analysis of client churn. Collects interaction history, support tickets, usage logs and exit feedback, then builds a timeline of decline and identifies root causes. CX Codex +1 244installs scout-pro scout-pro scans conversation history, verifies installed tools, and builds multi-skill chains tailored to your current development task. CX Codex +1 244installs

Project sponsors

Companies that keep this analytics open