Trinity Bound — Resource Center
Understanding Claude AI
A Practical Masterclass
An educational guide for team members and collaborators — how Claude works, what each plan delivers, and how to put it to work in your role.
All plans at a glance
Free
$0 / month
- Claude Sonnet model
- Projects & Artifacts
- Basic app connectors
- Priority access
- Claude Code
- Full MCP integrations
Most popular
Pro
$20 / month
- Claude Opus + Sonnet
- 5× usage vs Free
- Claude Code access
- Full MCP integrations
- Priority access
- Extended file analysis
Max 5×
$100 / month
- Everything in Pro
- 5× Pro capacity
- Higher Code limits
- Cowork (desktop tasks)
- Priority access
- Early feature access
Max 20×
$200 / month
- Everything in Pro
- 20× Pro capacity
- Highest Code limits
- Cowork (desktop tasks)
- First priority access
- Power & agentic work
The key distinction between Pro and Max is not features — it is capacity. Max does not unlock new capabilities; it removes the ceiling on how much work you can do per session. If you are not regularly hitting Pro's limits, Max adds no value yet.
Feature-by-feature comparison
| Feature | Free | Pro | Max 5× | Max 20× |
|---|---|---|---|---|
| Claude Sonnet model | ✓ | ✓ | ✓ | ✓ |
| Claude Opus model | ✗ | ✓ | ✓ | ✓ |
| Usage per session | Baseline | 5× free | 25× free | 100× free |
| Priority access | ✗ | ✓ | ✓ | ✓ |
| Claude Code | ✗ | ✓ | ✓ higher | ✓ highest |
| Cowork (desktop) | ✗ | ✗ | ✓ | ✓ |
| Full MCP connectors | ✗ | ✓ | ✓ | ✓ |
| Projects & memory | ✓ | ✓ | ✓ | ✓ |
| File upload & analysis | Basic | Full | Full | Full |
| Early feature access | ✗ | Some | ✓ | ✓ |
| 1M token context (Opus) | ✗ | ✓ | ✓ | ✓ |
| Web & mobile apps | ✓ | ✓ | ✓ | ✓ |
Key concepts — select to expand
Think of the context window as Claude's working memory for a conversation. A token is roughly three-quarters of a word. Opus on Pro and Max offers up to 1 million tokens in beta — meaning you can load an entire manuscript, a full codebase, or months of organizational documents and Claude holds all of it at once without losing track. The practical meaning: longer context produces fewer back-and-forth sessions, less re-explaining, and deeper work per conversation.
Claude Code is a command-line tool that gives Claude direct access to your computer's file system and terminal. It can read your files, write new ones, run code, test results, and fix its own errors — without you copying and pasting anything. For non-developers: think of it as Claude that can open your files and work inside them autonomously. Pro includes it; Max extends the session limits for longer uninterrupted coding work. It also integrates as an extension inside VS Code and JetBrains IDEs.
Cowork is a desktop tool available on Max plans. It allows you to delegate complex, multi-step tasks to Claude and have it work through them independently in the background while you focus elsewhere. This is not chat — it is task delegation at scale. Example: "Research these 15 organizations, summarize each one's mission, identify overlaps, and produce a comparison document." Cowork handles it while you manage other operations. For multi-brand operators and ministry leaders managing multiple programs, this is a significant capability.
MCP is the open protocol that allows Claude to connect to external tools and services — Google Drive, Notion, Slack, GitHub, and more. Free users get basic built-in connectors. Pro and Max unlock full MCP support, meaning you can build custom integrations and connect Claude to your own tools, creating automated workflows between services. For anyone managing a multi-brand ecosystem or ministry platform, MCP is the mechanism that moves Claude from a standalone chat tool to an active layer inside your daily operations.
The API (Application Programming Interface) is how developers build Claude into their own products — websites, apps, internal tools, and automated pipelines. Unlike subscription plans, the API has no chat interface; it is pure model access via code, priced per unit of text processed rather than a flat monthly fee. This is not a replacement for Pro or Max. It is a separate capability layer for builders. A founder might use Pro personally for daily work while simultaneously using the API to power a client-facing tool or an automated content pipeline. Both layers can and often do coexist. If you are building something that other people will use — the API is where that lives.
Claude does not reset your usage at midnight like a daily cap. Instead, limits reset on a rolling session cycle — roughly every five hours of active use, with additional weekly caps on Max plans. This means a heavy burst of work does not permanently penalize the rest of your day. Practically: spreading deep work across sessions is more sustainable than pushing through a ceiling in one marathon sitting. Understanding this helps your team plan workflows without unexpected interruptions.
Projects are persistent workspaces within Claude where you can store instructions, context, brand voice, SOPs, and background documents. Claude remembers everything in a Project across conversations. For an organization like Trinity Bound, the right structure is one Project per brand or function — TruthSeekers Publishing, Walking The After, UR Worthy, Thrive & Dwell — each containing its own voice guidelines, audience profile, key documents, and standing instructions. Team members working in a Project do not need to re-explain context every session. It is already there.
Use cases by role
Ministry leader / nonprofit director
Recommended: Pro → evaluate Max 5× at scale
- Draft grant proposals, donor letters, and program reports with full document upload — no size limit on Pro+
- Store your organization's mission, tone, and audience profile in a Project so Claude always works in alignment
- Build teaching curriculum, devotional series, and Bible study frameworks that maintain doctrinal consistency
- Connect Google Drive via MCP — Claude reads your existing documents and builds on them directly
- Max becomes worth it when you are producing content daily across multiple programs or ministries simultaneously
- Cowork (Max) can draft a monthly newsletter, pull relevant scripture references, and structure a social calendar in one delegated session
Multi-brand ecosystem operator
Recommended: Max 5× or 20×
- Create one Claude Project per brand — each holds its own context, SOPs, brand voice, and standing instructions
- Cowork handles cross-brand background tasks while you manage active operations in another brand
- Opus's 1M token context window lets you load entire brand playbooks — not summaries, the full document
- MCP connects Claude to your e-commerce, publishing tools, scheduling, and content platforms simultaneously
- Max 20× is justified when Claude is running 4–8 hours of productive work across brands daily
- Claude Code becomes the build layer when creating automated pipelines, internal tools, or custom integrations across the ecosystem
Content creator / writer / publisher
Recommended: Pro, upgrade when hitting limits
- Pro is sufficient for most individual content producers — 5× the message volume of Free
- Store your brand voice, style guide, audience profile, and content pillars in a Project — Claude works from that context every session
- Upload source documents, research, and transcripts — Claude reads the full file, not a summary of it
- Max becomes justified when producing content daily across multiple channels without workflow interruption
- Cowork (Max) can take a single brief and produce a full series outline, drafted posts, and a publication schedule
- The honest check: are you hitting Pro's limit regularly? If not, Max adds nothing yet
Developer / technical builder
Recommended: Max 5× or 20× for heavy Code use
- Claude Code is the primary value driver — autonomous terminal and file-system work without manual copying
- Pro's Code session limits are reached quickly in extended builds; Max is specifically designed for this use case
- Max 20× vs API: at medium-to-heavy usage (50–200M tokens/month), Max is dramatically cheaper than pay-per-token API pricing
- Opus's 1M token context handles large codebases without chunking or losing architectural awareness
- MCP connects Claude to GitHub, CI/CD pipelines, and internal tooling as part of the development loop
- The API is a separate consideration — for building products that other people use, not for your own daily work
Solopreneur / single-brand business owner
Recommended: Pro
- Pro handles the full workload for most solo operators who are not running Claude for six-plus hours daily
- Build one Project as your business command center — store your offers, voice, client types, and SOPs permanently
- Use file upload to analyze contracts, financials, proposals, and reports in full — not just extracted summaries
- MCP connects Claude to Google Drive, Notion, Slack, and the tools you already use daily
- Max is worth evaluating when you are regularly hitting limits mid-project and it is costing you time
- The benchmark: if $80/month more recovers more than $80/month of billed time — the upgrade makes financial sense
Health, wellness, and holistic practitioner
Recommended: Pro
- Upload clinical research, protocols, and patient education materials — Claude reads and synthesizes the full document
- Build client-type or condition-specific Projects — Claude holds the full context for each type of care
- Draft patient communications, intake materials, and educational content with consistent tone and accuracy
- Claude accelerates documentation, research synthesis, and communication — it does not replace clinical judgment
- Privacy note: do not input personally identifiable patient data — Claude's subscription tier is not HIPAA-certified infrastructure
- Max is worth it for practitioners running multiple programs, building educational platforms, or producing high-volume written content
Find your plan — self-assessment
Cost-benefit calculator
Your hourly rate ($/hr)
$75/hr
Hours saved per month
10 hrs
$750
Monthly time value
37×
ROI on Pro ($20/mo)
7×
ROI on Max 5× ($100/mo)
This estimates the dollar value of time recovered relative to plan cost. ROI above 1× means the plan pays for itself. This is a directional tool — actual value depends on your workflow and how you deploy recovered time. A plan only earns its cost if you are actively using it at that level.
Integrations — what connects and how
Google Drive
Claude reads your Drive files directly in conversation — pull in documents, spreadsheets, and slides without downloading. Available as a full MCP connector on Pro and Max.
Pro+
Notion
Connect Notion databases and pages. Claude can query, reference, and build on your existing knowledge base — SOPs, project tracking, living documents, content frameworks.
Pro+
Slack
Claude connects to Slack channels and messages. Useful for summarizing threads, drafting replies, or building team-facing Claude workflows and internal communication systems.
Pro+
GitHub
Read repositories, issues, and pull requests. Used alongside Claude Code for development workflows, code review, and managing technical project documentation.
Pro+
Claude Code
Direct file system and terminal access — Claude writes, edits, runs, and fixes code autonomously. Available as terminal tool, VS Code extension, and JetBrains plugin. Higher limits on Max.
Pro+
Cowork
Desktop tool for background task delegation. Hand off complex multi-step projects and let Claude work through them independently while you focus on other operations. Max plans only.
Max only
Web search
Claude searches the web in real time during conversations — current information, fact-checking, research, and source verification without leaving the conversation.
All plans
Custom MCP
Build your own connections to proprietary tools, internal databases, or custom APIs. The MCP protocol is open — if a service has an API, it can be connected. This is where Claude becomes infrastructure, not just a tool.
Pro+
The integration layer is where Claude shifts from a chat interface to an operational layer embedded in your workflow. MCP is the mechanism; the connector directory continues to expand. For team environments, this is the layer worth investing in early.
The full tier ladder — as you grow
Free → Pro
The first meaningful upgrade. Pro delivers model quality (Opus), 5× capacity, Claude Code, full MCP access, and priority service. This is where Claude moves from occasionally useful to consistently reliable. Most individuals — team members, collaborators, and solo operators — belong here as a foundation.
Pro → Max 5× or 20×
Not a feature upgrade — a capacity upgrade. Max is designed for people whose work genuinely exceeds Pro's ceiling: running Claude 4–8 hours daily, managing multiple parallel projects, doing intensive agentic or coding work. If you are not hitting Pro's limits regularly, Max provides no additional value. Evaluate honestly before committing the additional cost.
Team plan — $25/seat standard · $100/seat premium
Built for organizations. Requires a minimum of five seats. Pooled usage across team members, shared Project workspaces, admin controls, SSO, and centralized billing. Premium seats add Claude Code access and 6.25× Pro capacity. The right move when staff, contractors, or collaborators need Claude access under one managed account with oversight and governance. This is the layer where Trinity Bound's internal team structure lives as it grows.
Enterprise — custom pricing (70+ seats, ~$60+/seat)
Negotiated directly with Anthropic. Designed for large organizations requiring custom data governance, compliance controls, dedicated infrastructure, enterprise SSO, and formal contracts. This is not an off-the-shelf product — it is built to fit the organization's regulatory environment and security requirements. Relevant when scale or compliance demands exceed what Team provides.
API — pay per token (builder layer)
The developer layer — not a subscription, not a chat interface. Pure model access via code, priced per unit of text in and out. This is how you build Claude into products that other people use: client-facing tools, automated pipelines, batch processing at scale. The API coexists with subscription plans. A founder using Pro personally can simultaneously deploy the API to power a platform their clients interact with. These are distinct capability layers, not substitutes for each other. When Trinity Bound's horizon builds — the TBI Handbook App, TruthSeekers Bible App, health and permaculture apps — the API is the infrastructure layer those products run on.
A word on stewardship
Every tier costs real money. The right plan is the one that actually fits your current workload — not the highest available. Start where you are. Move up when the evidence is clear: you are hitting limits consistently, it is costing you time, and the upgrade pays for itself in recovered capacity. Faithfulness in how resources are deployed matters as much here as anywhere else in the operation.
Every tier costs real money. The right plan is the one that actually fits your current workload — not the highest available. Start where you are. Move up when the evidence is clear: you are hitting limits consistently, it is costing you time, and the upgrade pays for itself in recovered capacity. Faithfulness in how resources are deployed matters as much here as anywhere else in the operation.