BiZZdesign HoriZZon Reviews

My main use case for BiZZdesign HoriZZon is to edit the meta-model, and I am able to model epics on this design.

A quick specific example of how I use it to analyze epics or edit the meta-model is the recent work on the meta-model for the technical layer, and I use it to publish.

The best feature that BiZZdesign HoriZZon offers is Enterprise Studio.

What stands out to me about Enterprise Studio is that it is all about collaboration, modeling, and optimizing, improving the meta-model to fit our IT systems.

A big impact that BiZZdesign HoriZZon has on my organization is to improve the overview of the whole system for people around us. I am in the architecture team, and this design can share everything, every work item we did and created on schemas with all the people around us, meaning that the entire technical team can see the impact and perform impact analysis to move forward for all the systems we manage.

BiZZdesign HoriZZon can be really quicker than today as we are experiencing some performance issues, so that is the most important thing.

I chose a six because this design needs to grow up more and come with useful functionalities that can help teams to go faster.

I have been using BiZZdesign HoriZZon for two years.

Regarding BiZZdesign HoriZZon's AI capabilities, I think its governance is good; almost good; the governance is pretty well, and the security is completely improved.

Integrating BiZZdesign HoriZZon with my existing tools or systems was hard.

My advice to others looking into using BiZZdesign HoriZZon is to be patient, get some training, and discuss the governance and meta-model topics to improve the implementation. My overall review rating for BiZZdesign HoriZZon is six.

Hybrid Cloud

Google

My main use case for BiZZdesign HoriZZon is to architect most of our ERP integrations, which includes all the business-to-business connections, transformations, and automations included. This maps out the entire ERP architecture.

Within our organization, BiZZdesign HoriZZon is particularly useful for creating a connected view of a large and complex technology landscape, as we operate across multiple business functions and use a combination of SAP and non-SAP applications, different integration platforms, APIs, and messaging systems. Without an architecture platform, this creates an information matrix that can easily become fragmented across spreadsheets, presentations, and technical documentations. BiZZdesign HoriZZon has helped us keep all of that in one place. For example, when assessing the future of SAP PO integrations, we need to understand how much more the number of interfaces can be in the future architecture. We need visibility into the business process supported by each integration, the source and the target applications, communication protocols, criticality, dependencies, ownership, and downstream impact. BiZZdesign HoriZZon helps connect these different architecture layers and allows us to relate business capabilities and processes to applications, integrations, and underlying technologies. This makes it easier to understand how a technical change could affect an actual business operation, such as procurement, finance, HR, manufacturing, or logistics.

Another valuable use case is impact analysis, where before changing or retiring an application or middleware component, it is really important to assess what all systems it is actually affecting when you take it out. This reduces the risk of overlooking indirect dependencies, so we have used BiZZdesign HoriZZon to understand what all downstream systems will be impacted.

The best features BiZZdesign HoriZZon offers are the ability to connect the business process application, integrations, and technologies within a single architecture repository. This is one of the most important things, as instead of viewing it at different layers and different areas, you get to view it all at once and also understand the important connections between those architectures.

BiZZdesign HoriZZon has positively impacted our organization by providing a combination of dependency visibility, impact analysis, and stakeholder-friendly visualization, which differentiates it from maintaining architecture information in spreadsheets or static diagrams.

BiZZdesign should really work on its documentation and user acceleration to enhance the experience. I find a lot of difficulties in trying to understand how to navigate it, and the documentation is also quite lengthy. There are no useful tutorials to guide users through anything, and the startup time of all features is a little bit tricky.

I have been using BiZZdesign HoriZZon for the last two years now.

While you cannot always quantify return on investment based on dollar values here, the manpower and man time saved are significant, and the efficiency which the organization is able to achieve after using BiZZdesign HoriZZon is great.

If you invest the time required for the initial training, it will reap you benefits later on. I would rate BiZZdesign HoriZZon a nine out of ten.

On-premises

My main use of BiZZdesign HoriZZon in my organization is for enterprise architecture and transformation management as an information systems urban planner.

As an example of how I use this tool as part of my missions as an information systems urban planner, I engage in transformation management, transformation modeling, and mapping in the context of changing a CRM tool, managing obsolescence, and moving to the cloud, particularly with Salesforce.

