The engagement

A 3-month contract. Full ownership at the end.

I build your marketing AI inside your own stack, train the team until it sticks, then hand over the keys. Staying on is an option, not a requirement.

How it works

Built in your stack, owned by your team.

Three months, fixed scope, one flat engagement — no seats to count and nothing metered. The work is getting your team to a shared marketing brain they fully own.

Schedule a demo →

Want me to stay on past handover? That's a separate, optional retainer — never a lock-in.

1
Month 1

Build in your stack

The agent, its memory, credentials, and billing live in your own Anthropic workspace, alongside your security team.

2
Months 2 to 3

Train until it sticks

1:1 and group sessions, customization to your voice and workflows, adoption in the open — not buried in private DMs.

3
Handover

Your team owns it

Full ownership and maintenance handed over. Your keys, your data, your workspace. No lock-in.

What's included

The whole system, running in your stack.

✦The conversational brain, in Slack, Microsoft Teams and the workspace
✦AEO / GEO — multi-engine sweeps & gap analysis
✦Image & video generation, on-brand
✦Content drafting in your voice
✦Connectors across your full stack
✦Scheduled tasks & proactive briefs
✦Any specific needs — the offering is shaped around your team's

Hands-on, the whole way

  • ✦Onboarding that connects your stack and stands the agent up in week one
  • ✦1:1 and group training until the team actually reaches for it
  • ✦Custom skills and workflows built around how your team already works
  • ✦Direct access to me on Slack for the full engagement

FAQs

A fixed implementation fee for the 3 months, quoted after a discovery call. If you keep me on after, it's a monthly retainer.
You pay Anthropic directly for AI usage on your own account. The agent picks the cheapest model that does each job well, so usage costs stay low. Extra capabilities like video and image generation run on usage-based services, also connected to your own accounts — you see every cost directly.
Because the tool isn't the product — the adoption is. I ran a marketing team and built this for my own team first, so months 2 and 3 are me working inside your Slack with your marketers until it's part of how they work, not another tab. The goal we set together: your whole team using it weekly by day 30.
That's what the 3-month structure is for. You're never locked into something your team isn't using, and everything built stays yours either way.
A discovery session up front, then normal work. The system lives in Slack channels they already use. The training happens on real work, not workshops.
The agent, its memory, all its skills and customizations, and your connector credentials are in your account from day one. The source code gets handed to you at handover. After that, improvements I ship to other customers stop flowing to you unless you take the update subscription.
It runs on its own day to day. For changes and updates, you need either someone mildly technical on your side, or my update subscription, where I keep pushing improvements and you keep owning everything.
No. Your keys, your data, your Anthropic account from day one. Leaving means revoking my access, which takes your admin about five minutes.
In your systems. The AI runs in your own Anthropic workspace under your data terms. Your CRM and analytics stay where they are, connected with credentials stored in your workspace, not mine. Full details in the security overview.
Yes, and they should. You get the security overview up front, source access is available for review, and the whole setup can sit alongside your security team's controls from day one.
Only if you turn that on. Everything starts in draft-and-approve mode. Autonomous publishing is a switch your admin controls, and every action the system takes leaves a receipt in your Slack either way.
Individual accounts make individual work better, and none of it compounds. This is one shared brain with your voice, your data, and your campaign history — the whole team works with it in the open, and it shows you which work produced pipeline.
An agency does the work and leaves with the knowledge. I install a system your team operates, and at the end you own it. The deliverable is capability, not deliverables.
Any tool with an MCP or API can be connected. Common marketing tools are included in setup; unusual ones are a fixed add-on.
Yes, and you should. Your implementation gets its own name, avatar, and personality — it's your team's agent, not a Vibier badge in your Slack.