Charm pricing (ending a price in 9, like $9 or $29.99) reliably lifts volume in value-oriented, consumer, and low-consideration purchases, because the left digit anchors perceived cost. Round numbers ($10, $30) signal quality, confidence, and premium positioning, and tend to outperform in B2B, luxury, and high-trust contexts. The right ending isn't a universal rule — it's a positioning statement you make on purpose.
Quick Answer: Use 9-endings when you're competing on price or volume and want to look cheaper than you are. Use round numbers when you're competing on trust, quality, or premium positioning and want to look confident, not desperate. Test within a single, deliberate frame — never mix signals across your own price list.
What the Research Actually Says About 9-Endings
Prices ending in 9 lift purchase volume primarily through the left-digit effect — shoppers encode $9 as "in the 8 dollar range, roughly" the same way they encode $2.99 as "two dollars and change," even though the true gap to $10 is a single cent. This isn't a fringe theory; it's one of the most replicated findings in pricing research.
The foundational field studies came from marketing researchers Eric Anderson and Duncan Simester, who ran real mail-order catalog experiments in the late 1990s and early 2000s. Their results, later summarized in widely cited Quantitative Marketing and Economics work, found that raising a price from a round number to a 9-ending (for example, $34 to $39) increased demand in some product lines — a result that only makes sense if buyers are processing the price's shape, not just its magnitude.
Why the Left-Digit Effect Works
The mechanism is a truncation heuristic: shoppers process multi-digit prices left-to-right and give disproportionate weight to the leftmost digit, understating the true magnitude of the reduction from $10.00 to $9.99. Behavioral economists studying numerical cognition (building on Daniel Kahneman and Amos Tversky's work on heuristics and anchoring) describe this as a specific case of anchoring: the first digit sets the anchor, and the remaining digits get compressed in working memory.
Three conditions make the effect strongest, according to the retail and grocery pricing literature:
- Low-involvement, frequent purchases — groceries, snacks, subscriptions under about $50
- Price-comparison contexts — a shelf, a search results page, a pricing table where buyers scan digit-by-digit
- Categories where "cheap" isn't a negative signal — commodities, staples, entry-tier SaaS plans
Where these conditions don't hold, the effect weakens or reverses — which is exactly why blanket "always use .99" advice from a decade of e-commerce blog posts doesn't transfer cleanly to B2B software pricing.
When Round Numbers Signal Quality Instead
A round price ($50, not $49.99) is processed as fluent and confident — it reads like a considered decision rather than a marketing trick, and fluency itself is a quality cue independent of the actual number. This matters most whenever the purchase is emotionally significant, expensive relative to the buyer's frame of reference, or evaluated on trust rather than price-per-unit.
Researchers Monic Sun, Kwanho Suk, and Jaehwan Kim's work on pricing endings, along with a widely cited Journal of Consumer Research study on "precision and trust in negotiation," found that round numbers are perceived as less carefully calculated but more confident, while precise, non-round numbers (like $9.99 or oddly specific figures) signal a deal was analyzed down to the penny — useful for discounts, less useful when you want to project premium stability.
Round numbers say "this is what it costs." Charm-priced numbers say "look how close I got you to a discount." Those are different personas, and your buyer notices which one you're playing.
The B2B Case for Breaking the .99 Convention
B2B and premium SaaS buyers evaluate credibility, not bargain-hunting instinct, so a $499/month price ending can read as retail-coded and slightly undermine a claim to enterprise seriousness. This is why most mature B2B SaaS pricing pages converge on round numbers — $50, $200, $1,000 — once they move upmarket from a self-serve, credit-card-entry tier toward a sales-assisted or enterprise tier.
The pattern shows up consistently across public SaaS pricing pages: entry/self-serve tiers often keep a $9 or $29 charm price to lower the psychological barrier to a first credit-card swipe, while the "Business" or "Enterprise" tier a few columns over almost always rounds. That's not inconsistency — it's the ending doing double duty as a tier-positioning cue, which connects directly to how you should be choosing your value metric in the first place, since the metric determines what number the ending is actually attached to.
Comparing the Two Approaches Directly
| Dimension | 9-ending (charm pricing) | Round number |
|---|---|---|
| Best-fit context | Consumer, self-serve, low-consideration | B2B, enterprise, high-trust |
| Signal sent | Value, deal, accessible entry point | Quality, confidence, premium |
| Mechanism | Left-digit truncation / anchoring | Cognitive fluency / precision cue |
| Where it backfires | Premium and luxury positioning | Deep-discount or clearance contexts |
| Typical SaaS placement | Free/Starter tier | Business/Enterprise tier |
| Buyer read if reversed | "Cheap trick" for a premium product | "Overpriced" or "arbitrary" for a bargain product |
The table's takeaway is simple: match the ending to the tier's job, not to a company-wide style rule. A pricing page with $9, $299, and $1,000 across three tiers isn't inconsistent — it's telling each buyer segment the right story, provided the jump is deliberate and not an accident of whoever set each tier's price last.
Left-Digit Effects Beyond the Ones Place
The left-digit effect doesn't stop at cents — it recurs at every digit boundary, which is why $99 vs $100 and $999 vs $1,000 are meaningfully different decisions from $9 vs $10, not just bigger versions of the same one. Crossing a leftmost-digit threshold (99→100, 999→1,000) produces a sharper perceived jump than the one-unit difference implies, because the truncation heuristic operates on whichever digit is leftmost at that price point.
This has a direct pricing-page implication: if your annual plan is hovering near $999 or $1,999, the decision to stay just under or round up to $1,000/$2,000 carries more psychological weight than the $1 gap suggests. Below are rough directional patterns drawn from the same body of anchoring and left-digit research, translated to SaaS-relevant price bands:
- Under $20: charm-ending is well tested and reliably lifts perceived value (freemium upsells, add-ons)
- $20-$100: mixed evidence; matters more who's buying (self-serve individual vs. procurement-reviewed team)
- $100-$1,000: round numbers increasingly favored as deal size and buyer sophistication rise
- Over $1,000: charm endings mostly disappear from credible B2B pricing; round or "custom pricing" dominates
If you're still deciding what unit that price attaches to — per seat, per workspace, per usage tier — that decision has to happen before the ending does, which is the core argument in choosing your value metric before you finalize any number on the page.
Testing Endings Without Losing the Positioning Thread
A price-ending test only produces a usable answer when it's run within one consistent positioning frame, because the ending's job is to reinforce a story your product is already telling — not to be optimized in isolation from it. Testing $29 against $30 on a page whose copy, design, and support tier all whisper "premium" measures a confound, not a clean effect.
Before running the test, decide:
- What positioning does this tier claim? Entry-level and accessible, or premium and trust-led — the ending should match, not fight, that claim.
- What's the comparison context? A charm-ending gains most of its power on a scannable comparison page (yours vs. a competitor's, or tier vs. tier); it does far less in a single-price checkout with no adjacent number to anchor against.
- What does the rest of the page say? A $9.99 price next to enterprise logos and a security-compliance badge sends a mixed signal that undercuts both cues.
- Is the sample big enough to trust a one-digit swing? Small SaaS trials rarely have the traffic to detect a genuinely small effect reliably — treat inconclusive tests as inconclusive, not as evidence either way.
None of this happens in a vacuum from your broader pricing architecture — how you charge (seats, usage, flat fee) interacts with what ending looks credible, and a deeper walkthrough of that whole system lives in the pricing and monetization complete guide. Whether you're building your case for a price bottom-up (in which case the value-based vs. cost-plus pricing tradeoff matters more than the ending) or trying to shorten time-to-value with a generous free tier, the ending is one of the last decisions, not the first.
Frequently Asked Questions
Does charm pricing still work in 2026, or have consumers caught on?
Yes, directionally — the left-digit effect is a low-level perceptual heuristic, not a trick that gets "solved" through consumer awareness, so it keeps showing effects in replicated studies decades after $X.99 pricing became ubiquitous. Awareness of the convention doesn't neutralize the underlying digit-processing bias it exploits.
Should a SaaS free trial or entry tier use a 9-ending?
Usually yes, if the entry tier's job is lowering the barrier to a first low-commitment purchase — this is the context where 9-endings have the strongest evidence behind them. Pair it with a clear, plain-language description of what upgrading unlocks, since the ending should invite a first step, not obscure the ladder above it, which ties back to how freemium vs. free trial time-to-value gets designed.
Is $99 meaningfully different from $100 psychologically?
Yes — crossing the leftmost-digit boundary from 99 to 100 tends to feel like a bigger jump than $1 implies, because of the same left-digit truncation mechanism that makes $9.99 feel closer to $9 than to $10. Treat every digit-count boundary ($9→$10, $99→$100, $999→$1,000) as its own decision point, not a rounding rule.
Can I mix charm and round pricing across tiers on the same page?
Yes, and mature B2B SaaS pricing pages frequently do this deliberately — a charm-priced self-serve tier next to a round-numbered enterprise tier is a positioning signal, not an inconsistency. The mistake is mixing them within a tier's own messaging (a $9.99 price next to enterprise-grade claims), not mixing them across tiers that are meant to feel different.
What's the single biggest mistake teams make with price endings?
Picking an ending by habit or competitor-copying rather than by what it signals about the specific tier's positioning — the ending is a stylistic choice with real perceptual consequences, not a rounding preference. The fix is deciding the tier's story first (value-led or trust-led), then choosing the ending that reinforces it, ideally checked against how your customer journey frames the buyer's expectations at that price point.
Key Takeaways
- 9-endings exploit the left-digit effect, a well-replicated truncation heuristic where buyers anchor on the leftmost digit and undercount the true price — strongest in low-involvement, price-comparable purchases.
- Round numbers signal cognitive fluency and confidence, which is why they dominate premium, B2B, and trust-led pricing contexts where a buyer is evaluating credibility over bargain-hunting.
- The left-digit effect recurs at every digit boundary ($9→$10, $99→$100, $999→$1,000), so the decision to round up gets more psychologically consequential as the price grows, not less.
- Mixing endings across tiers on the same page is a deliberate positioning tool, not an inconsistency — a charm-priced entry tier next to a round-numbered enterprise tier tells two buyer segments two different, appropriate stories.
- Test price endings within one consistent positioning frame, not as an isolated digit swap — the ending should reinforce the tier's claim, and a small-sample test result should be treated as inconclusive until it's actually conclusive.
- Mock the price in context before shipping it — how a number reads next to a tier name, feature list, and surrounding copy matters as much as the digit itself.