Regarding my use of BiZZdesign HoriZZon in this context, I would add that it facilitates strategic alignment with the portfolio and execution which is easy to use.

In my opinion, the best feature that BiZZdesign HoriZZon currently offers is application rationalization.

Application rationalization, as a feature of BiZZdesign HoriZZon, helps me concretely in my activity because it is very easy to get through the tool and it gives me a synthetic view of the tools that are becoming obsolete.

BiZZdesign HoriZZon has a positive impact on my organization through the management of mappings, the management of application portfolios and the modeling of architectures via BPMN or ArchiMate, as well as impact analyses for change.

In my opinion, BiZZdesign HoriZZon could be improved especially in the management, for example, the management of licenses.

I have been using this solution since the beginning.

I would rate the stability of BiZZdesign HoriZZon in my environment as rather stable.

I rate the scalability of BiZZdesign HoriZZon as it adapts easily to the evolution of my needs or to an increase in workload. However, we have no visibility regarding BiZZdesign HoriZZon and the acquisition of Mega or Hopex on this matter.

I find the customer support of BiZZdesign HoriZZon to be good.

I did not use another solution before BiZZdesign HoriZZon, so there is no suggestion to make.

My advice to those who are considering using BiZZdesign HoriZZon is to conduct a proof of concept to start with, so that it properly meets the expected needs.

My company does not have a business relationship with this vendor other than as a customer; I am a user.

I have seen measurable improvements and concrete benefits, with time and productivity gains resulting in time savings with a ratio of twenty to thirty percent and an ability to deploy quite quickly, since we found modules that already existed or applications that already existed and in that case, we gained in power.

Before choosing BiZZdesign HoriZZon, I evaluated other options such as other vendors including Mega and Hopex.

On-premises

BiZZdesign HoriZZon is primarily used for enterprise architecture processes. My clients mostly use it for architecture modeling and planning.

BiZZdesign HoriZZon's visualization techniques help my clients make data-driven decisions. The best function of BiZZdesign HoriZZon is the visualization part, which is unique and the most useful in the product.

The collaboration and integration capabilities of BiZZdesign HoriZZon are strong. The product is easy to integrate and collaborate with. The ArchiMate modeling language feature is excellent.

The reporting dashboard functionality of BiZZdesign HoriZZon is comprehensive and valuable.

BiZZdesign could improve BiZZdesign HoriZZon in several areas. There are potential areas of improvement that should be addressed to make the product better.

I have been using BiZZdesign HoriZZon for five years.

I would rate the stability of BiZZdesign HoriZZon as a nine out of ten.

I would rate the scalability of BiZZdesign HoriZZon as a ten out of ten.

I would rate the technical support as a five out of ten.

I previously used Orbus Infinity. Based on my expert view, BiZZdesign HoriZZon is the best product when compared to the three.

The initial setup of BiZZdesign HoriZZon is simple. I am working with a cloud-based deployment model.

I last worked with BiZZdesign HoriZZon recently. BiZZdesign HoriZZon is deployed on Amazon Web Services. I was not involved in the purchase process, as it is totally on the client side. I would rate BiZZdesign HoriZZon pricing as a ten out of ten, indicating that pricing is low. My overall rating for BiZZdesign HoriZZon is ten out of ten.

The typical use case with BiZZdesign HoriZZon is basically for enterprise architecture and also for business process modeling.

The most valuable features of BiZZdesign HoriZZon include the diagrammatic representation of BPMN models, which I find good for modeling, and things such as capability maps. It allows for collaboration as if I work on something, someone else can pick up on it too.

Regarding ROI from BiZZdesign HoriZZon, it does what it's supposed to do, mapping capabilities and interacting with users effectively. The benefits are present in the tool, but it's also about user adoption within the company.

There is room for improvement in BiZZdesign HoriZZon. It's quite robust and has good online forums where people discuss it, though maybe the interface can improve, but I don't want to criticize it since I don't have comparisons of other tools. It takes a long time to learn and understand, which is a learning curve you have to go through, but once you know how it works, it's very nice to work with.

My experience with BiZZdesign HoriZZon spans approximately three to four years.

The stability of BiZZdesign HoriZZon rates at a 9 since it's very stable, although we haven't really strained it under very large landscapes that might test big designs.

The scalability of BiZZdesign HoriZZon rates quite highly at a 9 if not a 10, as for our use case with a small team, it was sufficient usage and any additional resources would find it easier to use.

