Charlotte B.

I build AI agents on Claude Code that run your day-to-day operations — email, CRM, reporting, content, admin. Agents with access to your real tools and real data, doing work your team currently does by hand. If your software has an API or an MCP server, I can automate the work you do inside it. That's the whole scope question — not which tools I've used before, but where the manual work is hiding in your process. Most automation stops at a single workflow: a Zap here, a Make scenario there, and six months later nobody remembers how it fits together or who owns it. I build the layer above that — a complete operating system for how your company works, with real engineering underneath, documented so your team owns it. What I build with - A brain — agents that read, decide, and do the work (Claude Code) - A memory — the system knows your clients, your history, what's already been handled (database software) - A switchboard — work starts on its own: new lead, deal moves, first of the month (n8n) - An undo button — every change tracked, anything broken rolled back in a minute, and the whole thing owned by you rather than sitting in a freelancer's account (GitHub) Plus documentation, always. I write down how it works and train your team, so you own something you can maintain with or without me. How I got here I started as a virtual assistant, doing day-to-day operations by hand — inbox, CRM, scheduling, reporting, all the admin that quietly keeps a company running. Then I got tired of doing the same task forty times a week and started automating it. That turned into building systems, and then into building complete operating systems on Claude Code. The useful part is that I've done the work I'm automating. When I map your process I'm not an engineer guessing at what your ops person does all day — I've been that person, and I know which steps look automatable on a diagram but aren't, and which invisible ones are eating the most time. That's usually the difference between an automation people actually use and one that gets quietly abandoned in month three. Day to day I'm now the operations architect for a B2B sales agency, where I own the internal systems the whole team works inside: Clay → n8n → HubSpot lead pipelines, Claude-powered internal tooling, HubSpot rebuilt from the object model up, and the Notion workspace holding it together. How we start: a paid discovery session where I map your current workflow and come back with a written build plan — scope, sequence, and what it costs. You keep the plan whether or not you hire me for the build. Based in northern Italy, working CET, fluent English and Dutch.