Fabric shows us everyone that clicked on a tweet and installed our app. We use it for user acquisition campaigns on Twitter.
If we build an update and want to distribute it, Crashlytics lets us do that easily. TestFlight doesn’t let you do that anymore after Apple acquired them. Crashlytics replaced TestFlight for us.
When we started out, and our team was just the founders, we used Evernote a lot. We still use it like Slack, but without the chat feature. We use it for sharing important links, information, snippets and PDFs.
The development team uses Slack because they are the only team spread out across different cities. The user support team works together in person, so they do not need an internal communication tool at this point. Right now, the only overlap is that the head of user support has been invited to Slack to see bug tracking and bug fixing information, just so he has a heads up about what’s being identified, and he can tell users when certain bugs will be fixed. My partner, the CTO, actually complains a lot about Slack because it doesn’t render code properly.
We are using our own custom ad hoc system for customer service. Users can contact us directly through our app, and the team gets an email and multiple people can reply. All of our customer feedback is put into a JSON database. We use the Alchemy API to run and scrape that database of feedback to run sentiment analysis, so we can see how users are feeling about a crash, for example. We can automate flags in our database to flag if sentiments about something are below a certain level. Then I will automatically get an email or text.
We chose Zenefits because a former colleague of mine was in Y Combinator with the founder of Zenefits, and they reached out to me when they were in a really early stage. So when we got seed funded, that was one of the first companies we reached out to for HR benefits. We have a love/hate relationship with Zenefits at this point. For new employees, the mobile onboarding is excellent, and easy to use. And their reporting tool is great. We got our medical benefits through them, and they need to get better at dealing with insurance providers. I don’t have time to spend on HR and the bureaucracy of dealing with providers, and they need to be better at dealing with all of that for super busy entrepreneurs like me. They’re also not connected well enough with payroll providers, so we’re having to cut lots of manual checks.
We’ve integrated a lot of our stuff to OpenShift, which is an AWS alternative. They allow us to run different types of programs on the back end in interesting ways.
For product, we’re hosted on AWS.
Our main social media activity is on Twitter and Instagram. I use Buffer for scheduling tweets. But at this point, we haven’t gotten to the point of sophistication to need to tie in messages across social media channels, so we just mainly use the direct websites. We communicate with potential investors and press via Twitter, and our users via Instagram. And everyone dislikes Facebook, so we mostly ignore it. We are looking into ads on Instagram in the future, and we’re really hoping we do not have to go through Facebook to advertise on Instagram.
We started out using Twilio for SMS, but we ended up moving to Plivo because their customer service by far dwarfs what Twilio offers. Sometimes companies like Twilio get so big, things like customer service falls by the wayside. Plivo’s reporting is also better. We need to know that SMS messages were delivered, for FCC reporting, and Plivo has much better reporting that messages were sent.
We use MongoDB for databases hosted on MongoLab.
Pusher is a great real-time asynchronous backend server.
We’ve also built our own interactive roadmap, and everyone runs a form of agile project management.
We use Pivotal Tracker for sprints and backlogs of different features and issues. We have Pivotal Tracker organized really well, so anyone can jump in at any point and see what is going on. We use it for both product and project management. We chose Pivotal Tracker because we had used it before at other companies. We had also used Trello in the past, but Pivotal Tracker is much better for people working in software development. I’ve used JIRA a few times at various companies, and I find that I like Pivotal Tracker much better than JIRA. And my partner dislikes anything from Atlassian, including JIRA, so we’ve stuck with Pivotal Tracker.