Numbers as cleared by the owner. Nothing rounded, nothing added.
01
The situation
A marketing agency with 25 people and one Slack channel per client. Knowledge about each client lived in calls and heads, and every write to the CRM was a manual step.
02
What was built
An operator, named Klaudiusz by the team, that lives in Slack: headless Claude Code with 27 skills, answering in the client channels.
Every write goes through one MCP gateway with 95 tools and an audit trail; nothing touches the CRM without passing that gate.
The brand voice was not a style guide: 2,315 sales-call transcripts were distilled into it.
03
What changed
The team asks the operator in the channel where the client already is. Writes are auditable, so the gate can be trusted with more over time.
04
How it runs
Slack, Claude Code, one MCP gateway, on the agency's accounts. The skills and the gateway are in the agency's repository.
How the pieces connect
The system on one map. Arrows show what feeds what; hover a piece to light its path.
Slack
87 client channels
Where the team and the operator meet.
CC
Headless Claude Code · 27 skills
The operator, with the distilled brand voice.
MCP
Write-gated gateway · 95 tools
One gate for every write, with an audit trail.
CRM
Agency CRM and systems
Reached only through the gateway.
Runs on
Claude
Anthropic
MCP
Typescript
Node.js
Workers
If you want one of these
Three steps. The six-step version, with the brief and the video request, is on the home page.
01
Scoping call
30 min, free
You describe the situation; I ask three questions and propose a shape.
02
Roadmap and architecture
$1,250 deposit
A written plan with a date. The deposit is credited to the first invoice; the documents are yours either way.
03
Build, handoff, operate
date on the roadmap
One engineer builds every layer on your account, documents it, and can keep operating it.
Questions I get about this
Tap a question. The answer comes back like a text.
Scoping calls · most weeks
A written roadmap and an architecture for your system, delivered after the scoping call. If we build together, the full amount comes off the first invoice. If not, the documents are yours to take to anyone.
You do. The repository, the Cloudflare account, the domains and the data sit under your company from day one. I get access, not ownership.
The roadmap gives you a date before you commit to the build. The stack is small and one person builds every layer, so nothing waits in a queue between departments.
Yes, before you send the brief if you need it. Send yours or use mine.
Adcare
WhiteContext
Seecontainerpool