Seilschaft › Architecture
As simple as possible, and no simpler.
Four columns, left to right: the people, the agents inside Claude, the connectors, and the systems Bergwärts already pays for. There is no automation platform and no new database. Click any piece to see what it is, why it is there, and who can change it.
__I:wave__ The rope, step by step
- Press "Follow the Roche enquiry"Each hop lights up on the map and plays that agent's note. Nothing here is a slide; it is the same path the agents take in the workspace.
The ladder we climb before writing code.
Every need starts at the top rung. We only step down when the rung above cannot hold it. That keeps the system small enough for Andrea to own.
Where it runs, and what it costs to keep.
Claude Team seats for the five people who use it. Two MCP servers in TypeScript, about 400 lines each, on Azure in Switzerland North so booking and customer data stay in the country. Scheduled agents such as the 06:40 briefing run on the Claude Agent SDK. Secrets live in Azure Key Vault, and nothing holds a payment key.
- Custom code to maintain
- 2small servers
- New databases
- 0uses SharePoint
- AI spend cap
- 300CHF / month
- Data location
- CH+ Anthropic DPA
What we deliberately leave out.
No Make or n8n in the middle
Every hop through an automation platform is one more place where logic hides from Andrea. Claude calls the systems directly through MCP, and the logic lives in skills she can read.
No separate vector database
Knowledge stays in SharePoint, where the team already writes it. Claude searches it through the Microsoft 365 connector, and Projects hold the few documents every agent needs.
No payments, no refunds by an agent
TWINT and the bank are not connected, on purpose. An agent can draft a refund; a person makes it in TrekkSoft.
No custom chat app
People work in Claude, Outlook and Teams, which they already have. Approvals arrive in Outlook and on the phone. The screens in this workspace show what that looks like end to end.