Tag: Claude AI

  • Leadership Operating System (Notion + AI)

    Leadership Operating System (Notion + AI)

    Leadership Operating System (Notion + AI)

    $397

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Hang the nine Notion tools. Run the 12-week spine. Talk your own Claude through 1-3-1, the bench, and the 5 Ds. Buy Now is the packaged flagship: the Notion workspace you duplicate, plus the 10-skill plugin zip, so you are not wiring the worksheets and the AI from a blank page.

    This is the Notion + AI operating system for a restoration owner who is still the bottleneck. Notion is the fill-in system of record. The plugin is the coach you talk to. Outputs from each skill are formatted to paste into the matching Notion tool. One company-profile.md powers both this kit and the Operations Kit if you already ran setup there.

    What it is

    Three cards for 1-3-1, 5 Ds, and bench building in a leadership toolkit
    Leadership OS — Notion tools + AI skills.

    Two halves that are meant to run together.

    Notion half. Nine plug-and-play tools. Duplicate them into one workspace page named something like Leadership. One sidebar section, the whole doer-to-leader system.

    AI half. A 9-skill Claude plugin plus a shared setup skill. A setup interview writes company-profile.md. Every leadership skill reads it, so the coaching speaks your team, your roles, and your pain points.

    You need a free Notion account and any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.

    The 9 Notion tools

    1. 1-3-1 Delegation Worksheet ($19). Teach the team to bring one issue, three options, one recommendation. Not just the problem.
    2. Owner Bottleneck Self-Assessment ($29). 25 statements across five areas. Find where the company still depends on you.
    3. 5 Ds Succession Risk Checklist ($29). Death, Divorce, Disease, Drugs/dependency, Departure/Disaster. A what-if-tomorrow check, not a retirement plan.
    4. Accountability Conversation Planner ($39). Plan a hard conversation so it stays about the work, not the person.
    5. Leadership Readiness Checklist ($49). Six sections. Can your team actually lead, or does everything still run through you?
    6. Middle Manager Evaluation Scorecard ($59). Score someone on nine traits before you promote them. Promote / Develop first / Not yet.
    7. Owner Dependency Audit ($99). What breaks if you disappear for 30 days? Nine areas, Low / Med / High, plus a Decision-Rights Map.
    8. Restoration Leadership Bench Builder ($149). One row per key function. Candidates, gaps, one observable 90-day action.
    9. 90-Day Doer-to-Leader Transition Plan ($199). Six two-week phases. The spine. The other eight feed it.

    The three smaller bundles sit inside this system. Conference Starter Pack is tools 1-3. Leadership Readiness Kit is tools 1, 4, 5, 6. Owner Freedom Kit is tools 1, 3, 7, 8, 9. This flagship is all nine, plus the AI half.

    How to hang the Notion half

    Restoration technicians training in a shop bay with equipment demo and whiteboard
    Hang the Notion half, then train the managers.

    Work the 90-day plan top to bottom. Do not skip ahead. Each phase sets up the next.

    Before Week 1, write three lines: your #1 reason to step back; the one person you are betting on as your first real manager; start date / target Week-12 date. Block 30-45 minutes every Friday.

    1. Weeks 1-2. Bottlenecks. Run the Owner Bottleneck Self-Assessment (0-25) and the Owner Dependency Audit (nine areas, Low = 1, Med = 2, High = 3, total 9-27). For one full week, log every interrupt for a decision. Sort into Delegate now / Delegate after training / Keep (truly owner-only). Circle the top 3. Tell the team: “I am working a 90-day plan to push decisions down. Expect me to hand more back to you.”
    2. Weeks 3-4. Install 1-3-1. One issue. Three real options with pros, cons, and rough cost. One recommendation. A default if they do not hear back by a deadline. When someone brings a raw problem, ask: “What are your three options, and which do you recommend?” Then wait. Run at least five real conversations. Phase done when at least one person brings 1-3-1s without being reminded.
    3. Weeks 5-6. Decision rights. List 10-15 recurring decisions (refunds, equipment, scheduling, scope changes, hiring, pricing exceptions). A dollar or scope threshold people can decide under without asking you, and who owns it when you are not in the room. Hand off one decision completely. Do not take it back.
    4. Weeks 7-8. One manager. Open the Bench Builder. One row per function. Use the Scorecard if you are torn on who. Have the conversation: “I want to grow you into running X.” Hand them one area end-to-end. Set a weekly 30-minute 1-on-1 and protect it.
    5. Weeks 9-10. Accountability rhythm. Weekly 15-minute huddle: numbers, jobs at risk, who needs what. 3-5 numbers someone other than you owns. Hold one real accountability conversation with the Planner (issue, behavior, what you have already allowed, the expectation, the consequence or support, what success looks like in 30 days).
    6. Weeks 11-12. Review and repeat. Re-score the bottleneck and the audit. Take a planned half-day fully off and note what broke. Raise one decision-rights threshold. Duplicate the 90-day page and start the next cycle.

    While you are in it, run the Readiness Checklist (six sections, red / yellow / green) and the 5 Ds. Check a 5 Ds box only if it is true and current today. Count the blanks. Pick the three that would hurt most if the D hit tomorrow.

    The 10 AI skills

    Three panels showing one problem, three options, one recommendation
    Ten AI skills on the leadership bench.
    1. restoration-setup. “Set up the kit.” Shared with the Ops kit. Writes company-profile.md.
    2. delegation-1-3-1. “Help me delegate this.” Convert an escalated question into one issue / three options / one recommendation.
    3. owner-bottleneck-assessment. “Where am I the bottleneck?” Scored self-assessment. Top places you are still the constraint.
    4. succession-5ds-checklist. “Am I exposed if something happens to me?” Exposure plus what to shore up.
    5. accountability-planner. “I have a hard conversation to plan.” Script plus a 30-day follow-up.
    6. leadership-readiness-checklist. “Is my team ready to lead?” Bench, single points of failure, next leaders.
    7. middle-manager-scorecard. “Should I promote this person?” Nine traits. Promote / Develop first / Not yet.
    8. owner-dependency-audit. “What breaks if I disappear for 30 days?” Functions plus a decision-rights map.
    9. leadership-bench-builder. “Build my leadership bench.” Candidates, gaps, a 90-day development plan per person.
    10. doer-to-leader-90-day. “Give me a 90-day plan to step back.” A personalized 12-week plan.

    Install the plugin yourself

    Option A (recommended). Save the leadership-kit folder. In Claude run:

    /plugin marketplace add /path/to/leadership-kit
