Programs tailored to your company, in person or online: one session for leadership, workshops by department or in mixed groups for team leads, and a technical Claude Code track for IT. With Claude Team or Enterprise setup, a data usage policy and adoption follow-up.
We reply on WhatsApp and put the proposal together: groups, schedule and plan.
Formats
Leadership, non-technical teams and IT have different questions. That is why we do not give one talk for everyone: we build the program with the tracks your company needs, from a single session to several weeks, in person or online.
What they bought, what it will cost per month and how it is controlled. Data governance, the admin console and each manager's role in adoption.
For non-technical areas: Operations, Finance and Administration, HR, Sales and Marketing. Groups by department or mixed, with examples from their own tasks.
The technical track: how to configure Claude Code so it understands the repo from the first message, and how to work as a team without breaking anything.
You choose the tracks, we define the groups together and build the demos with real documents and tasks from your company. There is no fixed syllabus: the pre-workshop form defines what each group practices.
In person at your office in Buenos Aires and surroundings. Online by video call for the rest of the country and the region, with the same exercise dynamic. They can also be combined: leadership in person and groups online.
Plan
It is the first decision and the one that raises the most questions. This is what changes between them. In the leadership session we turn it into numbers with your company's usage estimate.
| Claude Team | Claude Enterprise | |
|---|---|---|
| Organization size | 2 to 150 users | From 20 seats, no cap |
| What the seat includes | Access and usage included, with per-session and weekly limits | Access only. Usage is billed separately at API rates, with no weekly limit |
| User provisioning | SSO with automatic creation on first login. Removal is manual | SSO + SCIM: automatic creation and removal from your directory, with groups |
| Roles and permissions | Predefined roles | Custom roles per group: which features, models and connectors each area sees |
| Spend control | Per organization and per user | Per organization, group and user, with alerts and budgets per area |
| Audit logs and Compliance API | No | Yes |
| Configurable data retention | No | Yes, from 30 days |
| US-only inference, customer-managed keys (CMEK), HIPAA | No | Yes, optional |
| Claude Code | Included in the seat | Included in the seat, usage is pay-as-you-go |
| Your data used to train models | No | No |
Enterprise is not the expensive version of Team: it is a different way of paying.
On Team the seat includes usage. On Enterprise the seat is access only and every token is billed separately, with no weekly limit. It is justified by governance and control (audit, retention, SCIM, budgets per area), not by price. If your compliance does not require any of that, Team is usually enough.
Groups
One talk for the whole company does not work: leadership wants to know what it costs and how it is controlled, IT wants to configure, and everyone else wants to solve Monday's task. That is why we split them.
Governance, usage and budgets, the manager's role in adoption. Not mixed with team leads: the questions are different.
Tokens and context, data security in the organization, Projects and how to load context once. The common floor before splitting up.
If departments are large, one group per department with its cases. If they are small, mixed groups of 5 to 6 people with the same content and exercises on each person's real task.
Its own hands-on track. It uses more than the rest and needs permissions, sandbox and repo conventions that other areas do not need.
Sample structure
For a 70-person company with 20 Enterprise users, the program looks like this: 1 leadership class of 2 hours (CEO and 4 managers), 1 general session of 1 hour for the 16 team leads and 3 mixed groups of 5 to 6 people, 1.5 h each. Total: 7.5 hours of sessions in one week, with a prior visit to align with managers.
Departments
Use cases we have already worked on in workshops, and the data limit each department has to respect. Examples are built from your company's documents.
Summaries of long reports, comparison of vendor proposals, drafts of internal communications, reading the usage dashboard.
Limit: Decides which data each management area approves.
Repo CLAUDE.md, PR review, tests, documentation, MCP to internal databases, GitHub Actions with Claude built in.
Limit: Secrets out of context, minimum permissions, usage audit.
Comparing PDF quotes, purchase order tracking, weekly dispatch incident summaries, procedures turned into checklists.
Limit: Contract excerpts, never the whole contract. Margins out of the shared Project.
Reconciliations between spreadsheets, executive summary of the monthly report, collection email sequences, contract clause review, audit checklists.
Limit: Every figure is verified by hand and the check is recorded.
Job descriptions, CV screening with explicit criteria, interview guides, 30-day onboarding, internal communication by audience.
Limit: Personnel files and salaries do not go in. Anonymize before uploading. The final decision is always human.
Proposals from a brief, sales analysis, content and campaigns, ecommerce descriptions, customer replies with the brand guide loaded.
Limit: No customer personal data in prompts. Prices and margins out of the shared context.
Methodology
Same structure in every group, in person or online. Half the time is practice on real tasks, because what gets practiced is what is still in use two weeks later.
Before the workshop each person tells us which tools they use and brings a real repetitive task. We build the demos from that.
We start with 3 questions they cannot answer yet. We come back to them at the end to measure what changed.
No generic slides. We work with the company's spreadsheets, PDFs and documents, anonymized when needed.
Half the time is exercise: each participant solves their task and builds a reusable prompt. Then they review a colleague's output.
One person explains to another how they solved it, without looking at the screen. If they cannot explain it, they did not learn it.
Everyone leaves with 3 tasks to automate, an owner and a 30-day review date. The department leaves with its Project ready.
Implementation
Training is useless if the organization is misconfigured. We get the platform ready before the first workshop: identity, permissions, budgets and usage policy. We do it together with your IT lead.
Organization creation, corporate domain capture, training opt-out and handling of the data processing addendum (DPA).
SSO with Microsoft Entra ID, Okta or Google Workspace. On Enterprise, SCIM with one group per department so removals are automatic.
Roles per group, which connectors and models each area sees, spend caps per organization, group and user, alerts before reaching the limit.
A document adapted to your company: which information can be processed, what gets anonymized, what never goes in and how an output is verified.
Google Workspace or Microsoft 365, GitHub, Slack if you use it. Shared Projects per department with initial instructions and context files.
Centralized configuration for the technical team: permissions, rules for secrets, sandbox, audit hooks and models enabled by cost.
We train the IT person who administers the platform: users, usage, permissions. Then 30 days of support for operational questions.
Deliverables
Material you use the next day, not a PDF of slides. It varies with the tracks you contract.
20 Enterprise users
Program design for 20 Enterprise users in 4 groups: leadership, general session and 3 mixed groups of team leads. 7.5 hours in one week, in person, with organization setup per department.
31 people, 9 groups
2-hour workshop on AI applied to daily work, split by department. NPS 65 and 8.9 out of 10 recommendation in the follow-up survey.
.NET IT team
Claude Code track delivered to the development team: CLAUDE.md for .NET repos, GitHub workflow, cost control and self-validation with hooks and tests.
Team
Two complementary profiles: technical implementation and day-to-day adoption. We cover both "how it works" and "how it is really used" in your organization.
We Make It Lab. Applied AI, Claude Code and Team / Enterprise setup
Helps companies adopt AI in a practical way: sets up Claude Team and Enterprise organizations, runs the department workshops and the technical Claude Code track. Uses the tools he teaches every day in campaigns, automations and development.
LinkedIn
We Make It Lab. Communication, adoption and follow-up
Focused on making sure the tool is used after the workshop: a clear message per department, internal champions, team habits and adoption metrics reviewed at 30 and 60 days.
LinkedInFAQ
The questions that come up on the first call with any company.
Team is the right fit for most companies with 2 to 150 people: the seat includes usage, cost is predictable and it has SSO. Enterprise is the right fit when compliance requires audit logs, configurable retention, SCIM or budgets per department. It is not cheaper: the seat is access only and usage is paid separately. We decide together in the leadership session with a real usage estimate.
Between 5 and 20. Small groups are more dynamic: 2-hour sessions have stretched to 3 because of the number of questions. That is why we run one block per group and keep leadership and IT separate from the rest.
If each department has 5 or more people, one group per department with its cases. If they are small, mixed groups of 5 to 6 people: everyone sees the same content and the exercises are done on each participant's real task. The company defines the composition.
Yes, always. You choose the tracks (leadership, groups, IT), we define the groups with you and the demos are built with real documents and tasks from your company. The pre-workshop form each participant fills in defines what gets practiced in each workshop. If the team already has a basic notion of Claude, we start from operational use.
No. Only the IT track is technical. Everyone else works from Claude's web interface, with everyday spreadsheets, PDFs and documents.
Not for the leadership session. For the group workshops, yes: each participant practices with their own user in the organization. If you do not have a plan yet, we set it up before the first session.
Both, with the same program and the same exercise dynamic. In person in Buenos Aires and surroundings, at your office. Online by video call for the rest of the country and the region. They can be combined: leadership in person and groups online. The company provides a screen and, if it wants, records the sessions.
Each department leaves with a 3-task plan and a 30-day review date. Optionally we add monthly support: a bank of online hours and a usage review with leadership.
By number of groups, hours, format and whether it includes organization setup. Message us on WhatsApp with how many people and which departments, and we put the proposal together with the schedule.
Message us on WhatsApp. Tell us how many people and which departments, and we propose the groups, the schedule and the plan. In person or online, tailored.