TL;DR

• Headcount growth and feature need are two different variables. Moving up a tier because your team got bigger, without checking feature usage, is a quiet source of SaaS waste.

• The test: pull about 90 days of feature usage, set it next to the tier’s feature list and upgrade only if you can document a gap.

• Start the test 90 to 120 days before renewal, so you have room to downgrade, negotiate or switch plans before an auto-renewal locks you in.

• Right-sizing cuts both ways. Sometimes the honest result is that a tier is underpowered and an upgrade is the right call.

Why Does Headcount Growth Lead to SaaS Tier Overspending?

Headcount growth gets treated as a proxy for feature need, and that substitution is where the waste starts. When a company goes from 40 to 80 employees, the instinct is to double the seats on every plan and often bump the tier along with it, assuming that more people automatically means more advanced features.

In practice, new hires often use the same core features the original team used. A sales rep added in month 14 needs what the sales rep hired in month one needed. They don’t need the enterprise tier’s custom API access or advanced reporting dashboards just because the roster got longer.

The gap between what you’re billed for and what’s actually opened in the product is the license optimization opportunity, and it tends to widen when tiers are bumped on headcount alone. A company that pays for advanced features across its whole team is often paying premium rates for basic usage.

The reverse also happens. A team can outgrow a tier without adding a single person, because a new workflow or a new department starts depending on a feature the plan doesn’t include. Headcount doesn’t tell you either way. Usage does.

What Should a Feature-Usage Test Include Before Renewal?

A feature-usage test is a short review you run against each SaaS contract before its renewal date. It asks one question: which features on this tier did we actually use, and which would we miss if they were gone?

Start 90 to 120 days before the renewal date. That window leaves time to negotiate, downgrade or move to another vendor. Once you’re past the notice period, many contracts roll into another cycle at the existing tier regardless of what the review finds. For how auto-renewals and notice windows work in practice, see the ShiftControl article “SaaS Renewal Traps.” For the full process, see “SaaS Renewal Checklist.”

For the tier decision specifically, the test needs three things:

• Feature usage logs: which specific features within the tier were accessed over roughly the last 90 days, not just login activity. A user who logs in daily may only touch two features.

• Tier feature list vs. actual usage: a side-by-side of everything the current tier unlocks against what’s actually been touched. Anything on the left with nothing on the right is what you’re paying for and not using.

• A documented feature gap before any upgrade: if someone wants the next tier, they name the specific feature, the team that needs it and the work it unblocks. “We have more people now” doesn’t count as a gap.

The hardest part is gathering the data consistently across every app before the renewal clock runs out. Many teams without a dedicated IT person skip the review for exactly that reason, and tiers get renewed on autopilot.

How Do You Read the Results?

The side-by-side usually lands in one of three places.

Usage matches the tier. The features you pay for are the features people use. Renew at the current tier, and use the seat count and renewal date to negotiate.

Usage sits well below the tier. Most of the premium features are untouched. Ask the vendor about the next tier down, and check which of the unused features, if any, a specific team would genuinely miss. If none, downgrade at renewal.

Usage exceeds the tier. People are working around limits, paying for add-ons or asking for a feature the plan doesn’t include. This is the documented gap, and an upgrade is justified.

In all three cases, the decision rests on what people actually did in the product, not on how many people are on the payroll.

What Role Does Shadow IT Play in Tier Right-Sizing?

You can’t right-size a tier for a tool you don’t know exists, so apps bought outside procurement skew your picture of what each team already has. Before you renew, check which connected apps each team uses so you don’t pay twice for overlapping features.

How Does ShiftControl Help With Right-Sizing SaaS Tiers?

ShiftControl is purpose-built for Google Workspace and helps companies without a dedicated IT hire run a disciplined renewal process. The SaaS spend view shows cost by department, tool and employee, plus contract-renewal dates, once you’ve entered each app’s cost data. With every renewal date in one view, you can see which contracts hit the 90-to-120-day window next instead of finding out after the notice period.

ShiftControl also surfaces the apps connected to your Google Workspace and the OAuth scopes they hold, which helps you find tools that never went through procurement. Setup takes as little as 10 minutes, using Google Workspace admin single sign-on.

Pricing is $10 per user per month, with everything included, billed yearly. Startups can get $2 per user per month for their first 10 seats in the first year.

Frequently Asked Questions

Does adding headcount always require upgrading a SaaS tier?

No. New hires often use the same features existing employees already use. A tier upgrade should be driven by a documented feature gap, not by seat count alone.

How often should I run the feature-usage test?

Run it 90 to 120 days before each contract renewal date.

What’s the difference between license optimization and cost-cutting?

License optimization matches spend to actual usage, which sometimes means upgrading a tier that’s underpowered, not just downgrading ones that are overpowered.

Can shadow IT affect contract negotiations?

Yes. Unaccounted tools often duplicate functionality already paid for in an existing tier, which weakens your negotiating position if you don’t know the overlap exists beforehand.

Do I need a dedicated IT team to run this process?

No. ShiftControl is purpose-built for companies without dedicated IT, with setup in as little as 10 minutes via Google Workspace admin single sign-on.

About ShiftControl

ShiftControl combines provisioning and access, SaaS spend visibility, app-permission insight and incident response in one system purpose-built for Google Workspace, with no dedicated IT hire required. Cyber incident response (IR-1, via Blackpanda) is included in every subscription rather than sold as an add-on. ShiftControl is SOC 2 Type 2 compliant and ISO 27001 certified. It also signed the CISA Secure by Design Pledge in 2024.

If your next renewal is approaching and you want your spend and renewal dates in one place before you sign, start a 14-day free trial of ShiftControl (no credit card required) or book a demo.