The models
we work with.

Most companies rent their AI: they send their work to a lab and get answers back. We build so that everything around the model belongs to you and lives in your systems.

Your context

The documents, decisions and exceptions the agents read, kept as files in your own storage.

Your evals

Tests written with your own experts, so every model has to prove itself on your work.

Your rules

Instructions, permissions and review steps, written down and owned by a named person.

Your connections

Access to your systems through MCP, which works with any model that supports it.

With those four in place, moving to a newer model, or to an open-weight model on your own servers, means running your evals again. Why this matters now

VibeLab, the team behind VANDAM, is a Claude implementation partner, and Hendrik is a Claude Ambassador. Claude is the stack we know best, so for a new build it is usually what we suggest first.

If your company runs on Microsoft 365, Google Workspace or ChatGPT, or has a stack it prefers, we build on that. Agents reach your systems through MCP, an open standard, so a later change of model keeps the connections in place.

1. Your task

   We try representative questions, documents and actions. Your team reviews the result against what a useful answer should contain.

2. Your environment

   We consider the systems you use, access requirements and where your information can be processed.

3. Everyday operation

   We compare response quality, speed and cost for the agreed workload, and document what should be reviewed as the work changes.