We have a global moderator, who is a system architect. This person distributes responsibilities to the regional level, such as North America and Latin America. EMEA and India are also regions, and I am responsible for India.

At this moment, it is a little early to talk about scalability because, for the part of our organization in India, I'm the first person using it. We will expand in the next two years and we will be doing a lot of activities. This includes transformational activities and we need to bring some brilliant brains together. When we do that, this tool will be a great help in terms of facilitating collaboration.

When we get to this point, we will definitely seek the help of Lucid experts.

We are working toward scaling and increasing our usage of this product. I think that's where we're trying to get to but it's a matter of finding the use cases throughout our organization to continue scaling and applying it a little bit more. I'm not really sure how many licenses we have to use it, but I think once you showcase the product, there are always opportunities to expand usage and apply it to individualized use cases, depending on what you're working on.

I don't know exactly how many users we have across the organization but it is probably fewer than 100.

It is pretty lightweight, and you're using boxes, shapes, and objects on a web app. In the integration settings in my account, it shows the integrations with Salesforce, Box, etc. It also shows the available space of 2 terabytes and the used space of 0%. I'm sure it is much more scalable, but I don't think enough people are using it for me to be able to make a comment about that.

I'm not really using it in a full operational capacity where a team of people are actively using it and building on it. It is probably getting very light usage because there are not that many people who have a license or the time to use it. It is still in its infancy in this organization.

I've been consulting at this company only for five weeks, and it is mostly being used by me to demo to senior management. It is being used extensively by me, and I will continue to use it extensively. It is a great tool for producing visuals for slide decks. I'm using it at least half an hour to an hour a day, so that's a pretty good sign, but I don't think I'm going to increase its usage because I'm not a person who just does process flows all day. I do a bunch of other things. I'm using it a lot more now because we're taking off a project. I'm using it to show statuses and updates and pitch the project that we're doing to senior management. I am showing them the flows that we're going to adopt and the roadmap that we're going to take. I will be using it probably a little bit more when I get into the business glossaries over the two months or so.

I don't know how far its usage will go for other people or employees in the company and whether there'll be a team of people to go further. The tool has potential, and I am hoping that the work that I'm doing will make more people, who are more permanent, adopt it as a tool to do a bunch of things, like a Swiss knife. Once that's done, they might then port some of the capabilities from an operational perspective into some flows where they're documenting these things a little bit more robustly than I am. So, I'm using the tool more in a sales and marketing style for a sales pitch or for pitching ideas. I am not using those capabilities that are more operational where you have flows that are documented. The tool does quite a lot of different opportunities for use cases, and I'm only using one or two facets of it.

It is very good in terms of scaling because you can save folders and content, and you can share it easily. I'm a small consulting firm and there are just three of us. One is an advisor and the other helps build the assessments and playbooks.

If my company grows and I get more clients, then I will expand my usage of Lucidchart.

I haven't had any scalability issues, even very large diagrams. I've never had any issues with that.

There are between 20 to 30 users that are mostly a mix of the engineering team, architects, and senior engineers.

The maintenance requires less than one part-time person. 

It meets our needs. We don't really have a reason to change it. We were forced to update the plugin to a different license type recently. We're still working through that, but it's still our preferred tool for diagramming at the moment.

Extendability-wise, I don't know how many third-party plugins or additional integrations are there, so I can't speak about that too much. 

Scalability-wise, I could easily see a future where every one of our employees has a license and is using it. It would actually make our lives easier as opposed to more complicated. In that sense, I would say that it is super scalable.

Currently, I'm the only one using it as a creator or editor. Our land acquisition guy is also using it. He is just looking at it; he is not editing. Our two co-founders, our VP of operations, and our VP of construction are using it as viewers. All four people at the executive or VP level are using it. I'm a director, so I'm not quite at the VP level, and everyone else above me is using it, which is cool. We'll very soon be at a place where there are people under me who are using it. That's definitely going to happen soon, so I would say across all levels of our company, it will be used. We have maybe six people right now, but in the next couple of months, we'll be at a point where we have 10 to 15 more people using it. As we get up to that point, we would probably have more editors too.

I am the only one driving it right now in the organization, but I certainly think there is more potential for it. I have been kind of testing it out.

Scalability depends on who is using it. For me, it was pretty good because I didn't use it extensively. I don't know how much they give you to use, in terms of time or space, but for me, it was pretty good.

Only two of us were using it regularly. I was designing and the other person is a computer programmer. In the future, I could see having three or four people working with it. If we need more charts and diagrams on a more regular basis then it would justify the monthly cost. At this point, we don't have plans to do so, but you can never say for sure.

