Conversational Operations

from €24,000

Your conversational Operating System, so you can command Claude to work inside your tools.

Deliverable: One conversational interface over the tools you already run, carrying your own logic, owned by your team.
For whom: Founders and operators (CEO, COO, CMO) who want their operations running more efficiently, especially multi-client or multi-project organisations where knowledge management carries its own layer of complexity.
Exit: Built to Leave. No retainer. You leave with a documented system, a proven ROA, and a team that builds its own Skills.

Where it sits

The umbrella OS Architecture service. It runs on its own; AI Strategy, Data Mapping and MarTech Tool Stacking are optional layers, not prerequisites.

When: you have the tools but no AI layer.

How it works

You give Claude one instruction in plain language. Claude is the brain that understands the task, plans the work and answers back, while n8n and Claude’s MCPs are the body that moves inside your tools to read, write and automate. Those tools, from CRM and ERP to mail, drive, Slack, your books and project boards, up to about twenty of them, stay exactly where they are, and so does your data.

What it is

Your company runs about twenty tools, and nobody wants all twenty. Everybody pays for that every day, in context-switching, onboarding and licences that sit half-used. Conversational Operations puts a single interface over the stack you already have: you talk to Claude in plain language, and Claude works inside your tools over n8n and MCP, reading, writing, analysing and building. Your tools stay and your data stays where it is, so you keep the ones your team likes while Claude takes over the ones nobody wants to touch.

Out of the box, Claude knows the tools but not your business. It doesn’t know your processes, your terms or your rules, and that is the gap Skills close: knowledge packages that carry your company logic into every conversation, so Claude speaks your CRM rather than any CRM.

What you get

Shadowing (Phase 0). We get onboarded like new team members, mapping your data, tools and decision logic, and hand back a blueprint plus a prioritised build list that is useful on its own even if nothing follows.
The wiring (Design). Your own server, self-hosted n8n and Claude connected over MCP, with connectors and credential handling for your tools, agent memory, and a governance baseline for who may do what. Available on its own, with Shadowing, as Conversational OS Setup.
Enablement (Operate). Two Skills that carry your company logic, three automations built along your build list, and two workshops: a basics session for everyone and a deep-dive for the builders. Judgment stays human where it should, and we are reachable in Slack or Teams throughout.
Control, in ROA. We baseline today’s effort during Shadowing and Design, then measure the adoption gains after a set period. The target is always an ROA above 2: one hour in the new system replaces more than two hours of manual work, in numbers a board can read.
Documentation throughout. Every stage is documented as a Claude project, so your team can operate, adjust and debug both the system and the server without us.

How it ends

No retainer and no lock-in. You own everything each stage produces and can stop after any stage without losing what came before. When we leave, your build list has more entries than we built and your team knows how to add the rest. That is the point.

Where this sits in the four phases.

Every service runs through the same method: shadow the live operation, design the architecture, operate with your team, then hand over.

Phase 0 This service

Shadowing Blueprint

Diagnose in your live operation. Decision logic, data flows, role boundaries. We watch how the work actually gets decided before we touch anything.

Phase 1 This service

Design Architecture

Channel logic, audience model, KPI framework, MarTech, workflow. The operating system on paper, agreed with your leadership before we build.

Phase 2 This service

Operate Running system

Operate with your team. Forecasting, media buying, automation. Enablement runs in parallel so ownership moves to your people while the system runs.

Phase 3 This service

Control Handover

Attribution, incrementality, business impact. Then the handover cut: documentation, access, and usually the full-time leader we helped you hire.

Not inside

This is not a rebuild. You already have an operating system, so we don’t replace your tools or migrate your data, and we don’t take over ongoing operations, campaign management or workflow-building as a standing service. Where more is genuinely useful, whether that is extra Skills, a migration that pays off or a quarterly system review, it comes as an optional module, scoped per effort.