VANDAMTeam Harness
Give the whole teamwhat your power users built for themselves.
Claude Code and Claude Cowork, set up for your team in three weeks. Permissions and approved connectors agreed with IT, a shared library of skills written from your own SOPs, each with an owner, a link to your company context and a usage standard people can follow.
$12,800 three weeks
How we handle a damaged return
SOP · Damaged goods, 2024 · owner Dana Ruiz, service lead
- 1Ask the customer for photos of the damage and of the outer box.
- 2Find the order and the shipment in the ERP.
- 3Open a claim with the order number, the photos and the carrier.
- 4Send the claim to Operations. No credit is promised before they review it.
- 5Reply with the claim number and the day they will hear from us.
---name: damaged-returndescription: Customer reports goods that arrived damaged.owner: dana.ruizconnectors: zendesk: read, draft erp: readnever: issue a credit or refund---1. Ask for photos of the damage and the outer box.2. Look up the order and shipment in the ERP.3. Open a claim: order, photos, carrier.4. Route the claim to Operations and wait.5. Draft the reply with the claim number and a date.
Reviewed by Dana Ruiz · in the library
12 of 12 use the shared library
- DanaService lead
- PriyaSales
- TomIT
- MeiPurchasing
- SaraFinance
- JonasService
- LucaService
- InèsService
- RaviSales
- AnaService
- PieterWarehouse
- KofiSales
Leaders use AI every day.
The front line has stalled.
- 51%
- of frontline employees use AI regularly, a figure that has stalled, while more than three quarters of leaders and managers use it several times a week.
BCG, AI at Work, 10,600 people, June 2025. - 1/3
- of employees say they have been properly trained to use AI. BCG, AI at Work, 2025.
- 78%
- of AI users bring their own AI tools to work.
Microsoft and LinkedIn, Work Trend Index, 31,000 people, 2024.
How do I ensure that I roll out claude code and cowork securely without putting my company data at risk?
TenexJuly 2026Source Start with the SOP people actually follow. The one in the shared drive is often from 2021.
Most teams have a few power users and a lot of logins.
In most companies we work with, three or four people have built a serious setup of their own: saved prompts, personal skills, connections to the tools they use every day. Everyone else has an account and uses it like a search box. Alex Lieberman, a founder of Tenex, heard the same from the CHRO of a $500m consumer business and wrote it down as their key challenge: “A widening gap between power users and the rest of the org; reluctance to roll advanced access to all employees without guardrails is creating tension.”
Both halves of that sentence are reasonable. Claude Code and Cowork read files, run commands and act in connected tools, so somebody has to decide what each role and each skill may touch. Once that is decided, the methods of the few can become the team’s. A skill is a written procedure the assistant follows, and most of yours already exist as SOPs, onboarding docs and the checklists your best people keep.
The harder part is keeping it shared. 
J.B. describes what most teams end up with: “Each person has to teach their AI what they know and how they work. The context, corrections, and workflows they create rarely reach anyone else.” A library with an owner per skill and a review step fixes that. One person’s improvement becomes everyone’s starting point the day the owner approves it.
A skill is a scary word. It’s nothing more than an SOP.
TenexApril 2026Source What the team works with after the rollout.
The library lists every skill with its owner, how often it ran this week and what it may touch. A change proposed by anyone waits for the owner, who sees what changed and approves it. Approved versions reach the whole team at once.
Next to the library sits the usage standard: which tools may hold customer data, who approves a new connector and when a person reads the work before it leaves the company. Anyone can ask what a skill may do and get an answer that points to the setting and the decision behind it.
What every rollout includes.
Your tools and procedures differ. The setup is built the same way each time.
Access plan
Who gets
Claude Code, who gets Cowork, on which plan and identity provider.Connector list
The approved connectors and what each may read, draft or change.
Data boundaries
What stays out of the assistant, written down and configured.
Skills library
10 to 15 skills from your SOPs, each with an owner and limits.
Review step
How a change to a skill is proposed, checked by its owner and published.
Distribution path
How every person gets the library and its updates.
Context link
The harness connected to your company knowledge.
Usage standard
A short document the team can follow, plus a session per team.
How the team gets set up in three weeks.
Set the boundaries first
With IT and the team leads we decide who gets
Claude Code, who gets Cowork, which connectors are approved and what each may read, draft or change. Data that stays out is written down. Accounts, roles and settings are configured to match, on your plan and your identity provider.Write the first skills from your SOPs
We collect the procedures the team already follows and pick the 10 to 15 that run most often. Each becomes a skill with a named owner, the connectors it may use and the steps it must never take. The owner reviews it against real cases before it is published.
Roll it out team by team
The library goes live with a distribution path, so every person has the same skills and updates arrive without copying files around. The harness links to your company context, such as a <a class="inline-link" href="/company-brain">Company Brain</a>. Each team gets a working session on its own skills, plus the usage standard.
Set up in three weeks.
Kept current every month.
Models change, connectors get added and teams write better versions of their skills. After the rollout we can look after the library each month: review the changes owners approved, retire skills nobody runs and add the next procedures worth sharing.
New skills
The next procedures turned into skills, reviewed by their owners.
Library review
Skills tested again after a model or connector change.
Access check
Connectors and permissions compared with the agreed list.
Usage report
Which skills ran, for whom, and which nobody uses.
What you
receive.
Configured harness
Claude Code and Cowork with permissions and connectors per role.Skills library
10 to 15 reviewed skills, each with a named owner.
Usage standard
What goes in, what stays out and how work gets checked.
Where Team Harness leads.
Each next step has its own service.
100×worker Program
Training on each person’s own work, so the rollout turns into results.
$8,000
Personal AI Setup
A fuller setup for the founders and executives who live in their inbox.
$4,800
Company Brain
Shared company context every skill and session can read.
$19,200
Token Ledger
Usage and spend per person and team, next to what it produced.
$9,600 + $1,600/mo
Before you ask.
Does it have to be Claude?
We usually suggest Claude Code and Cowork, because they run skills and connectors the way this setup needs. If your team has chosen another harness, the library, owners and usage standard are built the same way on that one.
Which SOPs do you need from us?
Whatever the team follows today: procedure documents, onboarding guides, checklists, a good example email. Where nothing is written, we interview the person who does the work and write it with them.
Who owns a skill after you leave?
A named person in your team, usually the one who owned the procedure. They approve changes, and the library shows who that is for every skill.
How do you keep company data safe?
Access, connectors and data boundaries are agreed with your IT lead before anyone gets a login. Each skill lists the connectors it may use and the actions it must never take, and those limits are set in the configuration as well as in the text.
How many people can you set up?
The price covers one team of up to about forty people. Larger rollouts reuse the same library and standard and are scoped per team.