WEBVTT
00:00:02.080 --> 00:00:07.759
I think the pre-2026 AI story was single player.
00:00:08.480 --> 00:00:25.280
Whether you were an individual small business owner or part of a large enterprise, I think the 2022 to 2025 strategy for AI was unfortunately a lot of copying and pasting and working in silos, but that's not changed.
00:00:25.600 --> 00:00:25.920
Right.
00:00:26.079 --> 00:00:34.000
We are in 2026 where everything is agenc first and headless and also multiplayer.
00:00:34.240 --> 00:00:37.200
So that's what we're going to be tackling on today's show.
00:00:37.359 --> 00:00:47.119
Not just that shift of AI going multiplayer, but specifically how everyone's favorite communication tools, Slack, is actually bringing that all together.
00:00:47.359 --> 00:00:49.600
So I'm excited for today's conversation.
00:00:49.759 --> 00:00:50.560
Hope you are too.
00:00:50.719 --> 00:00:52.159
Welcome to Everyday AI.
00:00:52.240 --> 00:00:53.200
My name is George Bolson.
00:00:53.359 --> 00:00:54.640
If you're new here, we do this every day.
00:00:54.799 --> 00:01:05.040
This is your unedited, unscripted live stream podcast and free business, uh, free newsletter, helping everyday business leaders like you and me not just keep up with what's happening in AI because it doesn't stop.
00:01:05.200 --> 00:01:07.280
But I tell you what matters, what doesn't.
00:01:07.439 --> 00:01:10.000
You take that information to grow your company in your career.
00:01:10.159 --> 00:01:12.400
So if that's what you're trying to do, it starts here.
00:01:12.560 --> 00:01:15.920
But make sure you go to our website at your everydayai.com.
00:01:16.079 --> 00:01:19.920
We're going to be recapping the highlights from today's podcast, and it's going to be a good one.
00:01:20.000 --> 00:01:27.920
We have a great guest in all the other AI news that you need to know to stay ahead and be the smartest person in AI in your company.
00:01:28.239 --> 00:01:29.519
Sounds like a good deal, right?
00:01:29.680 --> 00:01:32.159
All right, but we have a treat for everyone today.
00:01:32.319 --> 00:01:34.319
It's not just going to be me yapping.
00:01:34.480 --> 00:01:40.000
We get to steal some of the secrets from someone building the tools we all get to use.
00:01:40.159 --> 00:01:40.480
All right.
00:01:40.560 --> 00:01:45.280
So I'm excited to bring on to today's show, live stream audience.
00:01:45.359 --> 00:01:49.439
If you could help me welcome to the show, uh, let's bring them on there.
00:01:49.519 --> 00:01:52.480
Ryan Gappin, the chief marketing officer at Slack.
00:01:52.560 --> 00:01:55.120
Ryan, thank you so much for joining the everyday AI show.
00:01:55.439 --> 00:01:56.719
Jordan, thanks so much for having me.
00:01:56.799 --> 00:01:57.680
It's great to be here.
00:01:57.920 --> 00:01:58.319
All right.
00:01:58.400 --> 00:02:02.079
So uh tell everyone a little bit what is your role at Slack, right?
00:02:02.159 --> 00:02:05.359
Everyone knows Slack, everyone knows CMO, but like what does that actually look like?
00:02:05.439 --> 00:02:10.240
Because you guys are shipping so many things, especially on the AI and agentic side.
00:02:10.560 --> 00:02:12.080
Yeah, uh, I appreciate it.
00:02:12.159 --> 00:02:14.879
Uh, I like to describe myself as middle management overhead.
00:02:15.039 --> 00:02:16.319
Um, that's really what I am.
00:02:16.400 --> 00:02:20.560
But I do get the privilege of looking after the Slack business and the marketing side.
00:02:20.639 --> 00:02:27.360
I have I also get to look after small meaning business here at Salesforce, uh, as well as like what something we call a digital growth systems team.
00:02:27.439 --> 00:02:35.120
But you know, it's Slack, it's really about how do we take and transform uh organizations and kind of get them ready for this moment.
00:02:35.280 --> 00:02:49.759
Um, it sounds cliche, but everyone is racing as hard as they can, and many are struggling with what's going on with just the pace of change, the innovation, you know, the the AI and agent buzzword drinking game continues, and like everyone's trying to figure out how they navigate it.
00:02:49.919 --> 00:02:54.479
Uh, and and Slack's become an incredibly important tool uh for many organizations to do just that.
00:02:54.560 --> 00:02:56.639
So that's where I'm spending a lot of my time these days.
00:02:56.879 --> 00:03:17.439
Yeah, walk us through uh, you know, I kind of uh previewed it, but it seems like, you know, so much of AI's strategy, you know, especially in the earlier years of the online chatbot, was really just about how individuals can bring, you know, their bests together, and then somehow you have to duck tape it all together.
00:03:17.599 --> 00:03:34.800
Uh, you know, first of all, tell us like what the heck is Slackbot for those of our you know audience who haven't used it or maybe they haven't heard, and then what's Slackbot doing to try to turn the player from a single player game into a multiplayer agentic collaboration?
00:03:35.120 --> 00:03:35.280
Yeah.
00:03:35.439 --> 00:03:38.240
So so there's there's a bunch there that's important to unpack.
00:03:38.319 --> 00:03:45.039
So I think, you know, first and foremost, uh, I'll kind of let me touch on the multiplayer piece and then I'll kind of get into Slackbot a little bit.
00:03:45.199 --> 00:03:52.879
You know, there's this interesting thing that's been happening that we've all experienced, like the this explosion of intelligence tools that are now at our fingertips.
00:03:53.120 --> 00:04:00.319
All of us have had our Checha GP moments, had our Claude Cowork and Claude Code moments, and just like been blown away what these things can go do.
00:04:00.639 --> 00:04:07.680
And you know, organizations and enterprises are sprinting, in some cases, spending unbelievable amounts of money to deploy these tools.
00:04:07.919 --> 00:04:25.279
But what's not happening is we're not seeing this throughput to employee productivity and the return of that investment in terms of the outputs of the business, you know, customer success, better revenue, you know, improved margins, like those impacts of like employee productivity aren't translating through the system.
00:04:25.360 --> 00:04:37.040
So there's like this like dissonance right now of like unbelievable great intelligence, but yet it's not showing up on one of the companies' most important resources, which is their people and the productivity of their people.
00:04:37.199 --> 00:04:43.759
And the reason for that is because work has always been a multiplayer sport, like work happens in the conversation.
00:04:43.920 --> 00:04:55.040
You know, a good idea is not nearly good enough in terms of it until it gets matured and maturated and debated and then built and built and built in the open in the collaboration, those ideas don't come to fruition.
00:04:55.120 --> 00:04:57.040
And so work has always been in the conversation.
00:04:57.199 --> 00:05:07.519
And so, what needs to happen is all this unbelievable intelligence needs to come to the humans, and it needs to come where the humans are working and collaborating, and it needs to come in a way that feels unbelievably accessible.
00:05:07.680 --> 00:05:19.519
And so, what Slack is really having this incredible moment right now is you know, it's always been for many companies this beloved collaboration tool, but it's rapidly turning into this critical component to companies' AI stack.
00:05:19.680 --> 00:05:30.000
You know, we like to say it's it's the 2% of your AI spend that unlocks the value from the other 98% because it's bringing AI into your humans and it's allowing your teams to work and collaborate together.
00:05:30.240 --> 00:05:41.839
And then, you know, to do that really successfully, you're gonna have all these incredible applications inside of Slack, whether it be from Salesforce or from third parties like Box or Atlassian or Propic, OpenAI, Perplexity, Linear, the list goes on and on.
00:05:42.000 --> 00:05:46.399
It's an open platform, but you know, how does an employee navigate all that?
00:05:46.639 --> 00:05:55.040
You know, how does an employee go through and get the value from all these enterprise systems, get the value from all that conversation, get the value from all these agents?
00:05:55.199 --> 00:05:59.839
You know, in the fullness of time, which may be like six months, who knows?
00:06:00.079 --> 00:06:04.720
Most companies are gonna have more agents than they're gonna have employees.
00:06:05.120 --> 00:06:08.560
But the problem is how do employees know what all those agents do?
00:06:08.800 --> 00:06:10.480
Like, how do they know what their skills are?
00:06:10.639 --> 00:06:11.759
How do they know where to find them?
00:06:11.839 --> 00:06:23.600
And like in some cases, we're making the same problem that we've had in the past worse by just spreading all this stuff to, you know, another system, another tab, another place to go to, another agent to go learn, another skill to go develop.
00:06:23.759 --> 00:06:28.959
And there's some poor employees just sitting in the middle of this thing, like, I don't know, I've got all this intelligence, I don't know how to use all this stuff.
00:06:29.120 --> 00:06:30.639
So this is where Slackbot comes in.
00:06:30.720 --> 00:06:35.759
So Slackbot is this unbelievably powerful tool inside of Salesforce that we built at Slack.
00:06:36.000 --> 00:06:40.000
It is the fastest growing feature in Salesforce history by far.
00:06:40.319 --> 00:06:53.759
Uh, and it's because it's an AI personal system for me that knows me, it knows my team, it knows my context, it has access to the permissions that I have inside of Slack, and it has and it's connected to all my enterprise systems.
00:06:53.839 --> 00:06:55.360
So it's trusted from day one.
00:06:55.519 --> 00:06:57.120
And I don't have to learn a thing.
00:06:57.360 --> 00:07:16.959
I just ask Slack, and Slackbot can go and query all those systems, whether it be an inbox, whether it be 15 different agents, whether it be uh my CRM, and it can not only read those things, it can write to those things, and I can just have a conversation and I can get work done across two dozen systems without ever knowing those systems exist in the back end.
00:07:17.199 --> 00:07:20.560
Uh it's unbelievably transformative for how we work.
00:07:20.720 --> 00:07:30.879
Um, it's unbelievably transformative for employees because now all this intelligence is actually accessible because we gave this simple, delightful personal assistant called Slackbot that allows you to get access to it.
00:07:30.959 --> 00:07:34.720
That was a bit of a long-winded answer, but no, yeah, a lot to unpack there.
00:07:34.800 --> 00:07:38.800
But I think Ryan, you brought up like a really important point, right?
00:07:38.879 --> 00:07:48.399
When you talked about, you know, not only does it bring in all of these enterprise systems, right, which your standard AI, you know, chat bots, they do that as well.
00:07:48.560 --> 00:07:51.279
But you said something important there that I want to unpack.
00:07:51.439 --> 00:07:54.959
You said it knows me and it knows my team, right?
00:07:55.040 --> 00:08:08.879
And I think that our our longtime listeners here will know I have this weird thing when you know I talk about the models themselves going from you know these these transformer next token predictors to models that can reason and go over logic.
00:08:09.040 --> 00:08:12.399
And I talk about this thing called first party reasoning data, right?
00:08:12.480 --> 00:08:21.040
Uh, because everyone can, you know, hook up your Salesforce and your email and all these other things, but it's how your team works, it's how they make decisions.
00:08:21.120 --> 00:08:26.959
And, you know, come to think of it, it's like, wait, so much of that just literally lives and it breathes inside of Slack.
00:08:27.120 --> 00:08:41.039
So walk me through uh kind of the the the reasoning or the rationale and how those Slack conversations that sometimes people think are just you know noise, that actually might be the gold that's hiding beneath the surface.
00:08:41.279 --> 00:08:43.039
It's it's massively the gold.
00:08:43.200 --> 00:08:53.200
Uh in the AI world, unstructured data is the is the context that fuels relevance for any AI system.
00:08:53.600 --> 00:09:01.679
And the most valuable unstructured data by far is the richness of years and years and years of organizational context.
00:09:01.840 --> 00:09:05.840
And one of the reasons why Slack is such a powerful tool is because it's open architecture.
00:09:06.000 --> 00:09:11.840
It allows for these public channels, these private channels where people are working and building in the open.
00:09:12.080 --> 00:09:16.320
They're not locked behind an inbox, they're not locked behind a you know, a simple chat message.
00:09:16.639 --> 00:09:22.720
You have organizational context in the open that's living and breathing, that honestly has always been valuable.
00:09:22.799 --> 00:09:25.840
But you know, once it kind of happened, it's largely been inaccessible.
00:09:25.919 --> 00:09:30.559
Because, you know, are you really going to go back in time to a message or a thread from three years ago?
00:09:30.799 --> 00:09:32.960
But now it is access accessible.
00:09:33.120 --> 00:09:34.000
And now it's there.
00:09:34.080 --> 00:09:41.679
And so, you know, I'll just give you an example of you know, I have hundreds and hundreds and hundreds of channels that I'm included in Slack.
00:09:41.919 --> 00:09:42.559
Do I read all of them?
00:09:42.720 --> 00:09:43.360
Heck no.
00:09:43.519 --> 00:09:44.799
Do I monitor all of them?
00:09:44.960 --> 00:09:45.840
Heck no.
00:09:46.240 --> 00:09:58.240
But what I can do is I can have a Slackbot skill that I have run every morning and it says, you know, Slackbot, go through and look at all the areas that my team are working on right now.
00:09:58.399 --> 00:10:03.519
I want you to give me a prioritized list for areas they may be struggling or need my help or maybe stuck.
00:10:03.679 --> 00:10:08.799
I want you to give me an update of where do you see my team making great progress on our stated goals?
00:10:08.960 --> 00:10:16.559
And then please help me understand what are the areas that I should probably have as my top focus areas for today and for this week based on what you're seeing.
00:10:16.879 --> 00:10:24.879
Now, simple prompt, but imagine like what would we require to get those answers like pre-Slack bot.
00:10:25.120 --> 00:10:27.039
I'd have to go maybe call a staff meeting.
00:10:27.120 --> 00:10:31.600
I might have to make, you know, a dozen different Slack messages or heaven forbid an email, dear Lord.
00:10:32.320 --> 00:10:36.000
You know, I might have to call a meeting and get everyone in a room and kind of, all right, what's you working on?
00:10:36.080 --> 00:10:36.799
What are we working on?
00:10:37.279 --> 00:10:40.799
But the reality is Slack is looking at all these channels that I'm not looking at.
00:10:40.960 --> 00:10:44.879
It's looking at all these conversations today, tomorrow, in the past, et cetera.
00:10:45.039 --> 00:10:48.399
And it's able to know when I say my team, it doesn't say who's your team.
00:10:48.480 --> 00:10:50.240
It knows my team because it knows me.
00:10:50.399 --> 00:10:52.639
It knows the people I'm working with, it knows what I'm talking about.
00:10:52.799 --> 00:10:55.759
When I say my goals, it doesn't say, okay, great, tell me your goals.
00:10:55.919 --> 00:11:01.519
It knows my goals because those are published in a document that I put in Slack that it's accessible via Google Drive.
00:11:01.679 --> 00:11:04.480
And it can read those and that and ration over those.
00:11:04.559 --> 00:11:13.440
Uh, and when I say look at all the full actions, it can look into the systems of like my calendar, it can look into the systems of record, like Salesforce, and then it can pull all that.
00:11:13.519 --> 00:11:15.120
And so I get one simple prompt.
00:11:15.200 --> 00:11:21.600
I get this unbelievably rich answer back that gives me insights of like, hey, your team has been over here debating this topic.
00:11:21.679 --> 00:11:25.200
They could really use your help, and you have no clue that's even going on.
00:11:25.360 --> 00:11:28.320
This thing's coming up, and you really need to spend some time on it.
00:11:28.480 --> 00:11:32.080
And here are the five areas that your team's made some incredible progress on your goals.
00:11:32.240 --> 00:11:38.559
And it's like, boom, in like two minutes, I'm like the best equipped manager I've ever been.
00:11:38.720 --> 00:11:44.480
Um, all because I've got Slackbot that's working on my half across all these systems, all in a conversational prompt.
00:11:44.639 --> 00:11:45.519
It's crazy.
00:11:45.679 --> 00:11:58.159
Uh, and it it that's like a very simple use case uh of how these things show up and why the the power of conversation and connecting you know the structured data and unstructured data becomes unbelievably powerful in this head.
00:11:58.720 --> 00:12:01.600
Yeah, you kind of gave that example, right?
00:12:01.679 --> 00:12:09.840
Of having these hundreds of channels and even channels that you like one human cannot go in and monitor hundreds of channels, right?
00:12:09.919 --> 00:12:11.519
So I think that that's a great use case.
00:12:11.679 --> 00:12:14.480
But maybe can you walk me back a little bit?
00:12:14.639 --> 00:12:20.080
You know, maybe when you were, you know, testing out Slackbot internally before it was released to the public.
00:12:20.320 --> 00:12:29.039
Did you have like one of those aha moments where you were like, wait, this is gonna change how we do multiplayer work?
00:12:29.120 --> 00:12:36.080
And if so, uh, you know, what can our listeners learn from maybe that example of you know dog fooding this internally?
00:12:36.399 --> 00:12:36.639
Sure.
00:12:36.720 --> 00:12:37.039
Yeah.
00:12:37.120 --> 00:12:48.320
I mean, one of the one of the things we we talk about a lot, uh, and we see it and do it inside of Slack, but it's also a pattern that plays out at all native AI companies right now.
00:12:48.559 --> 00:12:54.559
And I think very quickly every leading company is gonna want to follow suit, which is what I call building in the open.
00:12:54.799 --> 00:13:12.080
Um, you know, if you look at like the origin stories of ChatGBT, if you look at the origin stories of computer from perplexity, anthropic, um, claude, and the the even announcement from a couple weeks ago with tagging Claude, all those in Slack bots, but all those are byproducts of building in the open.
00:13:12.320 --> 00:13:20.960
You're in Slack, you're working on this project, you're iterating with a group of people who are writing code, developing, building new pull requests.
00:13:21.039 --> 00:13:25.759
They're going through, they're they're they're saying this is working, this isn't working, I'm trying this, et cetera.
00:13:26.000 --> 00:13:33.919
And you iterate, you iterate, you're iterate, and you go through and you collectively go and build this thing at unbelievable speed.
00:13:34.080 --> 00:13:36.080
Um, that's how we built Slackbot.
00:13:36.159 --> 00:13:39.279
You know, Slackbot started as a small team that was working on something.
00:13:39.440 --> 00:13:42.159
There's a channel, everyone's in there, we're testing it out, et cetera.
00:13:42.240 --> 00:13:48.480
We have a thing called Slackbot Unbaked, which is like the, you know, where the team's like, hey, I just built this feature, everyone go try it out.
00:13:48.559 --> 00:13:50.639
And we all bang on it and say, ah, this is working.
00:13:50.720 --> 00:13:51.679
This is great, this is amazing.
00:13:51.759 --> 00:13:52.960
This totally didn't work.
00:13:53.200 --> 00:14:00.639
Um, and it's unbelievable the collaborative power when you build in the open and the speed that happens there.
00:14:00.799 --> 00:14:12.559
And something super powerful is happening right now, which is it used to be that building was the domain of product and engineering, but now builders are everybody in your company.
00:14:12.720 --> 00:14:16.720
And everybody at your company now needs a platform to build in the open.
00:14:16.960 --> 00:14:18.799
If you're in marketing, you need to build in the open.
00:14:18.879 --> 00:14:35.279
If you're in finance, if you're in HR, everyone's a builder and you have these incredibly powerful tools, not just Slackbot, but tools from Vercel, uh, tools from Anthropic, tools from OpenAI, Linear, Kurz, all these tools are deployed in Slack because that's where the humans are working, that's where the collaboration is coming together.
00:14:35.440 --> 00:14:39.440
And then you can use these tools to go and build and create incredible stuff.
00:14:39.679 --> 00:14:47.919
Um, and so that that kind of moment for us, when I saw the pace and the power of building in the open, how quickly we could iterate by doing that.
00:14:48.080 --> 00:14:53.440
Uh, and then I, you know, we're seeing that play out through all of these unbelievable um AI companies out there.
00:14:53.679 --> 00:14:56.960
It, you know, it dawned on me as like this is how everyone's going to be working in the future.
00:14:57.120 --> 00:15:00.879
We're just a little bit ahead of the curve, but everyone's a builder and everyone needs a building platform.
00:15:01.440 --> 00:15:03.279
Yeah, Brian, that's that's a great point.
00:15:03.360 --> 00:15:11.759
And I think it was Zachier, um, you know, last week, the CEO there, who was talking about that exact same thing, right?
00:15:11.919 --> 00:15:16.320
Building in public and and maybe doing less in DMs, right?
00:15:16.399 --> 00:15:25.039
Uh, for the reason that you can share uh more of that decision making with your team and make AI more um, you know, multiplayer.
00:15:25.200 --> 00:15:47.120
So, you know, I'm wondering, you know, with the uh advent of Slackbot and you shared, you know, some of those obvious wins, does it change how you communicate, whether for the better or worse, you know, knowing that essentially what you're putting into Slash is probably gonna help you and your teammates in, you know, three months or three years.
00:15:47.279 --> 00:15:52.240
How does that change even how you use Slack or how you communicate something?
00:15:52.960 --> 00:16:08.879
Yeah, um, you know, I'll and just building on your opening point, you know, there's um I'm gonna, I'm not gonna get it perfectly right, but the the Shopify CEO Toby, he made it, they built an incredible agent called River and they deployed it and they said it's only allowed to be deployed to channels in Slack.
00:16:09.200 --> 00:16:29.279
And the reason why, and I'm not gonna get his quote exactly right, but he basically said, hey, if you're not like using AI and building and learning in the open, like you're you're fundamentally in this kind of closed loop system where like an individual is working and getting better, maybe they're getting productive, but the larger team, the larger group, the larger system, that learning is not compounding.
00:16:29.360 --> 00:16:31.120
And so, like, you have to be in the open.
00:16:31.200 --> 00:16:42.320
And that's why, you know, I think companies that still run out of the inbox are going to be in trouble in this in this era, because we do need to go to move at the speed that the market demands right now.
00:16:42.559 --> 00:16:45.200
Learning has to compound and has to compound quickly.
00:16:45.440 --> 00:16:54.080
And so that's why, you know, having you know a tool like Slack where like you are working in channels and you are doing that in the open, it's really simple things.
00:16:54.159 --> 00:16:58.720
Of course, there's always a time and a place for an individual message or something that's more private.
00:16:58.799 --> 00:17:04.400
And like, you know, of course, we have all the affordances for that inside of Slack with private messages and private channels, et cetera.
00:17:04.720 --> 00:17:17.200
But the simple truth is when I have a question for an individual, there are nine times out of 10, there are eight other people on the team that are going to benefit from seeing that back and forth and learning from that.
00:17:17.359 --> 00:17:27.039
Uh, and when you know, someone gives a piece of product feedback on uh a feature and there's a response of I, the whole team being able to see and understand that benefits.
00:17:27.279 --> 00:17:37.359
So, you know, this idea of learning and building in the open and allowing your AI to see and learn from that means the AI becomes exponentially more valuable.
00:17:37.519 --> 00:17:40.319
It becomes trusted because I know it knows me.
00:17:40.400 --> 00:17:43.519
And it when it talks and it's giving data, I know it's coming from the net.
00:17:43.759 --> 00:17:45.440
I can see the sources in Slack.
00:17:45.599 --> 00:17:55.039
So, you know, that is why you know, things like Slack bottom and like this incredibly fast adopt feature because it it creates that trust where you're not coming into this with like, oh, what do I share?
00:17:55.119 --> 00:17:56.160
What do I not share?
00:17:56.400 --> 00:17:59.920
Like it's this is my Slack and it's it's in my permission base.
00:18:00.079 --> 00:18:02.079
It's in my I trust everything in there.
00:18:02.240 --> 00:18:05.039
And then I know that AI is permissioned against that.
00:18:05.119 --> 00:18:08.319
And so I can just operate as I would like a trusted teammate.
00:18:08.640 --> 00:18:09.759
Uh, and that's how it feels.
00:18:09.920 --> 00:18:14.880
It feels like I have a trusted teammate uh who I you know trust just as much as I would any other team.
00:18:15.200 --> 00:18:15.440
Yeah.
00:18:15.680 --> 00:18:25.119
And you know, we've been talking a lot so far working inside Slack, which I think is super valuable because so many teams, you know, run their day-to-day inside of Slack.
00:18:25.200 --> 00:18:51.279
Um, but there's been a recent shift, which you alluded to, with you know, things like Claude Tag, uh, right, which integrates with Slack, you know, uh mono context protocol, you know, the recent Slack MCP, and you know, the Slack parent company Saleshorse has been a leader and one of the first big SaaS companies to say, hey, we're gonna really focus on headless uh in the future.
00:18:51.440 --> 00:19:05.279
So can you explain kind of this shift from maybe you know, quote unquote pushing people to go into Slack and use Slack versus should we be just using the data from Slack in these other platforms?
00:19:05.599 --> 00:19:11.359
How do you begin to unpack that in kind of this more recent shift toward just working hidden?
00:19:12.400 --> 00:19:14.240
Yeah, so it's a great question.
00:19:14.400 --> 00:19:26.160
The you know let's just start with Salesforce and and and uh the announcement that we made last week, which was you know, anything Salesforce can do, you can now do through Slackbot.
00:19:26.319 --> 00:19:27.279
It's like it's the simplest.
00:19:27.359 --> 00:19:40.400
So we Slackbot's an MCP client, it connects to our Salesforce MCP servers, and so so Slackbot can not just read, but it can write and can take actions and go uh and and work directly with your CRM, which is unbelievably powerful.
00:19:40.480 --> 00:19:43.039
And I'll we'll start with kind of a just a simple frame.
00:19:43.279 --> 00:19:49.039
If you back up and you say, wow, many companies use Salesforce, sales service marketing.
00:19:49.200 --> 00:19:55.680
But the reality is, even as successful as Salesforce event, only a small percentage of the employees actually ever see Salesforce, right?
00:19:55.920 --> 00:19:59.200
The sellers see it, the service team may see it, maybe the managers see it.
00:19:59.279 --> 00:20:01.839
If you're on the marketing side and you're using marketing, you'll see it.
00:20:02.000 --> 00:20:06.160
But like the product and engineering teams don't, you know, maybe marketing teams don't see SalesCloud.
00:20:06.240 --> 00:20:08.400
Like they don't use that system.
00:20:08.480 --> 00:20:10.640
It's uh, but it's an unbelievably important system.
00:20:10.720 --> 00:20:12.960
It's like the customer record, it's the source of truth.
00:20:13.119 --> 00:20:16.480
It's it's where you're seeing what's going on with your customers' service issues.
00:20:16.640 --> 00:20:21.759
Like this is unbelievably valuable data, but it's not really accessible to most employees.
00:20:22.079 --> 00:20:30.000
So, what happens when you can take a tool like Slackbot and you can safely, in a permissioned way, have that connected up to the Salesforce data?
00:20:30.079 --> 00:20:33.440
Well, it turns out that data becomes infinitely more valuable.
00:20:33.599 --> 00:20:42.400
That resource, that system of record becomes infinitely more usable because now, whether in marketing, you may never have seen Salesforce, you may not even know what it looks like.
00:20:42.559 --> 00:20:46.079
But now I can ask a simple question of like, hey, I'm prepping for this IBM meeting.
00:20:46.240 --> 00:20:47.839
What's been going on with the IBM account?
00:20:47.920 --> 00:20:48.640
What's the latest issues?
00:20:48.720 --> 00:20:50.559
Are they having any service issues right now?
00:20:50.720 --> 00:20:59.680
Um, tell me about the last five meetings we've had with them, what went well, what didn't go well, and what do you think are the things that they're going to be most uh excited to hear about from?
00:21:00.160 --> 00:21:05.200
Now, Slackbot can go talk to the service, you know, our Agent Force Service uh cloud.
00:21:05.279 --> 00:21:17.759
It can go talk to our Agent Force Sales Cloud, it can go look into the IBM account channel again that's in lay open and go and see all the discourse of how the team's been working through it and bring me back this incredibly rich answer and insights.
00:21:17.920 --> 00:21:20.319
And not only that, I can then take action based on that.
00:21:20.400 --> 00:21:23.440
I can say, oh, that opportunity record, I actually just met with them.
00:21:23.519 --> 00:21:25.359
The opportunity is actually 250,000.
00:21:25.440 --> 00:21:26.400
It's not 200,000.
00:21:26.480 --> 00:21:27.359
Update that opportunity.
00:21:27.440 --> 00:21:29.519
And I can just do this by talking to Slackbot.
00:21:29.680 --> 00:21:34.400
And you know, I'll just I'll give you, I was reading a stat um just last week, it's kind of blew me away.
00:21:34.480 --> 00:21:42.480
There was 1.8 million Slackbot messages that were sent uh inside of sales by Salesforce employees uh just last week.
00:21:42.880 --> 00:21:49.039
750,000 of those were talking to and writing to Salesforce.
00:21:50.240 --> 00:21:59.759
So, like, think about that, like in terms of and and these these people Slackbot will tell you, hey, it's clearing Salesforce, but these people didn't have to say go talk to Salesforce or go talk to Agent Force.
00:22:00.079 --> 00:22:00.240
Sales.
00:22:00.400 --> 00:22:02.000
They just said, what's going on with this account?
00:22:02.079 --> 00:22:03.680
Or I want to go in this opportunity.
00:22:03.920 --> 00:22:12.240
So this headless strategy is like the exponential unlock for the value of your CRM data.
00:22:12.480 --> 00:22:29.119
And when you can bring it into the conversational interface of Slack, when you can bring it into where the humans are working, and when you can make it super accessible with a tool like SlackBot, that, you know, to cite a design principle that we have at Slack, you know, you know, we think we say all the time, like when we build software, we don't want you to have to think.
00:22:29.200 --> 00:22:30.319
Like, don't make me think.
00:22:30.480 --> 00:22:31.680
It should just work.
00:22:31.839 --> 00:22:35.599
Um, and when you can couple those things, it's a really, really powerful moment.
00:22:35.759 --> 00:22:38.400
And of course, it extends to our entire ecosystem.
00:22:38.480 --> 00:22:41.839
So you're talking about anthropic, you know, Slack's an open platform.
00:22:41.920 --> 00:22:50.400
So whether you're Box at Lassian, whether you're Vercel or Linear, all these organizations are building their AI into Slack.
00:22:50.480 --> 00:22:54.480
Um, because that open ecosystem, we know the enterprise doesn't stop at just Salesforce.
00:22:54.559 --> 00:22:59.599
It's got Microsoft, it's got Google, you've got all these other enterprise systems, got your own custom applications.
00:22:59.759 --> 00:23:01.839
All those need to be working connected in.
00:23:02.000 --> 00:23:07.599
Um, and the power of those systems becomes exponential when it's easy to access with this conversation.
00:23:08.240 --> 00:23:20.559
So, you know, obviously, as builders of the technology, you know, I assume that many within the Slack organization have been working with an agentic first mindset for quite a while.
00:23:20.720 --> 00:23:32.240
But for the rest of our audience, you know, for our maybe non-technical business leaders who, you know, their organizations run inside of Slack, how should they be changing their mindset right now?
00:23:32.400 --> 00:23:32.559
Right.
00:23:32.720 --> 00:23:39.519
Like, how does someone become an orchestrator of work, you know, versus just a doer of tasks?
00:23:39.759 --> 00:23:46.000
And, you know, how does that change with things like Slack bot or the you know Slack MCP?
00:23:46.559 --> 00:23:48.400
Yeah, I mean, there's a couple fundamental trends.
00:23:48.480 --> 00:24:01.680
Like one, uh, you know, we do need to kind of recognize that uh this agent and agent capabilities are are kind of reaching this like explosion inside the enterprise.
00:24:01.920 --> 00:24:07.119
And you have to empower your teams and your individuals to be able to manage that din.
00:24:07.680 --> 00:24:13.039
And I say din not to diminish these tools or the value of them, they're incredible.
00:24:13.279 --> 00:24:18.160
But you know, at the at the end of the day, there's still an employee who's trying to get their job done.
00:24:18.480 --> 00:24:25.119
And we're asking them to leverage and take advantage of these tools and technologies, but it's overwhelming in some cases.
00:24:25.279 --> 00:24:26.480
In some cases, they're training.
00:24:26.559 --> 00:24:40.319
So the first thing you need to do is you realize you've got to have a platform that you can go through and have a deployment place for all this technology and intelligence that your employees can use and understand and make it accessible.
00:24:40.480 --> 00:24:43.759
So you need to have those agents connected into something like Slack.
00:24:43.839 --> 00:24:48.000
Um, Slack's really the only platform right now that allows you to do this at scale.
00:24:48.400 --> 00:24:53.599
And then allow your humans to be able to work with those agents by a simple interface like Slackbot.
00:24:53.759 --> 00:24:58.319
So, to your point, we can get to the place where everyone can start to feel like a builder.
00:24:58.480 --> 00:25:04.400
Um, so you know, I have more agents available to me inside of Salesforce and Slack than I even know about.
00:25:04.559 --> 00:25:12.079
Um, but when I, you know, think about getting a task done, I'm deploying probably four or five different agents in any given Slackbot query that I don't even know about.
00:25:12.160 --> 00:25:15.039
And that that allows me to work without friction.
00:25:15.200 --> 00:25:29.599
Um, and it allows me to tap a lot of these capabilities without, you know, under underlying kind of the you know patterns and practices of the sins of enterprise software, which has been, you know, we have a thousand enterprise applications inside of our enterprise.
00:25:29.759 --> 00:25:35.920
I'm switching between 10 to 12 of them every single day, and I'm wasting 40 to 50% of my day on like the work of work.
00:25:36.240 --> 00:25:38.000
And I think that's the the real thing.
00:25:38.160 --> 00:25:43.359
The the piece that many people aren't talking about right now is you know, go back to something I started with.
00:25:43.599 --> 00:25:47.440
Employee productivity like sounds kind of like buzzword nonsense.
00:25:47.519 --> 00:25:50.880
And sometimes it's like, oh yeah, what does it really mean?
00:25:51.119 --> 00:25:57.440
Like most companies spend most of their money on their people, like 30 to 60 percent of companies spend that, you know, their capital on people.
00:25:57.599 --> 00:26:04.960
And if you can make your people like three to four X more productive and get the work of work off their plate, that's like a hundred percent revenue growth.
00:26:05.200 --> 00:26:09.039
There's not a lot of hundred percent revenue growth ideas just floating around the boardroom.
00:26:09.200 --> 00:26:14.559
Uh and so this is a moment where everyone kind of needs to reevaluate how your oh how your company works.
00:26:14.640 --> 00:26:16.799
And that's why I made the comment earlier about the inbox.
00:26:16.960 --> 00:26:18.559
The inbox is death for this.
00:26:18.720 --> 00:26:24.319
Like if you if your company employees are spending a good percentage of their work time in the inbox, you're in trouble.
00:26:24.480 --> 00:26:28.160
Um, you've got to you've got to shift that because you you will not be able to keep.
00:26:28.880 --> 00:26:31.039
Yeah, that's that's a great uh call out there.
00:26:31.119 --> 00:26:44.559
But you know, Ryan, uh, we've talked about a lot on today's episode, uh, you know, from what's new in Slackbot, headless revolution to changing your mindset and the value of those back and forth conversations.
00:26:44.880 --> 00:27:06.240
But you know, what's the one most important thing business leaders can do today as they're grappling with maybe transitioning, you know, their AI strategy from being a collection of individual AI contributors to that true multiplayer agencorchation, what's the one most important move they can make?
00:27:08.480 --> 00:27:23.599
Well, you know, I I don't know if I can always sim it down to one, but if your company like Box, Box is saying, hey, our sales team out of their working time, their non-selling time, they're gonna spend 80% of it all in Slack.
00:27:24.240 --> 00:27:30.240
And those the Slack is going to be the connective tissue between all the enterprise systems that they have, including Salesforce.
00:27:30.400 --> 00:27:45.920
You know, if your engine, who gets like 800,000 customer inquiries, they're saying the way we're gonna manage the the the scale of our business and having one connected truth is by bringing it all into a connected system like Slack.
00:27:46.079 --> 00:27:57.359
So the the the one thing I would encourage is like you have to really take a cue from how, you know, a perplexity or an open AI or Enthropic, how they build.
00:27:57.440 --> 00:28:01.039
There's a reason why those companies say Slack is their work operating system.
00:28:01.200 --> 00:28:03.839
You know, Enthropic says Slack is our work operating system.
00:28:03.920 --> 00:28:05.279
There's a reason why they say that.
00:28:05.440 --> 00:28:08.160
They run the company from this tool.
00:28:08.480 --> 00:28:18.799
And, you know, if the one thing I would encourage everyone to do is like this is the moment to re-evaluate how your organization works and how you build and how you enable everyone to become a builder.
00:28:19.039 --> 00:28:28.799
And it's not about one tool or one AI, it's about all the tools and all the AI and being able to unleash those in a way that is sensible and manageable for your employees.
00:28:28.960 --> 00:28:33.039
Uh, and that's kind of why Slack and Slackbot are kind of having this incredible moment right now.
00:28:33.119 --> 00:28:39.920
It's almost a renaissance in many ways, because we're seeing this explosion of AI coming into Slack.
00:28:40.079 --> 00:28:45.759
We're seeing an explosion of AI utilization in Slack because of Slackbots making it simple and approachable.
00:28:45.920 --> 00:28:48.559
Um, so it's time to rethink work, is the short answer.
00:28:48.799 --> 00:28:49.279
I love that.
00:28:49.359 --> 00:28:50.480
And what a great way to end.
00:28:50.640 --> 00:28:51.359
Rethink work.
00:28:51.440 --> 00:28:53.279
It's what we're doing every single day.
00:28:53.359 --> 00:28:59.359
And hey, at least for today, Ryan, you helped us uh give us the the good insights on how to do that.
00:28:59.519 --> 00:29:04.079
So uh thank you so much for taking time out of your day to join the show, Ryan.
00:29:05.039 --> 00:29:07.359
Jordan, I really appreciate you and uh I hope it was helpful.
00:29:07.519 --> 00:29:08.720
Look forward to chatting again soon.
00:29:08.880 --> 00:29:11.039
All right, and hey, if you missed anything, don't worry.
00:29:11.119 --> 00:29:15.359
We're gonna be recapping all those golden nuggets, Ryan just dropped in today's newsletter.
00:29:15.440 --> 00:29:18.799
So if you haven't already, please make sure you go to your everydayai.com.
00:29:18.960 --> 00:29:21.119
Sign up for the free daily free daily newsletter.
00:29:21.200 --> 00:29:21.759
Thanks for tuning in.
00:29:21.920 --> 00:29:24.640
Hope to see you back tomorrow and every day for more everyday AI.
00:29:24.720 --> 00:29:25.599
Thanks, y'all.
00:00:02.080 --> 00:00:07.759
I think the pre-2026 AI story was single player.
00:00:08.480 --> 00:00:25.280
Whether you were an individual small business owner or part of a large enterprise, I think the 2022 to 2025 strategy for AI was unfortunately a lot of copying and pasting and working in silos, but that's not changed.
00:00:25.600 --> 00:00:25.920
Right.
00:00:26.079 --> 00:00:34.000
We are in 2026 where everything is agenc first and headless and also multiplayer.
00:00:34.240 --> 00:00:37.200
So that's what we're going to be tackling on today's show.
00:00:37.359 --> 00:00:47.119
Not just that shift of AI going multiplayer, but specifically how everyone's favorite communication tools, Slack, is actually bringing that all together.
00:00:47.359 --> 00:00:49.600
So I'm excited for today's conversation.
00:00:49.759 --> 00:00:50.560
Hope you are too.
00:00:50.719 --> 00:00:52.159
Welcome to Everyday AI.
00:00:52.240 --> 00:00:53.200
My name is George Bolson.
00:00:53.359 --> 00:00:54.640
If you're new here, we do this every day.
00:00:54.799 --> 00:01:05.040
This is your unedited, unscripted live stream podcast and free business, uh, free newsletter, helping everyday business leaders like you and me not just keep up with what's happening in AI because it doesn't stop.
00:01:05.200 --> 00:01:07.280
But I tell you what matters, what doesn't.
00:01:07.439 --> 00:01:10.000
You take that information to grow your company in your career.
00:01:10.159 --> 00:01:12.400
So if that's what you're trying to do, it starts here.
00:01:12.560 --> 00:01:15.920
But make sure you go to our website at your everydayai.com.
00:01:16.079 --> 00:01:19.920
We're going to be recapping the highlights from today's podcast, and it's going to be a good one.
00:01:20.000 --> 00:01:27.920
We have a great guest in all the other AI news that you need to know to stay ahead and be the smartest person in AI in your company.
00:01:28.239 --> 00:01:29.519
Sounds like a good deal, right?
00:01:29.680 --> 00:01:32.159
All right, but we have a treat for everyone today.
00:01:32.319 --> 00:01:34.319
It's not just going to be me yapping.
00:01:34.480 --> 00:01:40.000
We get to steal some of the secrets from someone building the tools we all get to use.
00:01:40.159 --> 00:01:40.480
All right.
00:01:40.560 --> 00:01:45.280
So I'm excited to bring on to today's show, live stream audience.
00:01:45.359 --> 00:01:49.439
If you could help me welcome to the show, uh, let's bring them on there.
00:01:49.519 --> 00:01:52.480
Ryan Gappin, the chief marketing officer at Slack.
00:01:52.560 --> 00:01:55.120
Ryan, thank you so much for joining the everyday AI show.
00:01:55.439 --> 00:01:56.719
Jordan, thanks so much for having me.
00:01:56.799 --> 00:01:57.680
It's great to be here.
00:01:57.920 --> 00:01:58.319
All right.
00:01:58.400 --> 00:02:02.079
So uh tell everyone a little bit what is your role at Slack, right?
00:02:02.159 --> 00:02:05.359
Everyone knows Slack, everyone knows CMO, but like what does that actually look like?
00:02:05.439 --> 00:02:10.240
Because you guys are shipping so many things, especially on the AI and agentic side.
00:02:10.560 --> 00:02:12.080
Yeah, uh, I appreciate it.
00:02:12.159 --> 00:02:14.879
Uh, I like to describe myself as middle management overhead.
00:02:15.039 --> 00:02:16.319
Um, that's really what I am.
00:02:16.400 --> 00:02:20.560
But I do get the privilege of looking after the Slack business and the marketing side.
00:02:20.639 --> 00:02:27.360
I have I also get to look after small meaning business here at Salesforce, uh, as well as like what something we call a digital growth systems team.
00:02:27.439 --> 00:02:35.120
But you know, it's Slack, it's really about how do we take and transform uh organizations and kind of get them ready for this moment.
00:02:35.280 --> 00:02:49.759
Um, it sounds cliche, but everyone is racing as hard as they can, and many are struggling with what's going on with just the pace of change, the innovation, you know, the the AI and agent buzzword drinking game continues, and like everyone's trying to figure out how they navigate it.
00:02:49.919 --> 00:02:54.479
Uh, and and Slack's become an incredibly important tool uh for many organizations to do just that.
00:02:54.560 --> 00:02:56.639
So that's where I'm spending a lot of my time these days.
00:02:56.879 --> 00:03:17.439
Yeah, walk us through uh, you know, I kind of uh previewed it, but it seems like, you know, so much of AI's strategy, you know, especially in the earlier years of the online chatbot, was really just about how individuals can bring, you know, their bests together, and then somehow you have to duck tape it all together.
00:03:17.599 --> 00:03:34.800
Uh, you know, first of all, tell us like what the heck is Slackbot for those of our you know audience who haven't used it or maybe they haven't heard, and then what's Slackbot doing to try to turn the player from a single player game into a multiplayer agentic collaboration?
00:03:35.120 --> 00:03:35.280
Yeah.
00:03:35.439 --> 00:03:38.240
So so there's there's a bunch there that's important to unpack.
00:03:38.319 --> 00:03:45.039
So I think, you know, first and foremost, uh, I'll kind of let me touch on the multiplayer piece and then I'll kind of get into Slackbot a little bit.
00:03:45.199 --> 00:03:52.879
You know, there's this interesting thing that's been happening that we've all experienced, like the this explosion of intelligence tools that are now at our fingertips.
00:03:53.120 --> 00:04:00.319
All of us have had our Checha GP moments, had our Claude Cowork and Claude Code moments, and just like been blown away what these things can go do.
00:04:00.639 --> 00:04:07.680
And you know, organizations and enterprises are sprinting, in some cases, spending unbelievable amounts of money to deploy these tools.
00:04:07.919 --> 00:04:25.279
But what's not happening is we're not seeing this throughput to employee productivity and the return of that investment in terms of the outputs of the business, you know, customer success, better revenue, you know, improved margins, like those impacts of like employee productivity aren't translating through the system.
00:04:25.360 --> 00:04:37.040
So there's like this like dissonance right now of like unbelievable great intelligence, but yet it's not showing up on one of the companies' most important resources, which is their people and the productivity of their people.
00:04:37.199 --> 00:04:43.759
And the reason for that is because work has always been a multiplayer sport, like work happens in the conversation.
00:04:43.920 --> 00:04:55.040
You know, a good idea is not nearly good enough in terms of it until it gets matured and maturated and debated and then built and built and built in the open in the collaboration, those ideas don't come to fruition.
00:04:55.120 --> 00:04:57.040
And so work has always been in the conversation.
00:04:57.199 --> 00:05:07.519
And so, what needs to happen is all this unbelievable intelligence needs to come to the humans, and it needs to come where the humans are working and collaborating, and it needs to come in a way that feels unbelievably accessible.
00:05:07.680 --> 00:05:19.519
And so, what Slack is really having this incredible moment right now is you know, it's always been for many companies this beloved collaboration tool, but it's rapidly turning into this critical component to companies' AI stack.
00:05:19.680 --> 00:05:30.000
You know, we like to say it's it's the 2% of your AI spend that unlocks the value from the other 98% because it's bringing AI into your humans and it's allowing your teams to work and collaborate together.
00:05:30.240 --> 00:05:41.839
And then, you know, to do that really successfully, you're gonna have all these incredible applications inside of Slack, whether it be from Salesforce or from third parties like Box or Atlassian or Propic, OpenAI, Perplexity, Linear, the list goes on and on.
00:05:42.000 --> 00:05:46.399
It's an open platform, but you know, how does an employee navigate all that?
00:05:46.639 --> 00:05:55.040
You know, how does an employee go through and get the value from all these enterprise systems, get the value from all that conversation, get the value from all these agents?
00:05:55.199 --> 00:05:59.839
You know, in the fullness of time, which may be like six months, who knows?
00:06:00.079 --> 00:06:04.720
Most companies are gonna have more agents than they're gonna have employees.
00:06:05.120 --> 00:06:08.560
But the problem is how do employees know what all those agents do?
00:06:08.800 --> 00:06:10.480
Like, how do they know what their skills are?
00:06:10.639 --> 00:06:11.759
How do they know where to find them?
00:06:11.839 --> 00:06:23.600
And like in some cases, we're making the same problem that we've had in the past worse by just spreading all this stuff to, you know, another system, another tab, another place to go to, another agent to go learn, another skill to go develop.
00:06:23.759 --> 00:06:28.959
And there's some poor employees just sitting in the middle of this thing, like, I don't know, I've got all this intelligence, I don't know how to use all this stuff.
00:06:29.120 --> 00:06:30.639
So this is where Slackbot comes in.
00:06:30.720 --> 00:06:35.759
So Slackbot is this unbelievably powerful tool inside of Salesforce that we built at Slack.
00:06:36.000 --> 00:06:40.000
It is the fastest growing feature in Salesforce history by far.
00:06:40.319 --> 00:06:53.759
Uh, and it's because it's an AI personal system for me that knows me, it knows my team, it knows my context, it has access to the permissions that I have inside of Slack, and it has and it's connected to all my enterprise systems.
00:06:53.839 --> 00:06:55.360
So it's trusted from day one.
00:06:55.519 --> 00:06:57.120
And I don't have to learn a thing.
00:06:57.360 --> 00:07:16.959
I just ask Slack, and Slackbot can go and query all those systems, whether it be an inbox, whether it be 15 different agents, whether it be uh my CRM, and it can not only read those things, it can write to those things, and I can just have a conversation and I can get work done across two dozen systems without ever knowing those systems exist in the back end.
00:07:17.199 --> 00:07:20.560
Uh it's unbelievably transformative for how we work.
00:07:20.720 --> 00:07:30.879
Um, it's unbelievably transformative for employees because now all this intelligence is actually accessible because we gave this simple, delightful personal assistant called Slackbot that allows you to get access to it.
00:07:30.959 --> 00:07:34.720
That was a bit of a long-winded answer, but no, yeah, a lot to unpack there.
00:07:34.800 --> 00:07:38.800
But I think Ryan, you brought up like a really important point, right?
00:07:38.879 --> 00:07:48.399
When you talked about, you know, not only does it bring in all of these enterprise systems, right, which your standard AI, you know, chat bots, they do that as well.
00:07:48.560 --> 00:07:51.279
But you said something important there that I want to unpack.
00:07:51.439 --> 00:07:54.959
You said it knows me and it knows my team, right?
00:07:55.040 --> 00:08:08.879
And I think that our our longtime listeners here will know I have this weird thing when you know I talk about the models themselves going from you know these these transformer next token predictors to models that can reason and go over logic.
00:08:09.040 --> 00:08:12.399
And I talk about this thing called first party reasoning data, right?
00:08:12.480 --> 00:08:21.040
Uh, because everyone can, you know, hook up your Salesforce and your email and all these other things, but it's how your team works, it's how they make decisions.
00:08:21.120 --> 00:08:26.959
And, you know, come to think of it, it's like, wait, so much of that just literally lives and it breathes inside of Slack.
00:08:27.120 --> 00:08:41.039
So walk me through uh kind of the the the reasoning or the rationale and how those Slack conversations that sometimes people think are just you know noise, that actually might be the gold that's hiding beneath the surface.
00:08:41.279 --> 00:08:43.039
It's it's massively the gold.
00:08:43.200 --> 00:08:53.200
Uh in the AI world, unstructured data is the is the context that fuels relevance for any AI system.
00:08:53.600 --> 00:09:01.679
And the most valuable unstructured data by far is the richness of years and years and years of organizational context.
00:09:01.840 --> 00:09:05.840
And one of the reasons why Slack is such a powerful tool is because it's open architecture.
00:09:06.000 --> 00:09:11.840
It allows for these public channels, these private channels where people are working and building in the open.
00:09:12.080 --> 00:09:16.320
They're not locked behind an inbox, they're not locked behind a you know, a simple chat message.
00:09:16.639 --> 00:09:22.720
You have organizational context in the open that's living and breathing, that honestly has always been valuable.
00:09:22.799 --> 00:09:25.840
But you know, once it kind of happened, it's largely been inaccessible.
00:09:25.919 --> 00:09:30.559
Because, you know, are you really going to go back in time to a message or a thread from three years ago?
00:09:30.799 --> 00:09:32.960
But now it is access accessible.
00:09:33.120 --> 00:09:34.000
And now it's there.
00:09:34.080 --> 00:09:41.679
And so, you know, I'll just give you an example of you know, I have hundreds and hundreds and hundreds of channels that I'm included in Slack.
00:09:41.919 --> 00:09:42.559
Do I read all of them?
00:09:42.720 --> 00:09:43.360
Heck no.
00:09:43.519 --> 00:09:44.799
Do I monitor all of them?
00:09:44.960 --> 00:09:45.840
Heck no.
00:09:46.240 --> 00:09:58.240
But what I can do is I can have a Slackbot skill that I have run every morning and it says, you know, Slackbot, go through and look at all the areas that my team are working on right now.
00:09:58.399 --> 00:10:03.519
I want you to give me a prioritized list for areas they may be struggling or need my help or maybe stuck.
00:10:03.679 --> 00:10:08.799
I want you to give me an update of where do you see my team making great progress on our stated goals?
00:10:08.960 --> 00:10:16.559
And then please help me understand what are the areas that I should probably have as my top focus areas for today and for this week based on what you're seeing.
00:10:16.879 --> 00:10:24.879
Now, simple prompt, but imagine like what would we require to get those answers like pre-Slack bot.
00:10:25.120 --> 00:10:27.039
I'd have to go maybe call a staff meeting.
00:10:27.120 --> 00:10:31.600
I might have to make, you know, a dozen different Slack messages or heaven forbid an email, dear Lord.
00:10:32.320 --> 00:10:36.000
You know, I might have to call a meeting and get everyone in a room and kind of, all right, what's you working on?
00:10:36.080 --> 00:10:36.799
What are we working on?
00:10:37.279 --> 00:10:40.799
But the reality is Slack is looking at all these channels that I'm not looking at.
00:10:40.960 --> 00:10:44.879
It's looking at all these conversations today, tomorrow, in the past, et cetera.
00:10:45.039 --> 00:10:48.399
And it's able to know when I say my team, it doesn't say who's your team.
00:10:48.480 --> 00:10:50.240
It knows my team because it knows me.
00:10:50.399 --> 00:10:52.639
It knows the people I'm working with, it knows what I'm talking about.
00:10:52.799 --> 00:10:55.759
When I say my goals, it doesn't say, okay, great, tell me your goals.
00:10:55.919 --> 00:11:01.519
It knows my goals because those are published in a document that I put in Slack that it's accessible via Google Drive.
00:11:01.679 --> 00:11:04.480
And it can read those and that and ration over those.
00:11:04.559 --> 00:11:13.440
Uh, and when I say look at all the full actions, it can look into the systems of like my calendar, it can look into the systems of record, like Salesforce, and then it can pull all that.
00:11:13.519 --> 00:11:15.120
And so I get one simple prompt.
00:11:15.200 --> 00:11:21.600
I get this unbelievably rich answer back that gives me insights of like, hey, your team has been over here debating this topic.
00:11:21.679 --> 00:11:25.200
They could really use your help, and you have no clue that's even going on.
00:11:25.360 --> 00:11:28.320
This thing's coming up, and you really need to spend some time on it.
00:11:28.480 --> 00:11:32.080
And here are the five areas that your team's made some incredible progress on your goals.
00:11:32.240 --> 00:11:38.559
And it's like, boom, in like two minutes, I'm like the best equipped manager I've ever been.
00:11:38.720 --> 00:11:44.480
Um, all because I've got Slackbot that's working on my half across all these systems, all in a conversational prompt.
00:11:44.639 --> 00:11:45.519
It's crazy.
00:11:45.679 --> 00:11:58.159
Uh, and it it that's like a very simple use case uh of how these things show up and why the the power of conversation and connecting you know the structured data and unstructured data becomes unbelievably powerful in this head.
00:11:58.720 --> 00:12:01.600
Yeah, you kind of gave that example, right?
00:12:01.679 --> 00:12:09.840
Of having these hundreds of channels and even channels that you like one human cannot go in and monitor hundreds of channels, right?
00:12:09.919 --> 00:12:11.519
So I think that that's a great use case.
00:12:11.679 --> 00:12:14.480
But maybe can you walk me back a little bit?
00:12:14.639 --> 00:12:20.080
You know, maybe when you were, you know, testing out Slackbot internally before it was released to the public.
00:12:20.320 --> 00:12:29.039
Did you have like one of those aha moments where you were like, wait, this is gonna change how we do multiplayer work?
00:12:29.120 --> 00:12:36.080
And if so, uh, you know, what can our listeners learn from maybe that example of you know dog fooding this internally?
00:12:36.399 --> 00:12:36.639
Sure.
00:12:36.720 --> 00:12:37.039
Yeah.
00:12:37.120 --> 00:12:48.320
I mean, one of the one of the things we we talk about a lot, uh, and we see it and do it inside of Slack, but it's also a pattern that plays out at all native AI companies right now.
00:12:48.559 --> 00:12:54.559
And I think very quickly every leading company is gonna want to follow suit, which is what I call building in the open.
00:12:54.799 --> 00:13:12.080
Um, you know, if you look at like the origin stories of ChatGBT, if you look at the origin stories of computer from perplexity, anthropic, um, claude, and the the even announcement from a couple weeks ago with tagging Claude, all those in Slack bots, but all those are byproducts of building in the open.
00:13:12.320 --> 00:13:20.960
You're in Slack, you're working on this project, you're iterating with a group of people who are writing code, developing, building new pull requests.
00:13:21.039 --> 00:13:25.759
They're going through, they're they're they're saying this is working, this isn't working, I'm trying this, et cetera.
00:13:26.000 --> 00:13:33.919
And you iterate, you iterate, you're iterate, and you go through and you collectively go and build this thing at unbelievable speed.
00:13:34.080 --> 00:13:36.080
Um, that's how we built Slackbot.
00:13:36.159 --> 00:13:39.279
You know, Slackbot started as a small team that was working on something.
00:13:39.440 --> 00:13:42.159
There's a channel, everyone's in there, we're testing it out, et cetera.
00:13:42.240 --> 00:13:48.480
We have a thing called Slackbot Unbaked, which is like the, you know, where the team's like, hey, I just built this feature, everyone go try it out.
00:13:48.559 --> 00:13:50.639
And we all bang on it and say, ah, this is working.
00:13:50.720 --> 00:13:51.679
This is great, this is amazing.
00:13:51.759 --> 00:13:52.960
This totally didn't work.
00:13:53.200 --> 00:14:00.639
Um, and it's unbelievable the collaborative power when you build in the open and the speed that happens there.
00:14:00.799 --> 00:14:12.559
And something super powerful is happening right now, which is it used to be that building was the domain of product and engineering, but now builders are everybody in your company.
00:14:12.720 --> 00:14:16.720
And everybody at your company now needs a platform to build in the open.
00:14:16.960 --> 00:14:18.799
If you're in marketing, you need to build in the open.
00:14:18.879 --> 00:14:35.279
If you're in finance, if you're in HR, everyone's a builder and you have these incredibly powerful tools, not just Slackbot, but tools from Vercel, uh, tools from Anthropic, tools from OpenAI, Linear, Kurz, all these tools are deployed in Slack because that's where the humans are working, that's where the collaboration is coming together.
00:14:35.440 --> 00:14:39.440
And then you can use these tools to go and build and create incredible stuff.
00:14:39.679 --> 00:14:47.919
Um, and so that that kind of moment for us, when I saw the pace and the power of building in the open, how quickly we could iterate by doing that.
00:14:48.080 --> 00:14:53.440
Uh, and then I, you know, we're seeing that play out through all of these unbelievable um AI companies out there.
00:14:53.679 --> 00:14:56.960
It, you know, it dawned on me as like this is how everyone's going to be working in the future.
00:14:57.120 --> 00:15:00.879
We're just a little bit ahead of the curve, but everyone's a builder and everyone needs a building platform.
00:15:01.440 --> 00:15:03.279
Yeah, Brian, that's that's a great point.
00:15:03.360 --> 00:15:11.759
And I think it was Zachier, um, you know, last week, the CEO there, who was talking about that exact same thing, right?
00:15:11.919 --> 00:15:16.320
Building in public and and maybe doing less in DMs, right?
00:15:16.399 --> 00:15:25.039
Uh, for the reason that you can share uh more of that decision making with your team and make AI more um, you know, multiplayer.
00:15:25.200 --> 00:15:47.120
So, you know, I'm wondering, you know, with the uh advent of Slackbot and you shared, you know, some of those obvious wins, does it change how you communicate, whether for the better or worse, you know, knowing that essentially what you're putting into Slash is probably gonna help you and your teammates in, you know, three months or three years.
00:15:47.279 --> 00:15:52.240
How does that change even how you use Slack or how you communicate something?
00:15:52.960 --> 00:16:08.879
Yeah, um, you know, I'll and just building on your opening point, you know, there's um I'm gonna, I'm not gonna get it perfectly right, but the the Shopify CEO Toby, he made it, they built an incredible agent called River and they deployed it and they said it's only allowed to be deployed to channels in Slack.
00:16:09.200 --> 00:16:29.279
And the reason why, and I'm not gonna get his quote exactly right, but he basically said, hey, if you're not like using AI and building and learning in the open, like you're you're fundamentally in this kind of closed loop system where like an individual is working and getting better, maybe they're getting productive, but the larger team, the larger group, the larger system, that learning is not compounding.
00:16:29.360 --> 00:16:31.120
And so, like, you have to be in the open.
00:16:31.200 --> 00:16:42.320
And that's why, you know, I think companies that still run out of the inbox are going to be in trouble in this in this era, because we do need to go to move at the speed that the market demands right now.
00:16:42.559 --> 00:16:45.200
Learning has to compound and has to compound quickly.
00:16:45.440 --> 00:16:54.080
And so that's why, you know, having you know a tool like Slack where like you are working in channels and you are doing that in the open, it's really simple things.
00:16:54.159 --> 00:16:58.720
Of course, there's always a time and a place for an individual message or something that's more private.
00:16:58.799 --> 00:17:04.400
And like, you know, of course, we have all the affordances for that inside of Slack with private messages and private channels, et cetera.
00:17:04.720 --> 00:17:17.200
But the simple truth is when I have a question for an individual, there are nine times out of 10, there are eight other people on the team that are going to benefit from seeing that back and forth and learning from that.
00:17:17.359 --> 00:17:27.039
Uh, and when you know, someone gives a piece of product feedback on uh a feature and there's a response of I, the whole team being able to see and understand that benefits.
00:17:27.279 --> 00:17:37.359
So, you know, this idea of learning and building in the open and allowing your AI to see and learn from that means the AI becomes exponentially more valuable.
00:17:37.519 --> 00:17:40.319
It becomes trusted because I know it knows me.
00:17:40.400 --> 00:17:43.519
And it when it talks and it's giving data, I know it's coming from the net.
00:17:43.759 --> 00:17:45.440
I can see the sources in Slack.
00:17:45.599 --> 00:17:55.039
So, you know, that is why you know, things like Slack bottom and like this incredibly fast adopt feature because it it creates that trust where you're not coming into this with like, oh, what do I share?
00:17:55.119 --> 00:17:56.160
What do I not share?
00:17:56.400 --> 00:17:59.920
Like it's this is my Slack and it's it's in my permission base.
00:18:00.079 --> 00:18:02.079
It's in my I trust everything in there.
00:18:02.240 --> 00:18:05.039
And then I know that AI is permissioned against that.
00:18:05.119 --> 00:18:08.319
And so I can just operate as I would like a trusted teammate.
00:18:08.640 --> 00:18:09.759
Uh, and that's how it feels.
00:18:09.920 --> 00:18:14.880
It feels like I have a trusted teammate uh who I you know trust just as much as I would any other team.
00:18:15.200 --> 00:18:15.440
Yeah.
00:18:15.680 --> 00:18:25.119
And you know, we've been talking a lot so far working inside Slack, which I think is super valuable because so many teams, you know, run their day-to-day inside of Slack.
00:18:25.200 --> 00:18:51.279
Um, but there's been a recent shift, which you alluded to, with you know, things like Claude Tag, uh, right, which integrates with Slack, you know, uh mono context protocol, you know, the recent Slack MCP, and you know, the Slack parent company Saleshorse has been a leader and one of the first big SaaS companies to say, hey, we're gonna really focus on headless uh in the future.
00:18:51.440 --> 00:19:05.279
So can you explain kind of this shift from maybe you know, quote unquote pushing people to go into Slack and use Slack versus should we be just using the data from Slack in these other platforms?
00:19:05.599 --> 00:19:11.359
How do you begin to unpack that in kind of this more recent shift toward just working hidden?
00:19:12.400 --> 00:19:14.240
Yeah, so it's a great question.
00:19:14.400 --> 00:19:26.160
The you know let's just start with Salesforce and and and uh the announcement that we made last week, which was you know, anything Salesforce can do, you can now do through Slackbot.
00:19:26.319 --> 00:19:27.279
It's like it's the simplest.
00:19:27.359 --> 00:19:40.400
So we Slackbot's an MCP client, it connects to our Salesforce MCP servers, and so so Slackbot can not just read, but it can write and can take actions and go uh and and work directly with your CRM, which is unbelievably powerful.
00:19:40.480 --> 00:19:43.039
And I'll we'll start with kind of a just a simple frame.
00:19:43.279 --> 00:19:49.039
If you back up and you say, wow, many companies use Salesforce, sales service marketing.
00:19:49.200 --> 00:19:55.680
But the reality is, even as successful as Salesforce event, only a small percentage of the employees actually ever see Salesforce, right?
00:19:55.920 --> 00:19:59.200
The sellers see it, the service team may see it, maybe the managers see it.
00:19:59.279 --> 00:20:01.839
If you're on the marketing side and you're using marketing, you'll see it.
00:20:02.000 --> 00:20:06.160
But like the product and engineering teams don't, you know, maybe marketing teams don't see SalesCloud.
00:20:06.240 --> 00:20:08.400
Like they don't use that system.
00:20:08.480 --> 00:20:10.640
It's uh, but it's an unbelievably important system.
00:20:10.720 --> 00:20:12.960
It's like the customer record, it's the source of truth.
00:20:13.119 --> 00:20:16.480
It's it's where you're seeing what's going on with your customers' service issues.
00:20:16.640 --> 00:20:21.759
Like this is unbelievably valuable data, but it's not really accessible to most employees.
00:20:22.079 --> 00:20:30.000
So, what happens when you can take a tool like Slackbot and you can safely, in a permissioned way, have that connected up to the Salesforce data?
00:20:30.079 --> 00:20:33.440
Well, it turns out that data becomes infinitely more valuable.
00:20:33.599 --> 00:20:42.400
That resource, that system of record becomes infinitely more usable because now, whether in marketing, you may never have seen Salesforce, you may not even know what it looks like.
00:20:42.559 --> 00:20:46.079
But now I can ask a simple question of like, hey, I'm prepping for this IBM meeting.
00:20:46.240 --> 00:20:47.839
What's been going on with the IBM account?
00:20:47.920 --> 00:20:48.640
What's the latest issues?
00:20:48.720 --> 00:20:50.559
Are they having any service issues right now?
00:20:50.720 --> 00:20:59.680
Um, tell me about the last five meetings we've had with them, what went well, what didn't go well, and what do you think are the things that they're going to be most uh excited to hear about from?
00:21:00.160 --> 00:21:05.200
Now, Slackbot can go talk to the service, you know, our Agent Force Service uh cloud.
00:21:05.279 --> 00:21:17.759
It can go talk to our Agent Force Sales Cloud, it can go look into the IBM account channel again that's in lay open and go and see all the discourse of how the team's been working through it and bring me back this incredibly rich answer and insights.
00:21:17.920 --> 00:21:20.319
And not only that, I can then take action based on that.
00:21:20.400 --> 00:21:23.440
I can say, oh, that opportunity record, I actually just met with them.
00:21:23.519 --> 00:21:25.359
The opportunity is actually 250,000.
00:21:25.440 --> 00:21:26.400
It's not 200,000.
00:21:26.480 --> 00:21:27.359
Update that opportunity.
00:21:27.440 --> 00:21:29.519
And I can just do this by talking to Slackbot.
00:21:29.680 --> 00:21:34.400
And you know, I'll just I'll give you, I was reading a stat um just last week, it's kind of blew me away.
00:21:34.480 --> 00:21:42.480
There was 1.8 million Slackbot messages that were sent uh inside of sales by Salesforce employees uh just last week.
00:21:42.880 --> 00:21:49.039
750,000 of those were talking to and writing to Salesforce.
00:21:50.240 --> 00:21:59.759
So, like, think about that, like in terms of and and these these people Slackbot will tell you, hey, it's clearing Salesforce, but these people didn't have to say go talk to Salesforce or go talk to Agent Force.
00:22:00.079 --> 00:22:00.240
Sales.
00:22:00.400 --> 00:22:02.000
They just said, what's going on with this account?
00:22:02.079 --> 00:22:03.680
Or I want to go in this opportunity.
00:22:03.920 --> 00:22:12.240
So this headless strategy is like the exponential unlock for the value of your CRM data.
00:22:12.480 --> 00:22:29.119
And when you can bring it into the conversational interface of Slack, when you can bring it into where the humans are working, and when you can make it super accessible with a tool like SlackBot, that, you know, to cite a design principle that we have at Slack, you know, you know, we think we say all the time, like when we build software, we don't want you to have to think.
00:22:29.200 --> 00:22:30.319
Like, don't make me think.
00:22:30.480 --> 00:22:31.680
It should just work.
00:22:31.839 --> 00:22:35.599
Um, and when you can couple those things, it's a really, really powerful moment.
00:22:35.759 --> 00:22:38.400
And of course, it extends to our entire ecosystem.
00:22:38.480 --> 00:22:41.839
So you're talking about anthropic, you know, Slack's an open platform.
00:22:41.920 --> 00:22:50.400
So whether you're Box at Lassian, whether you're Vercel or Linear, all these organizations are building their AI into Slack.
00:22:50.480 --> 00:22:54.480
Um, because that open ecosystem, we know the enterprise doesn't stop at just Salesforce.
00:22:54.559 --> 00:22:59.599
It's got Microsoft, it's got Google, you've got all these other enterprise systems, got your own custom applications.
00:22:59.759 --> 00:23:01.839
All those need to be working connected in.
00:23:02.000 --> 00:23:07.599
Um, and the power of those systems becomes exponential when it's easy to access with this conversation.
00:23:08.240 --> 00:23:20.559
So, you know, obviously, as builders of the technology, you know, I assume that many within the Slack organization have been working with an agentic first mindset for quite a while.
00:23:20.720 --> 00:23:32.240
But for the rest of our audience, you know, for our maybe non-technical business leaders who, you know, their organizations run inside of Slack, how should they be changing their mindset right now?
00:23:32.400 --> 00:23:32.559
Right.
00:23:32.720 --> 00:23:39.519
Like, how does someone become an orchestrator of work, you know, versus just a doer of tasks?
00:23:39.759 --> 00:23:46.000
And, you know, how does that change with things like Slack bot or the you know Slack MCP?
00:23:46.559 --> 00:23:48.400
Yeah, I mean, there's a couple fundamental trends.
00:23:48.480 --> 00:24:01.680
Like one, uh, you know, we do need to kind of recognize that uh this agent and agent capabilities are are kind of reaching this like explosion inside the enterprise.
00:24:01.920 --> 00:24:07.119
And you have to empower your teams and your individuals to be able to manage that din.
00:24:07.680 --> 00:24:13.039
And I say din not to diminish these tools or the value of them, they're incredible.
00:24:13.279 --> 00:24:18.160
But you know, at the at the end of the day, there's still an employee who's trying to get their job done.
00:24:18.480 --> 00:24:25.119
And we're asking them to leverage and take advantage of these tools and technologies, but it's overwhelming in some cases.
00:24:25.279 --> 00:24:26.480
In some cases, they're training.
00:24:26.559 --> 00:24:40.319
So the first thing you need to do is you realize you've got to have a platform that you can go through and have a deployment place for all this technology and intelligence that your employees can use and understand and make it accessible.
00:24:40.480 --> 00:24:43.759
So you need to have those agents connected into something like Slack.
00:24:43.839 --> 00:24:48.000
Um, Slack's really the only platform right now that allows you to do this at scale.
00:24:48.400 --> 00:24:53.599
And then allow your humans to be able to work with those agents by a simple interface like Slackbot.
00:24:53.759 --> 00:24:58.319
So, to your point, we can get to the place where everyone can start to feel like a builder.
00:24:58.480 --> 00:25:04.400
Um, so you know, I have more agents available to me inside of Salesforce and Slack than I even know about.
00:25:04.559 --> 00:25:12.079
Um, but when I, you know, think about getting a task done, I'm deploying probably four or five different agents in any given Slackbot query that I don't even know about.
00:25:12.160 --> 00:25:15.039
And that that allows me to work without friction.
00:25:15.200 --> 00:25:29.599
Um, and it allows me to tap a lot of these capabilities without, you know, under underlying kind of the you know patterns and practices of the sins of enterprise software, which has been, you know, we have a thousand enterprise applications inside of our enterprise.
00:25:29.759 --> 00:25:35.920
I'm switching between 10 to 12 of them every single day, and I'm wasting 40 to 50% of my day on like the work of work.
00:25:36.240 --> 00:25:38.000
And I think that's the the real thing.
00:25:38.160 --> 00:25:43.359
The the piece that many people aren't talking about right now is you know, go back to something I started with.
00:25:43.599 --> 00:25:47.440
Employee productivity like sounds kind of like buzzword nonsense.
00:25:47.519 --> 00:25:50.880
And sometimes it's like, oh yeah, what does it really mean?
00:25:51.119 --> 00:25:57.440
Like most companies spend most of their money on their people, like 30 to 60 percent of companies spend that, you know, their capital on people.
00:25:57.599 --> 00:26:04.960
And if you can make your people like three to four X more productive and get the work of work off their plate, that's like a hundred percent revenue growth.
00:26:05.200 --> 00:26:09.039
There's not a lot of hundred percent revenue growth ideas just floating around the boardroom.
00:26:09.200 --> 00:26:14.559
Uh and so this is a moment where everyone kind of needs to reevaluate how your oh how your company works.
00:26:14.640 --> 00:26:16.799
And that's why I made the comment earlier about the inbox.
00:26:16.960 --> 00:26:18.559
The inbox is death for this.
00:26:18.720 --> 00:26:24.319
Like if you if your company employees are spending a good percentage of their work time in the inbox, you're in trouble.
00:26:24.480 --> 00:26:28.160
Um, you've got to you've got to shift that because you you will not be able to keep.
00:26:28.880 --> 00:26:31.039
Yeah, that's that's a great uh call out there.
00:26:31.119 --> 00:26:44.559
But you know, Ryan, uh, we've talked about a lot on today's episode, uh, you know, from what's new in Slackbot, headless revolution to changing your mindset and the value of those back and forth conversations.
00:26:44.880 --> 00:27:06.240
But you know, what's the one most important thing business leaders can do today as they're grappling with maybe transitioning, you know, their AI strategy from being a collection of individual AI contributors to that true multiplayer agencorchation, what's the one most important move they can make?
00:27:08.480 --> 00:27:23.599
Well, you know, I I don't know if I can always sim it down to one, but if your company like Box, Box is saying, hey, our sales team out of their working time, their non-selling time, they're gonna spend 80% of it all in Slack.
00:27:24.240 --> 00:27:30.240
And those the Slack is going to be the connective tissue between all the enterprise systems that they have, including Salesforce.
00:27:30.400 --> 00:27:45.920
You know, if your engine, who gets like 800,000 customer inquiries, they're saying the way we're gonna manage the the the scale of our business and having one connected truth is by bringing it all into a connected system like Slack.
00:27:46.079 --> 00:27:57.359
So the the the one thing I would encourage is like you have to really take a cue from how, you know, a perplexity or an open AI or Enthropic, how they build.
00:27:57.440 --> 00:28:01.039
There's a reason why those companies say Slack is their work operating system.
00:28:01.200 --> 00:28:03.839
You know, Enthropic says Slack is our work operating system.
00:28:03.920 --> 00:28:05.279
There's a reason why they say that.
00:28:05.440 --> 00:28:08.160
They run the company from this tool.
00:28:08.480 --> 00:28:18.799
And, you know, if the one thing I would encourage everyone to do is like this is the moment to re-evaluate how your organization works and how you build and how you enable everyone to become a builder.
00:28:19.039 --> 00:28:28.799
And it's not about one tool or one AI, it's about all the tools and all the AI and being able to unleash those in a way that is sensible and manageable for your employees.
00:28:28.960 --> 00:28:33.039
Uh, and that's kind of why Slack and Slackbot are kind of having this incredible moment right now.
00:28:33.119 --> 00:28:39.920
It's almost a renaissance in many ways, because we're seeing this explosion of AI coming into Slack.
00:28:40.079 --> 00:28:45.759
We're seeing an explosion of AI utilization in Slack because of Slackbots making it simple and approachable.
00:28:45.920 --> 00:28:48.559
Um, so it's time to rethink work, is the short answer.
00:28:48.799 --> 00:28:49.279
I love that.
00:28:49.359 --> 00:28:50.480
And what a great way to end.
00:28:50.640 --> 00:28:51.359
Rethink work.
00:28:51.440 --> 00:28:53.279
It's what we're doing every single day.
00:28:53.359 --> 00:28:59.359
And hey, at least for today, Ryan, you helped us uh give us the the good insights on how to do that.
00:28:59.519 --> 00:29:04.079
So uh thank you so much for taking time out of your day to join the show, Ryan.
00:29:05.039 --> 00:29:07.359
Jordan, I really appreciate you and uh I hope it was helpful.
00:29:07.519 --> 00:29:08.720
Look forward to chatting again soon.
00:29:08.880 --> 00:29:11.039
All right, and hey, if you missed anything, don't worry.
00:29:11.119 --> 00:29:15.359
We're gonna be recapping all those golden nuggets, Ryan just dropped in today's newsletter.
00:29:15.440 --> 00:29:18.799
So if you haven't already, please make sure you go to your everydayai.com.
00:29:18.960 --> 00:29:21.119
Sign up for the free daily free daily newsletter.
00:29:21.200 --> 00:29:21.759
Thanks for tuning in.
00:29:21.920 --> 00:29:24.640
Hope to see you back tomorrow and every day for more everyday AI.
00:29:24.720 --> 00:29:25.599
Thanks, y'all.
