CMOs as Builders: I'm a Marketer Who Learned to Build AI Systems. You Can Too.
Post 1 of 8 in the CMOs as Builders series: A step-by-step guide for marketing leaders who are ready to build with AI.
This is the guide I wish I’d had.
Most CMOs I know are smart, curious, and already using AI every day. But there’s a gap between using AI and building with it, and that gap is where your next real competitive advantage lives. This series is a step-by-step primer for technology CMOs who are ready to cross it. No computer science degree required. No prior coding experience assumed. Just a willingness to learn a new way of working that most of your peers haven’t found yet.
You can do this. Let’s go.
Subscribe to get every post in this series delivered to your inbox: kevinkerner.substack.com
The Series: CMOs as Builders
Why CMOs Who Build Will Win (You are here) The case for moving from AI user to AI builder, and why stepping out of the chat window changes everything.
Your First 10 Minutes with Claude Code How to open the terminal, run Claude Code for the first time, and understand what you’re actually looking at.
How to Give Claude Code Its Orders The difference between a prompt and a directive, and how to communicate with Claude Code so it builds what you actually want.
Stop Losing Your Work: Sessions and Context Why Claude forgets everything when you close a session, and the simple habits that make your work carry forward.
Skills, Efficiency and Model Switching Haiku, Sonnet, Opus: what each model is for, when to use which one, and how the wrong choice cost me $75 in a single session.
Beyond the Terminal: MCP, n8n, JSON and the Tools That Connect Everything The infrastructure layer that turns Claude from a smart assistant into the brain of an automated system.
From Terminal to Teammate How to bring your team into the systems you’ve built without losing control of what you’ve created.
The CLAUDE.md Blueprint The one document that ties everything together: your operating manual for building with AI at scale.
What you’re about to understand: why the gap between chatting with AI and building with it is bigger than you think, and why that gap is yours to close.
You’re already using AI. Probably every day. And if you’re honest, you’re pretty good at it. You know how to prompt. You get useful output. Maybe you’ve even built a GPT or a Gem for your team. That’s real progress. But there’s a whole other level underneath the chat window that most CMOs have never seen, and the people who find it are doing things that simply aren’t possible from a chat interface. Not harder things. Different things entirely.
By the end of this post you’ll:
Know exactly what Claude Code can do that chat AI cannot. The difference is not incremental. It is categorical.
Know why stepping out of the chat window makes you a better marketing leader. Not just a faster one.
See what “building” actually looks like in practice. Real systems, real outputs, real time saved.
Feel confident that this is something you can do. Because it is, and I’m going to show you how.
Why this matters for you as a CMO:
The leaders who understand what these tools actually do, not just what they can generate in a chat window, will make better decisions, push their teams further, and build advantages that compound over time. You don’t need to become a developer. You need to understand what’s possible. That alone puts you ahead of most people in your seat.
Time to read: 8 minutes
What you need: Nothing. This is the starting point.
Let me guess where you are right now
You use ChatGPT or Claude daily. You’ve gotten real value out of it. Meeting summaries, briefs, research, copy, evals. It’s made you faster and you know it.
But somewhere in the back of your mind, there’s a quiet doubt. You’ve heard about Claude Code. You’ve seen people talking about building things with AI, not just chatting with it. And part of you is curious. Part of you wonders if it’s real or just hype. And maybe, if you’re being completely honest, part of you thinks that stuff is for developers, not for you.
I’m here to tell you that last part is wrong. And this series is going to prove it.
I’m not a developer. I’m a marketer and a CEO. I built my career on messaging, positioning, demand generation, and leading marketing teams. I did not grow up writing code. And I am now building sophisticated automated systems that run my business. Systems that save real hours, eliminate real costs, and do things I genuinely could not do before.
If I can do it, you can do it. Full stop.
Why I’m the one writing this
I’m not a developer by trade. I know a bit of code and have built repos before, but I’ve never studied it formally. I started my career in tech marketing in 1990, back when marketing meant print ads and maybe emails. I spent the next 25 years doing what most of you have done: leading marketing teams, running agencies, building strategies, and managing the relentless pressure of doing more with less in B2B tech. I know a bit of code. Have built repos before. But really, I’m a noob.
In 2014 I founded Mighty & True, a B2B tech marketing agency based in Austin. I am the CEO and, functionally, the CMO. I run the strategy, the team, the client work, and increasingly, the systems that hold it all together. I also host Tech Marketing Rewired, a podcast where I talk to some of the best marketing leaders in B2B tech about what’s actually working right now.
About three years ago I started moving our business deeper into systems building, automation and now AI (after the great books eMyth and Traction). Not just using it in a chat window, but actually building with it. We built a platform called FlowOS that uses AI and automation to improve the work between our team and our customers.
All along, I taught myself. I made mistakes. Just this month, I ran up a $75 API bill in a single session because I had the wrong model selected. I built systems that didn’t work and rebuilt them until they did. And I came out the other side running a materially different business than the one I had before.
I’m building every day. LaunchPod, my podcast automation system. LinkedIn Content Machines. Solutions Messaging Strategy Automation. SEO, AEO and User Flow analysis. Dashboards for clients managing dozens of brands. Real systems, built by a marketer, running in production today.
I’m writing this series because I genuinely believe any CMO can do what I did. You don’t need a technical background. You need curiosity and a willingness to sit with something uncomfortable for a few hours. The payoff is real. I’ve lived it.
That’s why I’m the one writing this.
Chat AI is a conversation. Claude Code is a construction site.
Here’s the most important thing I can tell you in this first post.
When you use Claude.ai or ChatGPT in a browser, you are having a conversation. You type something, AI responds, you type something else. It’s powerful. It’s useful. And it has a ceiling.
“Chat AI is a conversation. Claude Code is a construction site. One has a ceiling. The other doesn’t.”
That ceiling is real. In a chat window, you can generate content. You can summarize documents. You can think through problems. What you cannot do is build something that runs on its own. You cannot connect your tools together and have them fire automatically. You cannot turn a flat document into a live application. You cannot create a workflow that wakes up every Monday morning, pulls data from three different sources, and delivers a finished report to your inbox before you’ve had your coffee.
For that, you need to step out of the chat window and into the terminal.
The terminal sounds scary. It isn’t. It’s just a different interface, a text-based window where you give your computer direct instructions. Claude Code runs there. And once you’re in it, a completely different class of work becomes possible.
Here’s the simplest way I can put it: the chat window is a conversation with a very smart person. Claude Code in the terminal is that same smart person sitting next to you at a workbench, with access to every tool in the shop, able to actually build things alongside you.
What becomes possible when you step out of the chat window
Let me be specific, because this is where it gets real.
You can connect your tools together. In a chat window, AI can talk to you. In the terminal with Claude Code, AI can talk to your other tools: your Google Drive, your CRM, your project management system, your publishing platforms. It can pull data from one place, process it, and push output somewhere else. Automatically.
You can build workflows that run without you. As mentioned above, I have a system called LaunchPod. When I finish recording a podcast episode, I drop the audio file into a Google Drive folder. That single action triggers a workflow that uploads to YouTube, publishes to Buzzsprout, builds a page in Webflow, generates eight pieces of content via Claude, and schedules everything to post across LinkedIn, X, and Substack through Late.dev. Start to finish, without me touching anything. I cancelled a part-time marketing hire because of it.
That is not possible from a chat window.
You can turn flat documents into applications. Raw survey data becomes a structured executive report. A spreadsheet of brand metrics becomes an interactive dashboard your whole leadership team can use. A list of customer support tickets becomes a synthesized voice-of-customer analysis with themes, quotes, and recommendations. These aren’t just better outputs. They’re different kinds of outputs entirely.
You can sequence and time things. Chat AI responds when you ask it something. Claude Code can be set to run on a schedule: every morning, every Monday, every time a file lands in a folder. Your reporting doesn’t have to wait for someone to remember to run it.
You can create shared infrastructure your whole team uses. This is one I don’t hear talked about enough. When you build in Claude Code, you create files that live in a project folder. Files your whole team can access, update, and build on top of. A CLAUDE.md file (we’ll cover this in depth in Post 8) is essentially an operating manual for how Claude should work within your organization. It’s persistent, collaborative, and updateable. A ChatGPT custom GPT or a Gemini Gem lives in a walled garden. Your team’s Claude Code project files live in infrastructure you own and control. That’s a meaningful difference for any CMO trying to systematize how their team works.
A word on the hype, and why this still matters
I know some of you are skeptical. And honestly, fair enough. There is a lot of hype around AI right now and not all of it is earned.
Here’s my honest take. Claude Code, and agentic AI building in general, is real and it works. I use it every day and it has materially changed how my business operates. Is it perfect? No. Is every use case worth the effort? No. Are there things that are harder than the demos make them look? Yes.
I also think we’re in an intermediary moment. The tools will keep evolving. At some point, the line between chat AI, coding AI, and agents will probably blur in ways that make some of this easier. But that future isn’t here yet. And waiting for it means falling behind the people who are learning now.
The CMOs who understand these tools today, who have actually sat in the terminal and built something, will be the ones who lead their teams most effectively when the next wave hits. You don’t have to build everything yourself. But you do have to understand what’s possible. That understanding is the advantage.
What this series is going to do
Over the next eight posts, I’m going to take you from curious and maybe a little skeptical, to someone who has actually built something. Not a toy. A real system that does real work.
Here’s the path:
Post 2: Claude Code basics. What it is, how to open it, how to actually use it for the first time.
Post 3: How to direct it well. The quality of what you build is directly tied to the quality of how you communicate what you want. We fix that early.
Post 4: Sessions and memory. How to not lose your work when Claude forgets everything at the end of a session.
Post 5: Model selection. Haiku, Sonnet, Opus: each one has a job. Using the wrong model at the wrong time costs real money. One session running the wrong model cost me $75.
Post 6: The connectors. MCP, n8n, JSON: the infrastructure that makes your systems talk to each other.
Post 7: Bringing your team in. How to hand off what you’ve built without losing control of it.
Post 8: CLAUDE.md. The document that becomes the operating manual for everything you build.
By the end, you’ll have the foundation to build systems like LaunchPod. Systems that eliminate real labor costs, move faster than any team, and give you a compounding advantage that most of your competitors aren’t building yet.
You can do this
I want to close this first post with something direct.
The thing holding most CMOs back from this is not intelligence. It is not technical ability. It is the belief that this is someone else’s job, that building is for developers and your job is to direct the people who build.
That belief made sense three years ago. It does not make sense today.
The tools have changed. The barrier to entry has dropped dramatically. And the leaders who cross that barrier, who actually sit down, open the terminal, and build something, come out the other side with a clarity about what AI can do that you simply cannot get from reading about it or watching someone else do it.
You are curious enough to be reading this. That’s the only qualification you need.
Let’s go build something.
Next: Post 2: Your First 10 Minutes with Claude Code. We open the terminal, run the tool, and you see what it actually does.
About the author
Kevin Kerner is the founder and CEO of Mighty & True, a B2B tech marketing agency based in Austin. He has spent 35+ years in technology marketing, leading teams, building agencies, and lately, building AI systems that run his business. He hosts the Tech Marketing Rewired podcast and writes about AI, marketing, and what’s actually working at the intersection of both.
He is not waiting for AI to get easier. He is building now. So can you.
Want the rest of the series?
All eight posts are coming. Each one builds on the last. By the end you will have gone from curious to actually building something real.
Subscribe at kevinkerner.substack.com and every post lands in your inbox the moment it drops. No algorithms. No feed. Just the guide, straight to you.
Excellent starter guide for CMOs joining the builder bandwagon.
Incredible article Kevin! Your insights on your CEO -> BUILDER journey are something other founders and CEOs really should listen to.