Issue #22 Single-Player to Multiplayer
Using AI to make yourself faster is the easy half; taking it to your whole team is a different and much harder job, and it's the one worth having.
Welcome back to The Customer Continuum. Issue #22. To everyone who reads, shares, and especially those of you who became paid subscribers this month, thank you. You’re the reason this keeps going.
Halfway through my keynote at Demand & Expand yesterday, the room reached for their phones, and not to check email. They were taking photos of the screen.
I had spent the first half of the talk walking through something I’m genuinely proud of, the thirty-person customer marketing function I built at Freshworks. Seven pillars, two years, real numbers behind every one of them. People listened politely, but the notepads mostly stayed closed.
Then I said one sentence. “If I had to build it again today, I wouldn’t build it the same way.” And I shifted the conversation from building a traditional organization to building customer-led growth with a layer of agents doing the operational work.
That’s when the phones came up. I could see it from the stage, a row at a time. They weren’t capturing a slide so much as capturing an idea they wanted to carry back to their own teams on Monday.
The same thing happened across all three talks I gave this week, the same moment landing the same way every time.
The messages afterward all said a version of the same thing: people wanted the slides. One organizer told me the session chat had filled with requests for the deck before I had even left the stage.
What stayed with me longer was a different kind of comment. Person after person came up to tell me they felt validated. They had been quietly building toward this, trusting an instinct they couldn’t quite name, and the talk gave them the language for it. They didn’t walk away thinking they had to start over, they walked away knowing they had been right all along, and that the tools had finally caught up to them.
So this issue is about that moment. Why it landed, and what it means for how you build customer marketing from here.
Single-player is the easy half
Here’s the part of the agent conversation that doesn’t get said enough.
Using AI to make yourself faster is the easy half, and you can do it this afternoon. You take the most repetitive task in your week, hand it to an agent, and get hours back. That’s real and you should do it. But be honest about what it is. It’s a productivity gain, the arithmetic of addition, where one person plus one good tool equals one faster person.
That’s single-player mode, and almost anyone can reach it now. The smaller and nimbler your team, the faster you get there, because you have less to untangle and fewer approvals standing between an idea and a working agent. It’s also why the biggest companies, the ones with the most budget and the most data, are often the slowest to move. They’re carrying a decade of systems that don’t talk to each other and layers of process between an idea and a shipped change.
Addition only ever makes the function you already have run a little quicker; transformation is something else entirely, and it’s the rest of this issue.
Multiplayer is the hard half, and that’s the point
Multiplayer mode is a different thing entirely.
I grew up on video games, and the difference between the two modes was never subtle. I spent years on StarCraft and Warcraft, then World of Warcraft, then Counter-Strike. Single-player was me against the game, at my own pace, and if I made a mistake I was the only one who paid for it. Multiplayer was a different sport. A Counter-Strike round turned on one player being out of position. A World of Warcraft raid put twenty-five people in a room where every one of them had to know their role, because if a few didn’t, the whole group wiped and started over.
That’s the part worth sitting with. Multiplayer was never single-player with extra people added in, it was coordination, roles, communication, and a dozen ways to fail that simply didn’t exist when you played alone. It was harder by an order of magnitude, and anyone who has run a raid knows it.
Customer marketing with agents works the same way. Multiplayer is taking the thing that made you faster and driving it across your team and the people around them. It’s the move from one faster person to a function where the work itself multiplies. And it’s infinitely harder than the single-player win, because the moment other people depend on what you built, you’ve inherited a new set of problems.
You have to maintain it, because a tool a team relies on can’t quietly break. You have to update it as the product changes and the customers change. You have to put governance around it so it does the right thing when no one is watching. You have to build guardrails for the cases you didn’t foresee. And you have to make sure people actually know how to use it, which is its own full job, because a powerful system nobody adopts is just expensive shelfware.
That list is the reason multiplayer is hard, and it’s also the reason multiplayer is worth anything at all.
When you clear all of it, the math stops being addition. One and one stop equalling two and start equalling twenty-five, because the thing you built is now multiplying across every person who touches it. That’s the real line between a productivity gain and a transformation. Productivity is the addition you can feel by Friday; transformation is the multiplication you build over quarters, and it only shows up on the far side of the hard, unglamorous work that most people skip.
The hard part is connection
Here’s what surprised me most in the rooms this week.
The hard part of all of this isn’t the AI getting smart enough, because the models are already good. The real hard part is everything around the model: the change management, the training, and the people who understand the plumbing, how to connect the tool to your data, your systems, and the real context of your customers.
Agents are only as useful as the context they’re given. An agent with no context is a very confident stranger. The work of feeding it the right context and connecting it to the right systems has become serious enough that it now has its own emerging standard, and the name of that standard matters far less than the reason it exists. Context is the hard part, not the intelligence.
So the person who matters most in this next chapter isn’t the fastest individual operator, it’s the strategist who can think in multiplication instead of addition. That’s the person who looks at a new tool and doesn’t ask how it helps them this week, but asks how it becomes something their whole team can run on, and what has to be true for that to work safely.
There’s an old line about power and responsibility, and it belongs in this conversation. The moment you build something a team depends on, you’ve taken on responsibility for what it does, how it fails, and who it touches. That responsibility is the job itself.
One attendee wrote to me afterward with the detail that stuck with me most. She had a 1:1 with her boss right after the session, walked in with the ideas she had just taken from the room, and her boss loved every one of them. That’s the whole point, because the thinking is only worth something if it helps you win the conversation that happens next.
What this means for your career
If you’re a Director of Customer Marketing reading this, here’s the part that matters most.
The old path to VP was a headcount path. You got promoted when your team grew large enough that someone decided the scope deserved the title. The new path is narrower and far more interesting. It belongs to the person who can take a function multiplayer, who can build something a team runs on, govern it, and bring people along without breaking what already works.
That’s harder to point at than a headcount number, and it’s far more valuable, because most people will stop at the single-player win. They will get personally faster and call it a transformation. The leader who earns the seat is the one who did the unglamorous part, the maintenance and the guardrails and the training, and turned a personal productivity gain into something the whole function compounds on.
You don’t need permission to start becoming that person, but rather thinking in multiplication.
How to start
You don’t need budget or permission to begin, just one pillar and one task.
Start with the pillar tied to your company’s top priority right now. If the whole company is focused on net revenue retention, start in lifecycle and adoption. If it’s closing deals faster, start in advocacy. Pick the pillar your CEO is already talking about, because that’s where a small win gets noticed.
Inside that pillar, find the single most repetitive task you do, the one eating an afternoon of your week. That’s your first agent. Build it, measure the hours it gives back, and show your manager what one designed agent did to your week.
That first agent is single-player, and that’s fine, because it’s how you learn. The real career move is what you do next, when you take that one working agent and ask the harder question. What would it take for a teammate to use this too? What has to be documented, governed, and trained before the function can rely on it, rather than treating it as a trick that only works when you run it? The day you start answering those questions is the day you stop being an operator and start becoming an architect.
If you want a map of where this goes, the CLG Flywheel app lays out the full blueprint. You can run the diagnostic on your own function, see where you sit across the seven pillars, and look at the agent designs that map to each one.
One more thing before I go
Someone came up after one of the talks and told me to think bigger about my own career, that I had impressed a lot of people in that room, and then offered to open a few doors for me. I’m sitting with that.
I share it here for one reason. The architect skill isn’t only how you build a function, it’s how you build a reputation. The people who learn to design systems, and who do it in the open where others can see the thinking, get noticed. That’s true for me, and it’s true for you. Build something visible enough and the doors start opening on their own.
What’s next
I want to try something with this newsletter.
Instead of only writing about the architecture, I’m going to build it in the open. I’m going to keep improving the CLG Flywheel app, designing new agents, refining the blueprint, and I’m going to bring you inside the process while I do it.
Call it Build With Me. You’ll see what I’m designing, why I’m designing it that way, what works, what breaks, and the governance and guardrails that make it safe to hand to other people. The goal is that you aren’t just reading about becoming an architect, you’re watching one work in real time, and borrowing whatever is useful for your own function.
That starts in the next few issues, and I think it’s going to be the most useful thing I’ve made here.
— Kevin
P.S. If this issue made you think about one task you could hand to an agent this week, forward it to one person on your team and ask them which task they would pick. The conversation is worth more than the read.