Notion AI’s new usage system took effect on August 3, 2026, and as of August 10, it has been live for exactly one week. Over the past few days, a very direct question appeared on r/Notion: if the personal Notion Agent now has both a 6-hour usage limit and a monthly allowance, why do Custom Agents still consume Notion Credits from the very first run? The poster estimated that replacing their current personal Notion Agent usage with Custom Agents could cost around $300 per month. However, the original post did not disclose the full calculation, and the author explicitly acknowledged that the relationship between Credits and Tokens is opaque. That means the $300 figure should not be treated as an official Notion price or applied directly to other workspaces.

The more useful part of the post is not that it proves Custom Agents necessarily cost $300 a month, but that it exposes the current difference in how billing starts. On Business and Enterprise plans, the personal Notion Agent first uses an included usage allowance governed by both 6-hour and monthly windows. Once that allowance is exhausted, administrators can choose to let members continue through Notion Credits. Custom Agents, by contrast, do not receive that included allowance and begin consuming Notion Credits from the first execution. In other words, the same Credits system can eventually apply to both, but the point at which billing starts is completely different.

Where Did the $300-a-Month Estimate for Notion Custom Agents Come From?

The Original Post Gave a Conclusion but Not Enough Data to Reconstruct the Full Calculation

The August 10 r/Notion post asked directly: “If Notion AI is already metered, why do Custom Agents still need their own Credits, and why would equivalent usage cost $300 a month?” The author said they had done some calculations and estimated that replacing their current personal Notion Agent usage with Custom Agents would cost roughly $300 per month. But immediately afterward, they also acknowledged that the conversion between Credits and Tokens is currently “completely opaque.” The original post did not disclose how many Tokens were used, how many Agent runs were involved, how much data each run read, or the complete formula behind the estimate. That means an outside reader cannot independently reproduce the $300 figure.

This is why the number must be described as a “user estimate.” Writing that “Custom Agents cost about $300 per month” would easily make it sound like a fixed pricing plan. Notion does not offer a $300-per-month Custom Agent subscription. Its current published price is $10 per 1,000 Notion Credits, while actual spending depends on how much data each Agent reads, how many steps it performs, which model it uses, and how many times it is triggered during the month.

“Maybe $300 Is the Actual API Cost” Is Also Only the Poster’s Speculation

The original post also left open another possibility: perhaps the $300 figure genuinely reflects something close to what Notion pays for model usage. That can be preserved as the poster’s speculation, but there is currently no public data that proves it. Another assumption in the post also needs to be treated carefully: that the Personal Agent and Custom Agent impose the “same input cost” on Notion. Notion’s own documentation instead indicates that Custom Agent Credit usage depends not only on the model, but also on the amount of content read, the number of tool calls, the number of workflow steps, and execution frequency. That means the two cannot be compared simply by looking at the Token cost of a single prompt.

For example, a simple Task Routing Agent might read one Slack message, look up the responsible person, and create a task. A more complex version might additionally search several databases, determine priority, create a full action plan, write information into subpages, and then send a Slack notification. Both may appear to be doing the same thing—“helping assign tasks”—but the actual workload is very different. This is one reason Credits cannot be reduced to a simple rule such as “one question equals a certain number of points.”

Notion Does Provide Cost Ranges for Custom Agents, but Not a Token Conversion Table

Common Custom Agent Runs Cost About $0.03 to $0.30 Each

Notion has already published estimated cost ranges for several common types of Custom Agents. A Q&A Agent costs roughly $0.03 to $0.11 per run; Task Routing around $0.05 to $0.15; Status Update around $0.08 to $0.18; Mail Triage around $0.04 to $0.10; and a Daily Brief that reads Calendar and Email data around $0.10 to $0.30. Notion also notes that these are only estimates based on current usage patterns and that actual Agent costs should be checked in the Credits Dashboard after each run.

Custom Agent Type	Official Estimated Cost per Run	Approximate Runs per 1,000 Credits／$10
Q&A	US$0.03–0.11	About 90–333 runs
Task Routing	US$0.05–0.15	About 65–190 runs
Status Update	US$0.08–0.18	About 57–133 runs
Mail Triage	US$0.04–0.10	About 100–250 runs
Daily Brief	US$0.10–0.30	About 33–100 runs

If someone really spent $300 per month, this table suggests a substantial amount of Agent activity. If every run were a $0.30 Daily Brief, that would be about 1,000 runs. If every run were a simple $0.03 Q&A task, it could approach 10,000 runs. This is still only a rough calculation because a real Agent can be simpler than these examples or much more complex, but it does confirm one thing: $300 is not a default monthly fee that ordinary Custom Agents automatically generate.

Notion Does Not Publish a Fixed Credit-to-Token Conversion Formula

One part of the community criticism is more clearly grounded: Notion does not provide a public table showing “1 Credit equals X Tokens.” The company has chosen to tie Credits to the amount of work completed rather than asking users to calculate costs from model input and output Tokens themselves. What users can see is how many Credits each Agent run consumed, not the exact amount of underlying model Tokens.

