Don't forget that any position that deals directly with clients also takes the brunt of their wrath if they're unhappy. As a non-dev in a SaaS company, I was the primary point of contact for a number of clients and if anything went wrong, I was the first person to hear about it. Clients are not usually pleasant when something is broken or if their project is running late.
My advice is to not underestimate the toll that can take on you. Trying to convey the importance of a specific item for a client to a developer is difficult, too, particularly if the dev is already pretty busy.
As someone who uses Buffer (free version) on a regular basis, I have to say that I'm fairly amused that it appears as though none of the commenters here have actually read much, if anything, about Buffer. They have quite a lot of information about corporate culture that would have answered some of the questions and concerns posted here. Further, they're a distributed workforce (which I don't think anyone picked up on -- this explains emails vs. face to face conversations).
My advice is to not underestimate the toll that can take on you. Trying to convey the importance of a specific item for a client to a developer is difficult, too, particularly if the dev is already pretty busy.