Skip to main content
Haney Strategy

Claude training for teams

Claude Team Training Real work. Real adoption.

Claude training for business teams. In four weeks, the sales, service, and administrative work your team assembles by hand every week starts running through workflows your team builds. Your people review and approve every piece before it goes out.

One teamFour weeks$6,500 per team

For SMB and mid-market teams. If your people assemble the same work by hand every week, it qualifies, whatever the business.

Book an Introductory Call
A rendered scene of a working session: a facilitator and a small team at a table in a meeting room.

The work you already do

The same work, week one and week four.

Four pieces of work most teams turn out by hand every week. Week 1 is how it gets done today. Week 4 is how it runs once the team has built it with Claude, Anthropic's AI assistant. In your four weeks, the list is your team's own work.

  • Client updates

    Week 1By hand, every week.

    Week 4Drafted with Claude. Your account manager checks it and sends it.

    What changesIt goes out the same day, and it reads the same way every week.

  • Quotes and proposals

    Week 1Rebuilt from the last one.

    Week 4Drafted with Claude. Your sales lead checks the numbers and sends.

    What changesLess rebuilding, and the numbers get checked in the same place every time.

  • Service follow-ups

    Week 1Written up after the visit.

    Week 4Drafted with Claude. Your service manager approves and sends.

    What changesThe follow-up leaves while the visit is still fresh, instead of waiting for a quiet hour.

  • Weekly reports

    Week 1Copied and pasted together.

    Week 4Assembled with Claude. You read it and sign.

    What changesIt is assembled before the meeting instead of during it.

An example. The work will be your team's.

From ideas to everyday use

I show your team how to use Claude in the work they already do, with real examples, live practice, and a simple plan to keep it going.

  • Hands-on and role-specific
  • Focused on real workflows
  • Built for lasting adoption

Which team goes first

The team with the most repeat work goes first.

Start with one team and the work it already does every week. I don't count heads: a big team splits into smaller working sessions, and the price stays the same. Just you, or two of you? That's a different conversation, and I'm happy to have it on the call.

Most of the companies I talk to already have AI somewhere. One person got good at it, the rest of the team watched, and the course everybody sat through last year did not change a single Tuesday. Using AI every week and getting real work out of it are two different things. The difference is whether anybody built anything.

Your team is ready when four things are true

  • A manager takes part.

    Not a boss who checks in at the end. The manager builds alongside the team and keeps the routine going afterward.

  • The work repeats.

    Weekly or monthly, the same kind of work, from the same kind of information.

  • The information is reachable and approved.

    The team can already get to what the work needs, and you are comfortable with Claude seeing it.

  • The team practices between sessions.

    The workflows get built in the sessions and tried on real work in the week between them.

Sales, service, marketing, or the back office

The work looks different from one business to the next, and the pattern repeats: something the team produces every week from the same kind of information. A few I see most:

Sales.

  • Proposal prep from discovery notes and approved product details
  • The follow-up after the call
  • The pipeline notes the manager reads on Monday

Service.

  • Service summaries after a visit or a ticket
  • Client review prep
  • The recurring reports clients wait on

Marketing and content.

  • The weekly newsletter
  • The social calendar
  • The first draft of a case study

Back office.

  • Renewal follow-ups
  • The month-end reporting
  • The vendor chasing that slips when the week gets loud

What this is not

  • Custom software. I do not build integrations into your systems, and nothing here depends on one.

  • A way around access. If your team cannot reach a piece of information today, a workflow cannot reach it either.

  • Unattended work. Nothing sends on its own. Every workflow stops at a named reviewer.

Inside the four weeks

Select it, build it, run it, improve it, demo it.

The four weeks are five steps, not a calendar of meetings. Each step happens first in a working session with me, then again in the team's normal week.

How the four weeks run

01

Select. We pick the recurring work with the manager: what the team produces every week, what it costs them to assemble, and what has to be reviewed before it leaves the building.

02

Build. The team builds each piece into a workflow, in plain English, with me working alongside them. Every workflow names the person who reviews it.

03

Run. The team runs the workflows in its normal week, on live work, and brings back what broke.

04

Improve. We fix what broke and write each workflow down, so it holds after the four weeks end.

05

Demo. Your team demos its own work, running, to you. That is the finish line.

What you keep

  • Named workflows. Every piece of work the team rebuilt, running, with the person who signs it off named inside the workflow.

  • The documentation. Each workflow written down in plain English, so it holds after week four.

  • The weekly rhythm. The manager's routine for keeping the work honest: what ran, what got signed, what needs a second look.

  • The sign-off. Claude does the assembly. Your people approve every piece before it goes out.

Which workflows we build, and who joins each working session, is agreed with the manager before the four weeks start.

Jim Haney

The proof

I run my whole practice with Claude. That is why I can teach it.