Notion says users can review actual consumption in the Credits Dashboard after each run and recommends starting Agents on a small scale, then observing one or two billing cycles before deciding how many Credits to purchase.

This approach is simpler for teams that do not want to deal with model API pricing, but it is more frustrating for users who want precise cost comparisons. This is especially true when the same Agent can switch between models and Auto may select a model depending on the task. Users can see how much they ultimately spent, but it is difficult to break the cost down beforehand into “how much was the model itself” and “how much came from Notion’s orchestration.”

What Is the Actual Difference Between Personal Notion Agent and Custom Agents?

Personal Agent Uses the Included Plan Allowance First and May Only Consume Credits After That

Business and Enterprise plans currently include a certain amount of Notion AI usage allowance. The personal Notion Agent, image generation, page translation, and Skills all count toward it. This allowance is governed by both a 6-hour window and a monthly window. If either one is exhausted first, the relevant AI features may temporarily stop. If the workspace administrator enables “Allow workspace to use Notion credits after AI limit is reached,” members can continue through Notion Credits instead of waiting for the next reset.

That means the current system can no longer be simplified as “Notion AI uses allowance, while Custom Agents use Credits” as though they were completely separate. A more accurate structure is:

Feature	How It Is Calculated at First	What Happens After the Allowance Runs Out
Personal Notion Agent	Uses the included Business／Enterprise AI allowance first	Wait for reset, or use Notion Credits if enabled by an administrator
Custom Agents	Uses Notion Credits from the first run	Pauses when Credits are insufficient until more are added
Workers	Uses Notion Credits	Handled through the Credits system
AI Meeting Notes	Separate daily 10-hour limit	Does not use the Personal Agent’s 6-hour／monthly allowance

What the Reddit poster finds difficult to understand is really the difference between the first and second rows. Both can read workspace data and use AI models, but one comes with included usage inside the Business／Enterprise subscription while the other is metered from the first run.

Custom Agents Are Paying for More Than “Asking AI a Question”

Notion’s product positioning for Custom Agents has never been simply “another chat window.” Custom Agents can start automatically on schedules or events, continuously monitor data, read from multiple sources, use tools, update databases, and then send results into other systems. When Notion introduced Custom Agents in February 2026, it explicitly described them as AI teammates that could work 24/7, and on May 4 it began charging for them through Notion Credits.

This does not automatically mean the current pricing is reasonable, but it does help explain why Notion did not place Custom Agents inside the same included allowance as the Personal Agent. The Personal Agent is generally invoked when a user opens a conversation and asks AI to do something. A Custom Agent, by contrast, can continue operating while nobody is online. Once trigger frequency, data volume, and repeated tool operations increase, the cost is no longer just the price of generating a short chat response.

Reddit Discussions from the Same Week Also Show That Notion’s Value Is Not Only About AI

One Freelancer Spent Three Weekends Consolidating Four Tools Back into Notion, Mostly Through Database Structure

On August 10, one freelancer shared that they had spent three weekends moving a freelance workflow previously spread across Trello, Google Sheets, Google Docs, and Airtable back into Notion. Trello had handled project management, Google Sheets tracked invoices, Google Docs stored SOPs, and Airtable handled CRM. After consolidation, the user linked Client CRM, Projects, Tasks, and Invoice databases together while keeping formal accounting in Wave. The useful part of this case is that the core structure did not depend on Custom Agents. It relied mainly on Databases, Relations, Formulas, Boards, and Timelines to reconnect information that had previously been scattered across several tools.

This type of work is useful to place next to the current Credits discussion. Consolidating four tools into one workspace does not require every action to call a large language model. If AI becomes useful later, an Agent can be placed on top of an already organized data structure. In the opposite situation, where the underlying information is disorganized, creating a Custom Agent first will often just force the model to spend more steps searching through messy data.

The “Slack Noise Dropped 80%” Case Actually Relied Heavily on Notion AI

Another point in the original draft needs clarification: this week’s post claiming that “Slack noise dropped 80% after using Notion as the company OS” cannot be used to show that successful Notion workflows generally do not need AI. The poster’s core rule was actually “before asking someone on Slack, ask Notion AI first.” The team consolidated playbooks, decision logs, and client data into one place. When members had questions, they first asked Notion AI to search the workspace, and only returned to Slack if no answer could be found. The author claimed this reduced repetitive-question Slack noise by about 80%.

However, this is the Reddit user’s own reported outcome, not a third-party-verified Notion case study, and the post also promotes the author’s own operations-related content. The 80% figure should therefore be presented as the author’s claim rather than as a typical result teams can expect from adopting Notion AI. The more useful part is another point the author made later: the system is not something that can be configured once and then ignored. Every time the AI fails to find an answer, someone needs to go back and add documentation or update outdated information. In other words, what allows AI to answer questions effectively is still a workspace whose knowledge is actively maintained by people.

