How it's built

The same architecture for every client. Adapted to the systems you already run.

Five layers. Each one replaceable. None of them locks you to a vendor, or to us.

01
The AI system
ClaudeChatGPT EnterpriseMicrosoft Copilot

Subscription in your name, from the vendor. We manage the environment, not the account.

02
The connectors
MCPPrioritySAP B1monday.comMicrosoft 365Google WorkspaceWhatsApp

Official connector when it exists. When it doesn't, we build and maintain it, and it stays yours.

03
The data
Open-source CRMPostgreSQL / SupabasePublic data sources

No CRM? We stand up an open-source one inside your environment that agents read from and write to.

04
The automation
Claude Code + Skillsn8nPower AutomateCron

In a Microsoft shop we work in Microsoft tools. In an open environment, in open source.

05
The controls
RBACHuman approval before writesFull logGuardrails

Every agent runs under its own service account. Every write to a core system passes a human.

Your data stays yours

Processing happens in your environment or the vendor's cloud, under a policy that forbids training on your data. Nothing is stored with us.

You hold the keys

You choose the provider and manage the keys. For Anthropic and for OpenAI alike.

The code transfers to you

At the end of the engagement, the code and data of everything we built are handed over. It's in the contract.

Questions

What we get asked on the first call.

A workshop at a fixed day rate. A retainer in a monthly hours quota, no minimum term. A project with a one-time fee plus monthly maintenance. It usually comes to less than one in-house AI hire's salary, with no recruiting and no dependence on one person. You get the numbers in a written two-page proposal, before we start.

Got a process that's blocking the organization? Let's open it.

30 minutes. No selling, no slides. We map the first step together and check whether there is ROI here.

This is what a Tuesday morning looks like, three months after we start:
  • The procurement manager doesn't type orders. She approves them.
  • The shift manager gets a brief at 6:50, before he walks onto the floor.
  • The IT person answers questions. He is no longer the bottleneck.