Your SaaS Bill Has 214 Tools and 41% Had Zero Logins Last Month

It is Monday, 9:04 AM. Your CFO opens the SaaS ledger in Vendr. 214 active contracts. She sorts by seat utilization. The top row is a data-observability tool that renewed May 12th for $84K, 40 seats provisioned, 6 active in July, three of the six are engineers who left in Q1. The next row is a sales-engagement platform on a $118K annual contract, 92 seats, 34 logins in the last thirty days, an auto-renewal notice landing October 4th.

She scrolls. 88 of the 214 tools show zero logins in July. Fourteen are duplicates of a tool the company already pays for on a different contract. Nine sit on an auto-renewal inside the next 90 days with no owner listed in the procurement Notion. One is a design-review tool the last CTO signed a two-year enterprise deal for in 2024 that nobody has opened since December. The finance line for software runs $2.4M against a headcount of 180.

Pull the last four quarters. Software spend grew 34 percent year over year against a 12 percent headcount growth. 41 percent of tools by count and 22 percent by dollar sit on zero or single-digit monthly logins. $340K of annual spend is shelfware the CFO could cancel this month without a single team noticing. The board deck shows software as a percentage of revenue. The board deck does not show that a third of the software line is paying for tools nobody opens.

Vendor management is a function. Most Series B and C teams have not staffed it because the first thirty tools were bought by the founder on a personal card and expensed. The count grew to 214 across five departments, a Vendr instance the previous head of ops half-configured in 2024, a Ramp card feed two finance analysts reconcile, an Okta directory with 340 apps registered against 214 paid contracts, a "Software" folder in Drive with 940 signed order forms nobody indexed, and a Notion page listing 62 tool owners against 214 vendors. The function lives in the gap between the CFO who owns the spend line, the head of IT who owns the SSO directory, the procurement analyst who chases renewals, the department heads who signed the order forms, and the security lead who cares about the vendor risk register. On the org chart it sits under Finance. In practice it sits inside a Google Sheet the ops lead rebuilds every second Friday.

The 214-tool shelfware math

Pull every active SaaS contract in the last twelve months. Log vendor, annual cost, seat count, active seats last 30 days, SSO login count last 30 days, renewal date, contract owner, department, and overlap with tools already under contract. Count tools with zero logins in the last month. Count tools where active seats sit under 40 percent of paid seats. Count contracts inside 90 days of renewal with no assigned owner. Most teams past Series B find 35 to 50 percent of tools by count are underused, 18 to 28 percent of annual spend maps to shelfware, and one in four renewals inside 90 days has no owner ready to negotiate.

Walk one tool. The data-observability contract renewed May 12th at $84K for 40 seats. Provisioned by the previous VP Engineering in 2024, championed by two staff engineers who left in Q1, migrated onto Okta in March. Login report shows 6 active seats in July, 4 in June, 7 in May. The renewal auto-triggered because the notice window closed April 12th, thirty days before renewal, and the calendar reminder sat in the departed VP Engineering's Google Calendar. Vendr flagged the contract as high-risk in February. The flag sat in a Vendr dashboard the CFO opens on the third Wednesday of the month.

The team that should own this knows it is broken. The CFO reviews the software line at month-close and reads a total against a budget. The head of IT sees SSO login data in Okta and does not tie it to the procurement contract. The procurement analyst tracks 214 renewal dates in a spreadsheet and negotiates the ten largest contracts by dollar. The department heads answer a quarterly software audit email in three sentences and move on. The security lead cares about SOC 2 evidence on the top 40 vendors and does not touch the long tail.

Hiring a procurement lead is the slow answer

The textbook fix is a senior procurement manager or a director of vendor operations. Loaded comp in the US runs $130K to $180K a year. Months one through three go to auditing the vendor list, mapping owners to contracts, and standing up a renewal calendar tied to the SSO login feed. Months four through nine are when shelfware spend drops from 22 percent of the software line to under 8, auto-renewals inside 90 days with no owner fall from 24 to under 4, and the first negotiation cycle claws back 12 to 18 percent on the top 40 renewals.

The fractional version is faster and stops at the same wall. Five to eight thousand a month buys ten to fifteen hours a week of senior procurement work. The first month rebuilds the vendor register and maps owners to renewals. The 214-contract volume keeps drifting because a fractional lead cannot pull SSO login data weekly, reconcile the Ramp card feed against the vendor register daily, catch every auto-renewal window before it closes, draft every negotiation brief on the top 40 contracts, and flag every duplicate tool inside a week.