I started where almost everybody started, in ChatGPT: email, copy, novelty. The shift came when I put Claude on real work and the work came back complete: proposals, business plans, and eventually the code behind this site. Today I run my whole practice with Claude, every single day: the research, the proposals, the client dashboards, the writing, the build. What your team builds in four weeks is the same discipline, on your work.

MIT

AI & Digital Transformation certificate

26

Years across sales, marketing, technology, and AI

33

Months of hands-on AI build, daily

As of September 1, 2026

200+

MSP leaders trained on AI at IT Nation Connect, 2024 and 2025

I also sit in the fractional chief marketing and technology officer seat for clients on retainer, which is where I get to watch what holds after a training ends and what quietly does not.

A peer, on the AI work

He has successfully integrated AI into marketing workflows, enhancing efficiency and maintaining the human element in AI-driven processes. His ability to keep the human voice and creativity central to AI-driven content truly stood out.

Natalie SuarezCyber Advisor at Huntress

The price

One offer. One price per team.

$6,500

Per team

Four weeks

Your team demos it

The price covers the team, the four weeks, and the demo. A big team splits into smaller working sessions at the same price. We'll work out the details on the call.

Book an Introductory Call

What the price covers

  • Direct work with me for the four weeks. Not a course, and not handed to somebody else.
  • The working sessions, and the practice the team does between them.
  • The documented workflows, each with a named reviewer.
  • The manager's routine for keeping them running after the four weeks.
  • The demo your team gives you at the end.
  • The written ground rules for what Claude may see and who approves what.

What you bring

  • A manager who takes part.

  • The team, and the recurring work it already produces.

  • Access to the information those workflows need.

  • Claude subscriptions, bought straight from Anthropic at their published prices. I sell no licences and take no commission on any of them.

The workflows we build and the access they need are agreed with you in writing before the four weeks start.

Questions

What owners ask before they start.

What is Claude Team Training?
Claude Team Training is a four-week engagement for one of your teams: one manager, the people on that team, and the real work they already produce every week. Claude is the AI assistant built by Anthropic; Haney Strategy is an independent practice, not affiliated with or endorsed by Anthropic. The team builds that work into named workflows that Claude carries out: gathering, assembling, drafting, and checking, with a named person reviewing every output before it goes anywhere. It ends with the team demoing their own work, running, to you. The training is the means. Work that runs is the point.
Do my people need to be technical?
No. If someone can describe a piece of their work in plain English, they can build it with Claude and me in the room. The whole four weeks run in plain language, and every workflow is documented the same way, so it holds up long after week four. The hard part is not the typing. It is knowing which work to hand over, where a person has to check it, and how to make it stick. That is the part I bring. Anthropic's own courses are the prework and they are free to anyone with a Claude account, so I never charge you for what the vendor gives away. What the vendor does not do is sit with your team for four weeks and rebuild the work that team turns out every week.
What Claude accounts do we need, and what if we already pay for another AI tool?
A paid Claude plan for each person on the team, bought straight from Anthropic at their published prices. That is the whole shopping list. Which plan fits depends on the work your team does, so it is one of the first things we settle on the intro call. It lands in writing with the ground rules: a company workspace rather than personal accounts, so the admin and data controls belong to your business. I sell no licences and take no commission on any of it, which keeps the recommendation honest. If your company already pays for another AI product, keep it. The four weeks are about your team's recurring work, not about swapping out your tools, and the workflows we build stay inside the tools your company has approved.
What about our data, and who is responsible for what goes out?
That is the first thing we settle, and we settle it in writing. The four weeks start with ground rules: what Claude may see, what it may never see, and who signs off on what. Nothing on this page shows a word of anyone's client content, and that is the same discipline your team learns. The ground rules also cover the data itself: where it lives, how long it is kept, and whether it trains the model. Each of those is set against Anthropic's published commitments, in writing. Responsibility does not move: every workflow ends at a named person in your company who reads the output and approves it before it goes anywhere.
Why Claude?
I stay current on all of it. I go deep on one. My advisory work stays neutral across the AI market, and Google's Gemini still makes my blog images. Claude is where my own work gets done every single day, and that is the honest reason it is the one I teach. That is a statement about my practice, not a ranking, and nothing here asks you to drop a tool your team already uses.
How is this different from a workshop?
A workshop puts skills in the room in a day. Claude Team Training lives inside one team's real work for four weeks and ends with that work running, demoed to you. One builds skills. This one rebuilds the work. Different jobs, and they stack.
What happens after week four?
Your team keeps everything: the workflows, the documentation, and the weekly rhythm the manager uses to keep the work honest. It is yours, built by your people, running inside your company, and your team maintains it the same way it maintains any other part of its week. The four weeks end at the demo, and anything after it is a separate conversation.

The intro call

Bring the team you'd start with.

It's free, and it's specific. Sixty minutes, no prep. Tell me which team you have in mind and what their week actually looks like, and we will map their four weeks together. You leave with a straight answer on whether this fits and which work I would start with, whether or not we ever work together.

Book an Introductory CallSee how the four weeks run
Related thinking

How I think about Claude training.