© 2026 Procr
Most mid-market companies never had a procurement team. They had a CFO, a VP of Operations, a CIO, and a growing pile of SaaS subscriptions that nobody fully owned. Today, the average mid-market company spends $7,300 per employee on software annually, with 81% of that spend controlled by business units rather than any central function (Zylo, 2026 SaaS Management Index). Without a structured buying process, that money disappears into a sprawl of auto-renewing contracts, redundant tools, and unused licenses.
This guide explains how to build a functional SaaS procurement process using the people and workflows you already have, without waiting for headcount approval on a dedicated procurement role.
Companies routinely underestimate what decentralized, ungoverned SaaS buying actually costs. Zylo's 2026 SaaS Management Index reports that the average organization leaves 36% of its SaaS licenses unused. For a company with $3 million in annual software spend, that is roughly $1.08 million in paid-for capacity that nobody is using.
The causes are predictable. Department heads buy tools to solve immediate problems without checking whether a license for equivalent software already exists in the stack. Finance cannot see the full picture because 51% of SaaS expenses are miscategorized in expense reporting systems as something other than software (Zylo). Renewals happen silently: vendors are contractually entitled to auto-renew, and few mid-market teams have a reliable system for tracking when those windows open.
The result is not one large procurement mistake. It is hundreds of small ones, compounding year over year, each individually too small to audit but collectively large enough to matter. A 140-person professional services firm that audited its SaaS stack found 34% of licenses unused and reduced annual spend by approximately $620,000 after consolidating platforms and renegotiating contracts (businesssaveguide.com, 2026).
The good news: fixing this does not require a procurement department. It requires a defined process.
The most common failure mode in mid-market SaaS buying is the absence of a single person who sees the full vendor landscape. IT sees infrastructure tools. Finance sees the P&L line items, partially. Department heads see their own subscriptions. Nobody sees all three.
Before building any process, assign a SaaS owner: typically a finance operations manager, VP of Finance, or senior IT lead. This person does not approve every purchase. They maintain the vendor register, track renewal dates, and serve as the mandatory first point of contact for any new software request above a defined threshold, typically $2,000 annually.
This is not a full-time role. At a 100- to 300-person company, it amounts to roughly 20-40% of one person's time, depending on portfolio size. The job is visibility and coordination, not evaluation. Evaluation happens through a standardized intake process.
Every new SaaS purchase should go through a brief intake review before any vendor demos happen. The goal is to capture enough information for a decision without creating friction that pushes buyers toward shadow purchasing.
A functional intake form covers five questions:
A five-question form submitted in writing forces the requester to articulate the justification and creates a record you can reference at renewal. It also surfaces redundancy early: 63% of companies with formal SaaS buying processes find at least one existing tool that overlaps with a newly requested one (Zylo, SaaS Procurement Best Practices).
Route intake submissions to the SaaS owner. For purchases under $5,000 annually, approval from the SaaS owner and the department manager is sufficient. For purchases over $5,000, add a finance sign-off. For anything involving customer data, employee data, or regulated data, add a security review step before approval.
Without a dedicated security team, vendor security reviews feel complex. They do not need to be comprehensive to be effective. For mid-market SaaS purchases, a four-question checklist handles the majority of meaningful risk:
These four questions catch the most common security gaps without requiring security expertise to administer. Any vendor that cannot answer all four clearly should be escalated for additional review before purchase. The stakes are real: 67% of data breaches involve third-party vendors, with average incident costs of $4.3 million (Auditive, 2025 SaaS Due Diligence Checklist).
Document vendor responses in your central register alongside contract terms. This becomes the foundation for annual vendor reviews and serves as evidence of due diligence if questions arise later.
Most mid-market teams negotiate SaaS contracts only when renewal pressure makes it unavoidable, which is the worst possible time. According to Tropic's analysis of more than $15 billion in software spend, companies that begin renewal negotiations six months out achieve average savings of 39%, compared to 14% for teams that start 30 days before the deadline.
The difference comes from leverage. Thirty days before renewal, a vendor knows you have limited time to evaluate alternatives. Six months out, switching costs are lower, and the vendor has more budget-period flexibility to offer concessions.
For new purchases, the same logic applies. Never accept the first pricing presented. Benchmarking current market rates against similar-stage companies matters because vendors price according to what they think you can pay. Mid-market buyers who benchmark before entering negotiations consistently find that list prices sit 20-30% above what comparably sized companies actually pay (Vertice, 2025 SaaS Inflation Stats).
When negotiating, prioritize three contract terms specifically: the price escalation cap (the ceiling on how much the vendor can raise your rate at renewal), the notice period required to cancel, and the termination-for-convenience window. These three terms determine the long-term cost of a contract far more than the first-year price.
Renewal management is the most mechanical part of SaaS procurement, and it is where mid-market companies consistently lose money. A tool no one monitors auto-renews. The notice period passes. Finance gets charged for another year of something they expected to cancel.
The fix is a shared renewal calendar with milestone alerts. Every vendor contract should be recorded with three dates: the contract end date, the notice deadline (30, 60, or 90 days before the end, depending on the contract), and a review trigger date set 90 days before the notice deadline. That review trigger is when the assigned business owner checks usage data and decides whether to renew, renegotiate, or cancel.
Maintain this in a shared document with automated date reminders at a minimum. Assign each renewal to a named individual, not a team or department. Shared ownership is no ownership.
The common objection is that maintaining this calendar takes too much time. The accurate accounting is the opposite: without it, renewal decisions happen reactively, under deadline pressure, with no time to run a competitive evaluation or prepare negotiation materials. A renewal caught 90 days out takes roughly two hours of work. A renewal caught at the deadline with an unfavorable auto-renew clause takes significantly more and usually ends in overpaying.
A functional SaaS procurement process at a 100-300 person company does not require specialized software, though it scales better with it. The minimum viable version has four components:
Companies with this structure in place identify an average of 15-20% in potential savings during the first full quarterly review, primarily from unused licenses and overlooked auto-renewals (Zylo, 2026 SaaS Trends). The first review typically returns the time invested many times over.
The more sophisticated version, once this process is running, adds contract storage with automated term extraction, renewal reminders keyed to specific notice deadlines, and peer benchmarking against what comparable companies pay for the same tools. That is where purpose-built contract management platforms earn their keep. But the underlying process has to exist first, and it can start today with the people you already have.
Zylo's 2026 SaaS Management Index reports that the average organization leaves 36% of its SaaS licenses unused. For a company spending $3 million annually on software, that is roughly $1 million in unused capacity. Shadow IT and untracked subscriptions compound the problem further, with benchmarks indicating 30-40% of total SaaS expenditure is wasted in organizations without centralized procurement governance.
Yes. At 200 employees with a portfolio of 50-100 active SaaS tools, a single designated SaaS owner spending 20-30% of their time on the function can manage intake, renewal tracking, and vendor reviews effectively. The role becomes unmanageable only when it lacks supporting structure: a vendor register, an intake form, and a renewal calendar. With those in place, one person can run the process without it becoming a full-time job.
Flag renewals in your calendar 120 days before the contract end date and begin the formal review at 90 days. This timeline gives the business owner time to assess usage, run a brief competitive check if warranted, and start vendor conversations while leverage still exists. Tropic's analysis of $15 billion in software spend shows teams that start negotiations six months out save an average of 39%, while teams starting 30 days out average 14%.
At minimum, request a current SOC 2 Type II report, confirm AES-256 encryption at rest and TLS 1.2 in transit, verify SSO compatibility with your identity provider, and obtain the vendor's breach notification policy in writing. These four checks address the most common compliance gaps and establish a documented due diligence record. For tools accessing customer PII or financial data, add a data processing agreement review before signing.
Most mid-market teams identify 15-25% in potential savings during the first year of running a structured process, primarily through unused license reclamation, tool consolidation, and improved renewal timing. Tropic's data shows a 15.5% average savings rate across $362 million in negotiated software spend in H1 2025. The first quarterly portfolio review of an unmanaged stack consistently surfaces immediate savings opportunities that far exceed the time invested in setting up the process.
Procr
See what Procr does with your real vendor portfolio.