Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
The work was very much a success. We went over budget a little bit. I suspect that’s normal and would happen anywhere. Tivix worked with me to make sure it wasn’t company-crushingly over budget. Everything was delivered in the way that I wanted. The result was very user-friendly. They explained everything well to me. The website has a pretty clean frontend design. The deliverables included a road map of what they did. We had some questions afterward, and they’re generous with their time in terms of answering them. It’s definitely a very good experience. I’m one of the few proponents of outsourced development, especially building early products through this channel, because I actually had a good experience, whereas most people in my world have a pretty negative experience with a lot of cutting corners. I thought they did a great job. I can’t compare their productivity or performance to another company since I’ve never used a different provider.
How did Tivix perform from a project management standpoint?
We used Basecamp and Slack. Slack is where we spent the vast majority of our time. I don’t think we did anything over email. We had video calls. I live in Los Angeles, and they’re in San Francisco, so the entire team is onshore and working out of their office. I was there about 10 days cumulatively going through things, which was really helpful.
What did you find most impressive about Tivix?
Their lead developer/CTO spent a lot of time with us. In general, his involvement was crucial as an access point and a go-to advisor. I would suspect that’s unique in a shop that has a number of different projects ongoing at the same time. I thought that was really useful.
Are there any areas Tivix could improve?
My only constructive criticism would be beefing up the transition aspect of moving the work to an in-house team. We were asking for help a lot, so it would be an interesting package to offer to have a live document or a day where they could implement the transition. They were generous with their time on the phone. No 2 developers are the same, so we had a lot of initial confusion because the documentation wasn’t built for people who don’t do things the way they do.
What tips or recommendations could you share that might increase the likelihood of success with Tivix?
Come in with a defined scope, very limited functionality, and an understanding of what functionality is needed because anything open-ended won’t turn out well.