How to Build the Business Case for SaaS Replacement (With Templates)

You're Convinced. Your CFO Isn't.

You've seen the numbers. SaaS pricing is inflating at 11.4% per year. Your company wastes $915,000 annually on unused subscriptions. Custom replacements save 73% over three years. The math is undeniable.

But math alone doesn't get budget approved. You need a business case -- a structured argument that speaks the language of finance, addresses the risks head-on, and gives decision-makers a clear path to yes.

Here's how to build one that actually gets approved.

Key Takeaways

A strong business case needs five sections: Current State (the problem), Proposed Solution (the fix), Financial Model (the math), Risk Assessment (the objections), and Implementation Plan (the timeline)

Lead with the 5-year total cost of ownership comparison -- the compounding difference is the most persuasive number

Address the three objections every CFO will raise: maintenance risk, build quality, and opportunity cost

Include a payback period calculation -- most SaaS replacements pay for themselves in 12-18 months

Frame the request as a pilot: one tool, one replacement, measured results -- then expand

Section 1: Current State Analysis

Before you can propose a solution, you need to document the problem in terms finance understands. No opinions. Just numbers.

What to Include

Total SaaS spend. Pull every subscription from your finance system, procurement records, and expense reports. Include shadow IT -- the tools teams buy on corporate cards without procurement approval. According to Gartner, the real number is typically 2-3x what finance has on file.

Per-tool breakdown. For every tool over $10K/year, document:

