The AI Native Organization: How We Set Up and Coordinate

How a team runs as an AI-native organization: a shared Claude Code and MCP tool stack, plus the daily report loop that keeps everyone aligned.

This go-to-market is different: we are running as an AI-native organization. That means everybody is on Claude Code — absolutely everybody — with access to the code base and the tools we use every day. AI is going to accelerate us by coordinating us toward our shared objective, and that only works if everyone is connected and communicating with one another. This article covers the tool setup, how we coordinate day to day, and what your responsibility is in the loop.

The Tool Stack: Everyone on the Same Setup

The first step is unifying the team on the same tools: Claude Code, Slack, Figma, and Jira, with Google Workspace connectable alongside them. We walked Keyshawn through the setup as an example, and the same walkthrough applies to every team member.

Inside Claude Code, running /mcp shows what you are hooked into. Everyone should be connected to the same MCP servers: Gmail so drafts can be managed directly, Context 7 and Code Graph, PostHog, Google Drive, and Sentry for errors. Whatever we need — maybe Mouseflow — everybody needs to be connected. The point is that everyone is on the same information, communicating and moving in the same direction. I will work with each of you individually, and every day we go through tutorials to make sure everybody is comfortable working in Claude Code.

How We Coordinate: Reports, Dailies and Slack

Once everyone is up to speed, it is about practicing as a team. The rhythm is simple: communicate what you are doing, and at the end of the day generate a report of what you did and where you are going next. That report goes into Slack.

Monday morning, a project command scoops up all the reports in the channel, reads them, and generates a custom report tailored to what you are doing. That way everybody on the team knows what everybody else is doing, and we can ask questions — which is expected — before we go into the dailies. You are expected to have your questions ready at the beginning of the meeting, so everyone is prepped and prepared before the daily.

The shared objective here is discovering organic conversions. End-of-day reports about what you did and where you are going let us align on that vision, avoid collisions, and get into better alignment.

We want to use AI to help us coordinate as a team.

Your Responsibility: Read and Write the Reports

This part is important, and I want to be adamant about it: everybody reads the reports and everybody makes a report. Generating yours is just a slash command — it scoops up what you did, you talk through where you are going next, and it posts to the channel.

Two practical notes. First, everybody should be on Whisper Flow; it is just a faster way to work, and if you do not have it, let me know — it is an essential tool. Second, the daily loop: make the report of what you did and where you are going, and in the morning review it, see what everybody else is doing, ask some questions, and then proceed.

What this effort really is, is making sure the team operates as one. Using AI is a new way of working, so we are going to learn from each other and discover our new ways of working and cooperating with one another.

Transcript

Uh, hey, guys. Uh, so this video, um, is going to be about organizing as a team. And, uh, so this, in this organization, everybody's going to be on cloud code. Absolutely. Everybody. Uh, so this is the AI native organization, the AI native setup. Uh, this is the go to market. Um, it's. We're going to be operating differently. Uh, so we want to get everybody on the same page is essentially. So we want, um, Claude code. Everybody's working on cloud code that accesses the code base, um, MCPS to slack, jira, uh, figma, uh, anything that we need. Uh, maybe it's mouse flow. Whatever it is, everybody needs to be connected and communicating with one another. Um, because where AI is really going to accelerate us is, uh, to coordinate us to our shared objective. Um, all right.

All right, so, uh, for the tool setup, um, I, uh, walked through Keyshawn. Uh, we got him set up. We, uh, want to get all the team, uh, kind of unified on, um, the same tools. So that's Claude Code, Slack, Figma, and Jira. We have Google Workspace. We can connect. And so, uh, I'll show you an example in cloud code. Um, uh, you can probably see it here. I'm just gonna, I'm gonna blow it up, uh, make this just a little bigger. Uh, on mcps, when you go slash mcp, we want to make sure that everybody is hooked up into all the same, um, uh, thing. So, you know you have Gmail here, right? We can. And this is like what Saga does too. But this allows us to edit the code base essentially. And they, they have other, um, mcps, uh, here. But so now I've just hooked this up into email. Um, and then we can manage drafts like, you know, this is what we want to be doing. Uh, so there's an example, like I'm hooking up to, uh, MCP server and there's going to be other ones. So, uh, we want everybody on code graph, like context seven. Um, and I, for some reason it's just not letting me see the. Oh, I have to shrink. But there's post hog, right? There's Google Drive. Uh, I should hook it up with Sentry for errors, right? So we got to make sure everybody's on the same information and we're communicating and we're moving in the same direction. So I'm going to work with, uh, each of you, um, and then every day is going to be, um, hey, we're going to go through tutorials, make sure everybody's comfortable with Claude code, uh, and working in it.

So once everybody um, is up to speed there, it's really about practicing as a team, how we coordinate. So basically it's going to be um, we have our, you have our daily. We communicate what we're doing, we generate a report at the end of the day of what we did and where we're going next. So what you did, where we're going next, uh, or where your plan is to go next, that report is going to go into a slack, right? And then Monday morning you, we're going to run a, we're going to have a project command to scoop up all those in the channel, um, and uh, uh, read it and generate you a custom, a uh, custom report to what you're doing. And so, you know, so everybody on the team knows what everybody's doing. Where we're organized, we can ask questions, uh, and that is expected, uh, to be done before we go into the dailies, uh, so we can ask any questions. M. And so you're expected to uh, have your questions ready at the beginning of the meeting. Um, and everybody's going to be prepped, um, and hopefully we can actually generate. Hey, what are people's questions? Right? And people, we can all be prepared before the daily. So that's the idea at the end of the day we talk about what we, what we did and where we're going, right? And so we can align onto the shared vision of getting uh, these conversions happening organically. That's, that's what we're trying to do. We're trying to discover organic conversions, um, and avoid, avoid collisions, um, and get into better alignment. Essentially. We want to use AI to help us coordinate as a team.

So the responsibility is very, uh, important. If you have to do this, generate, uh, this report, we're going to have a. Commands. It's just going to be a slash command. Uh, it'll be able to scoop up what you did. Um, you'll be able to, uh, talk. Oh, everybody should be on whisper flow. It's just a faster way to work. If you don't have whisper flow, uh, let me know. Um, that's an essential tool. So we make the report of what we did, where we're going, right? And then in the morning, we review it, we see what everybody else is doing, right. A quick summary, we ask some questions, uh, and then we proceed. Um, okay, and that should wrap it up. But you know, really what this effort is, is making sure, um, the, the team operates as one. That's, that's what we're doing here. Uh, and we're going to learn from each other, right. Of. Because using AI is a new way of working. And so we're going to discover our new ways of working and, uh, cooperating with one another.

Frequently Asked Questions

Claude Code, Slack, Figma and Jira, with Google Workspace and MCP connections to things like Gmail, Context 7, Code Graph, PostHog, Google Drive and Sentry.


A slash command scoops up what you did and where you plan to go next, and the report is posted into Slack for the team to read.


A project command scoops up all the reports in the Slack channel, reads them, and generates a custom report tailored to what you are doing.


To discover organic conversions, avoid collisions between team members, and stay aligned on the shared objective.

    The AI Native Organization: One Tool Stack, One Daily Loop | SAAGA Solve