Run the pack internally when
One or a few renewals are in play, the exports are already reachable, and an internal owner can finish the reconcile and owner review before the notice date.
Renewal usage evidence without a platform
How CFOs Assemble SaaS Renewal Usage Evidence Without Torii, Zylo, or CloudEagle.
Build a finance-led usage evidence pack from invoices, SSO, admin lists, and vendor reports. A SaaS management platform is not a prerequisite for the next renewal conversation.
The fork
The quote came back at last year's seats. The board wants unused-seat proof.
The renewal landed at last year's seat count, or the vendor sent a usage screenshot as if that settled the number. The board asked what is unused. IT said you would need Torii, Zylo, or CloudEagle to prove it. The notice window is inside 30 to 90 days.
SaaS management blogs treat a utilization dashboard as the prerequisite to negotiate. CloudEagle's June 30, 2026 post is the current example of that "walk in with the usage data you actually need" pitch. It is a product path. It is not proof that finance cannot assemble evidence without buying the platform first.
You have three next steps: assemble a light evidence pack from exports you already have, buy an SMP for continuous utilization ops across a large estate, or hire an independent Keep / Cut / Renegotiate / Replace review.
SaaS Spartan is not a SaaS discovery or management platform and not a usage-dashboard product. It is an independent, done-for-you review. This page covers the sources, how to assemble the pack, how Keep / Cut / Renegotiate / Replace apply to the findings, when an SMP fits, and when to get help.
The first conversation with Josh Roybal is free. No documents are required.
Primary source used as a SERP peer to contrast, last checked 2026-09-22: CloudEagle's renewal usage-data post (June 30, 2026). Cited for the "buy a dashboard to walk in prepared" pattern only. Illustrative seat counts and dollar-per-user tables from that post are omitted. Confirm current products and terms with each provider.
Definition
What a renewal usage evidence pack is (and is not).
A renewal usage evidence pack is a time-boxed, vendor-specific (or short-list) artifact: a one-pager plus dated source exports. It shows contracted seats, assigned seats, active and needed seats, dormant candidates, a proposed renewal count, and owner sign-off. That is enough for a board packet or a vendor conversation on rightsizing.
"Without a platform" does not mean without evidence. It means you choose how evidence is gathered, and you do not treat a discovery-product login as the decision.
This page is usage and rightsizing evidence: how many seats or what tier you actually need. Peer price evidence is a different packet. How to get that without buying Tropic, Vendr/Vertice, or Zip lives on SaaS pricing benchmarks without a platform.
Assembling proof of unused seats is also not the same as finishing the true-down or rightsizing negotiation. Once the pack exists, the seat-cut and clause asks live on true-up vs true-down.
The pack is also not the same as staffing the renewal queue. Who owns each mid-list and tail row when a platform only covers the top lives on staffing the mid-list SaaS renewal queue.
Sources you already have
No SMP required to start the pack.
Pull types finance already touches. This is not a 2,000-word inventory manual, and it is not discovery automation.
Sources for a renewal usage evidence pack, what each contributes, and the limit that keeps the pack honest
| Source | What it contributes | Limit / caveat |
|---|---|---|
| Invoices / order forms / AP | Contracted seats, SKU or tier, annual dollars, renewal and term dates. | Shows what you pay, not who is active. |
| IdP / SSO | App assignments and last successful login windows from Okta, Entra ID, Google Workspace, or the equivalent you already run. | Login is not feature engagement. Exclude service accounts carefully. |
| Vendor admin seat / user lists | Provisioned users, roles or tiers, and last activity if the console exposes it. | The vendor UI is an opening position, not a neutral fact. |
| Vendor usage / activity reports | In-app activity beyond login (creates, tickets, sends, or the priced action for that SKU). Request the export if the admin list stops at login. | Define "active" the same way for the whole pack. |
| HRIS / offboarding list | Terminated or leave users who are still licensed. | High-confidence Cut candidates. |
| Expense / card lines (light) | Tools paid outside the central invoice. | A pointer only. Discovery depth lives on shadow IT. |
| Department owner attestation | A short answer to "Can you name the workflow this seat supports?" | Catches shelfware SSO will not. |
Finding dormant, overlapping, and former-employee seats across the estate is the job of duplicate licenses. This page uses those sources for a vendor-specific renewal pack. It does not rebuild the inventory SOP.
The finance moves
How CFOs assemble the pack: reconcile, define active, one-pager.
Ordered assembly work. This is not a 90-day product calendar.
01
Pull the notice or renewal date first
Missing the window locks last year's count. Treat every renewal as a decision before that date. Notice hygiene lives on auto-renewals.
02
Reconcile four counts
Contracted seats from the order form, assigned or provisioned seats from identity or the admin list, active seats under your written definition, then needed seats: active plus documented exceptions plus a small buffer only if finance owns the buffer rule. Write the four numbers on the same page.
03
Define "active" in writing before the vendor call
Example practice: a successful human login and/or a meaningful in-app action inside a window you choose and document (30, 60, or 90 days). Record seasonal, board, and integration exceptions. Prefer in-app activity over SSO-only where the priced capability is the thing you are buying. The window is playbook practice you define. It is not a SaaS Spartan outcome guarantee.
04
Run an owner review on dormant candidates
Send the dormant list to managers with a short reply window. Reclaim or deprovision where policy allows before the ask. Re-harvesting unused seats inside the same committed count is not the same as lowering the commitment. The seat-cut and true-down asks live on true-up vs true-down.
05
Build the one-pager fields
Vendor; SKU or tier; contracted seats; assigned; active; dormant candidates; proposed renewal seats; annual dollars at contracted versus proposed; notice date; Keep / Cut / Renegotiate / Replace lean; evidence sources and export dates; owner. That is the artifact you put in front of the board or the vendor.
06
Treat vendor-dashboard divergence as a reconciliation request
If the vendor screenshot and your four counts disagree, ask for line-item detail. Do not surrender the pack because a seller-controlled dashboard shows a different number.
Language for the board
How to decline last year's seat count without buying a platform first.
Contracted seats are not the same as needed seats. We assembled a usage evidence pack from invoices, identity or SSO exports, admin lists, and vendor activity reports, with export dates on the page.
The proposed renewal count is pending named owner exceptions. The decision is Cut or rightsize the committed count, or Renegotiate the commercial, not "buy a discovery platform before we can talk to the vendor."
We will not rubber-stamp last year's seats for lack of a dashboard, and we will not invent a utilization percentage the board cannot stand behind.
Keep / Cut / Renegotiate / Replace
Apply the four decisions to pack findings.
The canonical four decisions live on Keep / Cut / Renegotiate / Replace. This table applies them to usage-evidence findings. Cut when the seats have no business job. Replace only after the replacement economics gate.
Keep, Cut, Renegotiate, or Replace applied to renewal usage evidence
| Pack finding | Keep | Cut | Renegotiate | Replace |
|---|---|---|---|---|
| Former-employee or zero-activity seats | Only if a named owner can show a current workflow those seats still serve. | No business job. Reclaim first, then lower the commitment. Re-harvesting is not enough if the bill stays. | If the vendor blocks a mid-term drop, write the reduced quantity into the renewal. | Not the first move. Unused seats do not require a new product. |
| Healthy usage, a weak unit price, or one-way true-up paper | Usage is real and the commercial position is already acceptable. | Only the unused remainder, not the working seats. | Price and terms, plus true-down or rightsizing language. Clause depth lives on true-up vs true-down. | Only if another product clears Year-1 net economics before the notice window closes. |
| Capability still needed after consolidation | The surviving product earns its place and the remaining seats are active. | Seats on the product you are leaving, once the workflow has moved. | Rightsize the surviving seat line. Do not keep paying for both stacks. | Same net-economics gate. Subtract switching cost before calling a cheaper stack a saving. |
| Another product is on the table | Switching would not create enough net value. | If the current product has no remaining job after the move. | Use a genuine alternative as leverage for seats, price, and flexibility. Method depth lives on how we negotiate. | Only after replacement operating, migration, and other switching costs still beat the current stack on a net basis. |
This table applies the four decisions. It does not redefine them. Peer price evidence stays on SaaS pricing benchmarks without a platform.
Several renewals need packs this quarter and finance lacks bandwidth? Talk to Josh. The first conversation is free. No passwords or system access required. You leave with a read on DIY pack vs SMP eval vs Savings Map sprint, not a promised unused-seat percentage. Talk to Josh →
When a platform fits
When a SaaS management platform is worth it.
An SMP fits when the bottleneck is continuous utilization, discovery, and reclaim ops across a large estate, the team will operate the platform, and renewals are ongoing workflow, not a one-time board packet.
Orientation only: Torii-class tools are built around discovery and usage workflows; Zylo-class tools around spend plus a renewal system of record and negotiation support; CloudEagle-class tools around utilization plus renewal-brief automation. That is enough to orient. It is not a feature matrix. Head-to-heads live on SaaS Spartan vs Torii, SaaS Spartan vs Zylo, and SaaS Spartan vs CloudEagle. The three operating models live on platform vs independent advisor.
Rejecting SMPs because you dislike another login is as weak as buying one because a blog said you cannot negotiate without a dashboard.
DIY or independent review
DIY pack vs independent Savings Map.
Bring an independent Savings Map when
Several renewals land in the same cycle, the vendor disputes usage, there is no bandwidth, or you need verified first-year savings without adopting discovery software.
The first conversation is a free spend assessment. A full engagement has no upfront consulting fee. The fee is a flat 25% of verified first-year savings you approve and implement. For replacements, that is Year-1 net after material implementation, migration, replacement operating, maintenance, AI/API, and other switching costs. Measurement runs Identified, then Approved, then Implemented, then Verified. Most first reviews take roughly 2 to 3 weeks once required data is available. SaaS Spartan is not a platform and not a usage-dashboard product.
See how it works, pricing, Keep / Cut / Renegotiate / Replace, and who it is for (roughly 100 to 500 people and $500K-plus software and AI spend). Start on contact if you already have the quote.
The free conversation is not a delivery of Torii-class telemetry or proprietary unused-seat percentiles.
Questions finance asks
Short answers you can quote.
What is a SaaS renewal usage evidence pack?
A renewal usage evidence pack is a time-boxed artifact, usually a one-pager plus dated exports, that reconciles contracted seats on the order form with assigned seats from identity or admin lists, active/needed seats under a written definition, and dormant candidates with owner review. It exists to support a board or vendor conversation on rightsizing. It is not a SaaS management platform login, and it is not the same thing as a peer-pricing benchmark packet.
How do mid-market CFOs assemble usage evidence without Torii, Zylo, or CloudEagle?
Pull what you already have: invoices and order forms for contracted counts and dates; IdP/SSO assignment and last-login exports; vendor admin seat lists and activity reports; HRIS terminations still licensed; and light expense-line checks for tools outside central AP. Reconcile contracted to assigned to active to needed, define active in writing, run a short owner review on dormant seats, and put proposed renewal seats on one page with source dates. You do not need a discovery platform to start; you need consistent definitions and exports you can stand behind.
Do we need a SaaS management platform to prove unused seats at renewal?
No. Not for a single renewal or a short list of renewals when invoices, identity, and admin exports are reachable and someone owns the reconcile before the notice window. An SMP helps when continuous utilization, discovery, and reclaim across a large estate is the real bottleneck and the team will operate the software. Buying Torii, Zylo, or CloudEagle is not a prerequisite to assembling a defensible pack for the next vendor call.
When is a SaaS management platform worth it?
When the gap is ongoing visibility and reclaim workflow across many apps, renewals are continuous operations work, and finance/IT will run the platform, not when the only prompt is a blog that says you cannot negotiate without a dashboard. For the broader operating-model choice (SMP vs procurement platform vs independent DFY), use SaaS Spartan's platform vs independent advisor page; for named product compares, use the relevant vs or alternatives pages. This page stays on the evidence-pack decision.
How is usage evidence different from pricing benchmarks without a platform?
Usage evidence answers how many seats or what tier you actually need. Peer pricing evidence answers whether the unit price is out of line with comparable deals. Mid-market finance often needs both, but they are different packets. Assemble usage/rightsizing evidence with this playbook; for peer price evidence without buying Tropic, Vendr/Vertice, or Zip, use SaaS Spartan's pricing benchmarks without a platform page.
When is an independent Keep/Cut/Renegotiate/Replace review the better next step?
Prefer an independent Savings Map when the pack sources exist (or can be gathered quickly), several renewals land in the same cycle, the vendor disputes counts, or the team lacks bandwidth to finish owner review and the ask before the notice date, and you want fees tied to verified first-year savings rather than another discovery subscription. SaaS Spartan's first conversation is free; full engagements charge a flat 25% of verified first-year savings with no platform fee. The conversation is a read on DIY pack vs SMP vs DFY sprint, not a delivery of proprietary unused-seat percentiles.
Related pages
Keep these jobs on their own pages.
True-up vs true-down
How to cut seats at renewal or negotiate true-down rights. This page stops at the evidence pack.
Pricing benchmarks without a platform
Peer price evidence without Tropic, Vendr, or Zip. Different from usage and rightsizing proof.
How we negotiate
Usage, terms, and credible alternatives. The evidence model this pack applies, not a playbook rebuild.
Platform vs independent advisor
The three-model essay. This page stays the usage-evidence-without-an-SMP fork.
Staff the mid-list renewal queue
Who owns middle and tail renewals when a platform only covers the top. Different from assembling the pack.
Talk through the pack with Josh.
The first conversation with Josh Roybal is free. Optional: bring the renewal quote or order form and a simple contracted-versus-active view, or the one-pager if you have started it. No invoices dump, passwords, or system access required to start. We will not promise a percentage seat cut or savings. See how it works and pricing.