For the initial standup, Zudy was great in that regard. From signing contracts to having environments that stood up was probably three weeks total. That was back and forth, coordinating calendars, and everything else.

There are a couple aspects to it that work really well. Most low-code development platforms enable you to get something built relatively quickly, but when you couple that with the strong business analysts that Zudy provides, they tend to ask all the right questions when you are having those initial conversations. They quickly get to a minimal viable product that will allow the organization to react. Typically, it's like a week or two from initial conversation to having a minimal viable product, and then you can iterate on that. Just the fact that things are moving that quickly, I think it gives the organization a great deal of comfort. It is a dynamic that really improves customer satisfaction. It is not like a black hole, where you have a conversation, months go by before you see anything, and you are not given anything to react to.

The initial setup was extremely simple. It may be different for enterprise app customers, but the setup was no big deal for us.  Our mobile dog product team received our log-in credentials, and we were good to go.

It took about three months to stand up all the features that we wanted in the sales employee portal. The first few features were developed in a matter of weeks, but as we identified different business requirements that we realized we wanted to enable for the field to use, we were able to quickly identify the requirements, build on the module, and tack it into the delivery workflow. So, the overall delivery of the portal, while stretching out over a course of several weeks, was actually a stack of different, smaller rollouts that each only took three to five weeks to develop.

The initial setup of Zudy VINYL was straightforward. We certainly had some more senior IT folks in the room to help get us launched, but in terms of big-picture and the strategy for what we needed and how they were going to build it, it was very clear and very straightforward: the data they needed to build, the results and information we wanted to get out of it. We sat through a couple of workshops and it was very crystal clear and very productive and the end result was exactly what we talked about.

Typically, with anything we do in our company, we do small-group rollout, small-group testing, and then large-group rollout. That's exactly what happened. We had a core team that was involved in the build. We had a slightly larger team that was involved in beta testing, using real life examples in our business. And then we had a more formal rollout that went out to all the applicable folks in our company.

From start to launch of the Zudy platform, it took seven months. Our core build team that was involved included about six of us. For maintenance, typically it's our core team. For things we can't figure out on our own, the Zudy folks have been terrific in terms of customer support and helping us nip those issues and solve them in pretty rapid fashion. We've been really happy with Zudy's services.

The setup was pretty easy. Initially, they did the setup for us. They hosted it in their own AWS instance. And somewhere around 12 to 18 months ago we moved it over to our own AWS instance, and that was fairly seamless from what I was told. We really haven't had any issues with it at all.

The technical setup was pretty clean. We were up and running pretty quickly. We got in and they merged everything into our single sign-on process really well. There were no issues that I know of.

From what my people have told us, it's easy to learn. We've had some Finance people learn it, as well as some people on the IT side.

Due to time constraints, we utilized Zudy's internal development team to provide the base setup, application details, and launch at AWS. It was extremely straightforward.

The setup was very quick. We actually delivered our first pilot within two weeks. In that time, we had the first application use case running in a few stores.

Regarding the setup itself, it took only a couple of hours to install it.

It's very easy to learn the platform. We have business users who have taken on roles now where they maintain and make changes to the platform. You really don't need to be a programmer.

We didn't really have to do a setup. The vendor came in and they did the install for us. It probably took about an hour. It wasn't very complicated. We just had to provide them with a Windows Server.

We really didn't need an implementation strategy. We set up a development server and then a production server, which was pretty close to a mirror of the development server. That way there is a way to take applications that you develop on the development server and promote them to the production environment. Once we had that path set, nice and clear, that was all it really took.

On our end it involved one or two members from the network operations team.

There really hasn't been too much maintenance going on with it. It's more like a set-it-and-forget-it. The Zudy team pretty much takes care of the maintenance for us when it's time for maintenance, but the application never crashes. It's up and running when we need it.

The setup of the initial [deployment] was extremely straightforward. Everything that they said they did, they actually exceeded.

Getting access to it, once we agreed and signed off on the dotted line, was within an hour. Then we started working on some training that we needed to do to get familiar with the platform. That was delivered that same day. We wanted to make sure on our end that we understood what we were getting ourselves into. As a team and staff we completed our training to get familiar with the Zudy platform. Within 48 or 72 hours we were done with what we needed and we started building out platforms and applications.

I can't say the developers had an issue with any development challenges. 

My staff is small. There were three of us involved in the deployment. We're a team of three but we act like a team of 30 now, because of what we have access to.

Installing and getting Zudy up and running was very easy from an infrastructure point of view. What was unique about us is that we were their first Dynamics AX integration. They had not done AX before, so it took them about three days to figure out the business connectors and the data model, and from there we were rolling.

The initial setup was very straightforward. They keep me aware of anything complex, but I do not have to expend any energy to deal with it.

They got a good demonstration application done for me in two months. This allowed me to get funding so I could survive as a business. The application was good enough to get customers interested. I like to say, "I would be working at Walmart if they hadn't been successful."

