Could you share any statistics, metrics or other feedback from your work with Clavax?
Our site is different from sites like eBay, where everything is happening at the interface between the site and the user. Our website is more driven by what is running in the background by talking to our devices and putting material in databases. The site that Clavax designed sends out text and email messages to all the users, depending on the data that it receives from the devices in the field. All this is going on in the background 24/7. Ultimately, there'll be thousands upon thousands of units connected to this site, but it will just perform the same function.
The only interaction the user has with the front-end of the website itself is just to add new devices to their account or change their credit card – things like that. They can monitor information on the website and see historical data, but they pretty much can do the same thing on their phone apps, which is what most people are doing. Once they've signed up on the website, they just use the app or just go to the text messages they get on a daily basis. Ultimately, thousands upon thousands of devices will be connecting to the site.
How did Clavax perform from a project management standpoint?
They were Good. Because I'm in engineering, I knew about the details of the project from the beginning. I knew exactly what I wanted to do and how I wanted the site to function. I defined the majority of the scope of the project before it even started. I didn't have to rely on Clavax to figure things out. They did have to figure out how they were going to get the project done, but as far as the details of how the project was going to work, that was something that I did upfront. I gave them as much detail as I could.
Working with them was not a problem at all. They have several programmers and a project manager here in the United States, but our project manager was a nontechnical person, so she would ultimately have to talk with the people in India anyway. Clavax allowed me to work directly with the developer working on the project, so I didn't have to get second- or third-hand information. I liked working directly with the developer himself because I could resolve problems right away. I could send him an email directly, and the next day everything would be resolved or the problem fixed.
Clavax didn't require me to go through a project manager. I was able to work with the developer directly, which because of the language barrier, is not always the case. In Clavax's case, I was able to work with our developer directly, which was very helpful.
What distinguishes Clavax from other providers?
I got several quotes from American companies versus offshore companies, so definitely from the standpoint of economics, working with Clavax did save us a considerable amount of money in developer costs.
Is there anything Clavax could have improved or done differently?
The one thing I actually had talked about to both their project manager and owner, was to suggest to them the potential importance of having developers here in California to take care of some of the needs that require them to be in the same time zone. I understand that they would have to charge at a different rate for U.S. developers. I suggested to them that the only thing that was a hurdle for us was the time difference, but we knew this was something we were willing to deal with going into the project. The time difference was sometimes a problem since I could only talk to our developer either late at night or early in the morning my time.