Building an AI-powered marketing team (Part 1)
How to turn your best AI habit into your team's system
This is Part 1 of a 3-part series on building an AI-powered marketing team. First up, I explore the individual trap of AI and how to build the first shared system.
I was recently checking out Supermetrics’ 2026 Marketing Data Report, and it turns only 6% of marketers say they've fully implemented AI across their team. Meanwhile 75% are stuck in what the report calls "performative AI": tools everywhere, real change nowhere. Adoption isn't the problem, but something else is broken.
What I think it is: AI is inherently individual. It runs on one machine, inside one context window, shaped by one person's prompts and one person's judgment about what "good" looks like.
That's a feature when you're the one using it, and genuinely great for personal productivity. But it's a liability the moment you try to turn it into a team capability, because the value never leaves the laptop it was built on.
You might have seen this play out at work. Someone on your team builds a useful AI workflow — maybe it turns raw sales call notes into a competitive intel brief, or drafts first-pass ad copy from a brief in a fraction of the usual time. It’s good and saves them hours a week.
Yet it lives entirely in their head and their prompt history. Nobody else can use it. When they’re out sick or leave the company, the workflow leaves with them, and everyone else goes back to doing it the slow way.
That’s the 75% stuck in performative AI. Lots of individual wins, zero organisational capability.
Why solo workflows don’t scale on their own
It’s not laziness or hoarding. It’s structural.
A workflow that lives in one person’s head has no shared version of the prompt, no shared version of the underlying data, and no owner responsible for keeping it working when the model updates or the data source changes.
Without those three things, “sharing” a workflow means sending a Slack message with a prompt pasted in, which decays the moment the recipient’s context, tools, or data differ even slightly from the original.
The four-part test for what’s worth centralising
Not every individual workflow deserves to become team infrastructure though.
Building shared systems has real overhead someone has to own it, maintain it, and keep it accurate. Before you invest in that, run the workflow through four questions:
Do multiple people need this same thing? If you’re the only one who ever needs this output, keep it personal. Centralising a one-person need is wasted effort.
Is the underlying data shared, not personal? A workflow built on your personal notes app doesn’t generalise. One built on your CRM, your shared drive, or your team’s call recordings does.
Does consistency across the team actually matter here? Some tasks benefit from everyone doing it their own way. Others, like positioning language, competitive claims, brand voice, actively suffer when five people each have their own version.
Is there a maintenance burden worth centralising? If keeping the workflow accurate requires real, ongoing work (updating data sources, adjusting prompts as the model changes), that’s a strong signal it should have one clear owner instead of five people quietly maintaining five broken copies.
If a workflow clears two or more of these, it’s a candidate for becoming shared infrastructure. If it clears zero or one, leave it as a personal tool and move on — not everything needs to scale.
How to actually build the team system
Once you’ve identified a workflow worth centralising, the build is less about the AI and more about the plumbing around it:
Name an owner. Not a committee — one person accountable for the workflow staying accurate and useful. This is the single biggest predictor of whether your shared AI workflow survives six months.
Move the data to a shared source. If the workflow pulls from someone’s personal notes, migrate it to the team’s actual system of record first. The AI layer is only as good as what it’s reading from.
Document the prompt like it’s a process, not a trick. Write down what the workflow does, what inputs it needs, and what a good output looks like. Treat it the way you’d treat any other repeatable process on the team.
Put it where people already work. A brilliant workflow that requires opening a separate tool nobody remembers to use doesn’t scale. Build it into Slack, your CRM, or wherever the team already spends time.
Review and re-test quarterly. Models change, data sources change, and a workflow that was accurate this month can quietly drift by November. Someone — that’s the owner — needs to be checking.
What this looks like in practice
Say someone on your team built a solid workflow for turning social listening data into content angles (if you haven’t seen last week’s issue on that exact process, it’s a good pairing with this one). Individually, it’s great. As a team system, it needs: a shared social listening data source everyone can pull from, one prompt template documented and version-controlled, an owner who checks quarterly that the output still matches what content and sales actually need, and a place it lives that isn’t buried in one person’s saved prompts folder.
That’s the difference between a clever trick and a capability. One disappears when the person who built it moves on. The other compounds.
Reply and tell me: what’s the one AI workflow on your team that’s still trapped on somebody’s laptop?
This is the first part of a three-part series. Part 2 will cover ROI, governance, and measurement — is it safe, and is it working. Part 3 covers adoption: getting the team to actually use what you’ve built.
The AI;DR
Elsewhere in the AIverse
Meta pushes AI into your feed, not just your prompt box. Meta’s Superintelligence Labs shipped three new models: Muse Image, now ranked #3 on Arena’s text-to-image leaderboard, is live inside Meta AI, Instagram Stories, and WhatsApp. Muse Video is teased for a wider release, and Muse Spark 1.1 — a low-cost agentic coding model — landed on Meta’s new Model API. Worth watching: image gen embedded directly into Stories means AI-generated visuals are about to become a native, one-tap option for anyone posting on Meta’s platforms, not just something you export from a separate tool.
Chinese labs keep closing the gap on price, not just performance. Tencent released Hy3, a smaller open-source model that outperforms its size class, and Meituan fully open-sourced LongCat-2.0 — billed as the first trillion-parameter coding model trained without Nvidia GPUs. The trend holds: Chinese labs are matching frontier US performance at a fraction of the cost, which keeps pushing the price of “good enough” AI toward zero.
SpaceXAI (formerly xAI) and Cursor’s first joint model just landed. Grok 4.5 is the company’s smartest model yet and its first release since acquiring Cursor. It’s comparable to leading frontier models and excels at coding, agentic tasks, and office work — it plugs directly into Word, PowerPoint, and Excel. Office-suite integration is the detail to note.