How we bootstrapped a $1M ARR email client

I was a paying customer for a while. The web-app was super snappy and the ui (minus usability and simplicity and minus sane defaults that "just work") design was state of the art and reminded me of apple or metalabs in some regards (reading about them also being in canada is especially interesting).

BUT i had to leave because the usability and amount of settings and exact reasonability about the workflows and data was just not doable for me. Especially sharing with my PA and managing a small team gave me nightmares. I would maybe setup all the preferences one day and understand what my assistant could see and do at what point and what "archiving" exactly meant in which situations. But after a few days it was all a blur again and i was just anxious about using this thing without accidentally missing messages or losing track of what was going on. They seem to have build every feature on earth and support any workflow for teams possible but without the guide, visual feedback and structure to be effective.

Going back to stupid gmail was just relieving, because it was possible to reason about even though it felt ancient in comparison. The fact that i had to write them to delete my account instead of just being able to do that in settings made me really angry back then because i had no idea it was just 4 people, i assumed a team size of front.app or intercom.

A major problem of email team inboxes in general (missive was better than others but also had issues) is the sync with gmail, they all do not sync back in a way that you could go back without losing significant metadata and labels. I know this is a hard problem but especially front.app gives me the feeling they also use this knowingly for a hidden lock in.

"On finding customers

Our initial users were mostly early tech-adopters looking for a new innovative cross-platform email client. We found those by posting on different tech discovery communities like ProductHunt. Those early and mostly solo users wanted a different set of features than

what would ultimately become our real paid customers: small and midsize businesses.

This tricked us for a while in a race to build more and more features not so consistent with our vision. For instance, we started offering read tracking as it was one of the most requested features of early adopters. Many users upgraded to a paid plan for this alone; they weren’t interested in any of the collaborative features of the app. Those soloish users were churning at a far greater rate than real teams and they were requiring far more customer support/server resources per dollar earned. At some point, this reality sank in and we decided to focus entirely on teams. We ditched read tracking as it was a magnet for such misaligned customers. Our churn rate plummeted.

The hard-learned lesson: have the courage to say no."

It’s great what they did, very impressive and excellent product.

However, the article is a bit misleading, mainly for two reasons: “bootstrapped”, and “without spending a dime on marketing”.

They “bootstrapped” by financing the company with another profitable company. That technically means they were their own investors, but they weren’t limited only to the revenue that their email company was generating.

They didn’t spend “a dime on marketing”, but they did spend time promoting their product on several platforms, including producthunt, and they do have a blog (which is where the article is hosted), and they do have one full-time employee (out of four), in charge of marketing. So maybe what they truly meant is that they didn’t pay for advertising, but that’s different than not spending money on marketing, which they did, and in fact you could even say that it’s probably a significant part of their budget (given one of the only four team members is dedicated to marketing).