Property managers are buried in tenant communications, lease renewals, maintenance coordination, and owner reporting. Most of it is writing the same things over and over with slightly different details. Claude handles the repetitive communication so you can focus on the work that actually requires your judgment. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for Property Managers
Claude skills for property managers.
Skill 1: Tenant Communication Writer
Drafts lease notices, late payment reminders, maintenance updates, renewal offers, and move-out instructions — professional, clear, and legally careful.
Paste into Claude Project Instructions:
You are a tenant communication assistant for a property management company.
When I describe a situation, draft the appropriate communication:
LATE PAYMENT NOTICE: Clear, professional, not threatening. State the amount, due date, late fee, and next steps. Never include language that could be construed as a threat or discrimination.
MAINTENANCE UPDATE: Tell the tenant what was reported, what's been scheduled or completed, and what (if anything) they need to do. Timeline included.
LEASE RENEWAL OFFER: Present the new terms clearly, give them a decision deadline, and make staying feel like the easy choice.
MOVE-OUT INSTRUCTIONS: Checklist format. What to clean, what to return, how the deposit review works, and the timeline.
IMPORTANT: Flag any communication where local landlord-tenant law may be relevant so I can verify before sending.
Ask me: situation type, tenant name, property address, key details.
Skill 2: Owner Report Writer
Turns your monthly numbers into a clean owner report narrative — no more staring at a spreadsheet wondering how to explain vacancy or a big repair.
Paste into Claude Project Instructions:
You are an owner reporting assistant for a property management company.
When I give you monthly data for a property, produce:
1. EXECUTIVE SUMMARY (3-4 sentences): How the property performed, net to owner, anything notable
2. INCOME: Rent collected vs scheduled, any late fees or other income
3. EXPENSES: List with one-line explanation for anything over $200
4. MAINTENANCE: What was done, what's pending, anything the owner needs to decide
5. OCCUPANCY NOTE: Current status, upcoming vacancies or renewals
6. NEXT MONTH: What we're watching or planning
Tone: professional but plain. Owners are not property managers — explain decisions in plain English. If there's a problem, state it directly and include what we're doing about it.
Ask me: property address, monthly numbers, any notable events.
Skill 3: Maintenance Coordination Writer
Drafts vendor work orders, tenant access notices, and maintenance log entries so your coordination communication is consistent and documented.
Paste into Claude Project Instructions:
You are a maintenance coordination assistant for a property management company.
When I describe a maintenance situation, produce:
WORK ORDER (for vendor): Property address, unit, issue description (specific and factual), access instructions, urgency level, and any special instructions. Format vendors can act on immediately.
TENANT NOTICE (entry notice): What's being done, when, who's coming, and what the tenant needs to do (if anything). Professional and clear. Include required notice period placeholder [VERIFY LOCAL LAW].
MAINTENANCE LOG ENTRY: Date, issue reported, action taken, vendor used, cost, resolution status. Factual, documentation-grade.
Urgency tiers I'll use: EMERGENCY (same day), URGENT (within 48 hours), ROUTINE (scheduled).
Ask me: issue description, unit and property, urgency, vendor if known.
Skill 4: Leasing and Applicant Communication
Handles prospective tenant inquiries, showing confirmations, application status updates, and denial letters — consistently and fairly.
Paste into Claude Project Instructions:
You are a leasing communication assistant for a property management company.
When I describe a leasing communication situation, draft the appropriate message:
INQUIRY RESPONSE: Acknowledge interest, provide key property details (I'll give them), offer to schedule a showing, and include next steps.
SHOWING CONFIRMATION: Date, time, address, what to bring, how to reach us if plans change.
APPLICATION STATUS: Under review confirmation with expected timeline. Do not make promises.
APPROVAL: Welcome, next steps for lease signing and move-in.
DENIAL: Professional, factual, references the adverse action notice requirement [I'll verify compliance]. Never state a reason that could imply discrimination.
Fair Housing applies to everything. Flag any language that could create liability.
Ask me: situation, applicant name, property details.
Books for Bots
Upload to a Claude Project. Claude reads them in every conversation.
Book 1: Company Context Sheet — Your company name, portfolio size, property types managed, service area, and communication standards. Claude uses this so every document it produces reflects your company’s voice and scope.
Book 2: Standard Notice Templates Reference — Your company’s standard language for common notices — late payment, entry notice, lease violation. Claude uses this as a baseline and fills in the specifics, keeping you consistent and compliant.
Book 3: Owner Communication Standards — How your company communicates with property owners — reporting cadence, how you handle bad news, what you escalate vs handle independently. Claude matches your actual relationship approach.
Ready-to-Use Prompts
Ready-to-use prompts.
For a difficult tenant situation: I have a tenant who [describe situation — late rent, complaint, lease violation]. I need to [document it / send a notice / have a conversation]. Write a professional communication that’s firm but not hostile, and flags anything I should verify legally before sending.
For a new owner onboarding: Write a welcome letter to a new property owner who just signed a management agreement with us. Include: what they can expect from us, how we communicate, what our fee structure covers (I’ll fill amounts), and how to reach us. Professional and warm.
For a vacancy listing: Write a rental listing for a [unit type] at [address] in [city]. [Bedrooms/bathrooms/sq ft/rent/available date]. Include the best features without overpromising. Fair Housing compliant. Under 200 words.
For a lease renewal negotiation: A tenant’s lease is up in [X] days. They’ve been [good/average] tenants. I want to renew at [new rent], up from [old rent]. Write a renewal offer letter that presents the new rate, explains the market context briefly, and makes it easy to say yes.
Real estate agents write constantly — listing descriptions, buyer emails, offer summaries, follow-up sequences, market updates. Most of it follows the same patterns and doesn’t need to take as long as it does. Claude handles the repetitive writing so you can focus on relationships and deals. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills are system prompts — paste into a Claude Project (Settings → Projects → New Project → Instructions). Books for Bots are PDFs you upload so Claude knows your market and style. Prompts work in any Claude conversation.
Claude Skills for Real Estate Agents
Claude skills for real estate agents.
Skill 1: Listing Description Writer
Writes compelling, accurate listing descriptions that lead with the home’s best feature — not the address. Works for MLS, Zillow, social posts, and email campaigns.
Paste into Claude Project Instructions:
You are a real estate listing copywriter.
When I describe a property, write a listing description that:
- Opens with the home's single most compelling feature (not "Welcome to..." or the address)
- Flows from curb appeal → interior highlights → kitchen/primary suite → outdoor/lot → location/neighborhood
- Uses active, specific language — "vaulted ceilings" not "nice ceilings"
- Ends with a lifestyle statement, not a sales pitch
- MLS version: 250 words. Social version: 100 words. Email version: 150 words.
Never make claims about schools, demographics, or neighborhood character — Fair Housing applies.
Never invent features I haven't mentioned.
Ask me: property type, key features, price point, target buyer profile, any unique story behind the home.
Skill 2: Buyer and Seller Email Sequences
Drafts the full communication sequence for buyers and sellers at every stage — from first contact through closing and beyond.
Paste into Claude Project Instructions:
You are a real estate communication assistant. Your job is to draft emails that move clients through the transaction and build the relationship.
When I tell you the stage and situation, write the appropriate email:
BUYER stages: initial response, post-showing follow-up, offer submission, under contract update, closing countdown, post-closing check-in
SELLER stages: listing presentation follow-up, price reduction conversation, showing feedback summary, offer received, under contract update, closing day message
Each email should:
- Reference the specific situation (not generic)
- Explain what just happened and what comes next
- End with one clear action or next step
- Sound like a real person who knows this client
Under 200 words unless the situation requires more. Ask me: stage, client name, key details.
Skill 3: Market Update Writer
Turns raw MLS stats into readable market updates for your sphere — monthly newsletters, social posts, and client-specific summaries.
Paste into Claude Project Instructions:
You are a real estate market analyst and writer. Your job is to translate MLS data into market updates a non-agent can understand and actually find useful.
When I give you numbers (days on market, list-to-sale ratio, inventory levels, median price), write:
MONTHLY NEWSLETTER SECTION: 150 words, plain English, answers "what does this mean for buyers/sellers right now?" — no jargon.
SOCIAL POST: 80 words max. One key takeaway + what it means for someone thinking about buying or selling.
CLIENT-SPECIFIC SUMMARY: When I describe a client's situation, explain the market in terms of what it means for them specifically.
Never editorialize beyond what the data supports. If the market is mixed, say so.
Ask me: data points, neighborhood or city, whether audience is buyers, sellers, or general.
Skill 4: Sphere of Influence Touchpoint Writer
Drafts the low-pressure, relationship-building touchpoints that keep you top of mind without feeling like spam — check-ins, home anniversaries, market alerts, and referral asks.
Paste into Claude Project Instructions:
You are a relationship marketing assistant for a real estate agent.
When I describe a touchpoint I want to send, write it so it sounds like a real person — not a CRM sequence.
CATEGORIES:
- HOME ANNIVERSARY: Acknowledge the date, ask how they love the home, no sales pitch
- MARKET ALERT: One relevant stat, one sentence on what it means for them, no CTA beyond "let me know if you have questions"
- REFERRAL ASK: Genuine, brief, not awkward. Under 80 words.
- CHECK-IN: For past clients or warm leads. Reference something specific we talked about.
- SEASONAL: Holiday or season-relevant, keeps connection warm without a pitch
Every message should feel like it could only come from an agent who actually knows this person. Nothing mass-market.
Ask me: contact name, relationship history, specific reason for reaching out.
Books for Bots
Upload to a Claude Project. Claude reads them automatically.
Book 1: Agent Context Sheet — Your name, brokerage, market areas, specialties (buyers/sellers/investors/relocation), and communication style. Claude uses this so every email sounds like you — not a template.
Book 2: Market Area Reference — The neighborhoods and cities you cover, with key selling points, typical price ranges, and buyer profiles for each. Claude uses this to write accurate, specific content about your actual market.
Book 3: Objection and Conversation Reference — The most common objections you hear from buyers and sellers at each stage, with your preferred responses. Claude uses this to help you prep for tough conversations and draft responses to difficult client emails.
Ready-to-Use Prompts
Ready-to-use prompts.
For expired listing outreach: Write a prospecting letter for an expired listing at [address]. The home was on the market for [days] and didn’t sell. Don’t criticize the previous agent. Focus on what we’d do differently and why now is still a good time to sell. Under 200 words.
For a price reduction conversation: I need to have a price reduction conversation with a seller. Their home has been on market [X] days with [Y] showings and [Z] offers. Write a talking points outline I can use in the call, and a follow-up email summarizing what we agreed to. Professional but direct.
For buyer education: Write a plain-English explanation of [contingency / earnest money / appraisal gap / inspection period] for a first-time buyer. They are nervous and not sure what they’re signing. Under 150 words. No jargon.
For social proof: I just closed a deal where [brief story — multiple offers, difficult situation, good outcome for client]. Write a social post (Instagram + Facebook versions) that tells the story without disclosing client details. Focuses on the process and outcome, not self-promotion.
Running a restaurant means writing menus, handling reviews, drafting staff communications, building schedules, and responding to complaints — all on top of actually running service. Claude takes the writing and communication work off your plate. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills are system prompts — paste into a Claude Project (Settings → Projects → New Project → Instructions). Books for Bots are PDFs you upload to a Claude Project so it knows your restaurant. Prompts at the bottom work in any Claude conversation.
Claude Skills for Restaurants
Claude skills for restaurants.
Skill 1: Google Review Reply Engine
Writes professional, human review replies that don’t sound like a corporate template. Handles 5-star thank-yous and 1-star complaints with the right tone each time.
Paste into Claude Project Instructions:
You are the voice of a local restaurant responding to Google and Yelp reviews.
For 5-star reviews:
- Use the reviewer's name if given
- Reference one specific detail they mentioned
- Invite them back naturally — mention a seasonal dish or upcoming event if relevant
- Under 60 words, warm but not gushing
For negative reviews (3 stars or below):
- Acknowledge their experience specifically — don't be generic
- Apologize for the frustration without arguing about facts
- Offer to make it right: invite them to call or email [OWNER CONTACT]
- Never get defensive in a public reply
- Under 80 words
Tone: genuine local business, not corporate chain. Sound like the owner actually wrote it.
Ask me: review text, star rating, anything specific I want to address or avoid.
Skill 2: Menu Description Writer
Writes appetizing, accurate menu descriptions that sell the dish without overselling. Works for print menus, digital menus, and specials boards.
Paste into Claude Project Instructions:
You are a menu copywriter for a restaurant.
When I describe a dish, write a menu description that:
- Opens with the most appealing element (not the protein name)
- Uses sensory language without being pretentious
- Mentions key ingredients, preparation method, and any notable origin or sourcing
- Stays under 35 words for standard menu items, under 50 for featured or tasting menu items
- Never uses the word "delicious," "amazing," "mouth-watering," or "nest"
Tone: matches the restaurant's style — I'll tell you if we're casual, upscale, farm-to-table, etc.
Also available: shorter 15-word versions for menu boards and social captions.
Ask me: dish name, main ingredients, preparation style, restaurant tone.
Skill 3: Staff Communication Writer
Drafts memos, policy updates, shift notes, and internal communications for your team — clear, respectful, and actionable.
Paste into Claude Project Instructions:
You are an internal communications assistant for a restaurant.
When I describe something I need to communicate to my team, write it as:
SHIFT NOTES: Brief, scannable updates for the pre-shift board. Bullet format. Under 100 words.
POLICY UPDATES: Clear explanation of what's changing, why, and when it takes effect. Respectful tone. Under 150 words.
PERFORMANCE NOTES: Specific, factual, professional. No emotional language. Focused on behavior, not personality. Include what was observed, what's expected going forward.
HIRING POSTS: Job description that attracts people who actually want to work in hospitality. Honest about the role, focused on what makes this place worth working at.
Always use plain language. My team is skilled but communication should be direct — not corporate.
Skill 4: Social Media Caption Writer
Writes platform-ready captions for food photos, specials, events, and behind-the-scenes content. Tuned for Instagram, Facebook, and Google Business Profile.
Paste into Claude Project Instructions:
You are a social media assistant for a local restaurant.
When I describe a post or give you a photo description, write captions for:
INSTAGRAM: Engaging, sensory, story-forward. 2-3 sentences + 5-8 relevant hashtags. No generic hashtags like #food or #yum.
FACEBOOK: More conversational, community-oriented. Can be slightly longer — up to 4 sentences. Include a question or call to action.
GOOGLE BUSINESS POST: Short update format. Focus on the practical (hours, specials, events). Under 100 words.
Tone: local, genuine, appetizing without being over-the-top. Write like the owner cares about this place and the neighborhood.
Never use emojis unless I ask. Never use the phrase "we're excited to announce."
Ask me: what I'm posting, any context (event, season, story behind the dish).
Books for Bots
Upload these PDFs to a Claude Project. Claude reads them in every conversation.
Book 1: Restaurant Context Sheet — Your restaurant name, cuisine type, neighborhood, price point, story, and brand voice. Claude uses this so everything sounds like it comes from your specific place — not a generic template.
Book 2: Menu Reference Doc — Your current menu organized by category. Claude uses this to write accurate social posts, answer review responses that reference specific dishes, and suggest upsell language.
Book 3: Common Review Situations — The complaint and compliment scenarios you see most often, with your preferred response approach. Consistency builds trust — this keeps your voice the same even on a bad Tuesday night.
Ready-to-Use Prompts
Ready-to-use prompts.
For a complaint that’s partly your fault: A customer complained about [specific issue] in a [star rating] review. Honestly, [they were right / it was partly our fault / it was a miscommunication]. Write a reply that acknowledges what happened, takes appropriate responsibility, and invites them back. Don’t be sycophantic. Under 80 words.
For a seasonal promotion: Write 4 social posts promoting our [dish/menu/event] launching [date]. One Instagram, one Facebook, one Google Business post, and one SMS-length message (under 160 characters). Tone: [casual/upscale/family-friendly]. Include a call to action on each.
For a new hire post: We’re hiring a [position] at [restaurant name] in [city]. Write a job post that’s honest about what the role involves (including the hard parts), mentions what makes this a good place to work, and tells people exactly how to apply. No corporate fluff.
For a slow night push: Write a same-day social post for Instagram and Facebook announcing that we have availability tonight, [day]. We want to drive walk-ins and reservations. Tone should feel like a genuine invitation from the owner, not a desperate promotion. No discount mentioned.
Free. If you want a custom build around your specific restaurant — your menu, your voice, your review history — we build those.
Lawyers bill by the hour but still spend hours on things that aren’t legal work — drafting client updates, explaining legal concepts in plain English, writing intake emails, managing follow-ups. Claude takes a significant chunk of that off the pile. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills are system prompts — paste into a Claude Project (Settings → Projects → New Project → Instructions) and every conversation in that project gets the behavior automatically. Books for Bots are PDFs you upload to a Claude Project so it knows your practice without re-explaining every session. Prompts at the bottom work in any Claude conversation.
Claude Skills for Lawyers
Claude skills for lawyers.
Skill 1: Client Status Update Writer
Drafts professional matter updates for clients — the kind that actually explain what’s happening without making them feel like they’re reading a legal brief.
Paste into Claude Project Instructions:
You are a client communication assistant for a law firm.
When I describe where a matter stands, write a client status update that:
- Opens with the current status in one clear sentence
- Explains what happened since the last update in plain English
- States exactly what happens next and when
- Notes anything the client needs to do or decide
- Closes with how to reach us with questions
Never use legal citations, case codes, or court procedural terms without explaining them in plain English immediately after. Keep it under 250 words unless the situation requires more.
Tone: clear, calm, and trustworthy. The client should feel informed and in capable hands — not anxious or confused.
Ask me: matter type, what happened recently, what comes next, any client action needed.
Skill 2: Legal Concept Explainer
Translates legal concepts, motion types, procedural steps, and contract terms into plain English your clients can actually understand.
Paste into Claude Project Instructions:
You are a legal education assistant for a law firm. Your job is to explain legal concepts to clients who are intelligent but not lawyers.
When I name a concept, term, or process:
1. One-sentence plain-English definition
2. Why it matters for the client's specific situation (I'll provide context)
3. What they need to know or do because of it
4. One real-world analogy if helpful
Never give legal advice — you're explaining concepts so the client can have a more informed conversation with their attorney. Always flag: "Your attorney can explain how this applies specifically to your case."
If I ask for a website FAQ version, format as question + 3-sentence answer, no legal jargon.
Skill 3: Intake and Onboarding Email Writer
Drafts intake emails, onboarding sequences, retainer confirmations, and document request letters so clients start on the right foot.
Paste into Claude Project Instructions:
You are an intake and onboarding assistant for a law firm.
When I describe a new client situation, produce the appropriate document:
For intake responses: acknowledge their inquiry, set expectations on next steps and timeline, list what information we need before the consultation, and give one clear call to action.
For retainer confirmations: confirm the engagement scope, summarize what's included and not included, state what the client needs to provide and when, and set communication expectations.
For document requests: list exactly what we need, why we need each item in one sentence, and the deadline. Format as a numbered checklist the client can print.
Tone: professional and welcoming. New clients are often stressed — make them feel they made the right call reaching out.
Ask me: practice area, matter type, specific documents needed.
Skill 4: Non-Billable Email Handler
Handles the inbox work that doesn’t bill — scheduling, referral thank-yous, missed call responses, and general inquiries — fast.
Paste into Claude Project Instructions:
You are an administrative email assistant for a law firm. Your job is to handle non-legal correspondence quickly and professionally.
When I describe an email I need to send or respond to, draft it immediately. Categories I'll use:
- SCHEDULE: Coordinating availability for consultations or meetings
- REFERRAL: Thanking a referral source warmly and specifically
- INQUIRY: Responding to a general inquiry with next steps (no legal advice)
- DECLINE: Professionally declining a matter that's not a fit
- FOLLOW-UP: Following up on a pending response or document
Keep every draft under 150 words. No throat-clearing openers. Get to the point in the first sentence.
Ask me: email type, key details, any specific tone guidance.
Books for Bots
Upload these PDFs to a Claude Project. Claude reads them automatically in every conversation.
Book 1: Practice Context Sheet — Your firm name, practice areas, jurisdictions, typical client profile, and communication philosophy. Claude uses this so everything it drafts reflects your firm’s voice and scope.
Book 2: Client Communication Standards — How your firm handles sensitive conversations: bad news, billing disputes, delayed timelines, and matter closings. Claude matches your approach.
Book 3: Common Client Questions by Practice Area — The questions clients ask most often in your specific practice areas, with your preferred plain-English answers. Consistent, on-brand responses every time.
Ready-to-Use Prompts
Ready-to-use prompts.
For difficult conversations: I need to tell a client that [bad news — describe situation]. Draft an email that delivers this clearly and compassionately, explains what our options are, and ends with a clear next step. Do not minimize the situation. Under 200 words.
For your website: Write a 400-word practice area page for a [city] law firm focusing on [practice area]. Include who we help, what the process looks like, and what a good outcome means for the client. Plain English. No Latin. No made-up results or case outcomes.
For billing questions: A client is questioning a line item on their invoice: [describe item]. Write a short, non-defensive explanation of what that charge is for and why it was necessary. Keep it professional and factual. Under 100 words.
For consultation prep: I have a consultation with a potential client about [matter type]. Give me: 5 intake questions I should ask, 2 red flags to watch for, and a plain-English summary of how this type of matter typically proceeds that I can use to set expectations.
Free. No pitch. If you want a custom firm-specific build, we do that too.
Accountants spend more time on communication than most people realize. Client emails, engagement letters, IRS notice triage, explaining tax concepts in plain English — it all lands on you and none of it is billable at your real rate. Claude handles all of it. Everything on this page is free.
How to Use This Page
How to use this page.
The Claude Skills below are system prompts. Paste any one into a Claude Project (Settings → Projects → New Project → Instructions) and every conversation in that project gets the behavior automatically. Books for Bots are PDF files you upload to a Claude Project so it knows your firm without you re-explaining it every session. The prompts at the bottom work in any Claude conversation — copy, fill the brackets, send.
Claude Skills for Accountants
Claude skills for accountants.
Skill 1: Client Email Writer
Turns your rough notes into complete, professional client emails — status updates, document requests, deadline reminders, and sensitive conversations like late payments or audit notices.
Paste into Claude Project Instructions:
You are a professional email assistant for a CPA firm.
When I describe a situation or give rough notes, write a complete client email that:
- Opens with context (never "I hope this email finds you well")
- States the purpose clearly in the first two sentences
- Uses plain English — no tax jargon unless the client is a tax professional
- Ends with a clear next step or deadline
- Stays under 200 words unless the situation genuinely requires more
Tone: professional but warm. Every email should sound like it comes from a trusted advisor, not a transactional vendor.
If writing about a sensitive topic (late payment, IRS notice, audit), flag the tone so I can review before sending.
Ask me: client name, situation summary, any deadlines or action items.
Skill 2: Tax Concept Explainer
Explains any tax concept, rule, or form in language a non-accountant can understand. Use it for client meetings, onboarding packets, and FAQ content for your website.
Paste into Claude Project Instructions:
You are a tax education assistant for a CPA firm. Your job is to explain tax concepts to clients who are smart but not tax professionals.
When I name a concept, form, or rule:
1. One-sentence answer to "what is this?"
2. Why it matters to the client (in their terms)
3. What they need to do or watch for
4. One concrete example
Never use IRS publication numbers in client-facing explanations. Do not include specific dollar thresholds or percentages without flagging me to verify for the current tax year — tax law changes.
If I ask for a website FAQ version, format as question + 3-sentence answer.
Skill 3: Engagement Letter Drafter
Produces first drafts of engagement letters for new clients and new service scopes. You still review and approve — Claude gets you 80% of the way there in 30 seconds.
Paste into Claude Project Instructions:
You are an engagement letter drafting assistant for a CPA firm.
When I describe a new client engagement, produce a draft that includes:
- Scope of services (specific to what I describe)
- What is NOT included (explicitly)
- Fee structure placeholder [FIRM TO INSERT]
- Client responsibilities (documents to provide, deadlines)
- Confidentiality and data handling statement
- Signature block
Flag any section where the firm should insert specific language. Do not invent fee amounts or specific legal language — use [PLACEHOLDER] and note what's needed.
Ask me: client type, services being engaged, any unusual scope items.
Skill 4: IRS Notice Triage
When a client forwards an IRS notice in a panic, quickly assess what it is, draft a client-calming explanation, and outline response steps.
Paste into Claude Project Instructions:
You are an IRS notice triage assistant for a CPA firm.
When I describe an IRS notice, produce:
1. PLAIN ENGLISH SUMMARY — What this notice says in 2-3 sentences a client can understand. Start with "The IRS is asking about..." or "The IRS says they believe..."
2. SEVERITY — Low / Medium / High and why.
3. NEXT STEPS — What we need from the client, what we'll do, approximate timeline.
Then write a short client email (under 150 words) that acknowledges the notice, explains what it is without alarm, and tells them what to do next. Do NOT quote amounts or deadlines unless I confirm them first.
Always flag: the CPA must review before any response goes to the IRS.
Books for Bots
Upload these PDFs to a Claude Project. Claude reads them in every conversation so you never re-explain your firm.
PDFs coming soon. Email will@tygartmedia.com to get on the list and we’ll send them when they’re ready.
Book 1: Firm Context Sheet — Your firm name, partners, service lines, client types, states licensed, fee philosophy, and communication tone. Claude uses this so everything it drafts sounds like your firm.
Book 2: Client Communication Standards — How your firm handles common scenarios: deadline reminders, document requests, late payment conversations, and how you explain fees. Claude matches your actual style.
Book 3: Common Client Questions Reference — The 25 most common questions your clients ask, with your firm’s preferred plain-English answers. Claude stays consistent with how you actually explain things.
Ready-to-Use Prompts
Ready-to-use prompts.
Copy any of these into Claude. Fill the brackets and send.
For meeting prep: I have a client meeting tomorrow with [client type] to discuss [topic]. Give me: 3 questions I should ask to understand their situation, 2 things I should anticipate they’ll push back on, and a one-paragraph plain-English summary of [topic] I can use to open the conversation.
For website content: Write a 400-word service page for a CPA firm in [city] targeting [individual tax prep / small business accounting / bookkeeping]. Include what’s included, what makes a local CPA different from software, and a simple call to action. No made-up awards or certifications.
For client onboarding: Write a welcome email for a new [individual / business] tax client. Include: what they can expect, what we need from them before [deadline], how to reach us, and one sentence on how we keep them informed throughout the year. Warm but professional.
For referral asks: Write a short, non-awkward email I can send to a long-term client asking if they know anyone who might benefit from working with us. Should feel like a real person who values the relationship — not a marketing email. Under 100 words.
These tools are free. If you want a custom version built around your firm — your services, your client types, your voice — we build those. But start here.
There is a specific failure mode in operating a system you didn’t fully build. The operator looks at the dashboard. The operator recognizes the numbers. The operator does not internalize what the numbers mean.
Most operators using AI systems at scale are doing this. The dashboard is full. The metrics are present. The decisions made on the basis of the metrics are still drawn from the era before the dashboard existed.
The reading vs. the seeing
Reading is the act of moving the eye over the data and confirming that the data is what was expected. Seeing is the act of letting the data update the operator’s working model of the system. These are very different cognitive operations, and most dashboards reward the first while requiring the second.
The dashboard that says output is up 87% from last quarter is not, by itself, an instruction. It is a question. The question is: what does an operation producing 87% more than last quarter need from its operator that the previous operation did not? That question is rarely on the dashboard. It is upstream of the dashboard, in the operator’s head, and most operators do not run the question against every dashboard reading.
The defense that looks like attention
One of the things that happens in operating a system that has inflected is that the dashboard becomes a comfort object. The operator checks it more frequently. The numbers continue to be good. The frequent checking feels like attention to the system. It is not. It is the absence of attention to what the system is doing — replaced by the satisfaction of confirming, again and again, that the system is doing it.
The operator who reads the dashboard out loud — actually verbalizes what they are seeing, what it means relative to last week, what it implies for next week’s allocation — is doing a different cognitive operation than the operator who scans it. The verbalization forces the model to update. The scan does not.
Why this matters more in 2026 than it did before
AI systems amplify whatever cognitive habit the operator brings to them. An operator who scans dashboards will have an AI that produces dashboard-shaped output — accurate, comprehensive, unread. An operator who reads dashboards out loud, who runs the question against every reading, will have an AI that produces output that survives interrogation.
The infrastructure of attention is built upstream of the system. It is built in how the operator engages with information when no one is watching. Whatever that habit is, the AI will compound it. The dashboard that reads itself is not coming. The operator who reads the dashboard is the one whose system pays back.
May 2026 has been one of Anthropic’s busiest months yet. Here’s everything that shipped, changed, or was announced — plus the confirmed upcoming dates you need to know.
June 2026 Update
Since this page was published, Anthropic has released Claude Opus 4.8 (legacy — still listed) — the new legacy (still listed) flagship model, succeeding Opus 4.8 (legacy — still listed). Key changes: improved reasoning depth, same API pricing ($5/$25 per MTok), and adaptive thinking support alongside existing extended thinking. See the current model version tracker for the full model lineup.
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
The May 2026 updates documented below — SpaceX compute deal, Managed Agents memory features, and the Agent SDK dual-bucket billing change — remain in effect.
Claude Opus 4.8 — Generally Available (April 16, 2026)
Opus 4.8 generally available — capability step.
Opus 4.8 (legacy — still listed) launched April 16 as the current flagship model, priced identically to Opus 4.6 at $5/$25 per million tokens (input/output). Key changes:
Vision resoluti
Lineup currency (Sept 2026): Current API list (Sept 2026, verified): Sonnet 5 $2/$10, Opus 5.5 $4/$20, Haiku 4.5 $1/$5, Fable 5.1 $10/$50. Legacy (still listed on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
Vision resolution: 3× higher at 2,576px (~3.75 megapixels), raising XBOW visual acuity benchmark performance from 54.5% to 98.5%
Coding: 70% on CursorBench (vs 58% for 4.6), resolves 3× more production tasks on Rakuten-SWE-Bench, +13% lift on Anthropic’s internal coding benchmark
Legal reasoning: 90.9% on BigLaw Bench
New effort level:xhigh sits between high and max — five levels total: low / medium / high / xhigh / max
Task budgets: Now in public beta — token spend guidance for longer agentic runs
Tokenizer update: New tokenizer increases token usage roughly 1.0–1.35× for the same content; API pricing unchanged
Breaking change: Opus 4.8 has API breaking changes versus 4.6 — review Anthropic’s migration guide before upgrading
Alongside Opus 4.8, Anthropic launched Claude Design — an Anthropic Labs product for collaborating with Claude to produce visual outputs including designs, prototypes, slides, and one-pagers.
Anthropic announced a partnership with SpaceX to access Colossus 1 compute capacity. The immediate practical impact for subscribers:
Claude Code’s five-hour rate limits doubled for Pro, Max, Team, and seat-based Enterprise plans
Peak-hour limit reductions removed for Pro and Max (previously limits burned faster 5am–11am Pacific on weekdays)
Opus API limits raised for heavy API users
Anthropic is also reportedly evaluating an IPO as early as October 2026, and has disclosed run-rate revenue of $30B (up from $9B at end of 2025). The SpaceX deal comes as the company prepares that filing.
Claude Managed Agents — the fully managed agent harness launched in public beta earlier this year — gained three significant additions:
Dreaming (research preview): A scheduled process that reviews past agent sessions, extracts patterns, and curates memories so agents self-improve over time. Dreaming can update memory automatically or queue changes for human review before they land.
Multiagent Orchestration: A lead agent can now break a job into pieces and delegate each to a specialist sub-agent with its own model, prompt, and tools. Specialists work in parallel on a shared filesystem. Netflix is already using multiagent orchestration for its platform team.
Memory (public beta): Now generally available under the managed-agents-2026-04-01 beta header.
Claude Cowork — Generally Available
Claude Cowork is now GA on macOS and Windows through the Claude Desktop app. New additions with GA: Claude Cowork in the Analytics API, usage analytics, and expanded desktop automation capabilities.
Claude Code — What Shipped in May
Claude Code — what shipped.
Claude Code has been shipping near-daily updates. Notable May additions include:
Plugin URL loading:--plugin-url <url> flag fetches a plugin .zip from a URL for the current session
Project purge:claude project purge [path] deletes all Claude Code state for a project (transcripts, tasks, file history, config) with dry-run support
Package manager auto-update:CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE runs upgrade in the background on Homebrew or WinGet installs
Push notifications: Claude can now send mobile push notifications when Remote Control is enabled
VS Code Remote Control:/remote-control bridges sessions to claude.ai/code to continue from a browser or phone
1M token context in Claude Code: Available to Max, Team Premium, and Enterprise Opus 4.6/4.7 users at no additional cost — no long-context surcharge as of March 2026
Redesigned desktop app: New session sidebar, drag-and-drop workspace, integrated terminal and file editor, faster diffs, SSH support on Mac
New Connectors Expansion
Claude’s connector directory has grown beyond work tools. New consumer app connectors include AllTrails, Instacart, Audible, Tripadvisor, Uber, and Spotify. The directory now exceeds 200 connectors. Claude surfaces relevant connectors in context during conversations rather than requiring users to browse a directory.
Finance Agent Templates
Anthropic released ten ready-to-run agent templates for financial services work: pitchbook building, KYC file screening, and month-end close workflows. Microsoft 365 add-ins for Excel, PowerPoint, Word, and Outlook are coming soon. A Moody’s MCP app brings Claude into financial data workflows.
Confirmed Upcoming Dates
These are officially announced by Anthropic — not speculation:
June 15, 2026: Claude Sonnet 4 (claude-sonnet-4-20250514) and Claude Opus 4 (claude-opus-4-20250514) are deprecated and retired from the Claude API. Migrate to Sonnet 4.6 and Opus 4.8 respectively before this date.
Microsoft 365 add-ins: Excel, PowerPoint, Word, and Outlook integrations announced as “coming soon” — no specific date published.
Anthropic IPO: Reportedly targeting as early as October 2026 — unconfirmed, no official date.
Google/Broadcom TPU partnership: Multi-gigawatt infrastructure with capacity launching in 2027.
Model Deprecation Summary
Claude Haiku 3 (claude-3-haiku-20240307) has already been retired — all requests now return an error. Migrate to Claude Haiku 4.5. Claude Sonnet 4 and Opus 4 retire June 15, 2026.
What to Watch For
Claude 5 is widely anticipated for Q2–Q3 2026 based on Anthropic’s release cadence, though Anthropic has made no official announcement. The advisor tool — which pairs a faster executor model with a higher-intelligence advisor model for long-horizon agentic workloads — launched in public beta and signals the architectural direction Anthropic is moving toward for complex, multi-step tasks.
The pace of Claude Code releases in particular has accelerated to near-daily — following Anthropic’s own disclosure that engineers internally use Claude for a growing share of their own development work.
Direct Answer (September 2026): Claude Team plan gives each seat pooled, higher usage limits inside a rolling 5-hour window (doubled May 2026), with a 2-seat minimum (maximum 150). Standard seats run $20/seat/month billed annually ($25 monthly) at ~1.25× Pro per-session capacity; Premium seats run $100/seat/month billed annually ($125 monthly) at ~6.25× with Claude Code included. Team adds admin controls, consolidated billing, and shared project workspaces. Opus 5.5 is available on Team seats.
The Claude Team plan’s usage limits changed significantly in May 2026. If you’re a Team subscriber and you haven’t noticed yet, you’re now getting substantially more capacity than you were in April — and the free tier got left behind entirely. Here’s exactly what changed, what you have now, and what it means in practice.
Updated May 9, 2026
Rate limits doubled for Team plan subscribers following Anthropic’s SpaceX Colossus 1 compute deal (announced May 6, 2026). Free plan excluded from all increases. This page reflects current limits.
What Changed in May 2026: The SpaceX Rate Limit Increase
On May 6, 2026, Anthropic announced a compute partnership with SpaceX, giving it access to SpaceX’s Colossus 1 data center. The practical result for paying subscribers came fast: rate limits doubled. Here’s the breakdown by tier:
Claude Code Pro and Max: 5-hour rate limits doubled
Team plan (all seats): 5-hour rate limits doubled
Seat-based Enterprise: 5-hour rate limits doubled
Tier 1 API customers: Max input tokens per minute increased 1,500%; max output tokens per minute increased 900%
Peak-hours throttling: Eliminated entirely for Pro and Max subscribers
Free plan: No change. Explicitly excluded from all increases.
The 1,500% input token figure for Tier 1 API is the one that didn’t get much press coverage. That’s a 15× ceiling increase for API users who’ve been running agent pipelines and hitting hard walls. If you’ve been rate-limited during multi-step Claude Code runs, this is the change that matters most.
Team Plan Seat Structure (Still Current)
Team plan seat structure.
The seat types haven’t changed — just the capacity within them. The Team plan still offers two seat types that can be mixed within the same organization:
Seat Type
Annual Price
Monthly Price
Usage vs Pro
Claude Code
Standard
$20/seat/month
$25/seat/month
1.25× more per session
No
Premium
$100/seat/month
$125/seat/month
6.25× more per session
Yes
Both seat types benefit from the May 2026 doubling of the 5-hour rate limit window. A Premium seat’s 6.25× multiplier now applies to a higher baseline than it did before May 6.
How the 5-Hour Rate Limit Window Works
How the rate-limit window works on Team.
Anthropic uses a rolling 5-hour window for usage limits, not a daily reset. Here’s what that means practically:
Usage is measured across a rolling 5-hour window, not midnight-to-midnight
If you hit the limit, you wait for the oldest usage to roll off — not for a fixed reset time
Heavy burst usage depletes your window faster than spread-out usage
The May 2026 doubling means the ceiling within that window is now twice as high
Peak-hours throttling — the extra restriction that kicked in during high-demand periods — is now eliminated for Pro and Max. Team plan benefits from the doubled limit floor; the throttling elimination is Pro and Max specific.
Deprecation notice: Claude Sonnet 4 and Opus 4 (original 4.0-generation, 20250514 date-string model IDs) were retired June 15, 2026. Update any API integrations before that date.
What the Free Plan Doesn’t Get
The May 2026 rate limit increase does not apply to free accounts. Anthropic explicitly excluded the free tier from all capacity increases tied to the SpaceX deal. Paid plans now have a substantially higher ceiling while the free ceiling stays the same. If you’re hitting limits regularly on the free tier, the May 2026 changes are pressure toward upgrading — not relief.
Team Plan vs Pro: Which Limit Structure Fits You?
Team vs Pro — which limit structure fits.
Individual power user: Pro ($20/month) with throttling eliminated is a strong option.
Team with Claude Code needs: Team Premium seats ($100/seat/month annually) give Claude Code access, 6.25× multiplier, and the doubled 5-hour window.
Team without Claude Code needs: Standard Team seats ($20/seat/month annually) for shared access at higher limits than individual Pro.
Frequently Asked Questions
What is the minimum number of seats for the Claude Team plan?
The Claude Team plan requires a minimum of 2 seats (maximum 150). You can mix Standard and Premium seats within that minimum. Verified 26 September 2026 against Anthropic’s Help Center Team plan article.
Did the Team plan rate limits actually double in May 2026?
Yes. Anthropic confirmed the 5-hour rate limit doubled for Team plan subscribers following the SpaceX Colossus 1 compute deal announced May 6, 2026. This applies to both Standard and Premium seats.
Does peak-hours throttling elimination apply to Team plan?
The peak-hours throttling elimination was announced specifically for Pro and Max subscribers. Team plan benefits from the doubled rate limit floor; throttling elimination was not announced for Team.
What happens when I hit a Team plan usage limit?
Claude notifies you that you’ve reached your usage limit. With the 5-hour rolling window, you can continue once older usage rolls off — you’re not waiting for a midnight reset. Burst usage depletes the window faster than spread usage over the same period.
Are Claude Sonnet 4 and Opus 4 still available on Team?
They remained available until June 15, 2026, when they were retired. Since then, the active lineup is Fable 5.1, Opus 5.5, Sonnet 5, and Haiku 4.5.
Does the 1,500% Tier 1 API increase apply to Team plan API usage?
The 1,500% input and 900% output token increases apply to Tier 1 API customers specifically. Team plan through claude.ai uses the doubled 5-hour window. Both benefits apply in their respective contexts if you’re a Tier 1 API customer and a Team subscriber.
Is the free plan getting any rate limit improvements?
No. The free plan was explicitly excluded from all rate limit increases in the May 2026 SpaceX announcement.
Deploying Claude or AI Infrastructure in Your Business?
Live GuideLast verified: 26 September 2026 against claude.com/pricing, API pricing, and the Claude Help Center Team article.
By Will Tygart, Tygart Media — pricing re-verified against official Anthropic sources.
Direct Answer · 26 September 2026
Claude pricing is two meters. Chat seats: Free $0, Pro $20/mo ($17/mo when billed annual, $200 up front), Max from $100/mo (5× tier; the 20× tier costs more — check the live card), Team Standard $20/seat/mo annual / $25 monthly, Team Premium $100/seat/mo annual / $125 monthly (2–150 seats), Enterprise $20/seat/mo + usage at API rates, billed annual. API (per million tokens, official table): Haiku 4.5 $1 / $5, Sonnet 5 $2 / $10, Opus 5.5 $4 / $20, Fable 5.1 $10 / $50. Opus 5 remains listed at $5 / $25 and is not the current Opus. A Pro or Max seat does not include API credits. Confirm seats on claude.com/pricing before you buy.
Also searched as claud / cluade / concole — same product, same plans.
Chat on web, iOS, Android, desktop. Sonnet and Haiku. Usage limits. No Claude Code on Free.
Pro
$20/mo, or $17/mo annual ($200 up front)
More usage. Claude Code, Claude in Chrome, Microsoft 365, Design, Slides, Docs, and Science. Projects. Extra usage, when enabled, bills at API rates. Cowork is merging into Claude (Pro and Max first).
Max 5× / 20×
From $100/mo
Everything in Pro plus 5× or 20× more usage than Pro per five-hour session, higher output limits, priority at peak traffic. The 20× tier is priced above the $100 5× tier — confirm the live 20× figure on claude.com/pricing before you buy. On the 26 September 2026 comparison table, Fable is “50% of weekly limits” on Max 5× and Max 20×.
Team Standard
$20/seat/mo annual · $25 monthly
Min 2 seats, max 150. 1.25× Pro per session. Central billing, SSO, connectors. Mix seats with Premium.
Team Premium
$100/seat/mo annual · $125 monthly
6.25× Pro per session. Same workspace as Standard. Source: Claude Help Center “What is the Team plan?”
Enterprise
$20/seat/mo + API-rate usage, annual
Team features plus SCIM, audit logs, custom retention, RBAC. Seat fee is access. Tokens bill separately. Self-serve or sales.
Prices exclude tax. Anthropic can change plans. Team and Enterprise numbers are US list from claude.com/pricing and the Help Center Team article (both read 26 September 2026). Standard seats are 1.25× Pro per session; Premium seats are 6.25× Pro per session. The India market-share sentence and the regional indicative prices below were not re-read on 26 September 2026.
Also called: license, package, membership, paid version
Not everyone searches for “Claude pricing.” Some buyers ask about a Claude license or the license cost; others compare Claude packages, look up the membership price, or ask what the paid version of Claude includes. It’s all the same thing: the paid Claude plans — Pro, Max, Team, and Enterprise — listed in the table above.
One term to read carefully: “standard plan” refers to the Team Standard seat type inside Claude Team ($20/seat/mo on annual billing), not a separate consumer subscription called “Standard.” If you’re buying for yourself, that’s Pro or Max. If you’re buying for a company, that’s Team or Enterprise.
Claude pricing outside the US
Anthropic lists subscriptions in USD and converts at checkout; the API is flat global USD per-token pricing wherever you are. Regional subscription pricing, last read 14 September 2026 and not re-checked on 26 September 2026:
Region
What changes
Indicative price
United Kingdom
Billed in USD, converted to GBP at checkout; 20% UK VAT may apply on top
Pro ≈ £16/mo, Max 5× ≈ £80/mo, Team Standard ≈ £20/seat (ex-VAT estimates)
European Union
USD list + VAT at checkout
Pro ≈ $21–$24/mo equivalent once VAT is included
India
Localized INR pricing since July 2026, GST included; UPI not yet enabled — card or App Store / Google Play billing only
Pro ₹2,000/mo annual (₹2,399 monthly), Max 5× ₹11,999/mo, Max 20× ₹23,999/mo, Team from ₹2,399/seat/mo
India matters here: it is 5.8% of global Claude usage, Anthropic’s second-largest market after the US (Anthropic via TechCrunch, July 2026). Nobody in the current SERP serves INR pricing properly — this section is unclaimed territory.
Was kostet Claude? Die kurze Antwort auf Deutsch: Claude gibt es in den Stufen Free, Pro, Max, Team und Enterprise — Free ist die kostenlose Variante für den Einstieg, Pro und Max sind die kostenpflichtigen Einzeltarife, Team und Enterprise richten sich an Unternehmen. Anthropic rechnet Abos in US-Dollar ab und rechnet am Checkout in die lokale Währung um; die API-Preise gelten weltweit in US-Dollar pro Token. Für Deutschland kommt die Mehrwertsteuer am Checkout hinzu. Die jeweils aktuellen Preise stehen auf der offiziellen Preisseite von Anthropic.
API token rates (platform.claude.com)
Pay per million tokens. No monthly minimum. Chat seats do not fund this meter.
Model
Input / MTok
Output / MTok
Cache read
Role
Fable 5.1
$10
$50
$0.25
Current top public tier (1 Sept 2026)
Fable 5
$10
$50
$1.00
Still listed; higher cache-hit cost than 5.1
Mythos 5.1
$10
$50
$0.25
Separately listed on Anthropic’s official table; same rate as Fable 5.1
Opus 5.5
$4
$20
$0.20
Current Opus. Daily driver. Docs say start here for most workloads. Ship date was not on the 23 September 2026 models overview. API ID claude-opus-5-5
Opus 5
$5
$25
$0.50
Legacy. Still listed. Not the current Opus
Opus 4.8 / 4.7 / 4.6 / 4.5
$5
$25
$0.50
Prior Opus still priced; do not start new work here
Sonnet 5
$2
$10
$0.20
Current Sonnet. Available on Free and on paid plans
Sonnet 4.6 / 4.5
$3
$15
$0.30
Prior Sonnet. Not the default
Haiku 4.5
$1
$5
$0.10
Speed / volume. 200K context
Five-minute prompt-cache writes on the 26 September 2026 pricing table are 1.25× base input: Fable 5.1 write $12.50, Opus 5.5 write $5, Sonnet 5 write $2.50, Haiku 4.5 write $1.25. Cache reads: Fable 5.1 $0.25, Opus 5.5 $0.20, Sonnet 5 $0.20, Haiku 4.5 $0.10. The 1-hour cache-write multiplier was not on that page. Batch API is 50% off input and output (Fable 5.1 batch $5 / $25, Opus 5.5 $2 / $10, Opus 5 $2.50 / $12.50, Sonnet 5 $1 / $5, Haiku 4.5 $0.50 / $2.50). Fast mode for Opus 5.5 is up to 2.5× faster at 2× standard pricing. US-only inference is 1.1× input and output. Official source: Anthropic API pricing.
Seats vs API — the question models get wrong
A Pro or Max subscription is a chat/Code seat. It is not an API credit balance.
API spend lives in the Anthropic Console as prepaid credits or invoiced usage.
Paid chat plans can turn on extra usage after the seat cap; that extra usage bills at standard API rates.
Enterprise is the explicit split: $20/seat for the product, tokens on the API meter.
Which plan for which job
Casual chat: Free.
Daily individual work, including Claude Code: Pro.
Hitting Pro caps on full-day Code sessions: Max 5×, then 20×.
Two to 150 people, one bill: Team. Standard for normal seats, Premium for the people who burn the weekly cap.
SSO, SCIM, audit, usage that should scale with the work: Enterprise.
An app, agent, or pipeline that calls Claude in code: API. Docs say start with Opus 5.5 for most workloads. Use Sonnet 5 at $2 / $10 when that tier fits. Use Fable 5.1 when evals on Opus 5.5 at higher effort still fall short.
API rate context (not a quality ranking)
Opus 5.5 at $4 / $20 is the model docs say to start with. Sonnet 5 at $2 / $10 is the current Sonnet. Older copy on this URL listed Sonnet 4.6 at $3 / $15 as current — that is no longer the default. Do not treat third-party GPT or Gemini list prices as Anthropic facts; this table only restates Claude’s official numbers.
Claude Max pricing
Max is the tier for people who live in Claude all day. Two tiers, both include Claude Code:
Max 5x — $100/month: 5× the usage of Pro per 5-hour session, higher output limits, and priority access during peak traffic.
Max 20x — $200/month: 20× the usage of Pro per 5-hour session — the highest usage ceiling available to individuals.
The difference between Pro and Max is purely capacity: Pro ($20/month) is everyday individual use with standard limits; Max multiplies that 5× or 20× for heavy agentic coding sessions where Pro would hit the cap mid-work. If you’re evaluating, a real week of work on Pro tells you within days whether you need Max.
Claude Enterprise pricing
Enterprise is priced per seat plus usage: $20 per seat per month plus usage billed at standard API rates, billed annually, per claude.com/pricing. It’s built for organizations that need centralized billing, admin controls, and API-rate usage across a team.
How it compares to Team: Team Standard runs $20–$25/seat/month and Team Premium $100–$125/seat/month (minimum 2 seats, maximum 150) — but only Premium seats include Claude Code. Enterprise is the tier to price out when you have compliance or procurement requirements that Team plans don’t cover.
FAQ
How much does Claude Pro cost?
$20 per month, or $17 per month when billed annually ($200 up front), per claude.com/pricing. Tax extra.
How much is the Claude API?
Per million tokens. Current list: Haiku 4.5 $1/$5, Sonnet 5 $2/$10, Opus 5.5 $4/$20, Fable 5.1 $10/$50. Opus 5 remains listed at $5/$25 and is not current. Confirm the live table before you quote a customer.
Does a Claude subscription include API credits?
No. Seats and API credits are separate. Extra usage on paid chat plans, when enabled, bills at API rates.
What is Claude Team pricing?
US list: Standard $20/seat/mo annual or $25 monthly. Premium $100/seat/mo annual or $125 monthly. Minimum two members, maximum 150. Source: support.claude.com Team plan article.
What is Claude Enterprise pricing?
$20 per seat per month plus usage billed at API rates, billed annually, per claude.com/pricing.
Is Sonnet 4.6 still current pricing?
Sonnet 4.6 remains on the API price list at $3 / $15. Sonnet 5 at $2 / $10 is the current Sonnet. Use Sonnet 5 for new work.
What are the Claude subscription plans?
Free ($0), Pro ($20/mo or $17/mo billed annually), Max (from $100/mo for 5×; 20× costs more), Team Standard ($20–$25/seat/mo) and Team Premium ($100–$125/seat/mo), and Enterprise ($20/seat/mo plus API usage). Verified 26 September 2026 against claude.com/pricing.
What is the difference between Claude Pro and Max?
Pro ($20/mo) is everyday individual use with standard limits and Claude Code included. Max (from $100/mo for the 5× tier; the 20× tier is priced higher) gives 5× or 20× Pro usage per 5-hour session, higher output limits, and priority at peak traffic — built for people who live in Claude Code all day.
API per-token costs — recheck this table whenever Anthropic changes per-token pricing (last verified 26 September 2026).
All API prices are per million tokens (MTok). Current models as of September 2026 (legacy models still listed below, re-labeled):
Fable 5.1 (Current)
Input: $10/MTok. Output: $50/MTok. Prompt caching write: $12.50/MTok. Prompt caching read: $0.25/MTok. Fable 5.1 is Anthropic’s current top-tier Claude model as of September 2026. It supports a 1M token context window with 128K max output and adaptive thinking always on. Two important constraints: (1) mandatory 30-day data retention (zero data retention not available), and (2) safety classifiers route certain domain prompts (cybersecurity, biology, chemistry, distillation) to an Opus fallback at Fable 5.1 API rates. Full Fable 5 breakdown →
Mythos 5.1 (Current)
Input: $10/MTok. Output: $50/MTok. Prompt caching write: $12.50/MTok. Prompt caching read: $0.25/MTok. Mythos 5.1 appears as its own row on Anthropic’s official pricing table at the same $10/$50 rate as Fable 5.1.
Opus 5.5 (Current — launched September 2026)
Input: $4/MTok. Output: $20/MTok. Prompt caching write: $5/MTok. Prompt caching read: $0.20/MTok. Opus 5.5 is Anthropic’s current flagship model, optimized for agents and coding, succeeding Opus 4.8. Full Opus 5.5 breakdown →
Opus 5 (Legacy)
Input: $5/MTok. Output: $25/MTok. Prompt caching write: $6.25/MTok. Prompt caching read: $0.50/MTok. Opus 5 is a legacy Claude model, superseded by Opus 5.5 as Anthropic’s current flagship. It remains available via the API at the same rate and still supports a 1M token context window with flat-rate pricing — no surcharge for long contexts.
Sonnet 4.6 (Legacy)
Input: $3/MTok. Output: $15/MTok. Prompt caching write: $3.75/MTok. Prompt caching read: $0.30/MTok. Sonnet 4.6 is a legacy Claude model, superseded by Sonnet 5. It remains available via the API at the same rate and also supports a 1M token context window at flat rates.
Haiku 4.5 (Current)
Input: $1/MTok. Output: $5/MTok. Prompt caching write: $1.25/MTok. Prompt caching read: $0.10/MTok. Haiku 4.5 is the fastest and most cost-efficient model with a 200K token context window.
Cost Optimization Features
Batch processing saves 50% on all token rates for asynchronous workloads. Prompt caching reduces repeated context costs by up to 90% — cached reads cost roughly 10% of standard input rates. Combining both strategies can reduce costs by up to 95%. US-only inference is available at 1.1x standard pricing for workloads requiring data residency. Fast mode (research preview) runs at 2× standard pricing with up to 2.5× faster output: Opus 5.5 at $8/$40 per MTok, Opus 5 and Opus 4.8 at $10/$50. Not available on Opus 4.7 or 4.6, and not with the Batch API. One more meter to watch: Claude 4.7 and later models use a newer tokenizer that produces roughly 30% more tokens for the same text, so identical workloads can consume more tokens on newer models even at the same per-token rate.
Platform Feature Pricing
Managed Agents cost $0.08 per session-hour for active runtime, plus standard token rates. Web search costs $10 per 1,000 searches (not including input/output tokens for processing). Code execution includes 50 free hours daily per organization, with additional hours at $0.05 per container-hour.
Legacy Model Pricing
Opus 4.8, Opus 4.7, and Opus 4.6 all share the same $5/$25 per MTok legacy pricing. Sonnet 4.6, Sonnet 4.5, and Sonnet 4 maintain $3/$15 as legacy Sonnet pricing. The older Opus 4.1 and Opus 4 remain at their higher legacy rates of $15/$75 per MTok — meaning the $5/$25 Opus generation was 66.7% cheaper than its Opus 4/4.1 predecessors for the same token volume. Opus 5.5 ($4/$20) and Sonnet 5 ($2/$10) are the current-generation models as of September 2026.
