What was the scope of their involvement?
Most of our business was done through the Magento site, while the WordPress one was a smaller sister site. In terms of actual website features, we were using AJAX Cart for the checkout process. We have a one-page checkout, rather than the native Magento accordion style, and are currently using GoMage Light Checkout.
The 1.9 version of Magento was our first tackle at having responsive functionalities natively. We were ahead of the curve, relative to our industry.
We had one main point of contact. We used Redmine for project management and had a few different people responding to tasks. I and another person from the company worked on the project from our side.
How did you come to work with Q Solutions?
I attended the Imagine Magento conference, actively looking for a solution partner or at least someone to help us with this change. I had also done some work with Jakub at a previous company and knew that he had good responsiveness and a highly coated, full-stack scope. We eased into the relationship, instead of going on a whim.
Q Solutions is based outside of the US, but they actually stand within the local pricing ballpark. With other solution partners here, we were paying more for billable hours rather than delivered goods.
What is the status of this engagement?
The site went live around October of 2015, after a 7-month development run. The timeline isn’t really reflective of the scope. Both of our companies had small teams at the time. I also worked with another solution partner in 2016, and we got 2 tasks done after spending 5 to 10 times what we would have spent for Q Solutions.