LeanIX licensing is calculated per application count; hence the cost will need to be assessed upfront while keeping in mind that the M&A or business strategy changes/roadmaps must be anticipated for the next few years.
The tool needs to include more flexible licensing options. We do not use the tool all the time. So pricing should be considered only when we use the tool.
Principle Research Director at a computer software company with 1,001-5,000 employees
Real User
2023-02-27T18:35:34Z
Feb 27, 2023
There is a sweet spot of where they need to be on pricing right now. They could go up a little bit in pricing, but it has to do with the cost savings, and it has to do with the practitioners using it. I use it where I get cost savings and I can justify it, but they probably have the ability to flex a 10% up channel on their sales on that. So, they could increase their settle price, not their offering price, when they sell. They can probably hold that up a little bit higher than it is because there are cost savings that we can drive from it.
The solution's pricing is based on a licensing model that is competitive and in line with other products. I rate pricing a ten out of ten because there is good value.
There are two pricing models. One is based on the number of what they call Fact Sheets, which are a representation of the things in your company, such as applications, technologies, and business capabilities. They are like a profile for each entity that you want to bring in and pricing is based on the number of those entities that you bring in. That's what we purchased. They introduced another pricing model based only on the number of applications that you bring in. In the first model, they give you fewer capabilities in the package, but you can use it for a larger number of entities. In the other offering, they give you more capabilities, maybe even way more capabilities, but you need to form your information in a way that you are conscious of how many applications you put in. The second way of doing things is very new. It was introduced a couple of months ago. When I looked at it for our use, it was not going to give us too much benefit. First of all, we were set up, and all our agreements were made based on a different licensing model. If we were to go back and remodel things, it would be a big effort so we decided not to go with it. We decided to stay with the pricing model that they had originally, based on the number of building blocks, not just applications.
CRM Manager at a tech services company with 501-1,000 employees
Real User
2019-07-29T10:11:00Z
Jul 29, 2019
The pricing is a bit painful in the sense that it depends on the number of elements you fit in the system. The price can be expensive if you use it a lot. It will cost you compared to other solutions if you have a lot of documentation. It's hard to predict the pricing of the system.
LeanIX delivers collaborative Enterprise Architecture designed for modern IT. Our open, data-driven architecture management model helps organizations adapt to the evolving demands of digital. From agile to multi-cloud and beyond, architecture teams using LeanIX have the power to strategically support the business and report 45% reduction in time to value delivery. More than 90,000 users across enterprises worldwide rely on LeanIX to manage their IT landscape, including adidas, Bosch, 7Eleven,...
The pricing is very good. We definitely get good value for the money.
LeanIX licensing is calculated per application count; hence the cost will need to be assessed upfront while keeping in mind that the M&A or business strategy changes/roadmaps must be anticipated for the next few years.
In terms of pricing, it's cheap. I would rate the pricing a one out of ten, where one is cheap, and ten is expensive.
The tool needs to include more flexible licensing options. We do not use the tool all the time. So pricing should be considered only when we use the tool.
There is a sweet spot of where they need to be on pricing right now. They could go up a little bit in pricing, but it has to do with the cost savings, and it has to do with the practitioners using it. I use it where I get cost savings and I can justify it, but they probably have the ability to flex a 10% up channel on their sales on that. So, they could increase their settle price, not their offering price, when they sell. They can probably hold that up a little bit higher than it is because there are cost savings that we can drive from it.
The cost is average.
The solution's pricing is based on a licensing model that is competitive and in line with other products. I rate pricing a ten out of ten because there is good value.
There are two pricing models. One is based on the number of what they call Fact Sheets, which are a representation of the things in your company, such as applications, technologies, and business capabilities. They are like a profile for each entity that you want to bring in and pricing is based on the number of those entities that you bring in. That's what we purchased. They introduced another pricing model based only on the number of applications that you bring in. In the first model, they give you fewer capabilities in the package, but you can use it for a larger number of entities. In the other offering, they give you more capabilities, maybe even way more capabilities, but you need to form your information in a way that you are conscious of how many applications you put in. The second way of doing things is very new. It was introduced a couple of months ago. When I looked at it for our use, it was not going to give us too much benefit. First of all, we were set up, and all our agreements were made based on a different licensing model. If we were to go back and remodel things, it would be a big effort so we decided not to go with it. We decided to stay with the pricing model that they had originally, based on the number of building blocks, not just applications.
The pricing is a bit painful in the sense that it depends on the number of elements you fit in the system. The price can be expensive if you use it a lot. It will cost you compared to other solutions if you have a lot of documentation. It's hard to predict the pricing of the system.