The technical support from the vendor of BiZZdesign HoriZZon has extensive documentation, and I rate it a 9 because we had substantial initial guidance and online forums where people discuss it.

Positive

The initial setup of BiZZdesign HoriZZon was straightforward for me because when we got it, it was already set up. I wasn't involved in that portion, and all I had to do was get access and start to work on the tool itself. Once you start using it, you have to really know what you want to achieve, but it's quite a very good tool for business process and enterprise architecture.

I'm talking about several tools on business solution designs, as there are many calls and I've worked with several tools in this area.

I am employed with a company that has a license for BiZZdesign HoriZZon, so you can say a partner or a user, and if you buy the license, you become a partner.

I'm not involved in the pricing of BiZZdesign HoriZZon as it was bought by the organization.

Based on my experience with BiZZdesign HoriZZon, which I rate as 8 out of 10, I definitely recommend it, but I think it would be beneficial if there were opportunities to trial it before purchase, as it is robust and comparable to other tools I've worked with.

Public Cloud

Other

I use the solution in my company for all sorts of things, like enterprise and solution architecture. As part of our design process, BiZZdesign HoriZZon is used for road mapping. We also use it for project governance, so all the project designs we do are subject to governance and are done using BiZZdesign. THe quality data from Bizzdesign is then fed into our CMDB, in order to keep the data synchronised across the two tools. We also import operational data from the CMDB back into Bizzdesign, and use this to enable us to check that the required changes to the CMDB have been carried out correctly.

The tool's most valuable feature is that its collaboration part is very good. The way it supports multiple users working together is very good. I appreciate the use of standards in the tool. The tool is based on standards, which is very useful. I find extending and customizing the tool easy, which is very useful for us.

The ability to generate charts and deal with a use case involving Kibana was quite difficult. We don't use the chart functionality much, and I think that is quite problematic at the moment. We have made some design decisions with the tool, but I don't want to get too technical. The way the tool deals with the built-in way of creating charts with Kibana is quite difficult to use, so we don't use that, which is a problem. We have a problem with some of the visualization parts, as they are very hard to use.

I would like to be able to update data from the built-in scripting, irrespective of how that data is put into BiZZdesign. Right now, that is very difficult to do. They have a number of ways to store data. For example, in an application, there are a number of ways of storing data, and it is very difficult to update, use, and store what the product refers to as data blocks from all sorts of applications. I would like to see if I can split or instead put all the data for our business into one database. I would be able to split across multiple databases and have them linked together. I think that would make things easy. We don't have to put everything in one place. It is not so much trying to protect ourselves from risks. It is just that you have everything in one space, and then when you try to open that repository, it is very slow sometimes. Make it a lot more manageable if we can break it into smaller pieces but still link them, as that would make things easier and make things run a lot faster.

I have been using BiZZdesign HoriZZon for six years.

It is a very stable solution. The back-end server side is incredibly stable, but the client side does crash. Stability-wise, I rate the solution an eight out of ten.

When it comes to the tool, I think it is very easy to adapt. There are some issues, but we didn't find it difficult to do it.

We don't need the large infrastructure because everything is hosted by BiZZdesign.

In my company, there are around 300 users of the tool.

My company plans to increase the usage of the tool in the future.

Many of our company's core processes rely upon the tool. We process documentations, and all of our architecture information is stored in the tool. The tool is used in many parts of the organization and within the data center.

I have communicated a lot with the technical support team for the solution. The technical support team is very supportive, and they do a lot of digging to make sure that we get sorted out. I rate the technical support a nine out of ten.

Positive

I have used a tool from an Australian company called Sparx Enterprise Architect. Another tool that I have used extensively, but not recently, was a tool owned by a company called CACI, which is called MooD.

I decided to use BiZZdesign HoriZZon because I had used MooD with one employer. I used  Sparx Enterprise Architect with a different employer. I didn't choose any of the tools I work with in any way. I used the tools offered by my employer.

If one is difficult and ten is easy to set up, I rate the product's initial setup phase as a ten out of ten.

The product's setup phase has been very easy.

