SaaS Subscription Audit 2026
SaaS Subscription Audit: How Much Are You Actually Spending?
The average company uses 130+ SaaS tools. Most don't know what they're paying — or that open source alternatives exist for 80% of them.
The SaaS Spending Problem
| Company Size | Average Annual SaaS Spend | Average Tools |
|---|---|---|
| 1-50 employees | $50,000-150,000 | 40-80 |
| 50-200 employees | $150,000-500,000 | 80-120 |
| 200-1000 employees | $500,000-2,000,000 | 120-200 |
Most companies discover 30-40% of subscriptions are underused or redundant.
Step 1: Find Every Subscription
Where to Look
- Credit card/bank statements — Search for recurring charges
- Expense reports — Individual team purchases
- Email receipts — Search "subscription", "invoice", "receipt"
- SSO dashboard — Shows connected apps
- Browser extensions — Installed by team members
- IT admin consoles — Google Workspace, Microsoft 365 app lists
Common Categories to Check
| Category | Common SaaS Tools | OSS Alternatives |
|---|---|---|
| Team chat | Slack ($8.75/user) | Mattermost, Rocket.Chat |
| Project management | Jira ($8.15/user), Asana ($13.49/user) | Plane, Taiga |
| Documentation | Notion ($12/user), Confluence ($6.05/user) | Outline, BookStack |
| Analytics | GA360 ($50K+), Mixpanel ($28/user) | Plausible, PostHog |
| CRM | Salesforce ($25/user), HubSpot ($20/user) | Twenty, EspoCRM |
| Email marketing | Mailchimp ($20+), SendGrid ($20+) | Listmonk |
| Customer support | Zendesk ($19/user), Intercom ($39/user) | Chatwoot |
| Design | Figma ($15/user), Adobe CC ($55/user) | Penpot, Inkscape |
| Scheduling | Calendly ($12/user) | Cal.com |
| Forms | Typeform ($29+) | Formbricks |
| Link management | Bitly ($35+) | Dub |
| Monitoring | Datadog ($15/host), PagerDuty ($21/user) | Grafana, Uptime Kuma |
| Authentication | Auth0 ($23+) | Keycloak, Authentik |
| Storage | Dropbox ($15/user), Google Drive ($12/user) | Nextcloud |
| Video calls | Zoom ($13.33/user) | Jitsi Meet |
Step 2: Calculate True Cost Per Tool
For each subscription, calculate:
True Annual Cost = (Monthly Per-User Cost × Users × 12)
+ Add-on Costs
+ Overage Charges
+ Admin Time Value
Example: A 50-Person Team's SaaS Stack
| Tool | Per User/Mo | Annual Cost |
|---|---|---|
| Slack Pro | $8.75 | $5,250 |
| Jira Standard | $8.15 | $4,890 |
| Notion Plus | $12 | $7,200 |
| Confluence | $6.05 | $3,630 |
| Figma Professional | $15 | $9,000 |
| Zoom Business | $13.33 | $7,998 |
| Calendly Teams | $12 | $7,200 |
| 1Password Teams | $4 | $2,400 |
| Mailchimp Standard | — | $3,600 |
| Intercom Starter | — | $9,480 |
| Google Analytics | — | $0* |
| Datadog (10 hosts) | — | $3,960 |
| Total | $64,608/year |
GA4 is "free" but costs user data and requires CMP.
Step 3: Identify Replacement Candidates
High-Impact Replacements (Save >$3K/year each)
| Replace | With | Annual Savings |
|---|---|---|
| Slack Pro → Mattermost | Self-hosted | $5,094 |
| Notion → Outline | Self-hosted | $7,092 |
| Figma → Penpot | Self-hosted | $8,892 |
| Jira → Plane | Self-hosted | $4,782 |
| Zoom → Jitsi Meet | Self-hosted | $7,842 |
| Calendly → Cal.com | Self-hosted | $7,092 |
| Intercom → Chatwoot | Self-hosted | $9,372 |
Total potential savings: $50,166/year (78% reduction)
Self-Hosting Costs
| Servers Needed | Monthly Cost |
|---|---|
| 3 VPS (Hetzner, 4-8 GB each) | $21-42 |
| Backups (Backblaze B2) | $5 |
| Domains | $5 |
| Total infrastructure | $31-52/month ($372-624/year) |
Step 4: Prioritize by ROI
Score each potential switch:
| Factor | Weight | How to Score |
|---|---|---|
| Annual savings | 40% | Dollar amount saved |
| Migration effort | 25% | Hours to migrate (lower = better) |
| Feature gap | 20% | What you lose (smaller gap = better) |
| Team impact | 15% | How many people are affected |
Prioritization Example
| Switch | Savings | Effort | Gap | Impact | Priority |
|---|---|---|---|---|---|
| Calendly → Cal.com | $7,092 | Low (2h) | None | Medium | 🟢 Do first |
| 1Password → Vaultwarden | $2,346 | Low (1h) | None | High | 🟢 Do first |
| Slack → Mattermost | $5,094 | Medium (4h) | Small | High | 🟡 Phase 2 |
| Notion → Outline | $7,092 | High (8h) | Medium | High | 🟡 Phase 2 |
| Figma → Penpot | $8,892 | High (16h) | Medium | Medium | 🔴 Phase 3 |
Step 5: Plan the Migration
Phase 1 (Week 1-2): Quick Wins
- Tools with easy migration and no feature gap
- Cal.com, Vaultwarden, Uptime Kuma, Plausible
Phase 2 (Month 1-2): Core Tools
- Communication and project management
- Mattermost, Plane, Chatwoot
Phase 3 (Month 2-4): Complex Migrations
- Tools with data migration needs
- Outline (Notion), Penpot (Figma)
The Bottom Line
Most 50-person teams can save $40,000-60,000/year by replacing SaaS with open source. Start with the quick wins — you'll save thousands in the first week.
Hidden Costs That SaaS Vendors Don't Advertise
The subscription line items in your audit are only part of the story. SaaS vendors have become increasingly sophisticated at structuring pricing so that the list price understates the true cost. Identifying these hidden costs before you run your audit gives you a more accurate savings calculation.
Per-seat pricing that scales faster than your team. Many SaaS tools charge per seat with tiered minimums or round up to plan boundaries. A team of 32 users on a plan sold in blocks of 25 pays for 50 seats. As your team grows from 25 to 26 users, the cost jumps immediately — sometimes doubling. SaaS vendors design these tiers intentionally to capture revenue at growth inflection points. When auditing, look at what tier you're actually on versus what tier your user count strictly requires.
Feature gating on core functionality. Jira's free tier supports up to 10 users with limited features. The features that most teams actually need — advanced roadmaps, time tracking, audit logs, API access above basic rate limits — are gated behind paid tiers. DocuSign gates API access behind the Business Pro plan ($65/user/month) while its Standard plan ($25/user/month) looks affordable. When calculating true cost, identify which features your team actually uses and map them to the tier that includes those features.
Data export and portability costs. Some SaaS tools charge for data exports or make export deliberately difficult. Mailchimp charges for contact exports above certain plan levels. Some CRM vendors provide CSV exports on lower tiers but require higher tiers for API-based data access that enables a smooth migration. Before canceling any subscription, verify that your data export path exists and doesn't require an upgrade to a more expensive tier to exercise.
Integration and add-on costs. The base subscription price rarely includes integrations. Jira Advanced Roadmaps is a separate add-on. Slack's Workflow Builder is included in Business+ but not Pro. Salesforce's integration marketplace has apps that individually cost more than the CRM license itself. When auditing, total the base subscription plus every add-on, integration, and workflow automation tool that enables your actual workflows.
Compliance and security feature tiers. SOC 2 compliance reports, audit logs, SAML SSO, and data residency options are frequently gated behind Enterprise tiers that cost two to five times more than the standard tier. For teams with compliance requirements, the price difference between "we have the feature" and "we can prove compliance with auditor-ready logs" can be substantial. Self-hosted open source tools give you audit log access by default since you own the infrastructure and database.
Contract minimums and renewal traps. Annual contracts offer discounts but lock you into 12-month commitments. If your team size changes significantly mid-year, you're still paying for the original seat count. Enterprise contracts often include auto-renewal clauses that require 60-90 day written notice to cancel — miss the window and you're committed for another year. Set calendar reminders 90 days before every annual SaaS renewal to evaluate whether the tool still justifies its cost.
Building the Business Case for Open Source Migration
The cost savings are clear on paper, but getting organizational buy-in for migration requires framing the decision in terms that resonate with decision-makers who aren't running the infrastructure themselves.
Frame it as risk reduction, not just cost. SaaS vendor risk is underappreciated. Any SaaS tool can change pricing, get acquired, shut down, or change features with limited notice. Heroku killed its free tier with 28 days notice. Adobe's subscription model was imposed on users who had purchased perpetual licenses with no grandfathering option. Self-hosted open source tools don't have these risks — you run the version you've tested, and you migrate to new versions on your schedule. For business-critical tools, this operational independence is worth quantifying separately from raw cost savings.
Calculate the total cost of ownership correctly. Engineering time to set up and maintain self-hosted infrastructure is a real cost that belongs in the analysis. A realistic estimate for maintaining the full open source remote work stack described in the remote work stack guide is two to four hours per month — roughly one sprint task of ongoing maintenance across all tools combined. At $150/hour loaded engineering cost, that's $300-600/month in engineering time, which is worth including in the comparison against $2,500+/month in SaaS costs.
Pilot before committing. The most effective way to build organizational confidence in an open source migration is a structured pilot with clear success criteria. Choose one tool, run the open source alternative in parallel for 60 days with a subset of users, and measure against pre-defined criteria: does it handle the team's actual workflows, what friction points appeared, what was the subjective satisfaction of the pilot users. A successful pilot with hard data is far more persuasive than a cost comparison spreadsheet.
Sequence migrations to maintain momentum. The prioritization framework above identifies quick wins (Cal.com, Vaultwarden) as Phase 1 specifically because early wins build confidence and momentum. When the Cal.com migration succeeds — it's fast, the feature gap is zero, and you immediately stop a $7,000/year charge — it demonstrates that the migration approach works and makes the Phase 2 and Phase 3 migrations easier to greenlight. Organizations that attempt to migrate communication tools first (the highest-disruption migration) often lose momentum when they encounter friction, abandoning the whole initiative.
For teams that want to understand the ROI calculation before starting, the how to calculate ROI switching to open source framework provides the specific formulas and worked examples to build a credible internal business case.
Ongoing Subscription Hygiene
A one-time audit is valuable, but SaaS spending tends to creep back up without ongoing oversight. Teams that cut their SaaS spend by 50% in Q1 often find they're back to near-original levels by Q4 if they don't maintain discipline. Building subscription hygiene into regular business processes is what converts a one-time audit win into durable savings.
Require approval for new subscriptions. The most effective single control is requiring manager or finance approval for any new recurring subscription, even free-trial signups that auto-convert to paid. Many SaaS tools make the purchase path so frictionless (one click, auto-renewal) that teams acquire subscriptions without realizing they've made a budget commitment. An approval step creates a natural checkpoint where someone asks: is there an open source alternative we should evaluate first?
Quarterly subscription review. Schedule a 30-minute quarterly review where the engineering lead, finance representative, and a business unit lead review the current subscription list. The agenda is simple: is each tool still being used? Is each tool still the right choice? Has anything changed in the open source landscape that makes a switch more attractive? This review creates accountability for subscription decisions and a regular opportunity to trim unused tools before annual renewals lock you in for another year.
Track active users, not licensed seats. Many SaaS tools report active users in their admin dashboards. Monthly active user counts frequently reveal that 20-30% of licensed seats are inactive — the tool was assigned during onboarding and never meaningfully used. For tools where your contract allows seat reduction, rightsizing based on actual active users is often the fastest savings opportunity. For tools with annual contracts, capture this data 90 days before renewal to negotiate down to actual usage.
Assign subscription ownership. Every subscription should have a named owner who is responsible for renewing or canceling it. When that person leaves the company, subscription ownership should transfer during offboarding. Orphaned subscriptions — tools still billing monthly years after the person who signed up for them left the company — are a consistent finding in SaaS audits. They persist not because anyone wants them but because no one notices and no one owns the decision to cancel.
The combination of a thorough initial audit and these ongoing practices keeps SaaS costs from re-inflating. The savings from open source substitution are most durable when paired with a culture that treats software spending with the same scrutiny as headcount decisions. For teams that have completed an audit and are ready to execute replacements, the best open source project management tools comparison is one of the highest-impact starting points — Jira and Asana often represent the second or third largest line items in an engineering team's SaaS budget. For a concrete cost benchmark across the most expensive tools in each category, see the most expensive SaaS tools and their free alternatives overview, which quantifies the potential savings for each tool class.
Find the best open source alternative for every SaaS tool at OSSAlt.