选档不是看价格，是看你撞的是哪堵墙。这一章你记一本账：一个月里每次撞墙记四栏，月底摊开看 —— 是该加购、该升档，还是其实该降。官方不公布额度数字，所以这本账只能你自己记。Choosing a tier isn't about price — it's about which wall you keep hitting. Here you keep a ledger: four columns each time you hit a limit for a month, then read it at month's end — buy extra, upgrade, or actually downgrade. Anthropic publishes no quota numbers, so this ledger is one only you can keep.
选档不是看价格，是看你撞的是哪堵墙。而「你撞的是哪堵墙」这件事，官网答不了，我也答不了 —— 只能你自己记一本账。Choosing a tier isn't about price — it's about which wall you keep hitting. And which wall that is, the vendor page can't tell you and neither can I. Only a ledger you keep yourself can.
— I
每一档解开的是一堵不同的墙Each Tier Unlocks a Different Wall.
不是笼统的「更高级」，是一堵具体的墙。截至 2026-08 的价目：1注 1Note 1Anthropic · Claude 套餐与价格 —— Free $0；Pro 年付 $17/月、月付 $20/月；Max 从 $100/月起，两档，相对 Pro 提供 5× 或 20× 用量、更高输出上限、新功能抢先体验与高流量时段优先访问；Team 标准座年付 $20/月付 $25，高级座年付 $100/月付 $125，两种座位可混用；Enterprise 自助档 $20/座 + 用量（随模型与任务浮动）。页面注明「用量限额适用……价格与套餐可能变动」。截至 2026-08。Anthropic · Claude Plans & Pricing — Free $0; Pro $17/mo billed annually or $20/mo monthly; Max from $100/mo across two tiers, giving 5x or 20x the usage of Pro plus higher output limits, early access to new features, and priority access at high traffic times; Team standard seats $20/mo annual or $25/mo monthly and premium seats $100/mo annual or $125/mo monthly, mixable; Enterprise self-serve at $20/seat plus usage that scales with model and task. The page notes 'usage limits apply… price and plans are subject to change.' As of 2026-08.Not a vague 'more premium' — a specific wall. Prices as of 2026-08:1注 1Note 1Anthropic · Claude 套餐与价格 —— Free $0；Pro 年付 $17/月、月付 $20/月；Max 从 $100/月起，两档，相对 Pro 提供 5× 或 20× 用量、更高输出上限、新功能抢先体验与高流量时段优先访问；Team 标准座年付 $20/月付 $25，高级座年付 $100/月付 $125，两种座位可混用；Enterprise 自助档 $20/座 + 用量（随模型与任务浮动）。页面注明「用量限额适用……价格与套餐可能变动」。截至 2026-08。Anthropic · Claude Plans & Pricing — Free $0; Pro $17/mo billed annually or $20/mo monthly; Max from $100/mo across two tiers, giving 5x or 20x the usage of Pro plus higher output limits, early access to new features, and priority access at high traffic times; Team standard seats $20/mo annual or $25/mo monthly and premium seats $100/mo annual or $125/mo monthly, mixable; Enterprise self-serve at $20/seat plus usage that scales with model and task. The page notes 'usage limits apply… price and plans are subject to change.' As of 2026-08.
档位Tier
价格Price
它解开的那堵墙The wall it unlocks
Free
$0
够你试用：对话、web search、memory、连接器、文件生成、Skills 都有Enough to try: chat, web search, memory, connectors, file creation, and Skills are all there
协作墙：SSO、admin、集中计费；默认不拿你的内容训模型The collaboration wall: SSO, admin, central billing; no model training on your content by default
Enterprise
$20/座 + 按用量（随模型与任务浮动）$20/seat + usage (scales with model and task)
管控墙：SCIM、审计日志、Compliance API、自定义保留、IP 名单、HIPAA-readyThe controls wall: SCIM, audit logs, a Compliance API, custom retention, IP allowlisting, HIPAA-ready
看出门道了吗：Free 到 Pro 解开的是功能，Pro 到 Max 解开的是额度，再往上解开的是协作与管控。2注 2Note 2Anthropic · Claude 套餐与价格 —— Free 档含网页/移动/桌面对话、代码生成、web search、memory、文件生成、桌面扩展、远程 MCP 连接器与 extended thinking，但不含 Claude Code、Cowork、Design、Science、Research 与 Microsoft 365 集成；Pro 在 Free 基础上加上这些，并给「更多用量」与无限项目。截至 2026-08。Anthropic · Claude Plans & Pricing — the Free tier includes web/mobile/desktop chat, code generation, web search, memory, file creation, desktop extensions, connectors with remote MCP, and extended thinking, but not Claude Code, Cowork, Design, Science, Research, or the Microsoft 365 integration; Pro adds all of those plus 'more usage' and unlimited projects. As of 2026-08.4注 4Note 4Anthropic · Claude 套餐与价格 —— Team 档功能中明确列出「默认不用你的内容训练模型」；Enterprise 另加支出上限、基于角色的访问控制、SCIM、审计日志、Compliance API、自定义数据保留、网络访问控制、IP 允许名单与 HIPAA-ready，以及 beta 阶段的 Claude Security。截至 2026-08。Anthropic · Claude Plans & Pricing — the Team tier explicitly lists 'no model training on your content by default'; Enterprise adds spend limits, role-based access control, SCIM, audit logs, a Compliance API, custom data retention, network access control, IP allowlisting, and a HIPAA-ready offering, plus Claude Security in beta. As of 2026-08.先认清你要的是哪一类，再看价格 —— 这三类墙的价格差得远，但它们不能互相替代：额度不够的人升到 Team 也还是额度不够。See the pattern: Free to Pro unlocks features, Pro to Max unlocks quota, and above that it unlocks collaboration and controls.2注 2Note 2Anthropic · Claude 套餐与价格 —— Free 档含网页/移动/桌面对话、代码生成、web search、memory、文件生成、桌面扩展、远程 MCP 连接器与 extended thinking，但不含 Claude Code、Cowork、Design、Science、Research 与 Microsoft 365 集成；Pro 在 Free 基础上加上这些，并给「更多用量」与无限项目。截至 2026-08。Anthropic · Claude Plans & Pricing — the Free tier includes web/mobile/desktop chat, code generation, web search, memory, file creation, desktop extensions, connectors with remote MCP, and extended thinking, but not Claude Code, Cowork, Design, Science, Research, or the Microsoft 365 integration; Pro adds all of those plus 'more usage' and unlimited projects. As of 2026-08.4注 4Note 4Anthropic · Claude 套餐与价格 —— Team 档功能中明确列出「默认不用你的内容训练模型」；Enterprise 另加支出上限、基于角色的访问控制、SCIM、审计日志、Compliance API、自定义数据保留、网络访问控制、IP 允许名单与 HIPAA-ready，以及 beta 阶段的 Claude Security。截至 2026-08。Anthropic · Claude Plans & Pricing — the Team tier explicitly lists 'no model training on your content by default'; Enterprise adds spend limits, role-based access control, SCIM, audit logs, a Compliance API, custom data retention, network access control, IP allowlisting, and a HIPAA-ready offering, plus Claude Security in beta. As of 2026-08. Name which class you need before looking at price — the three cost wildly different amounts and none substitutes for another: someone short on quota is still short on quota after moving to Team.
— II
动手：记一本墙的账Do It: Keep a Ledger of Walls.
一个月，每次撞墙花二十秒记四栏。这是全书里最省力、也最容易被跳过的一件产出。One month, twenty seconds and four columns each time you hit a wall. It's the least effortful deliverable in this book and the one most likely to be skipped.
四栏够了。第三栏是关键 —— 光记「撞了」没用，要记「当时在做什么」，因为解法取决于那件事值不值。Four columns is enough. The third is the load-bearing one — recording that you hit a wall is useless; recording what you were doing is what matters, because the fix depends on whether that thing was worth it.
01
先分清你撞的是哪一类墙First, name which class of wall it was
三类：额度（它让你等）、功能（这一档根本没有）、协作与管控（你能用，但团队用不了或合规不让）。分错类的话，后面所有决定都会错 —— 额度墙升到 Team 是白花钱。Three classes: quota (it made you wait), feature (this tier simply doesn't have it), collaboration and controls (you can use it, but your team can't or compliance won't allow it). Misclassify and every later decision is wrong — moving to Team over a quota wall is money burned.
02
记下「当时在做什么」，这一栏最重要Record what you were doing — the load-bearing column
因为月底你要问的不是「我撞了几次」，是「那几次值不值」。为了一件本可以用 Haiku 做的批量分类撞墙，和为了一次真正重要的重构撞墙，是两件完全不同的事。Because the month-end question isn't 'how many times did I hit it' but 'was it worth it each time.' Hitting a wall on bulk classification that Haiku could have handled, and hitting one on a refactor that genuinely mattered, are entirely different events.
03
记下你当场的对策Record what you did about it on the spot
等一等？拆成几段？换个便宜的模型？还是干脆手动做完了？这一栏会告诉你一个残酷的事实：很多次撞墙的真实代价是零 —— 你等了二十分钟，然后照样做完了。Waited? Split it up? Switched to a cheaper model? Or just did it by hand? This column tells you something uncomfortable: many walls cost you nothing at all — you waited twenty minutes and finished anyway.
04
月底摊开，只看两个数At month's end, read only two numbers
撞了几次；其中同一堵墙撞了几次。第二个数才是决策依据 —— 分散的四次和集中在同一件事上的四次，答案完全不同。How many times you hit a wall, and how many of those were the same wall. The second is the one that decides — four scattered hits and four hits on the same thing lead to opposite answers.
提示词Prompt月底读账Reading the ledger
下面是我这个月的撞墙记录。帮我判断该怎么办，别替我推销更贵的档。
<把 walls.md 的表格贴这里>
请回答四件事：
1. 这些墙按「额度 / 功能 / 协作管控」分，各几次？
2. 有没有哪几次其实是我自己用错了（比如该用便宜模型的活用了最贵的、该交给定时任务的手动跑了）？
3. 按这本账，我该加购额度、升档，还是其实该降档？给一个结论加一句理由。
4. 如果答案是「先别动」，直接说先别动。Below is my log of the walls I hit this month. Help me decide what to do — don't upsell me.
<paste the walls.md table here>
Answer four things:
1. Sorted into quota / feature / collaboration-and-controls, how many of each?
2. Were any of them actually my own misuse (running on the priciest tier work a cheap one could do, doing by hand what a scheduled task should)?
3. Based on this ledger, should I buy extra usage, upgrade, or actually downgrade? One conclusion plus one line of reasoning.
4. If the answer is 'change nothing yet,' say change nothing yet.
下面是我这个月的撞墙记录。帮我判断该怎么办，别替我推销更贵的档。
| 08-03 | 用量（周限额） | Cowork 整理 Q2 发票，第 2 次跑 | 等到第二天 |
| 08-06 | 功能（Free 没有） | 想用 Research 查供应商条款 | 手动开了 12 个标签 |
| 08-11 | 用量（会话内） | Claude Code 重构 auth 模块 | 拆成三段，隔天继续 |
| 08-19 | 协作（没法共享） | 想让同事接手一个 Project | 复制粘贴给他 |
请回答四件事：
1. 这些墙按「额度 / 功能 / 协作管控」分，各几次？
2. 有没有哪几次其实是我自己用错了？
3. 按这本账，我该加购额度、升档，还是其实该降档？给一个结论加一句理由。
4. 如果答案是「先别动」，直接说先别动。Below is my log of the walls I hit this month. Help me decide what to do — don't upsell me.
| 08-03 | quota (weekly) | Cowork tidying Q2 invoices, 2nd run | waited until the next day |
| 08-06 | feature (not on Free) | wanted Research for vendor terms | opened 12 tabs by hand |
| 08-11 | quota (in session) | Claude Code refactoring the auth module | split into three, continued next day |
| 08-19 | collaboration (can't share) | wanted a colleague to take over a Project | copy-pasted it to them |
Answer four things:
1. Sorted into quota / feature / collaboration-and-controls, how many of each?
2. Were any of them actually my own misuse?
3. Based on this ledger, should I buy extra usage, upgrade, or actually downgrade? One conclusion plus one line of reasoning.
4. If the answer is 'change nothing yet,' say change nothing yet.
— III
怎么读这本账How to Read the Ledger.
三条判断，按顺序用。付费档撞限额时都能临时加购用量额度，不必直接跳档 —— 这一点很多人不知道，于是为一个月两次的墙付了一年的钱。3注 3Note 3Claude 帮助中心 · 用量与长度限额如何运作 —— 用量限额是你的「对话预算」，不同套餐额度不同；帮助中心不公布具体的小时 / 日 / 周数字。付费档（Pro / Max / Team 与按座位计费的 Enterprise）可以购买额外用量额度。截至 2026-08。Claude Help Center · How usage and length limits work — usage limits are your 'conversation budget,' and different plans carry different allowances; the help center publishes no specific hourly, daily, or weekly numbers. Paid plans (Pro / Max / Team and seat-based Enterprise) can purchase additional usage credits. As of 2026-08.Three calls, in order. Every paid tier can buy extra usage when it hits a limit, without jumping a tier — a fact many people don't know, and so they pay for a year to fix a wall they hit twice a month.3注 3Note 3Claude 帮助中心 · 用量与长度限额如何运作 —— 用量限额是你的「对话预算」，不同套餐额度不同；帮助中心不公布具体的小时 / 日 / 周数字。付费档（Pro / Max / Team 与按座位计费的 Enterprise）可以购买额外用量额度。截至 2026-08。Claude Help Center · How usage and length limits work — usage limits are your 'conversation budget,' and different plans carry different allowances; the help center publishes no specific hourly, daily, or weekly numbers. Paid plans (Pro / Max / Team and seat-based Enterprise) can purchase additional usage credits. As of 2026-08.
先别升Don't upgrade yet
一个月撞墙没几次、当前模型够用、没人要和你共享工作区 —— 加购额度比升档划算。而且先看第 2 问的答案：如果那几次撞墙里有一半是自己用错了档，修用法比修账单便宜。You hit the wall only a few times a month, the current model is enough, and nobody needs to share your workspace — buying extra beats upgrading. And read the answer to question 2 first: if half those hits were you running the wrong tier, fixing your usage is cheaper than fixing your bill.
该上 MaxTime for Max
几乎每周都撞额度、靠它吃饭、想第一时间用上新功能 —— 这时买的是额度和优先级，不是面子。两档的差别是 5× 和 20×，先上 5×，撞满了再说。You hit the limit almost weekly, depend on it for work, and want new features first — here you buy quota and priority, not prestige. The two tiers are 5x and 20x; start at 5x and revisit when you saturate it.
该上 TeamTime for Team
要和同事共享 Project、要统一管控（SSO、admin、集中计费）—— 这是协作计划，不是「个人 Max 的更高档」。标准座和高级座可以混用：大部分人标准座，重度用户给高级座。You need to share Projects with colleagues and want central control (SSO, admin, central billing) — a collaboration plan, not 'a higher Max.' Standard and premium seats mix: standard for most people, premium for the heavy users.
其实该降Actually downgrade
最少被考虑、却常常正确的一条。整月一次墙都没撞、Cowork 和 Research 一次没开过 —— 那你买的是安心，不是能力。这本账最大的价值可能就是让你省下这笔。The least considered and often correct answer. A whole month with no walls and Cowork and Research never opened once — you're buying peace of mind, not capability. Saving you that may be this ledger's largest return.
— IV
换个域，谁先撞墙Who Hits the Wall First, by Field.
这一栏很少撞额度墙 —— 写字的 token 消耗其实不大。真正撞的是功能墙：需要 Research 查证、需要 Cowork 批量出稿。所以这一栏的答案通常是「Free 升 Pro 就够，别碰 Max」。如果你在这一栏还是天天撞额度，先回第 3 章 —— 大概率是拿最贵的档在写日常草稿。This field rarely hits the quota wall — writing doesn't consume that many tokens. What it hits is the feature wall: needing Research to verify, needing Cowork to produce in bulk. So the answer here is usually 'Free to Pro is enough, skip Max.' If you're still hitting quota daily in this field, go back to Chapter 3 — you're almost certainly drafting everyday copy on the priciest tier.
这一栏最快撞额度墙，因为 Claude Code 的重活比对话吃得多。判断很简单：如果你每周有两天下午因为限额停下来，Max 的钱是赚回来的；如果是每月两次，加购就够。这一栏也最容易发现「其实是用法问题」—— 一次漫无目的的长会话，比一次有验收标准的循环贵好几倍。This field hits the quota wall fastest, because heavy Claude Code work consumes far more than chat. The call is simple: if two afternoons a week stop on a limit, Max pays for itself; if it's twice a month, extra usage is enough. This field also most often reveals 'it was a usage problem' — one aimless long session costs several times a loop with acceptance criteria.
这一栏撞的往往不是前两堵墙，是第三堵：你个人用得挺好，但同事看不到你的 Project、公司要求审计日志、法务问数据保留策略。这时候再多的额度也解决不了 —— 直接看 Team 和 Enterprise 那一行的功能，而不是看价格差。This field usually hits neither of the first two walls but the third: it works fine for you personally, and then colleagues can't see your Project, the company wants audit logs, and legal asks about the retention policy. No amount of quota fixes that — go read the feature rows for Team and Enterprise rather than comparing prices.
三种典型的撞墙形状。认出自己那一种，能省掉一整个月的观察。Three typical shapes. Recognizing yours can save you a month of observation.
— V
API 不在订阅里The API Isn't in Your Subscription.
这是最容易踩的一条，也是唯一一条需要我说明推理过程的判断。This is the easiest trap, and the one judgment in this chapter where I owe you my reasoning.价格页把 API 作为独立区块单列计价，与订阅分开；连 Enterprise 自助档也写成「$20/座，用量成本随模型与任务浮动」—— 座位费与用量是分开的两笔。5注 5Note 5Anthropic · Claude 套餐与价格 —— 页面把 API 作为独立区块单列计价，与订阅分开；Enterprise 自助档写明「$20/座，用量成本随模型与任务浮动」。截至 2026-08。Anthropic · Claude Plans & Pricing — the page prices the API in its own separate section, apart from subscriptions; the self-serve Enterprise tier is written as '$20/seat. Usage cost scales with model and task.' As of 2026-08.说明一句：官网页面上没有一句原话说「订阅不含 API 额度」。这条是从它的计费结构读出来的推论，不是引语。但结构本身很清楚：客户端的用量走订阅，程序化调用走开发者平台的 token 计费。The pricing page prices the API in its own separate section, apart from subscriptions; even self-serve Enterprise is written as '$20/seat. Usage cost scales with model and task' — the seat fee and the usage are two different lines.5注 5Note 5Anthropic · Claude 套餐与价格 —— 页面把 API 作为独立区块单列计价，与订阅分开；Enterprise 自助档写明「$20/座，用量成本随模型与任务浮动」。截至 2026-08。Anthropic · Claude Plans & Pricing — the page prices the API in its own separate section, apart from subscriptions; the self-serve Enterprise tier is written as '$20/seat. Usage cost scales with model and task.' As of 2026-08.To be straight with you: nowhere on that page is there a sentence saying 'a subscription does not include API credit.' That's an inference from the billing structure, not a quote. But the structure is unambiguous: client usage runs on the subscription, programmatic calls run on the developer platform's token billing.那条线在哪：当你要把 Claude 接进自己的程序、做自动化集成、跑批量任务时，才跨到 API；只在客户端里用（网页、桌面、手机、Claude Code），订阅就够，开 API 是白花钱。Where the line sits: you only cross to the API when wiring Claude into your own program, building automated integrations, or running batch jobs. If you only use the clients (web, desktop, mobile, Claude Code), the subscription is enough and opening an API account is wasted money.
— VI
收束 · 本章验收Sign-off.
建了一份 walls.md（或一条便签），四栏齐了。Created a walls.md (or one note) with all four columns.
至少记了一次真实的撞墙，包含「当时在做什么」。Logged at least one real wall, including what you were doing at the time.
知道付费档可以临时加购额度，不必直接升档。Know that paid tiers can buy extra usage without jumping a tier.
确认自己没在为根本没打开过的功能付钱（Cowork、Research、Design 上个月开过几次？）。Confirmed you're not paying for features you never open (how many times did you use Cowork, Research, Design last month?).
如果你只在客户端里用，确认自己没有多开一个 API 账户。If you only use the clients, confirmed you haven't also opened an API account you don't need.
贵的不是高档，
是买了用不上的那一档.
The costly tier isn't the high one,
it's the one you don't use.
Aklman Library
— 讨论Discussion
讨论Discussion.
评论区初始化中…Initializing comments…
01 / 01
没有匹配结果No matches.
换个关键词，或按 Esc 回到页面Try another keyword, or press Esc to return