Field	What to Capture
Tool name	The SaaS product
Annual cost	Current subscription cost
Cost trend	Last 3 years of pricing (shows the compounding)
Seats licensed	Total seats you're paying for
Seats active	Monthly active users (get this from IT or the tool's admin panel)
Feature utilization	What % of the tool's capabilities your team actually uses
Contract end date	When the renewal hits
Vendor ownership	Is the vendor PE-owned? Recently acquired?

Waste quantification. Calculate the dollar value of unused licenses. If you have 200 Salesforce seats at $65/month but only 140 people logged in last month, that's $46,800/year in pure waste on that one tool. Industry data shows 30-53% of licenses go unused.

Growth projection. Model what your SaaS spend looks like in 3 and 5 years under the current trajectory. Use the vendor's historical price increase rate. If you don't have it, use 10% as a conservative baseline (the 2025 average was 11.4%).

Template: Current State Summary

> Current annual SaaS spend: $[X]

> Number of tools over $25K/year: [X]

> Estimated waste (unused licenses + feature bloat): $[X] ([X]% of total)

> Projected 3-year total cost (at current trajectory): $[X]

> Projected 5-year total cost: $[X]

> Year-over-year cost increase (last 3 years): [X]%

This section should take one page. No recommendations yet. Just the facts.

Section 2: Replacement Candidates

Not every SaaS tool should be replaced. Your business case needs to identify specific candidates and explain why each one qualifies.

Scoring Framework

Score each tool on four dimensions (1-5 scale):

Cost Impact (weight: 40%) -- How much does this tool cost, and how fast is the cost growing?

5 = Over $100K/year with 10%+ annual increases

3 = $25K-$100K/year with 5-10% increases

1 = Under $25K/year with stable pricing

Feature Waste (weight: 25%) -- How much of the tool are you actually using?

5 = Using less than 20% of features

3 = Using 20-50% of features

1 = Using 80%+ of features

Build Feasibility (weight: 20%) -- How complex is a custom replacement?

5 = Simple workflows, standard data, clear requirements ($5K-$20K build)

3 = Moderate complexity, some integrations ($20K-$50K build)

1 = High complexity, deep integrations, regulatory requirements ($50K-$80K+ build)

Vendor Risk (weight: 15%) -- How likely is the vendor to make things worse?

5 = PE-owned, history of aggressive increases, product declining

3 = Public company, moderate increase history, stable product

1 = Well-funded, competitive pricing, strong product

Replacement Priority Score = (Cost Impact x 0.4) + (Feature Waste x 0.25) + (Build Feasibility x 0.2) + (Vendor Risk x 0.15)

Tools scoring above 3.5 are strong replacement candidates. Rank them by score and present the top 3-5.

Template: Candidate Summary Table

Tool	Annual Cost	Cost Trend	Feature Util.	Priority Score	Estimated Build Cost
[Tool A]	$[X]	+[X]%/yr	[X]%	[X.X]	$[X]
[Tool B]	$[X]	+[X]%/yr	[X]%	[X.X]	$[X]
[Tool C]	$[X]	+[X]%/yr	[X]%	[X.X]	$[X]

Section 3: Financial Model

This is the section that determines whether your business case gets approved or filed. Make it bulletproof.

The 5-Year TCO Comparison

For each replacement candidate, build a year-by-year comparison:

Year	SaaS Cost	Custom Cost	Annual Savings	Cumulative Savings
Year 1	$[X]	$[X] (build + maintenance)	$[X]	$[X]
Year 2	$[X] (+[X]%)	$[X] (maintenance only)	$[X]	$[X]
Year 3	$[X] (+[X]%)	$[X]	$[X]	$[X]
Year 4	$[X] (+[X]%)	$[X]	$[X]	$[X]
Year 5	$[X] (+[X]%)	$[X]	$[X]	$[X]
Total	$[X]	$[X]	$[X] ([X]%)

Key Metrics to Calculate

Payback period. How many months until the custom build pays for itself?

> Payback Period = Build Cost / (Monthly SaaS Cost - Monthly Maintenance Cost)

Most replacements have a payback period of 12-18 months. Anything under 24 months is typically approvable.

3-year ROI. The percentage return on the build investment over three years.

> 3-Year ROI = (3-Year SaaS Cost - 3-Year Custom Cost) / Build Cost x 100

A well-chosen replacement candidate typically shows 200-400% ROI over three years.

5-year savings (aggregate). If you're proposing multiple replacements, sum the savings. This is your headline number.

Template: Financial Summary

> Proposed replacement targets: [X] tools

> Total build investment required: $[X]

> Annual maintenance cost (all tools): $[X]

> Payback period (weighted average): [X] months

> 3-year savings: $[X] ([X]% reduction vs. continued SaaS)

> 5-year savings: $[X] ([X]% reduction vs. continued SaaS)

> 3-year ROI on build investment: [X]%

Section 4: Risk Assessment

Your CFO will raise objections. Address them before they're asked. This is what separates business cases that get approved from ones that get tabled.

Objection 1: "What if maintenance costs more than projected?"

Response: Model the sensitivity. Even if you triple maintenance costs, the 5-year savings remain significant because the fundamental math -- flat costs vs. compounding costs -- doesn't change.

Include a sensitivity table:

Scenario	Build Cost	Annual Maintenance	5-Year Total	vs. SaaS Savings
Base case	$45K	$11K	$100K	84%
2x maintenance	$45K	$22K	$155K	75%
3x maintenance	$45K	$33K	$210K	66%
2x build + 2x maintenance	$90K	$22K	$200K	67%

Even the worst-case scenario saves over 60%.

Objection 2: "Custom software breaks. Who fixes it?"

Response: Maintenance is included in the cost model. Custom software with a 10-20% annual maintenance budget ($500-$3,000/month) has the same or better uptime as SaaS tools. The difference is you're paying $6K-$36K/year for maintenance instead of $100K+/year for a subscription.

Additionally, with custom software, when something breaks, you have full access to the codebase and can fix it immediately. With SaaS, you submit a ticket and wait.

Objection 3: "Our engineers should be building product, not internal tools."

Response: Agreed. That's why we use a SaaS replacement agency. Zero product engineering time diverted. The replacement is built by specialists whose entire focus is replacing SaaS subscriptions with custom tools. Your engineers stay on the product roadmap.

Objection 4: "What if the business requirements change?"

Response: Custom software adapts to your requirements. SaaS forces you to adapt to theirs. When requirements change, modifying a custom tool is a maintenance task ($2K-$10K). Switching SaaS vendors is a multi-month migration project.

Section 5: Implementation Plan

Don't propose replacing everything at once. Propose a pilot.

Phase 1: Pilot (Weeks 1-8)

Replace one tool -- the highest-scoring candidate from Section 2

Estimated build cost: $[X]

Estimated timeline: 4-8 weeks

Success criteria: tool deployed, team adopted, subscription cancelled

Phase 2: Measure (Weeks 9-12)

Track actual maintenance costs vs. projected

Survey users on satisfaction vs. the SaaS tool

Calculate actual savings vs. projected

Document lessons learned

Phase 3: Expand (Months 4-12)

If Phase 1 succeeds (and it will), apply the same process to the next 2-4 candidates

Each subsequent replacement is faster because the process is proven

Aggregate savings fund subsequent builds

Template: Implementation Timeline

Phase	Weeks	Activity	Investment	Expected Savings (Annual)
Pilot	1-8	Replace [Tool A]	$[X]	$[X]
Measure	9-12	Track results	$0	--
Expand #1	13-20	Replace [Tool B]	$[X]	$[X]
Expand #2	21-28	Replace [Tool C]	$[X]	$[X]
Total	28 weeks	3 tools replaced	$[X]	$[X]/year

Presenting It

Keep the executive summary to one page. Lead with three numbers:

Current trajectory cost (5-year SaaS spend at current growth rates)

Proposed alternative cost (5-year cost with custom replacements)

Total savings (the delta)

Then: "I'm proposing we pilot this with one tool. Here's the specific tool, the build cost, and the payback period. If it works, we expand. If it doesn't, we're out $[X] and we learned something. The downside is capped. The upside is $[X] over five years."

That's a business case that gets approved. Not because it's optimistic, but because it's specific, conservative in its assumptions, and structured as a low-risk pilot with a clear expansion path.

Need help building the business case for your specific stack? Get your free SaaS audit. We'll provide the current state analysis, identify your top replacement candidates, and build the financial model your CFO needs to see. Takes 5 minutes to start. Results in 24 hours.