/plugin install leadership-kit@profit-detective
/leadership-kit:restoration-setup

    Option B. Copy each folder inside skills/ into ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then say “run restoration setup.”

    Keep company-profile.md in the folder you work in. Every skill reads it. If you already ran setup from another Profit Detective kit, it reuses the same profile.

    If you want the packaged system

    You can rebuild this from the outline above. Buy Now is the flagship delivered by email after checkout: Notion duplicate links for the nine tools, the plugin zip (ten skill folders and the README), and the setup sequence so you drop it in and run. Same Square button at the top of this page.

    Coaching and operational system only. Not legal or HR advice.

    Related on Tygart Media: Notion Command Center · leadership toolkit · operations kit.

  • Conference Starter Pack

    Conference Starter Pack

    Conference Starter Pack

    $97

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Score where you are still the bottleneck. Install 1-3-1 so the next problem comes back as a recommendation. Walk the 5 Ds as a what-if-tomorrow check. Buy Now is the packaged bundle: three Notion tools plus the matching Claude skills, so you are not assembling the starter pack from blank pages.

    The grab-and-go pack from the Restoration Leadership Toolkit. Three of the most-used tools, bundled. For restoration owners who just heard the doer-to-leader message and want something they can run this week, not a 12-week program on day one.

    What’s in the pack

    Four-phase board covering a 12-week owner freedom transition
    Conference pack: start with the bottleneck assessment.
    1. 1-3-1 Delegation Worksheet
    2. Owner Bottleneck Self-Assessment
    3. 5 Ds Succession Risk Checklist

    The matching skills from the Leadership AI plugin: delegation-1-3-1, owner-bottleneck-assessment, succession-5ds-checklist.

    Run them in this order. The bottleneck names the constraint. 1-3-1 is the first habit. The 5 Ds is the exposure you do not want to discover the hard way.

    1. Owner Bottleneck Self-Assessment

    Find out where your company still depends on you. An owner bottleneck exists when growth, decision speed, and consistency are limited by your personal involvement in day-to-day decisions. You become both the most important and the most constraining person in the business.

    Check the box for each statement that is true today. Count the checks in each section, then total them. Range is 0-25. Be honest. The value is in the truth.

    1. Decisions only you make. Estimate / pricing approvals over a set dollar amount. Hiring and firing. Vendor choices. Which jobs you take. Refunds, credits, concessions.
    2. Interruptions by department. Production calls daily. Office pulls you into billing or scheduling. Sales checks pricing before quoting. Techs call from job sites. Customer complaints land on you.
    3. Recurring questions. The same operational questions every week. People wait for you. “Ask the owner” is the default. You re-explain the same processes. Things stall when you are unavailable.
    4. Tasks that should be delegated. Estimates you could hand off. Scheduling / dispatch. Collections / AR. Ordering equipment. Work others could produce.
    5. Areas with no backup. No one else can run production. Only you hold key carrier relationships. Only you see the full financial picture. No written SOPs for the things you do. If you are gone a week, something breaks.

    Bands: 0-6 Mild (tighten the remaining gaps). 7-13 Moderate (you are the bottleneck in one or two areas; fix the worst one first). 14-19 Heavy (the business runs through you; start delegating now, deliberately). 20-25 Severe (you ARE the business; this is the #1 risk to growth and to an exit).

    Write your top 3 to delegate first. For one full week after you score, log every interrupt for a decision. Sort into Delegate now / Delegate after training / Keep (truly owner-only). The department with the most checks is this quarter’s target. Install 1-3-1 there first.

    2. 1-3-1 Delegation Worksheet

    Three panels showing one problem, three options, one recommendation
    1-3-1 worksheet — force recommendations on the floor.

    The old way (escalation): “Hey boss, the dehu on the Maple St job died. What do you want me to do?” You just took back the problem, the thinking, and the decision. That is three jobs.

    The 1-3-1 way (delegation): “The dehu on Maple St died. Here are three options I looked at, here is the cost of each, and here is what I would do. Just need your yes.” You own one job: the decision.

    • 1. One issue. The decision that is actually needed, in one or two sentences. Not the whole story. The fork in the road.
    • 3. Three real options. Each with pros, cons, and a rough cost or effort. “Do nothing” can be one when it is honest. Stuck at two? Push for a third. Even “do nothing and revisit Friday” or “escalate to the carrier.”
    • 1. One recommendation. The option they would pick if it were their call, and why in one line.
    • A default. What they will do if they do not hear back by a deadline, so the job does not stall waiting on you.

    Explain the rule once, out loud. Pin the format where decisions get made (truck, office, group chat). When someone brings a raw problem, ask: “What are your three options, and which do you recommend?” Then wait. Run at least five real conversations. Approve the recommendation whenever it is reasonable. Resist solving it yourself, even when you are faster. Note who takes to it quickly. That is a signal for a future-manager pick.

    The first few 1-3-1s will be lopsided. Three fake options, or a recommendation with no reasoning. Coach it. Do not grade it. Phase done when at least one person is bringing 1-3-1s without being reminded.

    Worksheet fields if you are copying it: prepared by, date, job / account, urgency (Today / This week / No rush); the issue; three options (what it is, two pros, two cons, rough cost); the recommendation and what they need from you; the default deadline; owner sign-off (Approved as recommended / Approved with changes / Chose a different option / Let’s talk).

    Owner gut-check before you sign: could this person have made this call without me? If yes, tell them so, and next time push it all the way down.

    3. 5 Ds Succession Risk Checklist

    Five colored panels labeled Do, Delegate, Defer, Delete, Decide
    5 Ds succession risk — decide what leaves with you.

    Succession is not a retirement problem. It is a what-if-tomorrow problem. Check a box only if it is true and current today. Not “mostly.” Not “we talked about it once.” A box you want to be true is still a blank box. Half-true protections fail exactly when the D hits.

    1. Death. Current signed will that names the business. Funded buy-sell if there are partners. Key-person life payable to the company. A second check-signer on file at the bank. Someone who can legally bind the company. Passwords in a recoverable place. A named person who can run production 30+ days. Spouse / heirs know who to call.
    2. Divorce. Separate vs marital property actually confirmed, not guessed. Prenup, postnup, or buy-sell provision. Books not commingled. A valuation method in writing. Operating cash structured so a personal dispute cannot freeze payroll.
    3. Disease. Someone has actually run production on a vacation test. Backup estimator. Payroll / AP / AR without your hands. Carrier relationships that will not collapse if you are unreachable. Disability and business-overhead coverage. A one-page interim chain-of-command with dollar thresholds.
    4. Drugs / dependency. Dual approval over a dollar threshold. A second set of eyes on the books. No single point of failure, including you. A trusted advisor allowed to tell you the truth. Key roles documented and cross-covered.
    5. Departure / disaster. Tribal knowledge written down. Relationships not owned by one person. Off-site backups you have test-restored. A continuity plan for your own shop. Backup vendor / equipment list.

    Count the blanks. Published bands on the scored sheet: 0-6 resilient; 7-15 moderate; 16-27 high; 28+ you are the company. Pick the three blank boxes that would hurt most if the D hit tomorrow. Name an owner and a date. Re-run it every year, and after any life or business change. This is an awareness tool, not legal, financial, or insurance advice. Use it to walk into the attorney, agent, and CPA prepared.

    What to do after the three

    Take the top-3 bottleneck list into a 90-day doer-to-leader plan (Weeks 1-2 are this assessment). After 1-3-1 sticks, write decision rights so people stop defaulting to you out of habit. The 5 Ds blanks that are also “no backup” boxes on the bottleneck assessment are the same exposure. Name them once.

    If you want the next layer after this pack: Leadership Readiness Kit (checklist, scorecard, planner, 1-3-1) or Owner Freedom Kit (audit, bench, 90-day, 5 Ds, 1-3-1).

    If you want the packaged pack

    You can run the three tools from the outline above. Buy Now is the bundle delivered by email after checkout: the three Notion pages (duplicate each so the master stays clean), plus the matching skills if you want the interviews walked. Same Square button at the top of this page.

    Coaching and operational tools only. Not legal, financial, insurance, or HR advice.

    Related on Tygart Media: leadership OS · owner freedom kit.

  • Complete Restoration Operating System (Notion + AI)

    Complete Restoration Operating System (Notion + AI)

    Complete Restoration Operating System (Notion + AI)

    $597

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Build the six Notion databases. Write the 17 SOPs. Hang the 12 KPIs. Talk your own Claude through intake, equipment, claims, and Friday numbers. Buy Now is the packaged flagship: the Notion workspace you duplicate, plus the 8-skill plugin zip, so you are not wiring the system of record and the AI from a blank page.

    This is the Notion + AI operating system for a restoration shop. Notion is the system of record. The plugin is the expert you talk to. Outputs from each skill are formatted to paste into the matching Notion tool.

    What it is

    Three cards for field SOPs, owner prompts, and KPI rhythm in an operations kit
    Complete restoration OS — Notion tools + AI skills on one bench.

    Two halves that are meant to run together.

    Notion half. Six plug-and-play tools plus an IICRC protocol lookup. Job tracking, equipment, claims, SOPs, KPIs, crew onboarding. Duplicate them into one workspace page named something like Operations. One sidebar section, whole business.

    AI half. An 8-skill Claude plugin. A setup skill runs a five-minute interview, writes a company-profile.md, and every other skill reads it. SOPs, KPI targets, claims drafts, and onboarding plans come out in your voice.

    You need a free Notion account and any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.

    The six Notion tools

    1. Restoration Job Tracker Pro. Every job from first notice of loss to final invoice, with live margin. This is the hub. Everything else hangs off jobs.
    2. Equipment Inventory & Deployment Tracker. Where every air mover and dehu is, and what each one is earning. Asset IDs, daily rates, current deployments.
    3. Insurance Claims Command Center. Claims, adjusters, documentation, supplements, and aging balances in one place.
    4. Restoration Company SOP Library (17 SOPs). The core procedures, written down. Status starts as Template. Flip to Adopted when you approve each one.
    5. Restoration Business KPI Dashboard. The 12 numbers that move profit. Friday 15 to update. One summary row on the first business day of the month.
    6. Crew Onboarding & Training Tracker. Roster, certifications with expiration dates, equipment sign-offs. Next hire, duplicate the checklist set.

    Plus IICRC Protocol Lookup. Ask “what does S500 say about Category 3 water?” and get a plain-English pointer plus PPE. It is a lookup assistant, not a substitute for the published standard. Defer to current IICRC text, local codes, and your certified judgment.

    The 17 SOPs to write (or adopt)

    If you are building this yourself, start a table with SOP #, title, category, owner role, linked standard, and status (Draft / In Review / Active / Needs Update). The kit’s 17 are:

    1. SOP-01 Water Damage: Initial Inspection & Scoping
    2. SOP-02 Water Extraction & Category Determination
    3. SOP-03 Structural Drying & Daily Monitoring / Psychrometry
    4. SOP-04 Antimicrobial Application
    5. SOP-05 Mold Remediation: Containment Setup
    6. SOP-06 Mold Remediation: Removal & Clearance
    7. SOP-07 Fire & Smoke: Soot Assessment & Cleaning
    8. SOP-08 Contents Pack-Out & Inventory
    9. SOP-09 Equipment Setup, Tracking & Retrieval
    10. SOP-10 PPE & Job-Site Safety
    11. SOP-11 Customer Communication & Daily Updates
    12. SOP-12 Photo Documentation & Moisture Logging
    13. SOP-13 Estimate Writing & Xactimate Scoping
    14. SOP-14 Insurance Adjuster Coordination & Supplements
    15. SOP-15 Job Completion, Walkthrough & Certificate of Satisfaction
    16. SOP-16 Invoicing & Collections
    17. SOP-17 New Job Intake / FNOL Handling

    Do not customize all 17 today. Adopt the water set first. The rest within the month. Swap in your company name, your equipment, your local disposal rules.

    The 12 KPIs

    Build a dashboard with KPI, category, definition, frequency, owner, target, this month, last month, trend. The kit tracks these twelve:

    • Revenue (Financial, monthly)
    • Gross Margin % (Financial, monthly, target ≥ 45%)
    • Net Profit % (Financial, monthly, target ≥ 12%)
    • Days Sales Outstanding / AR Aging (Financial, monthly, target ≤ 45 days)
    • Average Job Size (Financial, monthly)
    • Lead-to-Job Conversion % (Sales, weekly, target ≥ 35%)
    • Jobs Sold (Sales, weekly)
    • Average Days to Dry (Production, weekly, target ≤ 3.5 days)
    • Labor Efficiency % (Operations, weekly, target ≥ 70%)
    • Equipment Utilization % (Operations, weekly, target ≥ 60%)
    • Rework / Callback % (Customer, monthly, target ≤ 3%)
    • Customer Satisfaction / NPS (Customer, monthly, target ≥ 70)

    Those targets are the kit’s starting case file, not gospel. Mix of mitigation vs reconstruction will shift them. The habit is the product: fifteen minutes every Friday updating statuses.

    How to hang it yourself

    Set them up in this order. Each one feeds the next.

    1. Job Tracker (30-45 min). Add 2-3 active jobs. Real jobs, not test data. Log today’s moisture readings.
    2. Equipment Tracker (30-45 min). Every dehu, air mover, scrubber, and meter, with asset IDs. Set actual daily rates. Log where everything is deployed right now.
    3. Claims Command Center (20-30 min). Add adjusters first. Then a claim record for every active claim. Log outstanding supplements and unpaid balances.
    4. SOP Library (20 min now, ongoing after). Read, customize, flip Status to Adopted as you approve.
    5. Crew Tracker (20 min). Roster, certs, equipment sign-offs.
    6. KPI Dashboard (15 min, then 15 min every Friday). Enter this month’s jobs and leads, including the ones you lost.
    7. IICRC skill (5 min). Install, then ask something real: “Cat 2 toilet overflow into a carpeted hallway. What’s the protocol?”

    If a template ships with rows marked (Sample), keep them while you learn. Delete them once your real data is flowing.

    How the system runs day to day

    Four-step flow: open skill, paste job facts, review draft, send or file
    Day to day: open the tool, paste facts, review, file.
    • Morning: Job Tracker board. What’s active, what needs a monitoring visit.
    • On every truck roll: equipment deployments updated; moisture readings logged to the job.
    • When the adjuster calls: Claims Command Center open. Every supplement, authorization, and dollar in front of you.
    • New hire starts: Crew Tracker checklist; SOP reading list; sign-offs gate the equipment.
    • Friday: the Friday 15 in the KPI ledger.
    • Month end: one KPI summary row. Review utilization before buying equipment.

    This does not replace JobNimbus, Encircle, or Xactimate. Those are job management, documenting, and estimating. This is the ops layer most shops never finish.

    The 8 AI skills

    Eight numbered skill cards from dispatch through review
    Eight AI skills hang next to the SOPs and KPIs.
    1. restoration-setup. “Set up the kit.” Guided interview. First run. The concierge.
    2. job-intake-assistant. “We just got a water call.” New-loss intake, water Cat/Class, scope plus safety, a paste-ready job summary.
    3. equipment-advisor. “How many air movers for this room?” Sizing, placement, monitoring plan.
    4. sop-generator. “Write an SOP for mold containment.” Any of the 17, or a new one, in your voice.
    5. claims-assistant. “Draft a follow-up to the adjuster.” Emails, supplement justifications, aging-claims chase.
    6. kpi-coach. “Here are my numbers this month.” The 12 KPIs computed and trended. Biggest leak named, with fixes.
    7. crew-onboarding-builder. “Onboard a new tech.” Week-1 / 30 / 60 / 90 plus an IICRC certification roadmap.
    8. iicrc-protocol-lookup. “What does S500 say about Cat 3 water?” Plain-English pointer plus PPE.

    Install the plugin yourself

    Option A (recommended). Save the restoration-kit folder. In Claude run:

    /plugin marketplace add /path/to/restoration-kit
/plugin install restoration-kit@profit-detective
/restoration-kit:restoration-setup

    Option B. Copy each folder inside skills/ into ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then say “run restoration setup.”

    Keep company-profile.md in the folder you work in. Every skill reads it.

    If you want the packaged system

    You can rebuild this from the outline above. Buy Now is the flagship delivered by email after checkout: Notion duplicate links for the six tools plus IICRC lookup, the plugin zip (eight skills and the README), and the setup sequence so you drop it in and run. Same Square button at the top of this page.

    This is an operational system only. Not legal, insurance, or licensing advice.

    Related restoration products

    The AI half of this system is the Restoration Operations Kit — Claude Edition. For the leadership side, see the Restoration Leadership Toolkit — Claude Edition. Software comparisons that pair with the Claims and Job Tracker tools: Albi vs DASH and Xactimate integrations. Lead-gen context lives in Google Ads for Restoration.

    Frequently Asked Questions

    Is there a refund policy?

    Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.

    How is this delivered?

    Within 24 hours of purchase via email from will@tygartmedia.com. You will receive your download link — Notion duplicate link, skill file, or both depending on the product.

    Related on Tygart Media: Starlink on a water job · S500 in the van · local SEO for restoration.

  • Claude AI for Nonprofits: Discounts & Grant Guide

    Claude AI for Nonprofits: Discounts & Grant Guide

    Claude for Nonprofits is Anthropic’s program that gives qualifying nonprofits up to 75% off Claude’s Team and Enterprise plans — with Team seats starting around $8 per user per month — plus nonprofit-specific data connectors, free AI training, and access to a $150M fellowship. If your organization holds 501(c)(3) status (or an international equivalent), you almost certainly qualify. Here’s what’s included, who’s eligible, and how mission-driven teams are putting it to work.

    Direct Answer (August 2026): Anthropic offers discounted Claude Team subscriptions and grants for verified 501(c)(3) nonprofit organizations, charities, and educational foundations, facilitating grant writing, donor communications, and operational reporting.

    What is Claude for Nonprofits?

    Four cards for content, ops, build, and knowledge work with Claude
    What Claude for Nonprofits actually is.

    Launched by Anthropic in 2026, Claude for Nonprofits packages the same Claude models used by enterprise teams into an offering built for the realities of mission-driven work: tight budgets, lean staff, and a constant need to do more with less. It bundles three things nonprofits rarely get together — steep pricing discounts, sector-specific integrations, and free training — into one program. It runs on the same foundation as Anthropic’s commercial plans, so nonprofits get the latest Claude models (Opus, Sonnet, and Haiku), not a stripped-down version.

    Who qualifies?

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Who qualifies — check eligibility before budgeting.

    Eligibility is broad, and Anthropic validates organizations through its partner Goodstack. The program covers:

    • 501(c)(3) nonprofits in the U.S., and organizations with equivalent charitable designations internationally
    • K–12 schools, public and private
    • Mission-based healthcare organizations with 501(c)(3) status — including independent Critical Access Hospitals (CAHs), Rural Emergency Hospitals (REHs), HRSA-designated Federally Qualified Health Centers (FQHCs) and FQHC Look-Alikes, and CMS-certified Rural Health Clinics (RHCs)

    If you can document charitable status, eligibility is usually straightforward.

    How much does it cost?

    Qualifying organizations receive up to 75% off Claude’s Team and Enterprise plans:

    • Team plan — discounted pricing starts around $8 per user, per month, which makes it realistic to roll Claude out to an entire staff rather than a single power user.
    • Enterprise plan — custom pricing for larger organizations; you contact Anthropic’s sales team.

    Both tiers include Claude’s current model lineup. Pricing and model availability change, so confirm the latest figures on Anthropic’s official Claude for Nonprofits announcement. Curious how discounted seats compare to standard rates? Run the numbers on our Claude pricing calculator.

    What nonprofits actually use Claude for

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    What nonprofits actually use Claude for.

    The highest-leverage uses cluster around the work that eats the most staff time:

    • Grant writing — drafting proposals aligned to a specific funder’s priorities, then tailoring them per application.
    • Donor stewardship — personalizing outreach and acknowledgements at a scale a small development team could never manage by hand.
    • Program evaluation & impact analysis — turning messy program data into the impact narratives boards and funders want.
    • Board & compliance documentation — generating board materials, reports, and compliance documents from source data.

    The common thread: Claude removes the blank-page tax on the writing- and analysis-heavy work that keeps nonprofit staff at their desks instead of in the field.

    Connectors built for the nonprofit stack

    Anthropic built integrations with the platforms nonprofits already run on, so Claude can work against real organizational data:

    • Benevity — access to 2.4M+ validated organizations for volunteering and donation research
    • Blackbaud — CRM and fundraising tools for donor management, campaign tracking, and donation optimization
    • Candid — data on nonprofits and funders to discover organizations, grants, and philanthropic opportunities

    Free training and the Claude Corps fellowship

    Two things set this apart from a plain discount:

    • AI Fluency for Nonprofits — a free course Anthropic developed with GivingTuesday, covering grant writing, program evaluation, donor engagement, and organizational efficiency. It’s aimed at staff, not engineers.
    • Claude Corps — a $150M fellowship initiative pairing nonprofits with AI expertise and resources to implement Claude across their operations. Anthropic also works with partners including The Bridgespan Group, Idealist Consulting, Vera Solutions, and Slalom to support adoption.

    How to get started

    1. Confirm your charitable status (501(c)(3) or international equivalent).
    2. Apply through Anthropic’s nonprofit page — eligibility is validated via Goodstack.
    3. Choose Team (self-serve, discounted seats) or contact sales for Enterprise.
    4. Enroll staff in the free AI Fluency for Nonprofits course to get value quickly.

    Start at Claude for Nonprofits, or read Anthropic’s getting-started guide.

    Related on Tygart Media: how to use Claude · Anthropic API key.

    Frequently asked questions

    Is Claude free for nonprofits?

    Not free, but heavily discounted — up to 75% off Team and Enterprise plans, with Team seats starting around $8 per user per month for qualifying organizations.

    Who qualifies for Claude for Nonprofits?

    501(c)(3) nonprofits (and international equivalents), K–12 public and private schools, and mission-based healthcare organizations with 501(c)(3) status. Eligibility is validated by Goodstack.

    Which Claude models do nonprofits get?

    The discounted plans include Claude’s current lineup — Opus, Sonnet, and Haiku — the same models on the commercial plans, not a limited version.

    What can a nonprofit do with Claude?

    Common uses include grant writing, donor stewardship, program evaluation, and board and compliance documentation, plus integrations with Benevity, Blackbaud, and Candid.

    Is there training for nonprofit staff?

    Yes. Anthropic and GivingTuesday offer a free “AI Fluency for Nonprofits” course, and the $150M Claude Corps fellowship provides hands-on implementation support.

    Want to see how discounted seats stack up against standard plans? Use our Claude pricing calculator, or compare tiers in our guide to Claude for business.

    💼 Deploying Claude or AI Infrastructure in Your Business?

    At Tygart Media, we engineer custom Model Context Protocol (MCP) servers, multi-model content pipelines, and AI operational systems. Explore our Claude AI Team Implementation Services or check out our complete Restoration Operations & AI Kit.

  • I Let Claude Run on My Business. The Moment That Mattered (2026)

    I Let Claude Run on My Business. The Moment That Mattered (2026)

    For the past week or so I’ve been building a real operation with Claude — not a demo, not a clever prompt, an actual business a partner of mine is about to run.

    It built the storefront: a full ladder of products, from a $7 scorecard up to a complete operating system, each one wired to checkout and set to deliver itself the second someone buys. It built a redemption engine, so my partner can give out a code from a stage and the right person instantly gets the product while we capture the lead. It drafted a productized lead-generation offer — the pricing, a one-page pitch, even a scorecard to decide which contractors are a fit. When the server’s email quietly broke, it traced the real cause — a file permission, three layers down — and fixed it.

    That’s the part everyone wants to talk about: look what it can do. And it’s real. But it’s not what I’ll remember from this week.

    The moment that mattered

    Five security domains: identity, data, code governance, audit, agents
    The moment that mattered.

    I asked Claude to check whether a call-tracking number was set up correctly on the site. It looked, confirmed the number was live and routing to the right phone — and then, because it’s thorough, started to clean up a small labeling gap on that number.

    And then it stopped itself.

    A safety layer caught the action before it ran and refused it. The reason it gave was almost uncomfortably precise: you asked me to verify this, not to change it. This is a live system other people depend on. That’s your call, not mine.

    I’d only asked it to look. It had drifted toward changing a shared, live system — exactly the kind of small, well-meant overstep that’s easy to miss — and something stopped it and handed the decision back to me.

    I’d spent a week watching this thing demonstrate real capability. The moment it earned my trust was the moment it demonstrated restraint.

    Capability was never the scary part

    Three stacked layers: chat UI, tools, agent runtime
    Capability was never the scary part.

    That’s backwards from how most people are sizing up AI right now. The whole conversation is capability — what can it do, how much, how fast. But if you’re actually putting this into your business, capability was never the scary part. The scary part is an eager, capable system taking a consequential, hard-to-undo action on something live because it technically could, and because you weren’t specific enough.

    What protected me wasn’t that the AI was timid by personality. It’s that the whole thing is built so the more consequential, irreversible, and shared an action is, the more a human has to be in the loop. Reading something? Go ahead. Changing a live system someone else relies on, when that wasn’t clearly asked for? Stop and ask. The gate tightens exactly as the stakes rise.

    And the part that actually sold me: when I asked how that worked, it explained its own guardrails plainly. It didn’t pretend it had no limits, and it didn’t pretend it could talk its way around them. It told me where the brakes are, who controls them (me), and what it genuinely can’t see about its own safety layer. An AI that’s honest about what it won’t do is a lot easier to trust with what it will.

    What I’d take from it

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    What I’d take from it.

    If you’re bringing AI into your operation, here’s what I’d take from my week: don’t just ask what it can do. Ask what it does when it isn’t sure. Ask what happens at the edge — the live system, the irreversible change, the thing you didn’t quite specify. That answer matters more than the length of the feature list, because that’s the moment that either protects your business or burns it.

    The most capable AI in the room is impressive. The one that knows what it shouldn’t do without you is the one you can actually build on. I got to see both this week. Turns out they were the same one.

    Related on Tygart Media: Anthropic invisible agent layer · is Claude worth it · how to use Claude.

  • Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

    Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    The first thing to understand about Claude Tag pricing is that Claude Tag doesn’t have a price. There’s no separate line item, no per-feature fee. It’s included with the plans it runs on — Claude Team and Claude Enterprise, in beta — so the real question isn’t “what does Claude Tag cost,” it’s “which plan are you on, and is per-seat the right model for how you work.”

    What you’re actually paying for

    Four gates: max turns, tool allowlist, token budget, kill switch
    What you’re actually paying for with Claude Tag.

    Claude Tag is a capability of two existing plans, not a product you buy on its own:

    • Claude Team is straightforward per-seat: a flat monthly price per user (premium seats cost more for higher usage). Predictable, easy to budget, good for a defined internal team. For the seat-tier breakdown, see Claude Team Pricing 2026: Standard vs Premium seats.
    • Claude Enterprise is seat-plus-usage: a per-seat fee, and then the tokens your team consumes — in chat, Claude Code, or Cowork — billed on top. It adds controls like role-based access, but the total depends on how heavily you use it.

    Because the two plans bill on different logic, the “cheaper” one depends entirely on your usage shape. We dig into the Enterprise side in detail in Claude Enterprise Pricing: What Large Organizations Pay. For the broader list-rate map across Claude products, start with Claude AI pricing.

    The launch credit (worth knowing now)

    At launch, Anthropic is subsidizing early adoption: as of June 2026, it’s offering $1,000 in Claude Code and Cowork credits for every Enterprise seat activated by July 2, 2026 (deadline passed). For a team that was going to adopt anyway, that credit covers a meaningful chunk of early usage — it makes the “turn it on internally and try it” decision close to free. It’s time-boxed, so if Enterprise is on your radar, the math is best before that date.

    When paying per seat is the right call

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    When paying per seat is the right call.

    For a single internal team, the per-seat model is the obvious answer. You get a current-generation teammate (Claude Tag runs on Opus 5.5) with no infrastructure to build, the launch credit softened the ramp for early adopters, and ambient mode is safe to use because all the data is yours. Buy the seats and move on.

    When building your own loop wins

    Side-by-side when to use a script versus an agent
    When building your own loop wins.

    Per-seat pricing is built for one company’s team. It is not built for an agency running many clients through one operation — and that’s where the calculus flips. Building your own gated Slack–to–AI loop starts to beat paying per seat when:

    • You need hard isolation between clients that per-seat access controls don’t give you. Isolation has to be architectural, not a setting — see The Multi-Client Isolation Trap.
    • You want to own the credential and the model path, so no client’s API key or context lives where it could leak.
    • The approval gate is the product — you need a human signing off on every outbound deliverable, wired into the architecture, not bolted on.
    • Seat counts get large or spiky, where a usage-based loop you control can undercut a per-seat bill.

    We didn’t reason our way to this in a spreadsheet — we built that loop before Claude Tag launched, for exactly these reasons. The story is in We Built a Slack AI Teammate Before Claude Tag.

    The honest answer

    For your internal team, adopt Claude Tag on a Team or Enterprise plan and take the launch credit — it’s the cheapest path to a real AI teammate. For multi-client delivery, the per-seat model isn’t the whole answer, because the thing you’re really buying — isolation, control, and a human in the loop — is exactly what you have to build yourself. That’s the part we build for clients at Tygart Media. Start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

    Related on Tygart Media: how to use Claude · Anthropic API key.

  • How to Set Up Claude Tag in Slack (and What to Lock Down First)

    How to Set Up Claude Tag in Slack (and What to Lock Down First)

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    Setting up Claude Tag in Slack takes a few minutes. The clicks are easy. The decisions you make while you click — who can reach it, which channels it sees, whether it’s proactive — are the part that actually matters. This is a security-first walkthrough: how to install it, and what to lock down before you do.

    The install, in plain steps

    Side-by-side cards defining what Claude Code is and is not
    The install, in plain steps.
    1. Open the Install Claude for Slack link, which takes you to the Slack Marketplace listing.
    2. Click Add to Slack and approve the requested permissions.
    3. Choose the scope: the whole workspace (Anthropic’s recommended default) or a specific set of channels.

    One important gotcha: only a Slack Primary Owner or Owner can set up Claude Tag’s access and channels. The Admin role can’t do this part. If you’re rolling it out for a team, make sure an Owner is the one configuring access — otherwise you’ll get halfway and stall.

    Lock this down first: who can reach Claude

    Five security domains: identity, data, code governance, audit, agents
    Lock down who can reach Claude first.

    Claude Tag gives you three Member Access modes. Pick the tightest one that still lets the right people work:

    • Anyone in the Slack workspace — broadest; fine for a single internal team, risky if outside collaborators or clients are guests in your workspace.
    • Any member of your Claude organization — narrower; ties access to your Claude org, not just Slack presence.
    • Role-based access — tightest; only members whose role allows it. This one is available on the Claude Enterprise plan.

    Default to the narrowest mode that doesn’t block real work. You can always widen later; clawing access back after the fact is harder.

    Then decide what Claude can see

    Access is who can talk to Claude. Visibility is what Claude can read — and it’s the bigger lever. Two settings deserve a deliberate decision, not a default:

    • Cross-channel learning is permission-gated — Claude only learns from other channels and data sources you allow, and it doesn’t report from private channels. Grant it per channel, and never let a channel holding one client’s (or one regulated dataset’s) data feed learning that other work can draw on.
    • Ambient mode turns Claude proactive. Leave it off for anything client-facing or sensitive, and on only where all the data is yours. We break down that call in Claude Tag Ambient Mode: Useful Teammate or Context-Bleed Risk?

    The lock-down-first checklist

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    The lock-down-first checklist.
    1. Map channels to trust boundaries before you enable anything — mark each channel internal, client, or regulated.
    2. Set Member Access to the narrowest mode that works.
    3. Ambient mode OFF by default; on only for internal-only channels.
    4. Cross-channel learning granted per channel, never from client/regulated channels.
    5. Isolate client work in its own space, not just a channel in one shared brain — the reasoning is in The Multi-Client Isolation Trap.
    6. Keep a human on the ship button for anything that leaves the building.

    If you’re migrating from the old app

    Claude Tag replaces the legacy Claude in Slack app. The old app switches over on August 3, 2026, and administrators have a 30-day window to opt in and control channel-level access. Don’t treat the migration as a silent upgrade — it’s the moment to redo these access and visibility decisions from scratch. More on what changed: Claude Tag vs. the Old Claude in Slack App.

    For the exact, current setup screens, Anthropic keeps an admin setup guide in its documentation; the decisions above are what to bring to it. For the full field guide, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • Claude Ambient Mode & Background Tasks: Setup Guide

    Claude Ambient Mode & Background Tasks: Setup Guide

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    Ambient mode is Claude Tag’s headline feature and its single most consequential setting. Turn it on and Claude stops waiting to be asked — it starts watching the channels it’s in and speaking up when it thinks you’d want to know something. Whether you should enable it isn’t a yes-or-no question. It’s a where question, and getting the where right is the whole game.

    What ambient mode actually does

    Four-step loop: observe, remember, act, update for managed agents
    What ambient mode actually does.

    By default, Claude Tag is reactive: you @-mention it, it works, it replies. With ambient behavior enabled, it becomes proactive. Anthropic describes it as Claude keeping you updated about whatever it thinks you might need to know — flagging relevant information from across the channels it’s in and the tools it’s connected to, and following up on threads or tasks that have gone quiet.

    In practice that means three things: it surfaces context you didn’t ask for, it connects information across more than one channel, and it chases loose ends nobody assigned it. Those are exactly the behaviors that make it feel like a teammate instead of a tool.

    Where it’s a superpower

    Inside a single team, ambient mode is close to magic. Every channel belongs to the same company, so “learning across channels” only ever connects your own dots. A proactive teammate that remembers the forgotten follow-up, links the spec to the standup, and flags the blocker before it bites is pure upside. This is the version Anthropic runs internally, and it’s why they can say a large share of their product team’s code now comes from their own version of the tool.

    If your Slack workspace is one company’s data and one team’s work, turn ambient mode on and enjoy it.

    Where it’s a risk

    Five security domains: identity, data, code governance, audit, agents
    Where ambient mode is a risk.

    Ambient mode’s proactive, cross-channel nature is exactly what makes it dangerous in two situations:

    • Multiple clients in one operation. The moment a proactive teammate is “surfacing relevant information from across channels,” relevance becomes the judge of what crosses the line between Client A and Client B. That’s a context-bleed risk we’ve lived — the whole subject of The Multi-Client Isolation Trap.
    • Regulated or sensitive data. Anywhere an unprompted message pulling context from elsewhere could expose something it shouldn’t — health, financial, legal, HR — proactive surfacing is a liability, not a convenience.

    A simple decision framework

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    A simple decision framework before you enable it.

    Don’t decide ambient mode globally. Decide it per surface, with one question: is everything this Claude can see owned by the same trust boundary?

    SurfaceAmbient modeWhy
    Internal team channels (one company)ONCross-channel proactivity only connects your own data
    Client-facing / multi-tenant channelsOFFProactive surfacing is where one client’s context leaks into another’s
    Regulated / sensitive-data channelsOFFUnprompted context-pulling is a compliance liability

    The rule of thumb: ambient mode should be on where the data is all yours, and off everywhere a human should still be pulling, not the AI pushing.

    If you do turn it on

    Enable it deliberately, not by default. Map which channels hold which trust boundary before you flip the switch, keep client and regulated channels out of cross-channel learning, and audit what the assistant can actually see. That sequencing — boundaries first, then ambient — is exactly how we walk through it in How to Set Up Claude Tag in Slack.

    The bottom line

    Ambient mode isn’t good or bad — it’s powerful, and power needs a boundary. For internal teams, it’s the best part of Claude Tag. For client work, it’s the part to leave off until isolation is airtight. For the full picture, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • Claude Tag: A Builder’s Guide (2026)

    Claude Tag: A Builder’s Guide (2026)

    Today Anthropic launched Claude Tag — a new way to work with Claude that starts inside Slack. Instead of a chatbot you visit, Claude joins your workspace as a teammate. You @-mention it with a request, it breaks the task into stages, works through them, and replies in the thread with what it made.

    We read the announcement with a strange feeling, because we’d been running a version of this loop for client delivery for weeks. So this isn’t a reaction piece written from the outside. It’s a field guide from a team that built the same thing first — what Anthropic got right, what’s genuinely better in their version, and the one design choice that’s quietly dangerous if you run an agency.

    What Claude Tag actually is

    Side-by-side cards defining what Claude Code is and is not
    What Claude Tag actually is.
    • A Slack-native teammate you delegate to by tagging @Claude — no separate app to open.
    • Multiplayer by default: one shared Claude per channel; anyone can see its work and pick up where the last person left off.
    • Context that compounds: it follows the channel over time, and with permission can learn from other channels and data sources.
    • Ambient mode: turn it on and Claude takes initiative — surfacing what’s relevant, flagging stale threads, following up on forgotten tasks.

    It runs on Opus 4.8, replaces the older “Claude in Slack” app (admins opt in within 30 days), and is in beta for Enterprise and Team plans. Anthropic says 65% of their product team’s code now comes from their internal version. That number is the tell: this isn’t a toy.

    What they got right

    1. The unit of work is a request, not a conversation. “@Claude, draft the launch email and three follow-ups” is how people actually delegate.
    2. Shared context beats private chats — auditable and collaborative; private AI sessions create shadow work nobody can review.
    3. It meets people where the work already is. The work happens in Slack, so the AI lives in Slack.

    The one thing agencies have to get right (and Claude Tag doesn’t, by default)

    Claude Tag’s standout features — ambient mode and cross-channel learning — are wonderful when every channel belongs to one company. But an agency is many clients sharing one operation. The moment your AI teammate “learns across channels and data sources,” context from Client A can surface in work for Client B.

    We learned this by living it. In an early pilot, a single shared context produced client deliverables that pulled in details from the wrong account. Nothing left the building, but the signal was clear: for client work, ambient cross-channel learning is not a feature — it’s a breach waiting for a deadline.

    So we rebuilt around two non-negotiables:

    • Hard isolation per client — each client’s room is walled, enforced in the architecture, not a prompt you hope it obeys.
    • Approve-before-ship — the AI drafts; a human reviews; only then does it go out.

    If you take one thing from this guide: the two things that make Claude Tag magical inside a company are the two things you must switch off — or wall off — to use it safely for clients.

    The pattern that works: split by surface

    Five security domains: identity, data, code governance, audit, agents
    Split by surface — the pattern that works.
    SurfaceUseWhy
    Your internal teamAdopt Claude TagAmbient cross-channel learning is a feature when all the data is yours
    Client-facing deliveryIsolated room + approval gateIsolation and human sign-off are the product

    How to roll it out without getting burned

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Roll it out without getting burned.
    1. Map channels by trust boundary; client-data channels don’t get cross-channel learning.
    2. Default ambient mode OFF for anything client-facing.
    3. Keep humans on the ship button for anything that leaves the building.
    4. Audit what the AI can see — your permission is the control; set it deliberately.
    5. Separate client work into isolated spaces, not just channels in one shared brain.

    Where this goes

    Claude Tag is a milestone: the AI teammate is now an operating model, not a demo. For internal teams, adopt it. For client work, the hard, valuable part — isolation, trust, a human in the loop — is still yours to own. That’s what we build for clients at Tygart Media.

    The rest of the field guide

    This pillar is the overview. The cluster goes deeper:

  • Claude Tag vs. the Old Claude in Slack App: What Changed

    Claude Tag vs. the Old Claude in Slack App: What Changed

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    If your team already used the “Claude in Slack” app, Claude Tag is not an add-on — it’s the replacement. Anthropic has said Claude Tag replaces the existing Claude in Slack app, administrators have a 30-day window to opt in, and the legacy app is retired on August 3. So this isn’t a “should we try it” decision. It’s a migration with a clock on it. Here’s what actually changed, and what to check before you flip the switch.

    What’s genuinely new

    Three stacked layers: chat UI, tools, agent runtime
    What is genuinely new in Claude Tag.

    The old integration was, in practice, a way to summon Claude in a thread. Claude Tag changes the model from “a chatbot you call” to “a teammate that stays.” Four things are new:

    • Multiplayer per channel. Within a given Slack channel, there’s one Claude that interacts with everyone. Anyone can tag it in and pick up where the last person left off, instead of each person holding a private session.
    • Ambient mode. When enabled, Claude proactively keeps people updated about what it thinks they need to know — flagging relevant information, following up on forgotten threads — rather than waiting to be asked.
    • Cross-channel learning. With permission, Claude can learn from other Slack channels and data sources. (Anthropic notes it doesn’t report from private channels.)
    • Opus 4.8 underneath. Claude Tag runs on Opus 4.8, so the reasoning behind the delegation is the current-generation model, not whatever the old app was pinned to.

    The migration timeline, plainly

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Migration timeline, plainly.

    Three dates and facts matter:

    1. Claude Tag is available today in beta for Claude Enterprise and Team customers.
    2. Administrators have 30 days to opt in and migrate.
    3. The old Claude in Slack app is retired on August 3. If you do nothing, that capability goes away.

    Anthropic is also issuing an introductory launch credit to eligible Enterprise and Team organizations, which makes the trial period genuinely low-stakes for internal use.

    What to check before you switch — especially if you serve clients

    Five security domains: identity, data, code governance, audit, agents
    What to check before you switch — especially for clients.

    For a single-company team, migrating is close to a no-brainer: you get a better model and a more capable teammate, and the launch credit covers the experiment. If you’re an agency or anyone handling more than one client’s data in one workspace, three checks come first:

    1. Decide cross-channel learning per channel, not globally. The new superpower is also the new risk. A channel that holds one client’s data should never feed learning that another client’s work can draw on. Map your channels to trust boundaries before you grant any cross-channel permission.
    2. Default ambient mode OFF for client-facing channels. Proactive surfacing is wonderful internally and dangerous across tenants. Turn it on where the data is all yours; leave it off where it isn’t.
    3. Keep your approval gate. Whatever human sign-off you had on outbound work in the old setup, carry it forward. A more autonomous teammate raises the stakes on “who hits send.”

    Our take

    Adopt it internally now — the model upgrade and the multiplayer surface are worth it, and the clock makes the decision for you anyway. For client delivery, migrate deliberately: the same features that make Claude Tag better make isolation harder, and isolation is the thing you can’t get wrong. We unpack exactly that failure mode in The Multi-Client Isolation Trap, and the on/off call for proactive behavior in Claude Tag Ambient Mode.

    For the full picture, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.