The solution's setup phase has been very straightforward, and I didn't have any issues with it. The one thing is that in terms of the setup features, the tool integrates with a dataset called Technopedia, which is owned by a company called Flexera. It enables you to have a database of all the IT products that you can buy. I can say this application runs on this version of all Windows. The issue is that, apparently, every customer wants such an integration to be done, but it takes six to eight weeks to make it happen. It is puzzling to me why, in this day and age, you have to wait six weeks to turn on a switch. It should be simple. It is not that big of a deal as we managed it, and it is running fine now.

The solution can be deployed on a hybrid cloud model. The client-server part typically runs on our laptops. Although sometimes we also use the SaaS client, most of us use it on our laptops, along with the repository and the web host by BiZZdesign, but the client server part takes an hour.

It did not take time to deploy the tool. It was done in a day or something.

The deployment process is something that I distinguish between the client and the server. We don't deploy the server part. To deploy the client, we typically package it. There are various technologies you can use to push and use that automatically. We could use SCCM, but we don't just ask users to download it because we don't have admin rights on our laptops. We package it ourselves using the base product from BiZZdesign. We take BiZZdesign Enterprise Studio product, package it, and then deploy it to all of our desktops and laptops that need it.

On the client side, one person is typically involved in the deployment process to package the tool.

If one is very cheap and ten is expensive, I rate the product price as a seven out of ten. The tool's price is justified. There are three different licenses, namely the designer, contributor, and consumer. I think the designer license is a little expensive.

My current employer also evaluated iServer and Alfabet, before deciding in the end to select Bizzdesign. I think that was a good choice, it fits very well into our environment.

Speaking about BiZZdesign HoriZZon's most beneficial part for risk management tasks, I would say that its ability to link risks to things affected by those risks is good. Risks don't just exist on their own. A risk is a risk to something, like an application, or to a process, and so on. The tool's key feature is its ability to see risks in the proper context and, therefore, drive behavior by letting us know what is affected by risk and what can be done rather than just seeing the risk as a standalone aspect.

Speaking about BiZZdesign HoriZZon's strategy and portfolio management features of the solution have impacted our organization; I would say that there are particular features built into the product. We have not really used the tool's built-in portfolio management features because we have our own way of doing it. With the tool, being able to understand what applications do and also record relevant information to be able to say which apps are needed to keep or get rid of are areas that can be managed by the tool. We are not using the built-in features of the product. We are using our own way of using the tool, but we are still using the base product.

I think we have not used BiZZdesign HoriZZon to support compliance with industry regulations.

There is the basic product, and then you have enhancements that my team provides on top of that. We maintain the product with help from the vendor. We maintain the tool, but the base product is something we don't maintain, as we don't. have the vendor to help us with it.

My suggestion would not be specific to BiZZdesign but common introductions. You can do anything with the tool, but you would have to be focused on doing something well with it or just dump stuff in and then find it. The data in the usual systems is never going to be those things you would want to create in BiZZdesign, as some of the things you would want for yourself would be elsewhere. The tool can help in mastering traffic., and understanding where they come from in the first place.

I rate the tool an eight out of ten.

I used BiZZdesign HoriZZon at two organizations. At Manchester Metropolitan University, I used it with a small team for architectural modeling of the student record system. We modeled teams, process objects, and their interactions with applications. We also used it to model a gradual rollout with plateaus showing migration over time. At the BBC, I used it to model software services for publishing content online. I showed key model views to senior stakeholders using Horizon, allowing them to modify and score applications and services.

There's always room for improvement. When I finished using it over a year ago, I discussed implementing C4 notation with BiZZdesign HoriZZon.They've likely done this now, but I haven't seen it. Setting up interactive views for stakeholders to score services was a bit difficult.

I have been using the product quite a lot. 

I don't recall any stability issues or bugs. The tool has a fully version-controlled data storage system that saves work continuously.

Scalability is great - it's one of the product's biggest benefits. Multiple team members can simultaneously contribute to the same model without overwriting each other's work.

I didn't contact the tool's technical support for problems, but I did contact them for guidance. They're very open and helpful. I could easily get in touch to ask how to do things, and they'd respond with video calls, screen sharing, and walk-throughs. This was especially useful for scripting functionality, which is powerful but not well-documented. We called them several times for proactive help, not to solve problems retrospectively.

We were customers and bought licenses from them. We used their remote instance initially but upgraded to the on-device version due to lag. For pricing, we paid about £1200 a year per seat for the client installation at an educational rate but that was a long time ago. I'm not sure about commercial rates. I managed to get a free evaluation copy at BBC since it was for evaluation purposes. 

