Confluence

with them.

What has changed, obviously, in the last couple of years is that this writing down step, right, like writing down the knowledge so that it can be accessed by others, which we've tried to do with Confluence and Wiki and intranets and so on, has now changed or almost goes away because that knowledge doesn't have to be captured because it's written down somewhere.

It can be... pulled out of the work itself.

So the emails, the Slack threads, the decisions that people make every day using the agent, and then it can be applied straight back into

Hypothetically, I may see questions come into a Slack channel that is designed for people to ask questions.

And I may have hypothetically shown all of these people how to use Rovo, which is the Confluence AI that can literally query all of the information inside of your corporate Confluence.

And to a great extent, like going into PDFs, going into presentations, going into anything.

And I may have shown them like, hey, you can say, hey, Rovo, how does my product do X? And it will go find you all of the information.

Obviously, you have to have the technology.

So, a really great example was, I know when we were doing the planner demo, when we switched between Jira and Confluence, the cursor was in exactly the same place.

Now, think about the tech required in the back-end engine to keep those cursors perfectly synchronized.

So, it's a really gnarly technical investment.

And then you have to think, well, what should it look like? Because if it isn't familiar, people are going to, what is that thing moving all over the screen? It'll be distracting, right? So that's what we call the patterns.

We have to have these ways of telling you what this means.

And then finally, there's the experience end, which is how is Confluence different or Jira different now that this multiplayer editing system with agents exists? So AMP is about connecting all three layers together And I think you saw today that some very cool new things come about.

One of my actual personal favorites was being able to see who and whose agent looked at the page.

So our data scientist there helped us integrate.

We've used Confluence just for the kind of the wiki for projects.

But she led a project where we integrated Flourish, the data viz project, a program that CAM required.

So it's a beautiful kind of data visualization product that kind of syncs in with our Google Sheet and then is able to create visual storytelling for donors and for the team.

And there's been a few use cases for this already for some of my customers where they want to integrate a whole application, not just one agent, and have it pull certain MCP stuff.

Sorry, Confluence stuff.

I know you start saying the words over and over and over and your brain just goes

on.