Could you share any statistics or metrics from this engagement?
When we started our work, we were essentially going through the process of coming up with a minimum viable product. We used Google Analytics, as well as our own customer analytics solution built by Kanda Software, in order to assess our position. Based on that information, we were able to refine a beta version.
There was one key event that was crucial to the direction of our company, namely our partnership with a frozen yogurt company. They decided to give away ice cream to people using our platform. This happened during wintertime, with -2 degree Fahrenheit weather. Giving out free ice cream was a nice experiment in this context. They were willing to do this in exchange for foot traffic to their retail locations. Additionally, we partnered up with another company that owns half of the billboards in Time Square. They were very interested in the technology developed by Kanda Software, and we were able to persuade them to give us free advertising in order to prove that the product would work in the wild. We made our campaign, running it for five minutes every hour for one week. The analytics of this trial were amazing. We were able to track where people were browsing these advertisements, how many converted to getting offers, and who actually went to the retail locations for the company, redeeming their offers. We proved that the whole system for conversions was actually fulfilling the task of users getting the product.
How did Kanda Software Development perform from a project management standpoint?
The work that was scoped out was always delivered on time, unless there were unknowns that presented themselves. We expected this type of evolution when working with third-party APIs [application programming interfaces] and software. It increased our scope, but didn't necessarily block the project. We always made sure that unforeseen elements were accounted for so that, when we were doing particular sprints to build our product's features, we could account for potential blocking and an increase in scope. Kanda Software always made sure that we knew what to expect.
They used Asana during our development as well as other Google tools, such as Docs, through which multiple people could edit and comment on the work.
What distinguishes Kanda Software Development from other providers?
The impressive part about them is that they are able to improvise when working with unknowns. When the project required fast iterations, during its proof-of-concept stage, they proved to be very resourceful and were able to build tools and code, which got us to the goal of having a functional result. Once this was done, they knew the difference between hacking code in order to make a working product, versus making a scalable platform, which can be maintained with little technical depth. Many developers I've worked with don't know how to make this distinction. When building a proof-of-concept, you won't necessarily spend much time developing stable code that can be scaled. This very much depends on the current goal.
Is there anything Kanda Software Development could have improved or done differently?
Looking back at the project, there are tools that we could've used in order to track the development better, but those tools weren't available to us at the time. Since working with Kanda Software three years ago, much has changed in the tech world.
I remember that they were always on top of new technologies that could document, project manage, and track progress. I haven't worked with them recently, but I'm sure that they're using better tools to do the job. In hindsight, if I had to do the work again, those would still be the tools I would have chosen at the time. I have no complaints about their customer service.