The brand brain
Build the foundational documents that teach an AI who you are — voice, positioning, customer, category, and the things you'd never say. Every person leaves with this built, not described.
Back to the front page
AI workshops
AI workshops
for teams
Your team has AI accounts. Your output looks the same as it did last year. That gap is the whole problem, and it isn't a tools problem.
Taking inquiries now for sessions beginning early 2027.
Everybody's using it. Nothing's changed.
Here's what AI adoption actually looks like inside most marketing and product teams. Somebody opens a chat window, types a request, gets back something generic, then spends twenty minutes rewriting it into something that sounds like the brand. Tomorrow, the same thing. The tool never learned anything. Neither did the team.
That's not AI working. That's a very expensive autocomplete, and it's why the enthusiasm curve flattens out about six weeks in.
The teams getting real leverage did one thing differently. They stopped treating AI as a thing you ask and started treating it as a thing you train — on the brand voice, the category, the customer, the competitive set, the way decisions actually get made in that building. Set up once. Useful permanently.
That setup is not technical. It's editorial and strategic, which is exactly why marketing and product people are better at it than engineers, and exactly why nobody has shown them how.
Your team builds it in the room.
Not a lecture with a slide about prompt engineering. Everyone works on your actual brand, your actual category, your actual bottleneck, and leaves with something running.
Turning field signal into an asset
Showroom conversations, dealer complaints, sales call notes, win-loss scraps. The unstructured mess that normally dies in a notebook becomes something the team can query and build on.
Your first working agent
One real piece of recurring work — the weekly report, the launch brief, the competitive scan — automated end to end and handed off before the session ends.
What never to automate
The judgment calls, the taste, the relationships. Knowing where the line sits is the difference between a team that gets faster and a team that gets generic.
- Half or full day
- Half day covers the brand brain and one agent. Full day adds the field-signal system and a second build.
- 8–25
- Small enough that everyone builds. Beyond 25 it becomes a lecture, which defeats the point.
- On site or remote
- In person works better. Remote works, and travels further.
- No prerequisites
- No technical background needed. If your team can write a brief, they can do this.
Who this is for.
A good fit: marketing, product, and brand teams in considered-purchase categories — building products, home goods, durables, fixtures, anything sold through a human channel. Teams with real brand guidelines and a real customer, who are tired of generic output. Leaders who want their people building rather than watching.
Not a good fit: teams already running multiple agents and automations in production. You're past this. Also anyone looking for a keynote with no hands on keyboards — that's a talk, and there's a page for that.
An operator, not an influencer.
Almost everyone selling AI training is selling the tool. I run product marketing for luxury hardware portfolios inside an $11B manufacturer, which means I've built this under the same constraints your team has — legal review, brand governance, a channel that doesn't care about your tech stack, and a P&L that wants results this quarter.
Twenty years across luxury hardware, plumbing fixtures, and outdoor power. A collection launch that came in 240% over projection. A smart lock integration shipped in nine months against an 18–24 month standard. The largest launch in my company's history. A product company I founded and sold.
The AI part is recent. The understanding of how a product organization actually works is not, and that's the part that makes the training stick.
Start a conversation.
Tell me the team, the size, and what isn't working. I'll tell you honestly whether a workshop is the right answer — sometimes it isn't.