There’s no need for us to change from HipChat to Slack. One, HipChat is cheaper. Two, we have all of our plugins for deployment and customer support setup to feed in and out of HipChat. It works just fine and we don’t need to change.
Our marketing guy uses SimilarWeb a lot. He gets interesting statistics and breakdowns of competitor spend and traffic, and to see what sites they’re linked too.
We use Ghost over WordPress for blogging and content. There’s an emotional side to it for us--it’s worth supporting Ghost (which is built in Node and not PHP) and the people building it. We have all of our backend development in Node, and we want the same tech stack across the board.
We obviously use Fluid UI to design our product. We do daily hangouts using the video calling feature in Fluid UI, and do design specifications and prototyping in our app. When our designer was finally able to cancel his InVision account, we shared a few beers :)
We use Intercom for all of our marketing automation and customer support. They started in the same co-working space as us, so we’ve known them since they were just a tiny company. We originally were using MailChimp until their fees for the size of our subscriber database got too high--Intercom were charging less for the same thing. Intercom has evolved and added customer support features, and we’re using that now too which is great. They’re not so cheap any more though :)
Our Sales Team is very happy using Yesware. We get pretty good metrics off it: open rates, response rates, etc. Yesware makes it easy to follow up with warm leads.
We use Fluid UI a lot for our daily stand ups and design spec’ing.
I would prefer to be on Stripe, but there’s an inertia and risk associated with switching payment providers. Realex (an Irish provider) does end up being slightly cheaper than Stripe, but it came at the price of 3-4 weeks of dev time setting it up versus the ease of Stripe.
We use ZenHub for Kanban style stuff. It’s plugged into GitHub and everyone, including our marketing team, uses it. It’s not difficult to learn although it might be a little more complicated than other kanban boards. We can on-board people pretty easily, even if they don’t have a technical understanding of GitHub because they only need to see the kanban. The advantage is that they have access to all the information on progress in the company in one place.