SaaS Renewal Management for Series B Companies
At 40 to 80 tools, informal tracking stops working, even for teams that have been reasonably diligent.
I spent years on the vendor side of enterprise software, and by Series B, most companies have a SaaS portfolio large enough, often 40 to 80 tools, that informal tracking genuinely stops working, even for teams that have been reasonably diligent up to this point.
Where Series B sits on the renewal ladder
Seed
A dozen tools or fewer, tracked from memory.
Series A
Tool count grows faster than process.
Series B
40 to 80 tools, informal tracking breaks.
300 to 500 people
100+ tools, volume forces a decision.
Departments now run their own stacks, several contracts are on a second or third renewal, and the original owner may have moved on without a clean handover.
Why this stage is different
Departments have matured enough to have their own tool stacks, several early contracts are coming up for a second or third renewal (often with unnoticed price increases already baked in), and the person originally responsible for renewals may have moved into a different role or handed it off without a clean transition.
What to prioritize at this stage
- Reconcile pricing history, not just current contracts. This is often the first point where a multi-year pricing pattern becomes visible, tools that have quietly increased two or three renewals in a row without anyone questioning it.
- Formalize cross-functional ownership. With multiple departments now running their own tools, a single informal owner is no longer realistic; build a clear ownership map across finance, IT, and department leads.
- Address consolidation opportunities directly. By this stage, overlapping tools across departments (multiple analytics tools, multiple project management tools) are common enough to be worth a deliberate consolidation review.
A practical starting point
Build a full renewal calendar with assigned owners across every department running SaaS tools, and pull pricing history for your top 15-20 contracts by spend to check for unchecked multi-year increases.
Where volume forces a deliberate call on process versus headcount.
SaaS renewals without a dedicated procurement functionHow to borrow the discipline without adding the department.
The SaaS renewal guide for CFOsPortfolio-level governance once contract count passes memory.