It's not easy for anyone to use without training. When we purchased licenses, we bought a week's training. The solution also offers consulting and training services, which is helpful. 

I would recommend the tool to others. I currently work for the British government and would love to use it here. I'd happily recommend it to anyone seeking an enterprise architecture tool, particularly those who like using different modeling notations that can interact with each other and for teams that could grow over time.

Key attributes include scalability and a unique feature that offers a window into the models for senior stakeholders without requiring installation on their machines. These are significant benefits of the product.

I rate the overall solution a nine out of ten. 

Our clients deal directly with BiZZdesign. They use it, but what we do is we have some experts who have hands-on experience, and we use that knowledge to implement solutions for them. We don't use any separate licenses for HoriZZon ourselves.

There could definitely be regulatory impacts to comply with industry regulations. 

Since we're currently supporting clients in two specific countries, I'm mostly confident it's compliant. If clients in other countries require it, they'd likely raise questions about regulatory compliance. 

As these clients seem to be familiar with the product, it's currently compliant. 

The features I like are that it's very easy to implement and it's reliable.

This is one of the best tools, especially because of its collaborative nature. Anyone using it can access previous projects and related data. It's definitely a strong collaborative tool.

It's configurable, meaning you can integrate this product with different tools. However, there are some restrictions. 

Integration definitely needs improvement. There are some restrictions. We've seen that it doesn't integrate with everything we might expect.

Out of ten products we want to integrate, maybe five or six integrate easily. The other four might face challenges due to lower investment in the products or compatibility issues. It's definitely not easy to achieve seamless integration for any product.

We can only test to a certain extent, and issues could arise from either BiZZdesign HoriZZon or the other product.

Another point is the cost of licenses. If they were a bit lower, it would be easier for businesses to acquire more licenses... something like an enterprise or bulk license model. Maybe different pricing tiers based on the number of licenses, like significant discounts for orders over one hundred. This could help clients adopt the product.

I have been using it for five to six years now. 

It is a very stable product. We don't have any challenges in this regard. 

I would rate the stability a seven out of ten. 

It is a scalable solution. I would rate the scalability a seven out of ten because it has an autoscaling option. It's generally scalable.

The solutions support medium and enterprise level businesses. 

We struggled once to get adequate support. It took a long time to receive the solution we expected.

Neutral

We don't use this product in isolation. Different clients use different products.

We can recommend the best products for our clients. Some clients may be new to us, or existing clients who already hold BiZZdesign HoriZZon licenses.

I would rate my experience with the initial setup an eight out of ten. The setup process is relatively smooth. 

We've only worked with cloud deployments. I'd also rate the cloud setup experience an eight out of ten. We have instructions, user guides, and support details provided. In case something happens, we have contacts to reach out to. However, we haven't tried on-premises deployments.

The deployment time depends on the complexity of the project. For complex projects, it definitely takes a few weeks. There might be dependent tasks involved. 

However, most deployments happen within minutes if there are no dependencies. If not, it takes a few hours, maybe three to four, based on any related tasks.

We are the implementors. We implement different solutions for our clients. 

In terms of licensing, my clients take care of everything directly with BiZZdesign. We don't intervene in that process. However, we provide advisory services. 

For example, if we determine that additional licenses are needed, we inform the client, and they manage the licensing changes.

In terms of this particular product usage, my clients currently only use per-user licenses.

I would rate the pricing a five out of ten, with ten being expensive. It's not too costly, but not particularly cheap either.

I would recommend using this product. However, it depends on the clients we acquire in the future. Not every client needs this type of software. If we encounter clients who aren't using HoriZZon, or are using a different solution, we might recommend this product if it aligns with their interests. 

We'd need to understand their current setup, costs, stability requirements, and any challenges they're facing before recommending a switch.

Overall, I would rate the solution a seven out of ten. 

Public Cloud

I've used the solution for business architecture.

The most valuable feature is that it allows you to work with different methods, using the same tool. You can work with ARki and BCNN as they are connected in BiZZdesign HoriZZon, which is fantastic. Its documentation is also really good. It's easy to read and it's open to the Internet.

BiZZdesign HoriZZon could use some improvement when it comes to the implementation of the tool. Its origin is quite pragmatic. Although it does have the project as a concept, it's not possible to look at it from a project perspective, which is not very practical.

