mcpField
S
saas-replacement-planner

saas-replacement-planner

github.com/onewave-aiProductivity393231 installsUpdated 1w ago
Repository

About saas-replacement-planner

A skill that evaluates a company’s SaaS stack and creates a costed plan for replacing selected subscriptions with AI-agent-powered alternatives. It weighs feasibility, risks, build costs, and migration priorities rather than assuming every tool should be replaced.

Key features

  1. 01Structured analysis for each SaaS tool
  2. 02Pricing and replacement research
  3. 03Build-cost and risk estimates
  4. 04Impact-versus-effort prioritization
  5. 05Migration timeline planning

Use cases

  1. 01Assessing a SaaS inventory for replacement candidates
  2. 02Comparing subscription costs with estimated build costs
  3. 03Planning a phased migration around dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/onewave-ai/claude-skills --skill saas-replacement-planner

After installing, type/saas-replacement-plannerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
analysis-framework.md
analysis-guidelines.md
output-template.md
patterns.md

Details

From the project README

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.

Comments

Markdown supported