Your software changed its pricing. Here is the 30-minute response plan

A pricing email creates urgency, but switching immediately is rarely the cheapest response. The useful question is not whether the new price feels high. It is whether the software still creates more value than its realistic alternatives.

You can reach a defensible answer quickly if you use actual account and workflow data.

First ten minutes: audit usage

Export the user list and identify active seats, occasional users, service accounts, contractors, and accounts that should be removed. Then check which paid features the team actually used in the last 90 days.

Use vendor activity reports where they exist instead of asking managers to remember. Microsoft 365 usage reports, for example, expose adoption across services and can be viewed for defined reporting periods. Google Workspace’s Reports API provides per-user usage information that can support the same inventory. Usage is not value, but it is better evidence than a purchased-seat count.

Next ten minutes: calculate the real increase

Include taxes, annual discounts, usage charges, minimum commitments, required add-ons, support tiers, and the cost of seats you cannot remove. Compare annual totals rather than headline monthly prices.

Then calculate cost per active user and per important workflow. A product used by ten people to run a revenue-critical process may justify more than a product opened monthly by one hundred people.

Final ten minutes: choose a response

Your options are usually to reduce seats, change plans, negotiate, accept the increase, or start a structured migration test. Ask the vendor for a written quote, effective date, feature mapping, and any grandfathering or migration terms. Set an owner and a deadline before closing the spreadsheet.

Do not threaten to leave without pricing the exit. Migration includes data cleanup, export, rebuilding automations, retraining, parallel operation, contract overlap, and lost history. A cheaper subscription can still be the more expensive twelve-month decision.

Create a renewal record for next time

Record the final annual cost, seats, active users, concessions, cancellation window, renewal date, data-export method, and the workflows that justify the purchase. Schedule review at least 60 days before the next deadline. The fastest response to a future price change is evidence collected before the email arrives.