I've used BiZZdesign HoriZZon for many years.

When it comes to stability, I give it a seven out of ten. It's a fairly stable solution but has issues with deployment. The database itself and the synchronization with the database of multiple users are not up to standard. A lot of manual synchronization steps are required from the user. The solution depends on someone to manually update the Central Point in order for it to receive the information. We had about 200 people using BiZZdesign.

Scalability is a bit of a problem for BiZZdesign. There is always a possibility it will failover. I would rate the scalability of the solution an eight out of ten.

We also use ARIS at our company, but BiZZdesign HoriZZon is a lot easier to use and allows you to maximize your knowledge and abilities while using it.

BiZZdesign has a lot of issues with deployment. It is web-based and can get a little complicated. It had to go through multiple streams such as Amazon and Virtual PC, which makes things pretty complex. 

The administration and the licensing part of BiZZdesign are quite easy since it's a smaller company. It is also not very cheap. It costs about $2,000 per year.

BiZZdesign HoriZZon has strong requirements for the technical aspect of things, but it is easy to start working on it if you have knowledge of VPN and UML. It gives you the chance to adapt it to your environment and to implement the things you already know.  Overall, I give it a ten out of ten.

Public Cloud

Amazon Web Services (AWS)

We use it primarily for architecture and capability-based modelling. We plan to use it more as an analysis rather than a modelling tool.

We previously used System Architect and Provision, which did not work for us. Since implementing BiZZdesign HoriZZon, many of our solutions and technical and segment architects have been using it actively. We recently changed how we developed BiZZdesign HoriZZon and have completely moved away from the word-based SAHLD, the high-level architecture design, to a fully automated and dynamic solution intent. The advantage of doing that is if one project finishes, the architecture can pick up from there, and all the architectural artifacts are already available in one place for the next project team to pick up.

The enterprise studio where the modelling happens is valuable and a critical part of the tool for non-architects and business stakeholders. In addition, the HoriZZon, where we share most of our models with the stakeholders, is a feature that businesses appreciate because it makes it a collaboration tool.

We are working with BiZZdesign to improve the interfaces with ServiceNow. There are also other tools where we bring the data application components, and data objects into BiZZdesign HoriZZon, and not all the offices are mastered. The initial design assumed that all of the content would be mastered there. So that's one area of improvement that BiZZdesign HoriZZon is working on.

There could be simpler modelling so that instead of users drawing the diagrams in the tool, they can create a table of contents that can automatically be used to create diagrams. In addition, it will make it simpler for non-architects to create representative models.

We have used this solution since the beginning of 2019, using SaaS from AWS.

I rate the stability a nine out of ten.

There is room for improvement with the scalability, and we have been working with BiZZdesign on that. So I rate the scalability a six out of ten. We have 750 active architects using this solution and developing models and about 5,000 stakeholders. We don't have any place to increase the usage right now, and I don't see a considerable increase in the active architects modelling in the BiZZdesign HoriZZon. However, there may be an increase in the number of stakeholders because only certain business stakeholders currently provide consumer access.

I rate technical support an eight out of ten. They're good at solving problems and have good lines of communication internally, so if the first line of support cannot solve the issue, the second line of support does. If the second line of support cannot resolve the issue, they escalate it to their development or product management team.

I rate the initial setup an eight out of ten, and I rate the features available a five out of ten. When we were implementing the solution, the product itself was being evolved. So the implementation was not that difficult, and it was relatively easy. However, many features you would expect from an enterprise architecture tool were still missing. I think a lot of the missing features are covered now, but a lot of them are still on their roadmap.

BiZZdesign technical support was primarily involved in the setup. There were third parties involved, and the documentation provided by BiZZdesign was helpful. The deployment took about three months, and it was not complicated. A lot of the challenges were post-implementation, and not everything is mastered in BiZZdesign. At the core team, four people from our organization were involved in the deployment comprising three consultants and the account manager from BiZZdesign. In addition, there is a support organization that looks after maintenance.

We are still working with BiZZdesign on some of the issues. So while we are in this transition period, we are still investing in the solution. So calculating ROI metrics is difficult at this point.

I rate the pricing a six out of ten, but I can't share more details about the costs. However, the pricing model could be improved considerably.

I rate this solution a seven out of ten.