At SaaStr AI Annual 2026, the CEO of Aurasell disclosed what most revenue leaders keep buried: 22 GTM tools, $3M in annual licensing fees, and 11 ops employees to run the stack. 1 Source 1 Aurasell CEO at SaaStr AI Annual 2026, June 7, 2026. Covered by SaaStr: ‘22 Tools. $3M in Fees. 11 Ops People.’ Add the headcount math — 11 ops staff at $150K fully loaded is $1.65M — and that stack costs $4.65M a year. 2 Source 2 Lynton analysis. $150K/year is a conservative fully-loaded estimate for a RevOps or marketing ops hire in most US markets. $3M licensing + $1.65M ops headcount = $4.65M total GTM stack TCO. One ops person per two tools, and a total annual cost that never shows up on a single invoice.
The question: is your number smaller, or bigger?
If you want to know how to audit your SaaS GTM stack costs in 2026 — actually audit it, not just pull license totals from the accounting system — here is the six-step framework we’ve built from watching how stacks accumulate and get rationalized across more than 2,000 integration engagements.
Step 1 — Build the real inventory (not the IT spreadsheet)
The actual list is never the one you think it is. Most companies undercount their GTM tooling by 20-30%: team-level subscriptions on individual credit cards, SaaS trials that became permanent, AI bundles added at renewal without a separate line item.
Pull from four sources: expense reports (full 12 months), credit card statements (corporate and individual team cards), your SSO directory showing every connected application, and IT asset management if you have it.
Categorize by function: CRM, marketing automation, sales engagement, call recording, intent data, enrichment, BI, communication, AI and automation. Flag anything without a named owner. Ownerless tools are the first to overlap with tools someone does own.
Output: Spreadsheet with tool name, function, annual cost, named owner, and monthly active users where available.
Step 2 — Calculate what the stack actually costs (licenses are only half the story)
A $3M tool bill is visible. The $1.65M in ops headcount isn’t.
Every tool has a maintenance burden: configuration, integration upkeep, user management, reporting, fielding questions from the team. That labor cost almost never appears on the SaaS invoice. For each tool, estimate monthly admin hours and multiply by the burdened hourly rate of whoever does that work. Add that to the annual license cost.
The Aurasell benchmark: 11 ops staff running 22 tools is about half an FTE per tool. At $150K fully loaded — a conservative estimate for a RevOps or marketing operations hire in most US markets — that’s $75K in headcount per tool on top of the licensing fee. Run the calculation and you’ll surface costs that renewal spreadsheets routinely miss.
The tools with the highest ops burden are usually the ones with the worst integration architecture. These are tools requiring manual exports, custom automation chains, or RevOps heroics to stay synchronized. High maintenance cost is an early indicator of which tools to remove first.
The tools that generate the highest ops burden are usually the ones with the worst integration architecture.
Output: Annotated spreadsheet with a total-cost-of-ownership column per tool, sorted descending. The top 20% by TCO deserve the hardest scrutiny at renewal.
Step 3 — What does GTM tool overlap actually look like?
GTM tool overlap looks like the same function covered by two or three different tools that nobody cross-referenced when they were bought. Call recording purchased by sales, then added by the CRM vendor as a renewal upsell. Contact enrichment from a standalone tool, then bundled into the ABM platform. BI dashboards built by RevOps, then replicated inside the marketing automation platform.
To map it, list every function your stack performs — lead scoring, contact enrichment, email sequencing, call recording, revenue reporting — then every tool that performs each one. What you’re looking for: any function covered by three or more tools, any capability already inside your primary CRM or MAP that you’re also paying a point solution to provide, and any AI feature you’re paying for twice.
The most expensive overlap we consistently see: companies paying $60K or more for an outbound sequencing tool that duplicates what their CRM’s native email engine can already do. The point solution was purchased when the CRM data was unreliable. If the data hygiene problem is solved, the sequencing tool is an inertia hold paying out of organizational memory, not business value.
The same pattern is now playing out across AI bundles. Your MAP vendor added a conversational AI feature at renewal. So did your CRM. If you also have a standalone AI prospecting tool, you’re paying for the same capability three times. The AI spend backlash in engineering is reaching GTM stacks next. 35% of enterprises already replaced at least one SaaS tool with custom software (Retool, 2026). 3 Source 3 Retool, ‘The Build vs. Buy Shift,’ February 2026. 817 respondents. 35% had replaced at least one SaaS tool. 4 Source 4 The Pragmatic Engineer, June 11, 2026. Engineering teams running informal audits and cutting AI tooling spend, and the same correction is underway in GTM.
Output: Overlap matrix with any function covered by two or more tools flagged as a consolidation candidate.
Step 4 — Score every tool: load-bearing or inertia hold
The $200/month tool nobody uses is easy. The $8,000/month tool nobody can explain is the real problem.
Apply a 2x2 to every tool. One axis: business impact — does this tool directly generate pipeline, close revenue, or produce attribution-critical data? The other: replaceability — is this functionality natively available in a tool you already pay for, or buildable in under 30 days?
- High impact, hard to replace: Keep. These are load-bearing. Don’t touch them without a migration plan.
- High impact, easy to replace: Consolidate. The function matters but you’re paying a point-solution premium.
- Low impact, easy to replace: Sunset now. These are inertia holds — kept active because canceling is more work than continuing to pay.
- Low impact, hard to replace: Investigate. Low value, deeply embedded, usually writing to other systems through an integration from a prior stack generation. Quantify the exit cost before deciding.
The bottom-left quadrant is your immediate list. The bottom-right is where the real lock-in problem lives. Companies that have replaced SaaS tools know this quadrant well — it’s where the migration surprises come from.
Output: Every tool placed in a quadrant. The bottom-left is your immediate sunset list.
Step 5 — Plan your exits before you serve notice
The most common migration failure we see: the replacement wasn’t ready when the contract ended.
Before canceling anything, build the exit criteria for each tool on your sunset or consolidation list. Four checkpoints: historical data exported to a format your company owns; the replacement function live and receiving data in the target system; any downstream tool re-pointed to the new source; contract renewal date mapped so you’re timing the exit, not scrambling after an auto-renewal.
Start with easy-to-replace tools. Quick exits build momentum and free budget before you get to the embedded-dependency tools that need real migration work. Never start with a hard-to-replace tool. You’ll hit the lock-in problem before you’ve freed up the resources to solve it.
Data portability is the contract term most teams forget to verify. If you can’t export your own records without a support ticket, that tool has more leverage over your exit than the contract suggests. The historical data question — what happens to the records in the tool you’re sunsetting — needs an answer before you serve notice, not after.
Output: Per-tool exit plan with criteria checklist, target completion date, sequence priority, and estimated exit cost.
Step 6 — How often should you audit your GTM stack?
Run a full GTM stack audit annually, timed to your budget cycle. In between, run a quarterly sweep of monthly active user data and a monthly gate on new tool requests. A one-time audit is a one-year fix. Stacks grow back because adding a tool is always faster than removing one.
The three cadences in practice: monthly, every new tool request goes through the overlap matrix and TCO calculation; any new tool should displace or consolidate something on the inventory. Quarterly, sweep for tools where MAU dropped below 25% of licensed seats. These have already become inertia holds, even if nobody said so. Annually, full re-run, recalculated TCO, re-scored ROI matrix, timed to the budget cycle.
The cadence is only as useful as the inventory. The spreadsheet from Step 1 needs a permanent home and a named owner. The teams that stay lean are the ones where “we already have something that does that” is a complete answer, which requires a list someone is keeping current.
The SaaStr AI Annual 2026 consensus across six verticals put it plainly: AI is now the commodity; the moat is data layer depth. 5 Source 5 SaaStr AI Annual 2026, June 11, 2026. Consensus across 6 verticals: AI features are table stakes. Moat = data layer architecture and integration depth. A 22-tool stack paying $3M for AI features now available for $20 per month from a foundation model API isn’t buying capability. It’s paying for lock-in.
Output: Governance calendar with named owner, monthly gate process, and annual re-audit date set.
What the audit recovers
Budget recovered from inertia hold tools is working capital, not a cost line trimmed but capital redirected. It funds owned infrastructure. It funds the AI agent architecture your stack doesn’t have a data layer to support. It funds pipeline experiments your competitors can’t run because they’re still paying $75K a year in headcount to maintain a tool three people actually use.
The Aurasell CEO made the $4.65M number public so everyone else didn’t have to guess. The question isn’t whether your stack looks like theirs. It’s which tools on your renewal list are actually earning their line item, and which are there because removing them was always next quarter’s problem.