VANDAMLet’s talk

VANDAMAgent Onboarding

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.

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

Onboard Iris, the order desk agent.

  1. Gmailorders@atlasco.comread · draft
  2. WhatsApp Business+1 212 555 0148read · reply with approval
  3. Shopify, over MCPorders, stock, customersread
  4. ERP APIsales orders, pricesread · draft order
  5. Google Drive/Policies, /Price listsread
  6. Slack#order-deskpost

Agent

Iris

Role
Order desk
Reports to
Mara Lindqvist, customer service lead
Knows
Price list 2026, returns policy, delivery zones
Hours
Weekdays 7:00 to 19:00
  • Messages to customersMara approves before they go out
  • Refunds and discountsSwitched off
  • Every actionLogged with its source

First task

WhatsApp · Hollis FoodsCan we get 30 cases of the 1 L olive oil by Friday?

  1. Checked stock in Shopify: 112 cases
  2. Checked delivery zone: Brooklyn, Thursday route
  3. Drafted sales order SO-2291 in the ERP

Draft reply · waiting for MaraYes, 30 cases can go out on Thursday’s Brooklyn route. I’ve prepared order SO-2291 for you to confirm.

Your people already brought their own agents.

78%
of AI users bring their own AI tools to work, per the 2024 Work Trend Index.
58%
of workplace Claude use runs through personal accounts, per the data-security vendor Cyberhaven, February 2026.
13/13
frontier models were hijacked at least once in a public red-teaming competition run with NIST’s CAISI, 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 and internal controls explain why those limits matter.

Agent Onboarding builds on your company brain: each agent loads its own slice of it, by role, on day one.

What the IT lead opens each week.

One connection map. Every inbox, number, API and MCP server is listed with its owner, the agents that reach it and the scope each one holds: read, draft or send. Access an agent has not used in a month is flagged for review, and the key dates sit next to each connection.

A new agent starts as a role card written in plain words. Name its manager, its sources and its gates, and each one links to the person or connection behind it. Drafts that need approval go to that manager, and every action the agent takes is logged with its source.

The layer under every agent.

Your sources and agents differ. Each agent runs on the same eight parts.

  • Source inventory

    Every document store, API, MCP server, inbox and number, with the person who owns it.

  • Connections

    Each source connected once, so agents stop running on pasted keys and personal logins.

  • Scopes

    Read, draft and send kept apart on every connection.

  • Identity files

    A role, a manager and working hours for each agent, in files you own.

  • Knowledge slices

    The documents each agent may load, and nothing beyond them.

  • Gates

    Messages to customers and anything that spends money start switched off until a person approves them.

  • Action log

    Every action an agent takes, recorded with the source it used.

  • Access review

    A written monthly record of what each agent reached, which keys were rotated and what was removed.

  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.

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.

The only way to stay safe there is to avoid that lethal trifecta combination entirely.Simon Willison, June 2025

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.