We haven't tried to scale it. There are three team members in my team who are using this solution.

I use it almost on a daily basis but typically, not for massive diagrams. I typically use it when I have to deliver something or when I need to collaborate with peers. I expect its daily use going forward.

It scales well. One of the strong points of Lucidchart, beyond the actual tool creation of sheets itself, is the organization: the fact that you can create folders, and that you can share those folders or share sheets. That portion of it is an added bonus.

Because I work on different projects at different times, in this current project, I haven't needed Lucidchart much yet. However, in my last project, it was one of my central tools that added value in many areas of the business, because the nature of the business was heavily process-oriented. It was a government-regulated environment, which means the process is everything. So it was one of my top two tools. 

Every project is unique and the tool scales well for each one. 

It was pretty scalable. My only concern goes back to having it fit onto one page. It didn't. It seemed very rugged to try to get everything to fit on a page. It took me an hour to create the chart and it took me two hours to make it fit on the one page.

Every department head is responsible for organizing how their hierarchy is within their section. Having the ability to drag and drop people and update people, I think they're going to find it very useful because it's a live document. If people get hired and fired and we add and we grow, we can just simply add and drop boxes and stuff like that. They'll probably be using it on a month-to-month basis as we grow as a company.

I plan to use Lucidchart very heavily in the future because one of my core jobs is to implement our organizational flow across the whole company. Our company is going to grow. We're at 30 people right now and we plan to expand up to 100 in the next two years. My job is to stay hyper-organized in planning ahead. I definitely am going to be reusing Lucidchart many times moving forward.-

We have tons of projects. We are multimedia-based and we have seven newspapers. We have an online presence, websites, and stuff like that. We design websites and all that for other companies. As we develop this, I could easily see the sales department using it when we go to talk to clients, I could easily see the digital department using it for project management, and I could easily see the editorial department using it for project management as well.

I plan to expand to other users in the company. I would love to learn and incorporate. We have six people in the leadership team, including myself, and I want them all to have access to our charts and then be able to create their own charts and share and collaborate with each other so that the sales department and the digital tech department will both know who they need to talk to. Now that the company is paying to have Lucidchart and not doing the free version, I'll be using it heavily every month.

We do not require any staff for deployment or maintenance. 

The software is very outreaching. It has a lot of different opportunities that we as a company can use it for. As far as extendability, we can use that in not only our sales department that we're primarily using it for right now but also our marketing and customer service. It can extend to all those different types of our company as well.

We are a growing team. My colleagues include managers, a Scrum Master, and a business user. 

In our limited use case, we have about 10 to 12 different flowcharts or wireframes or mock-ups that we've done, so the scalability has been fine. I don't think we're a true judge of scalability, given we've only had a few months of Lucid experience.

We have four users using Lucid in our company, from platform development and product management. At this time we don't have plans to increase usage. Maybe as we add additional staff, that is something we will take a look at.

I have to admit I've hit the maximum, however, for my personal project, it might be due to the fact that I'm using the free version. I did get a warning that told me that I reached the limit, the maximum number. Honestly, it is a decent number. It's around 300, and my chart is definitely very, very big. There is a limitation, however, for the free version.

At my company, there are different teams using the product, and I don't have visibility on everyone. The product team definitely uses it. The team that uses it the most is product owners and product designers, and anyone who's really working directly in how the product flow works would use it. For example, they would be mapping customer journeys through our products - how they enter into our platform and what they do, which steps could they follow for conversion, et cetera. All of that is very much done on Lucidchart, and that's the product team mostly. There are also some engineers, probably the more senior ones that intervene more in the actual product development steps. 

The big users and the ones who installed and set up Lucidchart and promoted it through the whole company are our agile coaches. We have a whole team of agile coaches due to the fact that our engineering team is 600 people. We are a very large organization with a very complex structure, and we have an entire team of 10 agile coaches whose role is to really help the engineering department run smoothly. They're really the biggest fans of Lucidchart and the first advocates of the product.

In the case of HR, we really only used it for that one very specific project, and we will never use it again. I really wouldn't say it's due to the product at all. It's simply due to the fact that we haven't really had any project that requires that as of now. That said, I would definitely be recommending it if we start a project that would really need some good visual representation. That would be my first recommendation to the team.

I know I can add other users and stuff like that. So, that's good.

For my team, it's scalable for the things that we need it to do. We have a little bit more of a narrow focus on what we utilize it for, but I could see using it for other things besides what I actually have to use it for regularly. My core focus is delivering demos, so using Lucidchart is not a core function of mine; it's a tool for me. But it's my go-forward tool for anything that's related to process flows: needing to capture a process flow or diagram or mock-up of how we want to design an instance, for a demo in the future. I won't use anything else. And if they make me, I'll probably pitch a fit.

