Dev

A price you cannot compute

The bill went up by $96 a year, which is nothing. What changed underneath it is that the number is no longer derivable: the included allowance has no published size, the free credit allotment has no published size, and the annual credit costs more than the monthly one. A price you cannot compute from published figures is an estimate, and an estimate is a different kind of dependency.

The email came on a Tuesday morning and opened with gratitude.

For a while, your workspace, [workspace], has had access to everything included
in your plan at a discounted price. We hope you've been able to put features on
your plan to good use, and we're grateful you've continued to choose Notion for
your life's work.

Then the number.

Your plan and features aren't changing. You'll continue to have access to
everything you use today. However, your price will be updated to current list
price of $240 per year, starting with your next renewal on February 17, 2027 PT.

Ninety six dollars a year more than I pay now. As money, this is not a story. It is less than a month of the AI tooling I already buy, and about two hours of the work I would spend arguing about it. I noticed I was annoyed anyway, which usually means the number is not the thing.

It was not the thing. The thing is that a year ago my bill was a figure I could derive from published prices, and today it is not.

What actually changed, in order

I keep a mailbox instead of a memory, so the sequence is checkable.

DateWhat happened
Until 12 May 2025Notion AI is a separate add-on at $8 per member per month billed annually, attachable to any plan, including the free one. Business is $15 per member per month billed annually.
13 May 2025The plans are restructured. The release note says Business and Enterprise "now include unlimited usage of Notion AI". The Business seat moves from $15 to $20 per member per month billed annually, visible on the pricing page by 16 May.
3 November 2025My add-on is discontinued. The notice says my subscription "will be upgraded to the Business Plan, at your current price".
24 February 2026Custom Agents ship. They are free through 3 May and then run on credits.
4 May 2026Credits go live at $10 per 1,000, and unused ones do not carry over.
10 September 2026Premium models leave beta, start drawing credits, and are "turned off by default" for the workspace that day.
22 September 2026The notice arrives: the grandfathered price will end at the February 2027 renewal, at list price.

Read that as a price history and it is ordinary: a vendor raises prices, honours a legacy rate for ten months, then stops. Read it as a history of units and something else shows up. The 2025 line item I could price was replaced by an included allowance, and the allowance was replaced, for the interesting part of the product, by a meter.

What does "unlimited" mean on Notion's own help page?

Not unlimited. Notion's current help page on the AI usage allowance says it plainly, and the sentence is worth reading slowly, because it is the same product the May 2025 release note called unlimited. Notion's "unlimited" always carried a fair-use caveat, including on the old add-on. What changed is that the caveat became the unit:

To keep Notion AI fast and reliable, Business and Enterprise plans include a
usage allowance for certain Notion AI features. If you come close to using the
full allowance, access to some AI features may temporarily pause until your
usage refreshes.

The allowance runs on two clocks, a six hour window and a monthly one. If you exhaust it, features pause and come back when the window rolls. And if you do not want to wait:

Use Notion credits to keep going.

Nowhere on that page, or on the pricing page, or in any of the notices I received, is the allowance given a number. Not per plan, not per window. You can see your own consumption inside the product, after you are paying, which tells you what you used and not what you get.

So the answer to "what does my $20 seat include" is: an amount Notion has measured and I have not been told. I can observe it by hitting it.

Why are the annual credits more expensive than the monthly ones?

Because they are not a commitment discount, they are a scheduling fee. Notion's own FAQ says the difference buys flexibility rather than a lower rate:

Are annual credits cheaper than monthly credits? No. Annual credits cost $13 per
1,000 credits, compared to $10 per 1,000 for monthly credits. The benefit is
flexibility. You can use annual credits anytime during your subscription year,
while monthly credits reset each month.

Thirty percent more per credit for the right to spend them on your own calendar. Neither kind rolls over: monthly credits reset each month, annual credits expire at renewal even if you bought them in month eleven. And the order in which they burn names another quantity, free credits, which are spent first and whose size is published nowhere at all.

Notion does publish estimates, and the estimates are the argument. Its own worked example says a status update agent running sixty times a month costs about $4.80 to $10.80, depending on how much it reads and how many steps it takes. Same agent, same number of runs, a factor of two and a quarter between the ends of the range. That is not a vendor being careless. That is what metering per unit of work does to a forecast when the work is a model reading things.

I am not claiming any of this is hidden. It is documented, openly, on pages anyone can read. That is what makes it interesting. Every individual sentence is honest, and the sum of them is a bill I cannot compute in advance. To forecast next year I would need the allowance size, the free credit allotment, and the credit cost of the specific work I do. Two of those three are unpublished, and the third is measurable only by running the work.

Was the trust broken by the increase or by the wording?

By the wording, and it is not a small distinction.

In November 2025 the migration notice said my subscription would move to Business "at your current price" on 1 December 2025. The move had a date. The price did not: no end date for it was named, and no transitional period was mentioned. Ten months later the same arrangement is described as a workspace that "has had access to everything included in your plan at a discounted price", and the discount is ending. Both sentences are true. Put them in sequence and they teach a customer something: a price stated without a term is not a term, it is a setting, and settings get changed by the party that holds them.

