We use QuickBooks Online for bookkeeping. We have a professional looking after our books, so I will reserve judgement on this tool.
We use FreshBooks for invoicing, and it’s awesome. It’s easy to use, powerful, inexpensive, and it’s easy to integrate your processes right to their API.
For certain person-tracking analytics, we use Kissmetrics, which makes cohort analysis and funnel tracking easy and out-of-the-box.
For just about any analytics use-case, we will eat our own dog food, of course, by using Elasticsearch and the ELK Stack, the technology we host and manage for our customers.
A huge pro with using Salesforce is that, if the functionality you seek isn’t native, there’s probably an extension or integration already available. Integration with Salesforce is pretty much mandatory if you have a person-tracking product, which is a huge swath of the application universe. In the early days, when I experimented with less expensive CRM’s, this wasn’t the case and I learned a lesson the hard way. As for cons, it’s expensive and complex.
We use Authorize.net, but they have work to do if they want to avoid getting disrupted. They’re the largest company in this space, and everyone wants to integrate with them, so that’s a big pro. But their reporting, UI, and API are all very last century. I’ve used Stripe before, and I would much prefer to use them. We may move over to Stripe sometime in the near future.
We are currently using Eloqua for this, thanks to a recommendation from our Demand Gen agency, which does much of our Eloqua administration, designing of workflows, and segmentation. I can see that it’s very powerful, but also very enterprise-y. I’m not sure I would choose it as an early-stage DIY startup.
We use Slack because it’s free, and everybody uses it. For the best collaboration, I truly believe that you have to be using what everyone is using, which at this point, is Slack. In the early days, when Slack was just emerging, I discovered (like many a tech CEO) that many on my team were using it without my knowledge. So, I just went with the flow and standardized on it. Since then, we’ve gone all-in with it. We’ve written our own internal applications to integrate with it. We’ve already integrated our GitHub deployment and pull requests, track our Twitter mentions, daily standups, and some customer alerting, all in Slack. We’re also currently on the verge of releasing a product, and one of the innovations of this product is that our cloud provisioner can be accessed with a Slack command line interface.
The pros of using Trello are that it is simple and inexpensive. The con with Trello is that while it does a good job of covering 90% of use cases, with the 10% that are more complex, it really doesn’t meet those needs. On the flip side, this is why most project management apps become bloated and unwieldy -- trying to be the 100% solution for everybody.
We also use the Elegantt (as in Gantt chart) project management plug-in for Trello.