Agent skill · marketing growth · onewave-ai
saas-replacement-planner
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.
Why this skill is useful
Provides a structured framework for evaluating SaaS replacements with specific analysis patterns and ROI calculations that the AI wouldn't generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-07-15. 242 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills onewave-ai/saas-replacement-planner