This post was originally published on LinkedIn.

I was asked on a call last week if we have an Al practice at CS2

My answer: yes, but there is more to it than that:

YES: We now have our GTM engineering practice led by Xander living deep in the future of Al in GTM. Claude Code, AI first, production level AI systems, the latest tools, agents, all of it.

BUT: Everyone on our team is fully embracing Al and building the muscle to operate Al natively in their domain of GTM Ops. Our GTM Ops leads, our solutions architecture team, our campaign ops team, analysts, leadership. Not just one person or one team. Everyone. This is a very clear expectation we have set with our team. It's on all of us.

So what does this mean in practice:

(1) Everyone on the team reviewing and challenging how we work, how we manage projects/comms, how we roadmap, and how we think about every core use case we build for clients across GTM Ops.

(2) Collectively working on a maturity model across 60 use cases we handle. And brainstorming, testing, iterating, and documenting how all of these core GTM ops components evolve as you move up AI maturity levels:

Level 1: Al Thought Partner

Level 2: Al Assistant

Level 3: Al Automation

Level 4: Autonomous Al agents.

(3) Weekly sessions with the team to walk through use cases, develop Al first roadmaps for clients, and share what we are learning.

(4) Claude Co-work and Claude Code for everyone on the team to leverage, test, build, and share use cases.

(5) Using Al to speed up shipping/building time. Specific client tasks (like auditing metadata before large builds) that used to take 10+ hours are taking Counterintuitively, figuring out what isn't changing with AI. So much is changing, but so many of the legacy issues our clients need solving are the same. We have to anchor on the objective/pain point, choose the right tool for the job, and build the right solution. It takes truly understanding GTM Ops and AI to know when to leverage AI and when to not.

There is more to it than this but the main principle we are operating by is that the companies that will win aren't just hiring one Al person and checking the box.

They're developing specialized Al expertise to get way ahead of the curve, while also building systems so every single person on the team becomes Al native in their specific domain.

Al isn't a thing that lives in its own silo. If you think that way it would be like having only one person on the team who knows how to use the internet.