Today, everything is in the Zudy space. We will then migrate it over into our cloud space, which they are capable of doing. We will keep them as our prototype vendor; whenever we are working on new things, they will do that for us. Some of the actual running systems, we will probably keep it on VINYL until we run into something that we can't do.

The initial setup was not that complicated. It was basically no more complicated than setting up any web app would be. I wouldn't say it was any more or less than what you would expect.

Their services are excellent. They typically provide a team of resources to get the environment set up and help build your first app.

I was starting off with an enormously complex ask. There were a lot of things that I was trying to accomplish, and with a deceptively simple front-end interface. They really understood what it was I needed. Even they underestimated its complexity a little bit, but they weren't so far off. Other people were way off. It was a complex thing that we were able to set up and I'm very happy that we were able to set that up. It had some complexity to it, but it was, overall, relatively simple, especially for the level of complexity that I was trying to build.

In terms of the staff that was required for the deployment and the integration, we did hire their development team to do that. I was working with two guys, mostly. They were able to pull off stuff in much faster times than what I was able to do with my previous team, and with the team before that, and with the team before that. We've been able to accomplish a lot and I'm happy with that.

I'm able to get in there and dig around and understand. I'm able to look at little micro things and say, "Oh, wait a second, that one particular column on that one particular table is not in the right spot. We have to move it because of some problem I'm going to have a year and a half down the road." The transparency has been great, and I've been able to do it on a minimal amount of staff.

The number of people that are using Zudy VINYL, in a hands-on sense, from the back-end perspective, I've got four guys who are working on different things. From a customer perspective, we're still early days with the launches, but I'm at about 20 users that have been on it. They've been super-happy with it. The fun part is that I built something that used to need 20 years of construction experience to be able to do and my best beta-tester is my mother. I love her, but she is terrible when it comes to computers, and she has been able to use it as a customer, and that's always been my goal. If mom can use it, anybody can use it. It's been exciting to be able to get it to that ease of use and simplicity.

The initial setup was straightforward. The data connections simply pull in data, and it took five minutes to start building an app.

It's easy to understand the basics and learn from other examples. However, it takes a bit of experience to know everything that it's capable of doing.

The initial setup was relatively straightforward and Zudy helped us scale how large of a system we should have, what type of license would be appropriate, and really ensure that it would grow with us without having to completely re-engineer our setup.

The initial setup is okay. But we needed Zudy staff to guide us on the first setup we did. We communicate with them to help stand up servers on our side, new servers like sandboxes and the like. In such cases, we will generally get help from the Zudy team. 

Overall, the setup is 50-50, complex and straightforward. The deployment took about four hours. Implementation of VINYL depends on domain. 

I wasn't part of the initial setup so I'm not sure what steps it took to get there but I think the complexity of the setup depends on what you're using it for. We've got a lot of different data sources coming together from a lot of places, so I imagine that getting that all together was a notable effort. We definitely had to work through permissions, allowing access on our server, allowing access on their server. There is a good amount of setup. I don't know how long it took.

The initial setup I came into my first week with the organization, so it was already ongoing. I'm not sure I'm a good perspective on that. It seemed scattered, but it may be our organization and not theirs, and it could just be the data.

While this tool was in-house before I started, but a typical application build takes a matter of weeks. 

Our company uses agile methodologies to quickly prototype, build, test, and deploy our solutions.

I wasn't involved in the initial setup but to my understanding, it took a little bit to get started. Once they got the ball rolling, it was pretty quick. It was just a matter of trying to connect to our many databases and get them set up in a way that's usable, because there are a lot of edge cases on our end. But once you developed those it was super-easy to do the rest from there.

I haven't gone, but I know that Zudy offers free training in Boston for this solution, which I think is excellent. Maybe that's just part of their way of getting their name out there. I am planning to go in the future. I imagine it's a great resource as well, on top of the manuals or the tech support or the "how to's" that they provide.

The initial setup was straightforward.

The initial setup was straightforward, not complex at all. We're not delving into the learning of how to use it yet. We have somebody in-house who is trying to learn it, but we have other projects going on, so it's taken a back-burner. But, as I said, its accessibility is very easy.

I came into the project after it had already started, so I only got, if not end result, the "first draft." It was pretty clear. There were some things that we suggested be changed and they were super helpful about that.

I was involved in getting it to go live. We had a lot of logic to build into it, and that's when I was brought on, to find ways to work with them, to figure out how to go from what's in our system to what the actual correct numbers should be.

It was easy to learn to use. What they present is final. You don't have that many ways to use it. It's not like a major ERP system where you have all these options, all these different menus that you can go through. What's presented on the screen is a report. For me, it's pretty intuitive if I want to change the date range, if I want to change what customer I'm looking at. I don't think anyone else has mentioned to me not finding it intuitive or finding issues with the navigation. It's a pretty straightforward tool, so I find it quite easy to work with.

I was not involved in the day-to-day of the initial setup, therefore it is hard for me to comment. However, I know that we were successful with it. Probably any limitations that we had at setup were due to some of the friction that we have internally in our network.

The setup was a little complex, but not that bad. I had Zudy specifically here. I was working with two of the developers and they were with me every step of the way.