Same product, new unit: which way the meter moves predicts which way the bill moves
Vendors are changing the unit an unchanged product is billed in. Eight corpus vendors did it in 21 days (2026-09-01 to 2026-09-21). The direction of the new unit predicts the bill: moves toward what the buyer counts lowered the common-case bill in 5 of 5 cases, and moves toward what the vendor incurs raised it or made it unforecastable in 3 of 3.
What's happening — and why
What's happening: most repricing changes a number. This changes the noun after it. The product stays the same and the unit it is counted in does not.
In three weeks of September 2026, eight vendors did it. Atlassian's automation went from rule runs to steps. Twelve Labs' Marengo 3.5 embeddings went from per-minute rates to per-1M-input-token rates. Glean's Meeting Notes went from per minute to per meeting at the same ~9 FlexCredits (p50). xAI's X Search went from $5 per 1,000 calls to $5 per 1,000 posts plus $10 per 1,000 profiles fetched. Labelbox's LBU is now charged once per data row instead of on each label submission. You.com stopped charging for cached pages. Vercel's Pro CDN metering became flat capacity tiers at $20, $100 and $300 a month. PhotoRoom now bills enterprise API customers only for images that pass its quality check.
Two directions. Some moved the unit toward what the buyer counts: an accepted image, a data row, a live crawl, a meeting, a capacity tier. All five of those lowered the bill for the typical customer. The others moved the unit toward what the vendor's system spends: automation steps, input tokens, records returned. All three of those raised the bill or made it impossible to predict before running the workload.
It is a tendency, not a law. Lorikeet moved to a buyer-legible dollar-per-resolution card and raised both plans 27-40% in the same change. And re-denomination is invisible to a unit taxonomy: none of the eight moved a `billing_units` tag, because the vocabulary word often survives while its definition changes.
How it works
Evidence over time
9 supporting · 3 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| PhotoRoom | Sep 2026 | BUYER-SIDE. Enterprise API billing moved from every generation attempted to generations that pass its in-house Fidelity Layer check ("pay-for-pass"); failed outputs are absorbed by PhotoRoom. The unit became the image the buyer accepts. Common-case effect: lower. |
| Atlassian | Sep 2026 | VENDOR-SIDE. Replaced "automation rule runs" with "automation steps" on Jira, Confluence and Jira Service Management. A rule run contains several steps, so the unit got finer. In the same change Enterprise lost "unlimited" for explicit caps: 1,000 (Jira), 500 (Confluence) and 9,500 (JSM) steps per user per month. Common-case effect: higher, via a new ceiling. |
| Twelve Labs | Sep 2026 | VENDOR-SIDE. Marengo 3.5 moved the Embed API from per-minute (video $0.042/min, audio $0.0083/min) and per-1,000-request rates to per-1M-input-token rates on five input types, adding Document at $0.162/1M. The calculator warns that "actual token counts vary with content". Common-case effect: no longer computable in advance. A Marengo 3.0 toggle keeps the old units. |
| Labelbox | Sep 2026 | BUYER-SIDE. The Annotate LBU is now charged once per data row, on first submission, instead of on each label submission to a project. Reusing a row in more projects is free. The unit became the buyer's asset, not the vendor's labeling event. Common-case effect: lower for any team running a corpus through more than one project. |
| You.com | Sep 2026 | BUYER-SIDE. Full-page extraction ($1.00 per 1,000 pages) is now billed only on live crawls. Cached pages carry no charge, and the docs' 20-page example fell from $0.025 to between $0.005 and $0.023. Common-case effect: lower. |
| Vercel | Sep 2026 | BUYER-SIDE. Pro's per-unit CDN metering (Edge Requests $2/1M after 10M, Fast Data Transfer $0.15/GB after 1 TB) became Flat Rate CDN capacity tiers at $20, $100 and $300 a month, with a one-day spike explicitly not triggering an upgrade. 50 TB now costs $20 against ~$7,350 of old overage. But included requests on Pro fell from 10M to 1M, so request-heavy, low-bandwidth teams go the other way. Common-case effect: lower for bandwidth-heavy teams, higher for request-heavy ones. |
| Glean | Sep 2026 | BUYER-SIDE. Meeting Notes on the Enterprise Flex rate card moved from per Minute to per Meeting at the same ~9 (p50) / ~18 (p90) FlexCredits. It had been the only duration-scaled line on the 13-capability card. Common-case effect: much lower for any meeting longer than a minute. |
| xAI | Sep 2026 | VENDOR-SIDE. X Search moved from $5 per 1,000 calls to $5 per 1,000 posts fetched plus $10 per 1,000 user profiles fetched. Parent and quoted posts each count. Cost now scales with what the agent pulls back, not how often it asks. Common-case effect: higher for broad thread fetches. |
| Klaviyo | Sep 2026 | BUYER-SIDE (currency). Composer moved from a 16,000-credit tier ($157 list, $110 intro) to a $20/month plan with $10 top-ups. Free-plan allowances were restated from credits into dollars ($5 of mobile messages, $5 of Composer usage). The new card does not state included usage, so old and new are not directly comparable. The sticker fell 82%. |
Counterexamples
- Lorikeet · Sep 2026 — A buyer-legible re-denomination that came WITH an increase. Credit pools (0.95/0.80 credits per chat resolution) became dollar rates ($0.99/$0.90 per resolution), and Start rose $1,500 to $2,100/mo (+40%) and Scale $4,000 to $5,100/mo (+27.5%) in the same change. A move toward the buyer's unit is not by itself a price cut.
- Vercel · Sep 2026 — Went the other way on a different line: flat $150/month Advanced Deployment Protection became Password Protection at $20 per project per month. A finer unit that is cheaper for teams with fewer than eight protected projects, dearer above that, and uncapped.
- Datadog · Sep 2026 — Restated Agent Observability retention as all-in per-10K-span rates ($5/$6.50/$7.50 annual for 30/60/90 days) in place of base-plus-surcharge. Each all-in rate equals the old base plus the old surcharge, so the unit was relabelled and the price did not change.
Trivia
-
None of the eight re-denominations logged between 2026-09-01 and 2026-09-21 moved a `billing_units` tag in the corpus, and the same-cohort unit vocabulary held at exactly 67. The field that is supposed to record what a vendor meters stayed silent for all eight.
-
Glean kept Meeting Notes at the same ~9 FlexCredits (p50) and changed only the word after the number, from "per minute" to "per meeting" (2026-09-21). An hour-long meeting now costs about what a single minute of one used to.
-
You.com's own docs example now has a 5x spread on one identical request, $0.025 when every page is crawled live against $0.005 when served from cache. One `extraction_source` string decides it (2026-09-11).
For buyers
Treat the unit definition, not the rate, as the first thing to re-read at renewal. A rate card diff will miss this entirely, because the number can stay put while what it applies to changes. When a vendor announces a new unit, take a month of your own usage and re-price it in the new unit before comparing anything else. Your usage shape decides the outcome: Vercel's flat CDN tiers made 50 TB cost $20 against about $7,350 of old overage, but included Pro requests fell from 10M to 1M, so a request-heavy, low-bandwidth team goes the other way. Be most careful with moves toward the vendor's cost unit. Twelve Labs' calculator itself warns that actual token counts vary with content, and xAI's X Search now counts parent and quoted posts, so a broad thread fetch costs more than the call count suggests. Where an old-unit toggle exists, as with Twelve Labs' Marengo 3.0, keep using it until you have measured the difference.
For vendors
Re-denominating toward the buyer's unit is the cleaner story: PhotoRoom's pay-for-pass, Labelbox's once-per-row charge and Glean's per-meeting line each give the buyer a number they can predict from their own work. It is also a real concession, since it moves waste and variance onto you. Moving toward your own cost unit protects margin but costs forecastability, and buyers notice. If you do it, ship an estimator or a legacy-unit toggle, and state the conversion from old to new. Datadog's all-in retention rates, where each new rate equals the old base plus the old surcharge, show how to relabel without leaving the buyer to reverse-engineer whether the price moved. And if you raise prices in the same change, as Lorikeet did, expect the new unit to be read as cover for the raise.
Outlook — what to watch
Eight cases in 21 days is a cluster, logged as `new`. The rule is falsified if, over the next two review windows, buyer-side re-denominations arrive with effective increases as often as with cuts, or vendor-side ones start arriving with cuts. Lorikeet is already one buyer-side case that came with a 27-40% increase, and Vercel's Password Protection went to a finer per-project unit that is cheaper below eight projects and dearer above. Watch also whether unit taxonomies catch up: the same-cohort unit vocabulary held flat at 67 through all eight moves, so trackers that count units rather than read their definitions will keep missing this.
Bottom line
Eight vendors kept a product the same and changed the unit it is billed in. Moves toward the buyer's unit cut the common-case bill in 5 of 5 cases, and moves toward the vendor's cost unit raised it or made it unforecastable in 3 of 3. Re-price your own usage in the new unit before you compare rates.
FAQ
What is meter re-denomination?
Meter re-denomination is changing the billing unit of an existing product without changing the product: rule runs become steps, minutes become tokens, per minute becomes per meeting. Eight corpus vendors did it between 2026-09-01 and 2026-09-21: PhotoRoom, Atlassian, Twelve Labs, Labelbox, You.com, Vercel, Glean and xAI.
Does a new billing unit mean a price increase?
It depends on which way the unit moved. When it moved toward what the buyer counts (an accepted image, a data row, a live crawl, a meeting, a capacity tier), the common-case bill fell in 5 of 5 cases. When it moved toward what the vendor incurs (automation steps, input tokens, records returned), the bill rose or became unforecastable in 3 of 3. Lorikeet is the exception: a buyer-legible dollar card that came with a 27-40% plan increase.
How do I check whether a unit change costs me more?
Take a month of your own usage and re-price it in the new unit. Averages mislead here. Vercel's flat CDN tiers priced 50 TB at $20 against about $7,350 of old overage, but included Pro requests fell from 10M to 1M, so request-heavy, low-bandwidth teams pay more.
Why don't pricing trackers catch these changes?
Because the unit word often survives while its definition changes. None of the eight re-denominations moved a billing_units tag in the corpus, and the same-cohort unit vocabulary held at exactly 67. You have to read the unit definition, not just the rate or the unit name.