Both versions assume the work is a person auditing a spreadsheet on a cadence. The work itself is reconciling the Okta login feed against the Ramp card feed against the Vendr contract register every day, flagging every tool crossing 30 days of zero logins the morning it happens, paging the contract owner 60 days before every renewal with a usage brief attached, drafting a negotiation memo on every top-40 renewal with three benchmark comparables and a proposed counter, catching every duplicate tool across departments inside a week, running a monthly shelfware digest the CFO reads before the finance close, and posting a vendor health note the CEO reads before the board pack. On 214 contracts with 340 apps in Okta and a rolling 90-day renewal window that is 36 to 48 hours a week of senior procurement work. No single hire clears that pile and holds the shelfware number at the same time.

What a fractional AI vendor management function does

Hand the Vendr contract register, the Okta login feed, the Ramp card feed, the Notion tool-owner map, the last four quarters of renewal outcomes, and the SSO app directory to a fractional AI agent. The agent does the work a procurement manager, a vendor operations analyst, and an IT ops lead would do together. The cadence is per-day on login reconciliation, per-week on the duplicate scan, per-60-day on renewal briefs, and per-month on the shelfware digest.

Every tool crossing 30 days of zero logins flagged the morning it happens. The data-observability tool crosses day 32 of zero logins on August 4th. By 9:14 AM the agent has posted a note in the CFO's Slack citing the $84K annual cost, the four departed champions, the May renewal decision, and a proposed 60-day non-renewal notice ready for the CFO to sign.

Every renewal briefed 60 days before the window closes. The sales-engagement platform on a $118K contract hits day 60 before renewal on August 5th. The agent drafts a two-page brief citing 34 active seats against 92 paid, benchmark pricing from Vendr's public dataset, three alternative vendors with feature parity, and a proposed counter of $76K on 40 seats routed to the VP Sales and the procurement analyst.

Every duplicate tool caught inside a week. The security team signs an order form for a new secrets manager on Tuesday. By Friday the agent has flagged that engineering already pays for the same tool on a different contract, cited both order forms, and paged the security lead with the overlap analysis before the new tool goes live.

Every Ramp charge reconciled against the vendor register daily. A $940 monthly charge appears on a Ramp card belonging to a departed marketing manager. The agent flags the charge, maps it to a tool not in the vendor register, and pages the head of marketing with a cancel-or-adopt decision inside 24 hours.

Every shelfware digest reconciled against three sources. The monthly digest shows software spend against the Okta login feed, the Vendr contract register, and the Ramp card feed. Fourteen tools move from active to shelfware because logins dropped below the threshold this month. The CFO reads a shelfware number tied to a live signal instead of a Vendr export from the third Wednesday.

The unit economics of a 214-tool ledger

A Series B company at $22M ARR running 214 SaaS contracts on a $2.4M software line is burning three specific things. The CFO, the head of IT, the procurement analyst, and five department heads spend a combined 10 to 16 hours a week on renewal chasing, license reconciliation, and duplicate-tool triage against a fully loaded hour of $180 to $310. That is $8K to $20K a month of senior time on work a live agent clears. The procurement analyst gets six to nine hours a week back inside the first sprint.

The cancellation line is the second one. Cutting the 88 zero-login tools and consolidating the 14 duplicates claws back $260K to $420K of annual spend the finance line stops carrying. On a $2.4M software base that is 11 to 18 percent off the line inside one quarter without touching a single active workflow. The WBR dashboard shows software as a percentage of revenue drop 40 to 80 basis points quarter over quarter.

The negotiation line is the third. Briefing the top 40 renewals with a usage cite and a benchmark counter clips 12 to 18 percent off the renewed price on average. On $1.6M of annual renewals inside the top 40, that is $190K to $290K of avoided spend the CFO books against the plan. The AR line picks up cash that used to feed shelfware.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to a Vendr seat than a procurement hire. Login reconciliation and shelfware flagging run in week one. Renewal briefs and duplicate scanning run in week two. The vendor health digest runs off a live feed before the sprint closes.

What changes after the sprint

Picture the same Monday, 9:04 AM moment, thirty days after the sprint ships. Your CFO opens the SaaS ledger. 192 active contracts. The data-observability tool shows a non-renewal notice sent July 8th, an executed cancellation dated August 12th, and $84K removed from the FY plan. The sales-engagement platform shows a renewal brief sent to the VP Sales August 5th, a counter accepted August 22nd at $76K on 40 seats, and $42K back to the plan.

By month-close the CFO reads a vendor health digest naming the 22 contracts cancelled this quarter, the six renewals negotiated below plan, the four duplicate tools consolidated, and a shelfware rate tracking to 6 percent against a prior baseline of 22. The procurement analyst runs point on the top ten negotiations because the agent cleared the audit. The department heads read a monthly usage note that names the two tools their team stopped using and asks for a keep-or-cancel signature.

If your SaaS ledger currently reads 214 contracts with 41 percent showing zero logins and a quarter of renewals landing without an owner, the version where every tool crossing 30 days of zero logins pages the CFO the morning it happens and every renewal briefs 60 days out is fourteen days away. Vendor management is a function. You can hire against it, you can retain a fractional procurement lead for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.