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.
SkillScore64Maintained
Automatic
◆Procurement pack
Last verified 8/27/2026
What it changes
Passed 13 of 21 test cases with the skill, and 8 of 21 without it.
Without skill36%
With skill64%
Checks it passed that the model alone missed
Writes the plan to saas-replacement-plan.md.
Assigns quantitative risk scores to candidate tools.
Sequences quick wins earlier to fund later investments.
and 6 more in the full report
6 fixed8 passed either way8 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+62%
Agent turns
0%
Response time
+73%
Model gemini-3.6-flashMeasured 8/27/2026v114 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We are preparing a rollout schedule to swap out 6 SaaS tools (Intercom, Zendesk, Mailchimp, Zapier, Calendly, Typeform) for internal AI agent systems. What timing strategy should be used to manage engineering capacity and risk?
What was checked, without and with the skill
Checked
Without skill
With skill
Schedules parallel running periods where legacy SaaS and new agents operate concurrently.
Passed
Passed
Sequences quick wins earlier to fund later investments.
Missed
Passed
case-08 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md24 lines5 files
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.
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
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.
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.
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.
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.
Generate the timeline. Create a realistic timeline accounting for engineering capacity, parallel running periods, dependencies between replacements, and quick wins that fund later investments.
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.
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.
Implement proven sales methodologies (MEDDIC, BANT, Sandler, Challenger, SPIN) across your team. Generate framework-specific questions, score deals, train reps, and enforce consistent qualification. Use when implementing or optimizing sales processes.