So far, how do you think that Clarity Ventures has performed?
Looking at the entire 14 months we’ve worked with them, we’ve been very pleasantly surprised with them. Having seen a lot of single developers at the time, and most of the time having them as the one source to tell us how long certain line items would take and whatever it might be, the quality of work we were getting wasn’t too good from the previous developers. Also, the delivery timelines were often extended. They’d be working on major projects, and the timeline would continue to move over three or four months. In our previous development cycles, it was just too slow for us.
Moving on to Clarity, we expected that we could expedite some of the development. However, we also expected that it would come at a much higher premium, because we’d be paying for hours and sometimes three or four developers working on our project at any one time. What we did find is not only was our development able to be released much more quickly, but also, we often didn’t have to bring in multiple developers on any one project. They would have a single developer. However, because they were tracking each of the hours so meticulously and making notes on it, we found the quality of those hours were much better than we were getting when it was a single developer in-house. And that partly is on management that was overseeing the in-house developers. But it’s also from the fact that with Clarity, we know that although they have a single developer working on any one project, they do go through a coterie process. They do have to document everything within the code and document the activities they participate in. So they’re held accountable to that.
There have been instances where we might have internally questioned someone in the house that a certain project with Clarity took. Ultimately, we were able to get down to the granular form—look at each individual hour, look at everything that happened. At the end of the day, if Clarity felt that, yes, after their code review and their time review that it did go over budget, they actually made up for that.
One of our main projects was the mobile app. After a full review, the timeline was extending and part of it was because internally, our staff members were changing our mind on some items. So Clarity would fully build one area and then we would change our mind and say, actually, we don’t really like it that way; let’s do it this way. So a lot of the extra time was spent in sometimes changing directions, and it wasn’t the fault of Clarity. It was because of us doing it internally.
One main developer that was working on the project left mid-project, and so it got transitioned to another developer. And in that time, during the transition, we felt that the quality of hours during that transition time weren’t of the quality that Clarity had been delivering. Ultimately, after those meetings, Chris at Clarity stepped up and admitted that he felt that the time spent there wasn’t of the quality that they expect internally. So, they credited us hours for that time.
As a whole, we’ve been very impressed with the amount of output and work that Clarity’s been able to provide. Previously, whenever we did releases, our customer care center would instantly get a giant influx of calls for different areas of bugs because the previous developers weren’t doing good testing. With Clarity, it’s very rare that we have a post-release bug. If we were to have a post-release bug, oftentimes, those bugs are resolved within about five to six hours. They’re able to release and we’ll be back, fully up and running in a certain area that might be throwing the bugs.
We’ve been impressed, and in the times that we’ve had any issue whatsoever with Clarity, they’ve been very open to sit down with us and go through the review process. In the few times that we’ve done it, they’ve actually come in and said, you know, we agree that this wasn’t what it was supposed to be, and they’ve actually credited us for those hours.