One more detail from the same stack of emails, which I noticed only because I went looking. The notice that premium models would be switched off by default arrived on a stream that carried an unsubscribe footer. The price increase and the terms change arrived as account notices with no unsubscribe. Anyone who had opted out of that stream, a reasonable thing to do, would have learned that their models were off when a workflow stopped working.

I am also not the first to read a sequence like this. On the day of the May 2025 restructure, someone posted an open letter to Notion's CEO on r/Notion that became the highest scoring pricing thread the forum has had, and the complaint in it is not the price either. It is that features an annual plan had been bought for were withdrawn while that plan was still running. Worth saying what the reaction does not show, though, because it is the part people usually skip: the anger stayed inside r/Notion. In the places where a migration would actually be visible, the self-hosting and note-taking forums, the serious discussion of Notion alternatives predates all of this. Loud, dated, and not a wave.

So what do you do about a dependency you cannot price?

You ask a narrower question than the one the email invites. The email invites "is Notion worth $240 a year", and the answer is obviously yes for most people who ask. I asked instead: how much of this product am I actually using, and what would it cost to own that part?

The honest inventory was small. Tasks with due dates and a status. Recurring work that reappears on a schedule. Notes attached to the thing they are about. Search across it. A phone view for triage. That is what I had been using a database-and-documents platform for, and none of it is technically hard. What had made it worth renting was that building it used to be a project, and keeping it alive used to be a second project.

So I built it. A small FastAPI service, SQLite for storage, one table per idea, a plain web UI, all of it reachable only inside my own network. The first working version took two days in February 2026, and it did almost nothing: a page, a database, a place to put notes. The parts that actually replaced what I was renting arrived over the spring, each in the week I needed it. Tasks in April. Recurring work a few days later, because the same things kept coming back. A scheduler that can start work on its own. Then, in June, a notification path so it could reach me, and a calendar sync, because I kept missing things that lived in two places. Nothing was designed in advance. Every feature was added the week I needed it, which is a luxury nobody building for a large installed base has.

What it cost is worth stating honestly, because the enthusiasm around building your own tends to skip it. It runs on hardware I already had. It has no mobile app, and I have never wanted one. It has no collaboration model, because it has one user, and adding a second would be real work, which is precisely the feature Notion sells and I do not need. I own the backups, and when I got that wrong the failure was mine. Against that: there is no renewal email, no allowance, no credit that expires at renewal, and no morning when a model I depend on is off by default.

When is this actually the right trade?

Three conditions, and I would not recommend it if any one fails.

The slice has to be small and stable. If what you use is the collaborative surface, the permissions model, the guest sharing, the integrations, the mobile capture, then you are using the product and you should pay for the product. My slice was small because my use was solitary and my data was text.

You have to be able to afford ownership, in the sense that matters: not the build, the decade after it. The build is now cheap. Running the thing, backing it up, migrating it when the runtime moves on, fixing it on the evening it breaks, that is the actual price, and it is paid in attention rather than dollars.

And the exit has to be real. I did not rage-migrate the day the email arrived. I am paid through February 2027, which turns their deadline into my runway: build, run both, export continuously, and cancel only when the old system holds nothing I would miss. A migration under time pressure is how you end up paying for two systems and trusting neither.

The rule I took away

The switching cost fell while the rent rose, and both happened for the same reason. Building a personal tool that does one job stopped being a project around the time that models got good enough to write the boring eighty percent of it, which is also the period in which vendors started charging for models by the unit. Notion is not doing anything unusual here. Anthropic metered the programmatic side of its subscription, announced in May, with the same shape: a familiar price, a new unit underneath it.

So the rule is about units, not vendors. If I can compute next year's bill from numbers the vendor publishes, it is a price, and I can plan against it. If I cannot, because the allowance has no size and the credit has no rate for my workload, then what I have is an estimate maintained by someone whose interests are not mine. That is a dependency, not a foundation, and the correct response to a dependency is not outrage. It is an exit that already exists, kept warm, before the next Tuesday morning email.

Discussion

No comment section here — all discussions happen on X.

Max Nardit

Max Nardit

@mnardit

More articles

Claude Code now reads AGENTS.md, and the default is a fallback

Anthropic solved loading again and left precedence where it was. The default decides which project file loads by what happens to exist on disk, the file it loads stays out of the inventories you would audit it with, and the old one-line import is still the setup that behaves the same across providers and versions.

The tool you install has your reach

An installed tool holds whatever authority you already have, and handing it over is the one security decision that gets no second look: taken once, in the least deliberate act of the whole install, and never revisited. You can contain what it can reach or read what its code actually touches; trusting the name does neither.

The compaction is an untrusted input

Input from outside gets a discipline and the agent's own output does not, so the summary it writes to survive a reset and the memory it recalls come back in as instructions with a standing nothing revoked. The author the harness records for them is the model itself, which is the exact reason the check lets them through.