Confluence

You are rewarded, right? from a usage perspective, significantly more if you're on the teamwork collections.

And I kind of feel on the product pricing, you kind of get a slight reward as well because it's not just Jira, like teamwork collection went up, but Jira and Confluence went up individually.

And I think the math might be higher if you don't go with the teamwork collection.

So they're just incentivizing everyone in team selection.

It's not across the board.

70, I quoted, is for if you're on a premium license for JIRA.

I think Confluence also has the same limit, but it varies.

There's a whole chart I have somewhere.

And so that piece for me is where we're landing.

Mike, to your point, I used, back in the day, I used Confluence, a Latin, like Wikipedia, a SharePoint tool.

No

Confluence anymore.

No, no Confluence anymore.

Their AI is not great.

But it was basically like this center of excellence for them or this knowledge center where all the resources, data validation schema, measure definitions, the meetings that we had.

A great example I always think about people like, you know, there's a lot of software tools that are now – you hear about these companies that have now been – bought for a billion dollars or whatever by i think it was canva was built or by adobe for a huge amount of money or whatever but a lot of these software tools that are being used project management tools like um trello and all this kind of stuff they were built as internal in-house products to start with you know in-house project management tools and they went this is quite a good thing let's start selling this outside and then they became these billion billion dollar businesses I do think there's a world where we as engineers can commercialize how we do it, our process.

Because, you know, project management tools, we use Jira and Confluence, which are Atlassian tools.

And they're great, but they don't fit exactly our development model.

We typically run a waterfall project management process.

Now we start to build it.

Now, like translating that into like a spec document, whether that's Figma or Confluence, etc.

And then finding and then collaborating with engineering to figure out, OK, if we have a timeline to build this in, what can we include? I've just found this edge case.

We can't we can't build it unless this other feature is built on the other side of the app that's owned by another team.

So firstly, by having Claude within our ecosystem, we're now giving Claude access to everything, right? I've connected it.

We've all connected it to our email, to Slack, to Confluence, to Jira, you know, all of that.

And our data warehouse.

Yeah.