# Agent Onboarding by VANDAM: Your data, tools and inboxes connected to every new agent

> We connect your documents, APIs, MCP servers, Gmail and WhatsApp numbers once, and give each agent a role, a manager and limits. A new agent starts work the day you need it.

URL: https://vandam.ai/agent-onboarding  
Contact: hendrik@vibelab.be

# Every system connected once. Every new agent ready on day one.

We connect your documents, APIs, MCP servers, Gmail and WhatsApp numbers once, and give each agent a role, a manager and limits. A new agent starts work the day you need it.

[Discuss the project](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Agent%20Onboarding)

**$9,600 + $1,600/mo** two weeks · then monthly

## Your people already brought their own agents.

- **78%**
  of AI users bring their own AI tools to work, per the 2024 [Work Trend Index](https://www.microsoft.com/en-us/worklab/work-trend-index/ai-at-work-is-here-now-comes-the-hard-part).
- **58%**
  of workplace Claude use runs through personal accounts, per the data-security vendor [Cyberhaven](https://www.cyberhaven.com/blog/sensitive-data-flowing-into-ai-tools), February 2026.
- **13/13**
  frontier models were hijacked at least once in a public red-teaming competition run with [NIST’s CAISI](https://www.nist.gov/blogs/caisi-research-blog/insights-ai-agent-security-large-scale-red-teaming-competition), March 2026.

## Every new agent starts with the same week of setup.

An agent is only as useful as what it can reach. The order desk needs the shared inbox, the WhatsApp number, the shop and the ERP; the finance agent needs invoices, the bank feed and the price lists. Without a plan, each agent gets its own pasted API keys and someone’s personal login, and after the third one nobody can say what reaches what.

We do the setup once, as a layer every agent uses. Each source is connected with its own scopes, and each agent gets an identity file: its role, the person it reports to, the knowledge it may load, its working hours and the gates on anything that sends a message or spends money. Our notes on [what agents can reach](https://vandam.ai/notes/what-your-agents-can-reach) and [internal controls](https://vandam.ai/notes/agents-and-internal-controls) explain why those limits matter.

Agent Onboarding builds on your [company brain](https://vandam.ai/company-brain): each agent loads its own slice of it, by role, on day one.

## From scattered keys to agents with a desk.

1. Map and connect: We list every source, API, MCP server, inbox and number with its owner, then connect each one once, with read, draft and send scopes kept apart. Connection map - Gmail · orders@read, draft
- WhatsApp Business · +32 9read
- Shopify · MCPread
- ERP APIread
- Send to customersoff
2. Give every agent an identity: Each agent gets a role, a manager, a knowledge slice, working hours and gates. Messages to customers and anything that spends money start switched off until a person approves them. Iris · order desk agent - **Manager**
  Mara, customer service
- **Knows**
  Orders, stock, delivery terms
- **Works**
  Mon to Fri, 7:00 to 19:00
- **Can**
  Read orders, draft replies
- **Needs approval**
  Sending, refunds, discounts
3. Keep it current every month: New agents are onboarded on the same layer, keys are rotated, and a monthly access review records what each agent reached and what changed. Access review · October - 2 new agents onboardedFinance, Sales
- Keys rotated14 of 14
- Unused access removedDrive · Iris
- Written review sentto IT lead

## Set up in two weeks. Kept current every month.

Agents get added, people change roles and keys need rotating, so the layer needs regular upkeep. The monthly fee covers that work.

- New agents: New agents onboarded on the same layer, each with a role card, a manager and gates.
- Key rotation: Keys and tokens rotated every month, with the date recorded on each connection.
- Access review: A written review of what each agent reached, what changed and which unused access was removed.
- Check-ins: A monthly session with your IT lead on the review, open requests and the next agents to onboard.

[Discuss the project](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Agent%20Onboarding%20care)

## What you receive.

- Connection map: Every data source, API, MCP server, inbox and number, with what can reach it.
- Agent identities: A role, a manager, a knowledge slice and gates for each agent, in files you own.
- First agents live: Up to three agents onboarded and tested on real work.
- Monthly upkeep: New agents onboarded, keys rotated and a written access review every month.

$9,600 + $1,600/mo

two weeks · then monthly

An indication from past projects. The final price can move a little with the size and complexity of your company, and we agree it in writing before we start.

For operations and IT leads at 30–500 person companies starting to run agents. Useful when every new agent means another week of keys, connectors and access questions.

[hendrik@vibelab.be](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Agent%20Onboarding)

## Where Agent Onboarding leads. Each next step has its own service.

### Company Brain

Comes before: the company knowledge each agent loads on day one.

**$19,200**

### Agent Attack Audit

Red-teams the connections you just opened, before someone else does.

**$6,400**

### Agent Ops

We run the agents after go-live, with the access map kept current.

**$3,200/mo**

### Token Ledger

Spend per agent, team and model, next to what each one produced.

**$9,600 + $1,600/mo**

The only way to stay safe there is to avoid that lethal trifecta combination entirely. (Simon Willison, [June 2025](https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/))

## Before you ask.

### Can an agent send a customer message or spend money on its own?

Not by default. Sending and spending start switched off, and a person approves them before they are turned on. Each agent’s gates are written in its identity file.

### What happens to the keys and logins people already use?

We list them in the mapping step with their owners. Each source is then connected once with its own scopes, so agents no longer run on someone’s personal login.

### How many agents are included?

Up to three agents are onboarded and tested on real work in the first two weeks. New agents after that are onboarded as part of the monthly upkeep.

### What does the monthly access review contain?

Which agents reached which sources, which keys were rotated and what access was removed or changed. It is written down and sent to your IT lead.