We make a lot of custom stuff for analytics because we care about them so much on our end. A lot of our tools are homegrown because we are building our own solution to give out to customers, engineers and so on.
We use Kibana with our custom tools to visualize a lot of data about metrics, miles, how many hard brakes happen, which customers have high scores versus low scores, etc.
We were using Zoho before Salesforce. When we were smaller, we used Asana as a “CRM” and then moved into Zoho for collecting leads, prospects and accounts. As our customer success team and business development teams grow, we find that more people are comfortable with Salesforce. Salesforce is also much more feature rich, so it made sense to do the switch now rather than at a later point in time.
We used to have our blog on Tumblr but we recently have moved to WordPress. Tumblr was good and easy to set up and get going. But as our needs and requirements grow, the blog needed to be more branded and easy to customize, so it was a better thing to move it to WordPress. We constantly post about driving safety on our blog.
Paul is our go-to guy for customer success and he has used a bunch of tools. He brought on Zendesk, and it has made it easy for our customers to get in touch with us. It allows customers to find FAQ and support links or message us when they have issues for quick resolutions. It also connects back into our engineering team so they can respond to specific technical issues. It’s all very streamlined with the integrations we have on top of Zendesk.
We use MailChimp for transactional emails that tell our customers/drivers about how things are going and how they are doing. We send messages to them about how their week has been, whether they’ve improved or not, and set goals for the next week. Because we are building a B2B business we don’t end up using a lot of marketing tools. We don’t do marketing campaigns by acquiring users on Facebook or Google. We get inbound leads that we curate with our business development team.
We use Google Apps quite extensively. Our documents go into Drive, and we also have internal wikis. Wikis are good for organizing information--but not good for writing. A lot of docs get written in Drive and are then shared in wikis for easy finding.
We did a whole scale move from our inboxes to Slack. All of our conversations happen on Slack now and the speed of communication has increased dramatically. We have our own document internally that describes how to use Slack and best practices.
Zoom has an integration with Slack that allows us to initiate video calls in Slack.
We use AWS for all of our servers and deployment. It’s probably the biggest thing we use, and we use a variety of things on AWS like Kibana, Elastic Beanstalk and SQS mechanisms.
Zendrive is a platform for driver behavior monitoring and improvement. The platform is allowed for anyone to use and build applications on top of. We help companies that have a lot of drivers (ride sharing aggregators, car sharing, traditional fleets). All these companies are using us as their own app to keep track of how their drivers are driving on the road and help to improve them. We are mission driven to make all roads safer. Zendrive is inspired by technology to curate information and insights for drivers to help identify behaviors that are risky and dangerous, and then become better, safer drivers. Better drivers lead to less collisions.
Asana is great for quick note taking and writing down tasks. It works fast and is very easy. A lot of our engineers use it for their task tracking.
We use JIRA for bug tracking, backlog, customer issues and sprint planning. JIRA is great at what it does, but it is somewhat clunky and difficult to use (to some extent).