Originally published on the Close.io blog.
In creating Close.io software for salespeople, we rely on a number of other startups and services to do what we do. While there are alternatives to using each of the following, we have chosen them for specific reasons because we think they’re the best.
The common theme is that these services allow us to move faster and have better insight into our business. We could live without any of them, but it would mean slower iteration and less innovation.
Powers our app
Plivo – Powers the backend telephony behind Close.io. We chose them over others like Twilio because of their low level sip telephony support, as well as their commitment to call quality.
AWS (EC2, ELB, S3, CloudFront) – Let the big guys handle our server infrastructure. Best AWS decision we’ve made is to host out of Oregon instead of the east coast, since almost all of the significant downtime AWS has had in the last year has been in Virginia.
Heroku – Used to host our static Close.io homepage because there’s really no simpler way to get a Flask/Python app deployed.
Technical insight & debugging
New Relic – Great way to monitor app server performance and server health. Expensive but worth it.
HockeyApp – Mac app crash reporting
User analytics & retention
Customer.io – Used for automatic drip marketing emails. By plugging in our Google SMTP credentials to send from, our marketing emails automatically get logged into Close.io so we can see all emails sent/received to our contacts.
Mixpanel – Used for user + event tracking within our app
Google Analytics – Used for overall traffic analysis
Tip: best decision here was to use Analytics.js which allows us to easily try out different analytics services with only a single line of code changed.
Campfire – Used for both internal team communication (and integrated with GitHub, New Relic, CircleCI, Close.io, etc.) as well as the “Live Help Chat” link from within our app where we provide technical support and get feedback from customers. While it’s been neglected, we like using the Propane app compared to the web client.
Olark – Used for “Live Help” on the Close.io homepage. Pops up in the team’s IM client when someone needs help.
Google Apps – Easiest way to get a team going with email, calendar, etc.
Stripe – A modern API for credit card processing.
Sales (& Telephony)
Last but not least, we eat our own dogfood by using Close.io for our sales process of keeping track of all customers and prospect data, and calls / emails with them.
The section that I think is missing from other similar blog posts as this is “what’s missing?”. Here are some areas that I think need more startup effort.
- Better user analytics. Mixpanel (and others we’ve tried) are good for some simple analytics but just don’t allow us to easily answer many of the higher-level questions we’d like to answer about usage (“which users fit X usage patterns”, “how many people fit Y criteria over time”, etc.). The data could be there, but the backend intelligence isn’t. Improvements in this space could really help both the sales process as well as product development processes.
- Better web integrations. We’d love to plugin a service that helps us help our users get their existing data into Close.io from many of the existing services out there.
- Better financial software. Stripe is great, but it’s pretty low level. For anything slightly complicated you still have to build your own system of database+code to manage subscriptions and invoices. Perhaps a combination of an open source library + an accounting/reporting service is needed.
- A non-Google email/calendar solution. There seems to be a lack of great alternatives for startups.
Any other great services we should be using? Tweet us at @closeio
– Phil Freo (@philfreo)