From what I have seen, it seems like it's pretty scalable. It must be because our company is so huge. It has to be scalable for a company of our size.

Obviously, anything that is that big can always go down too, as far as the number of users that are hitting it goes. 

In terms of extensibility, they should continue to keep integrating it with other cloud apps, the way that it's been integrated with Google Suite and Slack, as those are helpful to us.

I did not use huge processes to test its scalability. It is good for my daily use. I also haven't heard any complaints from any of my peers.

We are a team of 20 people, and almost 15 people use Lucidchart for building processes and designing and modeling.

It's very scalable because it's called a browser-based product. It is browser-based and it is a collaboration-centered tool. So it definitely is very scalable.

It is just myself and my boss who's a director of finance that uses Lucidchart. We got the product on our own. We own it. We don't get any support from IT. It's pretty much just me and her that use it to be able to collaborate and provide feedback on what I need to do.

It does not require any maintenance that I can think of. 

I can't comment on how the tool might scale but I can say that with what I have in front of me, it works pretty well. There have been no problems with scaling in our organization.

In terms of it being scalable, we have gigabytes in documents and it has always worked fine. Scalability isn't a problem.

I have a team that works under me. I am the lead business analyst and I have several team members that are continuously collaborating on different projects. My team has increased in size.

The business analysts, product team, and technical analysts all use it.

It is pretty scalable. I don't have any issues around the solution's capability.

While most of us are PC users, having the flexibility to accommodate both Mac and PC users is important because you never know who will be coming onto the team.

Everybody in our company uses Lucidchart, as there is a senior-level person involved. Right now, there is one primary user (me), as well as six to eight people who are collaborating using the tool.

It is quite scalable. We are a small department. Currently, two departments have access to it. We have only about 30 people, and out of them, only four are using it.

I am pretty new here, and we're just figuring out APAC processes and hiring new people. I will be using Lucidchart a lot more in the coming months because we're trying to figure out all the processes and the process flows amongst all the regions.

I can't speak too much abou its scalability. We could probably expand it and get multiple supervisors at my plant using it. But in terms of getting the information made and sharing it out, it's pretty quick and pretty easy. If we were to add a company server for it and 18 people working on it at the plant, I don't know if there would be scaling or server issues.

I hope we have plans to increase usage of Lucidchart. Our business is split up into four plants across the country. In the Continuous Improvement department there are four of us. We each have a license. There are plans to bring one more person onto the team. I'm hopeful that we would then be looking at getting it at least for our operations and production managers, which would potentially be an additional two licenses per site.

It could definitely grow. It has been used in lots of different industries and areas. It's a really fantastic platform that, until this company, I didn't know about. I'd definitely use it for other areas of roles at different points in my life, I'm sure.

At this point, Lucidchart is being used all day, every day. I'm probably the main person using it, but there's someone who's a transformation specialist who uses it as well, who's above me. And anyone else who is a team specialist would use it as well.

Our company has 400 employees. Only about 15 or 20 use Lucidchart. They're in software development, operational work, marketing, and one person is using it for UI/UX.

Scalability was not a problem. It did exactly what I needed to do and it didn't require that I spend several hours to figure it out.

All of us are in the project. There are multiple users.

My team consists of five people. In my company, there are a lot of people who use it. We get our licenses on an as-needed basis, e.g., if we need to run a project, then we use it. Not everybody in the company uses Lucidchart. If we need it for a project, then your credentials are created and you are enabled access. 

Only people who are a little bit in the middle management level of leadership use it. Not even our leadership uses it because they have people working for them.

We are a relatively small company of 40 people, where 10 to 15 people have used Lucidchart. There are probably eight of us who are real regular users of it, so scalability hasn't been a factor. 

Our users' job roles vary. They are mostly account management and development.

At this point, I am not sure of how scalable the product is.

Our team in Singapore is very small, so I'm subscribing as an individual user for now. I have a subscription for one year. I have recommended this solution to my wider team in our main office and they are looking into getting a team of users there. The things that I do here may also coincide with some of their charts and other types of drawings.

Scalability is very good. You can map a whole product development cycle through sales and interacting with the customer, and probably roadmaps going forward.

It is being used company-wide and I think that most people are probably using it. We have approximately 30 in the UK and in Canada, it is probably 150 more. It seems to be the de facto system and I suppose that as the company expands, the usage will increase.

I did not notice any problems with scalability.

I haven't encountered any slowdowns at all. It's a modern web solution. It's going to scale. It uses the same technology like Google and Amazon and every other cloud provider. It's going to be fine. Scalability shouldn't be a problem.

