Should a SaaS Show Annual Savings in Dollars or Percent?

Should your SaaS pricing page show annual savings in dollars or as a percent?

For most B2B SaaS plans, show the yearly savings in dollars next to the price, and keep a short percent label on the billing toggle. Once the savings figure is above about one hundred dollars, a dollar amount feels bigger than the same saving written as a percentage, and it is easier for a buyer to repeat to a manager.

This sounds like a tiny copy decision. It is not. The annual billing toggle is one of the few places on a pricing page where you ask a buyer to commit to more, and the way you describe the reward shapes whether they take it.

It is easy to argue about this for a week and then ship "Save 20%" because that is what everyone else does. There is a better way to decide, and it starts with a well known pricing rule.

What is the Rule of 100 and why does it matter here?

The Rule of 100 is a pricing heuristic described by Jonah Berger. On his own site, he explains that under 100, percentage discounts seem larger than absolute ones, but over 100, things reverse, and absolute discounts seem larger. The economic value is identical. Only the perception changes.

Berger's own examples make it concrete. A $20 shirt marked down to $15 sounds better as 25% off than as $5 off. A $2,000 item sounds better as $500 off than as 25% off, even though the math is the same in both cases. He discusses this idea in connection with his book Contagious.

For a SaaS pricing page, the rule gives you a starting point rather than a law. Most B2B annual savings land well above one hundred dollars once you add up twelve months, and often far above it once you multiply by seats. That puts most SaaS companies on the dollar side of the rule.

The catch is that many SaaS prices are shown per seat per month, which is usually a small number. That is where teams get confused, and where the framing choice really matters.

Why does "Save 20%" feel weak on a B2B pricing page?

"Save 20%" feels weak because it asks the buyer to do math and gives them nothing concrete to repeat. A B2B buyer often has to justify annual billing to a finance lead. A specific dollar figure, tied to their plan and seat count, is a reason they can forward. A percentage is a slogan.

There is also a sameness problem. So many pricing pages carry a percentage badge on the toggle that buyers barely read it anymore. It has become decoration. A dollar figure that changes with the plan they are looking at stands out because it is specific.

And there is a trust problem. Percentages invite a quiet question: twenty percent of what? If the monthly price is shown per seat and the annual price is shown per seat per month billed yearly, the buyer has to reconstruct the real saving themselves. Many will not bother, and the incentive you designed to win commitment stops working.

That is why I treat the savings figure as part of the offer, not as a label. If it does not help the buyer make the case internally, it is not doing its job.

When does a percent work better than a dollar figure?

A percent works better when the actual savings amount is small, such as a low priced self-serve plan where twelve months of savings might be under one hundred dollars. It also works as a consistent, at a glance label on the billing toggle, because it stays the same across every plan and seat count.

If your entry plan costs a few dollars a month, the yearly saving might be a small dollar figure that sounds underwhelming. In that range, the Rule of 100 suggests a percent will feel more generous, so it is the better lead for that plan.

The toggle is the other good home for a percent. A toggle sits above every plan at once, so it cannot show one dollar amount that fits all of them. A short label like "2 months free" or a percentage tells the buyer that annual billing is cheaper without pretending to be precise.

I like "2 months free" in particular when it is accurate, because it turns a percentage into something tangible. It only works if the annual price really equals ten months of the monthly price. If it does not, do not round to make the label work.

How should you combine both on one pricing page?

Use the percent or a "months free" label on the billing toggle, and show the dollar savings on each plan card once annual billing is selected. That gives buyers a quick signal at the top and a concrete, plan specific number where they actually make the decision.

A simple layout that works well looks like this in prose. The toggle reads "Monthly" and "Annual, save 2 months." When the buyer switches to annual, each plan card shows the annual price, then a short line under it such as "You save $1,200 a year on this plan." The number is specific to the card the buyer is reading.

If your pricing is per seat, add a seat selector or show the saving at a typical team size, and say which team size you used. Showing "$240 a year per seat" is honest and still lets a buyer multiply it for their team.

The order of the toggle matters too. Whether you lead with monthly or annual changes which price feels like the default. I covered that choice separately in my piece on whether to show annual or monthly first on a SaaS pricing page.

How do AI assistants read your annual savings claim?

AI assistants read the text on your pricing page, not the visual state of a toggle. If your annual savings only appear after a click, or only inside a badge image, an assistant may miss them or report the wrong price. Write the savings in plain HTML text that is visible without interaction.

This matters because buyers can ask AI assistants to compare tools and summarize pricing before they ever visit a site. A pricing page that hides the annual price behind JavaScript state can lead to answers that quote only the monthly price, or mix the two up.

The fix is simple. Somewhere on the page, in plain text, state both prices and the saving in a sentence. For example: "The Growth plan costs $50 per seat per month billed monthly, or $40 per seat per month billed annually." That sentence is easy for a person to read and easy for a model to quote.

I wrote about the toggle problem in more detail in my article on how AI assistants read a pricing page with a toggle.

What mistakes make an annual discount look untrustworthy?

The biggest mistakes are inflated savings, mismatched math, and hidden conditions. If "Save 20%" does not match the actual difference between monthly and annual prices, or the annual price excludes something the monthly plan includes, buyers notice, and the whole page loses credibility at the exact moment you need trust.

Check the arithmetic on every plan. Rounding a 17 percent saving up to 20 percent might look harmless, but a finance lead will do the math, and once they find one inflated number they will question the rest.

Be clear about what the annual commitment means. Is it paid upfront? Can the buyer add seats mid term? What happens at renewal? You do not need to answer everything on the card, but a short note or a pricing FAQ should cover it.

Finally, do not let the saving distract from fit. A buyer who picks annual billing on the wrong plan becomes an unhappy customer for twelve months. Make the plan differences clear first, and let the annual saving be the reason to commit, not the reason to choose.

How do you test which framing works for your buyers?

Run a simple A/B test on the plan cards, with one version showing dollar savings and the other showing a percent, and measure the share of new subscriptions that choose annual billing. Keep everything else identical. If your traffic is low, watch the trend over a few months instead of waiting for statistical certainty.

The metric that matters is the annual billing take rate, not clicks on the toggle. You want to know whether more buyers commit to a year, and whether those buyers stay. Track it in your billing system or CRM so it is tied to real revenue.

Many B2B SaaS pricing pages do not get enough traffic for a fast, clean test. That is fine. Make the change, note the date, and compare the take rate across the next quarter. Pair it with a few sales call notes about how buyers describe the annual option. Qualitative signal counts at low volume.

For self-serve sign-ups, the Webflow toggle itself is easy to build. If you need a starting point, my monthly and annual pricing toggle tutorial covers the build.

What should you do next?

Open your pricing page and check three things: whether the yearly saving appears as a specific dollar amount on each plan, whether the percent or "months free" label on the toggle matches the real math, and whether both prices are written in plain text. Fix any mismatch first, because accuracy beats clever framing.

Then apply the Rule of 100 as a default. If a plan's yearly saving is above one hundred dollars, lead with dollars on the card. If it is below, lead with a percent. Keep the toggle label consistent across plans.

If you are reworking your pricing page, or the systems behind it like plan tracking in your CRM and billing data in your reports, reach out. I build B2B SaaS websites and the automations behind them, and pricing pages are where those two things meet. Let's chat.