Audit a 25% Workspace Jump Before Switching

A price jump is a control event

The invoice lands, and the line for your core suite is 25% higher because the Plus introductory price ended on 2026-10-20. The old price is still in the renewal math.

A jump like that should trigger a short audit and a logged stay-or-switch decision, not another unexamined invoice. SaaS costs expand through a hundred small, individually reasonable decisions, including added seats, auto-renewals, and orphaned licenses, without one person seeing the whole stack. Nearly 30% of SaaS spend goes unused each year.

For Google Workspace, the audit separates a plan change from a billing-plan change and from the end of introductory pricing.

The audit does not need a vendor call. It needs the invoice, the admin console, and a place to write the result. Make the decision visible to the next person who owns the stack.

The invoice carries the numbers

Starter is $7 per user per month when billed yearly, Standard is $14 per seat per month, and Plus is $22 per user per month when billed yearly. That introductory price was limited to new customers, the first 20 users added, and a 12-month period, after which standard pricing applies.

Annual/fixed-term billing costs less per user per month than flexible billing. Starter, Standard, and Plus can be purchased for up to 300 users. If the invoice line does not match the plan you expect, re-run it before you challenge the number.

Keep the invoice line next to the admin console. The line should show the plan, seat count, billing period, and per-seat amount. If the invoice and console disagree, the console tells you what you are actually paying for.

A short checklist finds the cause

For a ten-seat stack, keep the audit to five moves: confirm the tier, check the billing plan, match the invoice, re-run the line, and log stay or switch. Each move is short enough to finish before the next meeting.

• Confirm the tier and per-seat price on the invoice.
• Check whether the account is on annual/fixed-term or flexible billing.
• Match the invoice line to the admin console and note whether introductory pricing ended.
• Re-run the line and compare paid seats to meaningful activity.
• Log stay or switch, the reason, and the follow-up control.

For each application, compare paid seats with meaningful activity over the previous 90 days. A 30-day window may flag temporary absences, and a 12-month window may be too broad to reveal idle seats. A small gap means the tool is probably earning its place; a large gap makes the price jump a chance to remove waste before you pay more.

Meaningful activity is the behavior that justifies the seat: sending mail, editing documents, sharing files, or using the app in the workflow. If a person is active in one tool but idle in another, question the idle tool. Write the gap next to the invoice line so the next owner can see it.

The log is the deliverable

Write the decision in the same place you write the ops log. Record the plan, billing plan, seat count, activity gap, and the reason for staying or switching. Stay when the tool is active, the billing plan is the cheaper one, and the increase is explained. Switch when the activity gap is large, the billing plan is avoidable, or the tool no longer fits the workflow.

Keep the log short enough to read in a meeting: what changed, what the evidence showed, and what control will catch the next change. If the answer is only a price, the audit is incomplete.

An audit without follow-up controls provides only about two quarters of benefit. The control can be a simple rule: any future increase above the logged price triggers the same audit.