Log SSO price cuts, re-run math at renewal

A scheduling tool's SSO tier adds the security controls a small team is trying to buy. When that tier gets cheaper, the instinct is to upgrade immediately. The better move is to record the change and re-run the math at renewal.

A cheaper SSO tier is a data point

Cal.com, a scheduling product, listed its Organizations tier at $28 per user per month on October 28, 2026, after previously listing it at $37 per user per month, and the change was recorded as a decrease. Those figures are annual billing rates.

The pricing model itself changed in February 2026, when Cal.com moved from one paid tier to multiple plans and set the organization tier at $37 per user per month. That makes the later drop worth tracking, not assuming.

The Organizations tier is the plan that adds SAML SSO and SCIM provisioning, and it also provides role-based permissions and a custom company subdomain. Those features are the reason a small team would consider the upgrade in the first place.

After the change, the Teams tier stayed at $12 per user per month on annual billing, separate from the SSO-enabled Organizations tier. The Organizations rate is more than double the Teams rate.

The log entry is the decision

Keep a single line in a shared doc, not a chat thread. The line should be readable by someone who was not in the meeting. It should answer what changed, what it costs, and what you will do next.

Use this checklist when a listed rate changes. The early items keep the scope honest, and the later items keep the decision reviewable.

• Name the tool and tier in a single line, with the old listed rate and the new listed rate.
• Count the seats that would actually use the tier, not the whole company.
• Convert the per-user difference into an annual delta using the same billing cadence.
• Note the renewal date and the next date the price can be rechecked.
• Write the action: hold, upgrade, or downgrade, with a reason.
• Check the live pricing page before the decision, because listed rates and features change.
• Store the entry where the ops lead can find it in a minute.

To calculate the annual delta, take the difference between the old and new per-user rates, multiply by the number of seats, and multiply by the length of the billing period. Do not use a monthly rate for an annual decision. Do not use an annual rate for a month-to-month decision.

The cadence matters because the Organizations tier carries a listed annual rate of $28 per user per month and a monthly-billing rate of $37 per user per month. Mixing those rates will make the upgrade look cheaper or more expensive than it is.

The renewal date is the checkpoint that turns the entry into a decision. A price change without a date is a note. A date gives the ops lead a reason to reopen the file, recheck the live page, and make a call before the invoice arrives.

The action should be hold, upgrade, or downgrade. The reason should be short enough to survive a future audit. A need for SSO is a stronger reason than a lower price. A small team's needs are a stronger reason than vague future use.

Store the entry in the same place where the company keeps its other vendor decisions. If the file is in a chat, it will disappear. If it is in a spreadsheet, it will be found. The owner should be the ops lead, not the person who saw the price change. The live page check is the only step that can invalidate the entry.

The renewal date forces the decision

Say you have a small team and a renewal coming up. The question is not whether the SSO tier is now cheaper. The question is whether the features you will actually use justify the annual delta.

Start with the seats that need SAML SSO or SCIM provisioning. If only a few people need automated provisioning, the upgrade may not pay for itself. If everyone books through the same domain and needs role-based permissions, the case is stronger.

Then compare the annual delta against the value of the subdomain and the permissions. The subdomain appears as yourcompany.cal.com. That is a branding detail, not a security control.

Do not let the price cut do the deciding for you. A lower listed rate changes the input, not the conclusion. At renewal, open the log entry, confirm the current rate, and choose the action you would have chosen if the price had not moved.