Atlassian: Reselling Jira and Confluence | In Practise

Atlassian: Reselling Jira and Confluence

Former VP, Product at Adaptavist, largest European Atlassian Reseller

Learning outcomes

  • How Jira can be deployed and which methods large and small companies choose
  • The stickiness of Jira for large enterprise customers
  • How Jira workflow compares to competing solutions
  • Core challenges for Atlassian moving large customers from server to the cloud offering
  • The importance of the third-party ecosystem and why plugins need to improve in the cloud
  • Pricing comparisons for server-based and cloud products
  • Opportunities and challenges to expand Jira and Confluence across non-software teams in organizations

Executive profile

Rafael Franco

Former VP, Product at Adaptavist, largest European Atlassian Reseller

Rafael is a Former Product VP at Adaptavist, the largest European reseller of Atlassian products. He spent 4 years selling Jira and Confluence across all deployment types to both large and small enterprises across Europe. Rafael has also ran engineering teams and is the current VP of Product at Influencer where he is now a customer of Atlassian using both Jira and Confluence products. Read more

Rafael, can you share some background about your experience at Adaptavist and what the company does and what you were selling?

When I was working for Adaptavist we were, essentially, building applications and plug-ins for Atlassian. You have your Atlassian offering as it comes standard, out of the box. But quite often, you need plug-ins to augment that experience and to provide additional functionality. What Atlassian provides is a marketplace, where vendors can go in and deploy and sell their products through those means. That’s what I was, essentially, involved in; leading the Confluence product portfolio, at Adaptavist.

Is Adaptavist is an Atlassian exclusive reseller or do they sell other products?

In this case, Adaptavist only focused on the Atlassian ecosystem. Obviously, it’s one of the many other partners that exist in the world. Some of them focus on other areas, not just Atlassian. In this specific case, Adaptavist focuses on Atlassian, exclusively.

Which type of customers were you, typically, selling to at the time?

It’s interesting, especially from the product management point of view, because you have a huge diversity of customers, from many different types of industries, both big and small. For example, you had customers such as Uber and Apple, which are obviously massive. But then you also had small and medium enterprises that you would sell to. You have to build a product that fits the bill for all of these cases, which is extremely challenging. Even for Atlassian themselves, building something that can cater for all of these different audiences, is extremely difficult. I think that’s why they built an extremely successful product.

What were the core differences in the way that, let’s say, Uber versus the local company, deployed Jira, for example?

It really boils down to the complexity and the sheer amount of data that these instances created. As you can imagine, with Uber, they have extremely complex systems and workflows and a lot of information share. In the specific case of Confluence, they have many pages they need to share; rightfully so as it is a massive company. Whereas, if you have a smaller company, they probably don’t have that amount of data or that complexity and their workflows are much simpler. You don’t have to follow too many processes and it’s great that Atlassian really allows this flexibility. It is one of their core value propositions, which is really to do with the customization that allows for different types of scenarios.

How did the large and small companies choose the different deployment methods?

It depends on a couple of factors. The first one has to do with where you want your data to lie. Do you want your data to stay in Atlassian servers, or not? Using Germany as a very good example, there is a law in Germany that doesn’t allow your data to stay in third-party servers. For lots of German companies, SaaS and cloud is not even an option. Then you exclude the SaaS offering and you have to go with the server. If you go with the server, we’re talking about one single instance, lying in a data center or, potentially, an AWS container. This mean that if, for any reason, that server goes down, the application will, pretty much, go down and everyone loses access to it. This might be totally doable; if the company is small, maybe they don’t need that high availability at all times. In this specific case, the server instance is just fine.

In the case of big companies, like Uber, for example, you naturally need to have high availability because having Jira, Confluence, Bitbucket or any of that down, can cause massive disruption in the business. For that, you need to have data centers. A data center, essentially, is a grid of servers that provides high availability, so that if one goes down, it automatically goes to another one and people don’t even realize that one of the servers has gone down. But at the same time, it also has benefits, in terms of performance. You can really split the performance and you can, pretty much, route some of the users to one server and some of the others to another one; it’s like a load-balancing solution. It is, obviously, much more expensive and harder to implement.

Sign up to read the full interview and hundreds more. No credit card details required.
Sign up to read


Atlassian: Reselling Jira and Confluence

September 16, 2020

Sign up to listen to the full interview and hundreds more. No credit card details required.
Sign up to listen