There are at least 150 people like me using it. We don't require any staff for maintenance. It's a browser app, we don't have to do anything but grant access. It's access management, that's it. Zero. There's no install. It opens in a browser.

I'm sure we will increase usage. As we grow, there'll be more licenses added. I can't imagine why we wouldn't add licenses as we gain employees.

It is scalable. As our team grows and we hire more people, it can definitely accommodate all the users that we need. I do not have the numbers, but I just know we're hiring a lot of new people, myself included, recently.

We have more than 100 licenses, and its users include the Business Development people and Sales Account Executives. I'm on the Business Development team. There are also some Customer Success Managers who get involved once a deal is closed. They need to know who the players are at various accounts. We also have a team of Sales Engineers. They definitely get involved in it as well. So, Business Development, Sales Account Executives, Customer Success, and Sales Engineers are the four groups that are the main players.

We haven't rolled it out across too many people, but we haven't had any issues so far with adding people. We're not a massive company, so we're only looking at 10 users or so, but on that sort of scale, it's not an issue.

The users are all engineers of varying levels.

I haven't really thought of Lucidchart in terms of scalability. From an enterprise perspective, if 1,000 or 2,000 people were collaborating on a particular canvas in Lucidchart, it would probably become a mess. It works well for smaller teams, perhaps a maximum of eight to 10 people. Beyond that, it's not really practically possible. Even in physical settings, we do not do whiteboarding with more than 10 people. If there are 20 or 30 people in a meeting, on a whiteboard, it becomes very messy. A small, nimble team, like an XP team or a scrum team, can use Lucidchart.

Whether we will expand our usage depends on how Lucidchart evolves as a product. If the product gains enough momentum and enough industry adoption, where more and more people end up using it, then everybody ends up using it. So it is dependent on the adoption of the product itself and is not necessarily something related to the product's features. If it provides better value through its pricing, people will start adopting it. That is the same curve that we saw with Google Suite. They provided immense value to organizations and now everybody is using Google Suite. There might be better products than Google Suite, but the adoption of Google Suite has spread. In the three organizations I have worked at during my career, I haven't seen any using Microsoft Outlook.

I would give the scalability a five out of 10. You have to download an image, which doesn't work as well.

It is pretty okay. We haven't encountered any compatibility or accessibility issues so far. 

Currently, we have about three employees who are maintaining the Lucidchart pack. They dedicate roughly one or two hours per day. Each one has a different role. One is handling development, one is handling the testing, and another one is handling the database and backend stuff. Their roles are IT manager, system engineer, and assistant system engineer. 

It is one common license. We just share the permissions. So, we have one account, and I am the one maintaining the account. I have three other people who have fewer privileges. I share the documents with them, but they can't do much editing. They can only do limited operations.

Currently, we don't have any plans to extend its usage. After three or six months, when our initial project is rolled out, we might expand it and purchase more licenses.

The tool is not scalable, per se, but it does allow the user to easily share diagrams with other parties. 

No.

I believe it is pretty scalable but I can't judge how it would perform if it was deployed on a server, whether that server was Lucidchart's or on-premises. But my initial impression is that it is quite scalable.

It is currently being used within my team only, consisting of three people, and we are all business support analysts or service analysts. I don't have the power to decide if it will be deployed further in my organization, but I would definitely recommend it. We could submit ideas of new, cool applications that would be helpful for our organization. I'm definitely going to do that.

There are 50 employees in our company who already use Lucidchart. So, everyone in the company is using Lucidchart.

Because it is a SaaS version, it should be really scalable. But that's just a guess because I haven't had to scale it, given that I have just started using it. But I will use it more and more with my customers.

I have no idea how many people are using Lucidchart in our organization, but I can imagine that all the solution architects would be using it. That would amount to 10 percent of the company using Lucidchart.

As of now, it's difficult for me to talk about its scalability. In time, I'll be running into different, more, and larger diagrams. For now, I haven't felt any kind of lag in the existing environment. I haven't had to think about whether Lucidchart would be able to handle a lot more data.

Honestly, I haven't tried to scale yet. At this stage, I manage about 35 businesses, and so far I haven't faced any problems. We have about eight licenses. 

This product is highly scalable. I didn't have the opportunity to use the presentation feature or collaborate on designing a flowchart or UML diagram or database schema, otherwise, I could have compared it and looked at the behavior.

The performance is very nice. Even when the internet speed is low, it is stable and performs well.

If you mean, the size of my board, then yes, I do remember having an issue with scalability in the past. I had to scale down all of my elements to make sure that they fit onto the board.

It has APIs and integration you can do. But I haven't tried to scale it yet. 

No.