Putting Company Knowledge in Notion Does Not Automatically Turn It into Knowledge Management

A New Employee Needed Three Weeks to Work Independently Because the Documentation Was Outdated

Another r/Notion post from the same week asked a very practical question: “How much of your company exists only inside one person’s head?” The poster said their company hired a new employee in June, and it took roughly three weeks before the person could work without asking someone else first. The problem was not that the new hire was slow. Many processes had never been documented, and some of the documentation that did exist was already eight months out of date. The workspace also contained HubSpot workflows, n8n automations, and systems running on Railway that only the original person who set them up truly understood.

The conclusion of this post was not praise for Notion. The poster described what they had hoped would solve the problem as eventually becoming a “graveyard” of outdated documentation. This adds an important limitation to the Agent discussion: putting all company information in one platform is not the same thing as building a reliable knowledge base. An Agent may read information faster, but if it reads an eight-month-old SOP, it will simply produce outdated answers more quickly.

This also makes the earlier Slack example more complete. The effective part was not merely “installing Notion AI.” It was the practice of updating documentation whenever someone asked a question that the workspace could not answer. The documents have to be maintained before the Agent can meaningfully reduce repetitive questions.

A More Practical Way to Estimate Custom Agent Costs Before Deployment

Do Not Directly Convert Personal Agent Usage Percentages into Custom Agent Monthly Costs

There is no official fixed conversion formula between Personal Agent allowance and Custom Agent Credits, so calculations such as “I have used 30% of my monthly allowance, therefore the equivalent Agent would cost X dollars” do not have a reliable basis. The two modes also work differently. Personal Agent requests are usually initiated directly by a person. Custom Agents may instead be triggered repeatedly by database updates, Slack messages, or schedules. If the frequency differs by an order of magnitude, the final cost can change completely.

A more practical approach is to choose one workflow that you genuinely plan to automate. For example: summarize Slack messages every day, produce one project summary per week, or create tasks whenever a new client is added. Run the Custom Agent 10 to 20 times, record the lowest, highest, and average Credit consumption from the Credits Dashboard, then multiply the average cost by the expected number of runs in a normal month. Notion itself also recommends starting with a small scope and observing one or two billing cycles before deciding how many Credits to purchase.

First Decide Whether the Task Actually Needs an Agent or Whether a Regular Automation Is Enough

If a process can be expressed clearly as “when status changes to Done, update the date,” “when new data is added, create a record in a fixed format,” or “when a field meets a condition, notify a specific person,” there is usually no reason to start by asking a large language model to make a judgment. Formulas, Buttons, Database Automations, and other deterministic workflows are often easier to predict in terms of cost.

Notion itself emphasized in its 2026 Developer Platform updates that Workers can use code for deterministic logic, and that these kinds of tasks are more reliable and use far fewer Tokens than sending them through LLM reasoning. That does not mean every team needs to write its own Worker. It means the product itself recognizes that fixed logic and work requiring AI judgment should be handled differently.

Do Not Rush to Give an Agent Access to Everything Before the Company Knowledge Is Organized

If SOPs, project status, and client information are still scattered across different pages and nobody is clearly responsible for keeping them updated, creating an Agent first is unlikely to solve the underlying problem. Start by cleaning up data sources, owners, last-updated dates, and expiration rules so that the workspace at least knows which document is the current version. Once that layer is stable, the parts that require semantic search, summarization, or cross-source reasoning can be handed to an Agent.

This step may appear unrelated to AI, but it directly affects Credits. The more content a Custom Agent reads, the larger its search scope, and the more steps it takes, the more Credits Notion expects it to consume. Organizing the underlying information first is therefore not only a knowledge-management issue, but also a cost-control measure.

One week after Notion AI’s new usage system launched, r/Notion discussion has gradually moved from “the allowance is too small” to the next question: how should Personal Agent and Custom Agents fit into the same cost model? The post estimating $300 per month does not provide enough evidence to show that this is a normal Custom Agent cost, but it does highlight the hardest part to calculate today. Personal Agent first uses the allowance included with the subscription and can optionally switch to Credits afterward. Custom Agents begin consuming Credits from the very first run, and there is no published fixed conversion between the two.

There is no need to decide whether to adopt Custom Agents based on the $300 figure alone. Notion already publishes estimated per-run cost ranges for several common Agent types, and actual Credit consumption can be reviewed after every run. A more reliable approach is to choose one workflow that genuinely benefits from automation, run it on a small scale, and multiply the measured average cost per run by the real execution frequency. As for documentation, CRM, project data, and SOPs, it is still worth building the non-AI layer first. That way, when an Agent is introduced, you are not spending Credits to clean up problems that could have been organized before AI entered the workflow.

FAQ

SUPPORT FENGNIII

喜歡這篇文章嗎？

如果這篇內容對你有幫助，可以透過小額贊助支持本站持續整理更多日文、韓文、旅行與數位工具內容。

小額支持本站

付款將由藍新金流安全處理