Close.io also fits nicely in that category as well. We actually started as a more typical Silicon Valley startup but over the last few years transitioned to now being a fully remote/distributed team (profitable with $X million ARR).<p>What I miss about being in-person is the unplanned conversations on the way to lunch about a problem or feature idea, that otherwise may not have happened at all.<p>But overall being remote has allowed our team to have better work/life balance, have recruiting/hiring advantages [1], support our world-wide customers better, and lead for more distraction-free work.<p>[1] We're currently looking for 1-2 senior engineers: <a href="http://jobs.close.io/?lever-source=hnsaasremote" rel="nofollow">http://jobs.close.io/?lever-source=hnsaasremote</a>
I know this goes against the usual attitude about remote work around here but...<p>That flow-chart at the bottom is hilariously true. I've been a part of remote work as both a manager and an engineer, and this is exactly how it is because of different locations, the lo-fi aspect of existing remote collaboration tools, and the activation energy required to communicate more often (and if you're in different timezones, good luck to you!).<p>If you're an engineer that wants to really understand what you're trying to build and why, or if you want to be part of the problem-identification stage rather than just implementing someone's specs, this type of arrangement will drive you insane.<p>Some engineers are perfectly happy with a detailed spec though. For them, I completely understand the lure of remote work.
Incase anyone is curious or missed this like I did the first time around: the metric they are using is ARR.<p>Which to be fair is not a whole lot of money so not having an office makes sense. Once you pay for servers, marketing, and payroll you're probably not left with much.<p>But also to be fair, most of these companies are quite a bit more than $1 million ARR.