Team Training
A monthly engagement in which your own people learn to use Claude to build and run their own simple workflows, one bottleneck at a time, with Natural State Logic coaching. It isn’t custom-built software; for that, see the done-for-you track.
The question is who does the building. If your people want to, this is the track. If you’d rather have it built for you, the done-for-you track starts with an Workflow Review. The services page sets the two side by side.
Good first jobs to build yourselves, shown on fictional data: a customer list cleaned up and customer reviews sorted by theme. Not sure which track fits? Read what a business automation consultant actually does.
Who Team Training is for. Small and midsize organizations whose people would rather learn to do the work than have it done for them.
A good fit when
- Your problems are several small, repeated tasks rather than one workflow worth building.
- The people who do the work want to learn to handle it themselves.
- Your organization holds, or will approve, Claude Team or Enterprise seats in its own name.
- Someone can manage your Claude organization and turn connectors on when they are needed.
Not the right track when
- You want a workflow built and kept running for you. That is the done-for-you track.
- You first need to know which workflow is worth building, and whether. That is the Workflow Review.
- Anyone would use a personal or Pro Claude account with company data.
- Your organization will not approve Claude. The done-for-you track may still fit.
What each month includes
Every call is a working session. Your people build on their own Claude accounts while Tanner coaches, and the call ends with something saved that you keep.
Two 45-minute calls
Working sessions: your people build on their own Claude accounts while Tanner coaches, and each call ends with something saved that you keep.
Support between calls
Questions between calls on Voxer, with no limit on messages and a reply within one business day.
A monthly Progress Note
A short note recording what was worked on, what your people built, and what comes next.
The Progress Note records what happened. It measures nothing against a baseline and is not a measurement report.
The first month. It starts building straight away rather than studying the business first.
An intake form
Your own list of the tasks that take your week, where work stalls, and what must not be touched. It asks for no passwords, record exports, or regulated data.
A first call that picks one bottleneck
Together, you choose one bottleneck to start on, and your people begin building on that call. The list stays yours: nothing is scored, ranked, or written up.
What your people build
Each piece lives in your own file storage or your own Claude organization, has a named owner inside your organization, and is yours. Natural State Logic keeps no copy.
Claude skills
Instructions Claude follows for one repeated job, including what it must never do and where a person checks the result.
Claude projects
A shared workspace for one team and one job, with its instructions and reference files.
Connector setup notes
For each connector your administrator turns on: what it is, why it is allowed, what access it has, and what it must not be used for.
Reusable prompts
Prompts in your people’s own words, with what to paste in and what to check in the answer.
The terms it rests on
- Claude only
- Your organization holds Claude Team or Enterprise seats in its own name. Personal or Pro accounts are never used with company data.
- Your people do the work
- One bottleneck at a time, chosen together. Tanner never signs in to your accounts and holds none of your credentials.
- You own what is built
- The skills, projects, and prompts your people build are yours, and stay yours.
Security holds on this track too
Your people doing the building changes who does the work, not the conditions it is done under.
The Security Constraint, with no exceptions
Least-privilege access, a clear view of where your data travels, and a person who approves anything with consequences. The same conditions as the done-for-you track.
The Connector Allow-list
On company data, only connectors in Anthropic’s directory and servers published by the vendor of the software they connect to. Anything else stays off until it has been inspected.
Your accounts, your credentials
Tanner never takes control of your screen, never signs in to your accounts, and holds none of your credentials. Calls are not recorded.
A line for support messages
Voxer is not for credentials or regulated data, and files are shared through your own file sharing rather than through Voxer.
The conditions are stated in full on the services page.
When a piece needs building for you: Move-up Triggers
Some work should not be built inside Team Training. A piece that needs any of these is routed to the done-for-you track, and the rest of your Team Training carries on unchanged.
- Custom code or a custom integration
- A connector or MCP server that does not exist yet
- Write access to a system of record, such as accounting, CRM, or HR
- Regulated or sensitive categories of data
- Anything that runs unattended
The trigger is named on the call, in a sentence you could repeat. That piece then enters the done-for-you track where it fits: an Intro call when someone else in your organization owns it, a Workflow Review when it is still open what to build, or an Automation Pilot when that is already settled. It is proposed separately, in writing, and you can decline it; it is then left alone rather than built inside Team Training.
Questions about Team Training
Can you build it for us instead?
Yes, on the done-for-you track: a Workflow Review, then an Automation Pilot, then Ongoing Support. The Intro call is where it is decided which track suits you.
Why Claude, and only Claude?
Team Training is built around Claude’s skills, projects, and connectors, so the coaching, the account checks, and the Connector Allow-list all apply to one set of tools. The done-for-you track is not tied to Claude in the same way.
Is this a lighter Workflow Review?
No. There is no findings document and no ranked list of opportunities, at the start or later. If you need to know which workflow is worth building first, that is what the Review is for.
Do we have to move on to the done-for-you track afterwards?
No. Most Team Training clients are expected to stay self-sufficient. Only a piece of work that hits a Move-up Trigger is routed there, and you can decline it.
Can we stop?
Yes. It runs month to month, and you can stop at the end of any paid month. What your people built stays yours.
What does it cost?
The terms, including the monthly fee, are set out in a short written agreement once the call has established that Team Training fits.
Start with the Intro call
Describe the work that fills your week. The call settles whether Team Training fits, or whether the work is better built for you.