3 ms·

Email though? Except in pre-sales, I can’t imagine anyone using an email heavy workflow in 2025. In my personal life, email is only for one way transactions.

Email though? Except in pre-sales, I can’t imagine anyone using an email heavy workflow in 2025. In my personal life, email is only for one way transactions. Where some company is sending email to me or spam. Even the one newsletter I subscribe to - Stratechery is available as a podcast and an RSS feed. In my professional life, of course all internal communication happens on Slack (700 employees) and even in consulting, the first thing we do after a deal closes is either invite customers to our Slack or ask to be invited to their platform. This is a solution in search of a problem.

isaachinman 1y ago
Actually, the complete opposite. We're building this app because we need it ourselves. Turns out a lot of other people do too.
- scarface_74 1y ago
  What’s the sales pitch for using email in 2025 for communication aside from sales?
  - isaachinman 1y ago
    No sales pitch at all. USPs are on our homepage. If it doesn't appeal to you I get it. Different people have different needs. There's been a massive influx of "new gen" email clients in the past year or so. That said, we're not an "AI product".
    - scarface_74 1y ago
      [flagged]
      - jamiek88 1y ago
        [flagged]
        scarface_74 1y ago
        This is a site run by a firm that encourages startups. What company has no idea how to pitch their product?
      - isaachinman 1y ago
        You are indeed quite rude, but I'll give you an answer. The selling point is that it's IMAP primitive, as the blog post mentions. Thunderbird is nice, but it's not cross-platform. Superhuman and Notion Mail are nice, but they only support Google and Outlook. Apple Mail is truly awful. There's a gap in the market, and as I said we're building it for ourselves.
        scarface_74 1y ago
        Yes, because as a business you shouldn’t have a sales pitch ready for people when they ask you why they should spend money on your product. It’s the first thing you do if you are trying to make a product that you plan to monetize is ask - who is the ideal user and how will we market it. If it’s just a hobby project to learn a new to you technology, that’s fine or if you just wanted to scratch an itch.
zenoprax 1y ago
> email heavy workflow What do you mean by this? I send 5-15 emails a day at a minimum throughout the day and receive just as many directly with another 2-3x as cc in various distribution lists (which I read in full). Add in server notifications, automated reports from data processing scripts, and the generic info@company.com inbox and it's probably close to 100 in a day with ease. Lots of skimming and Ctrl-Q'ing and it's hardly a burden. The lasting power of email is that it's one of the few federated communication channels that has a global network effect. Email and chat are two different media for different purposes. You have plausible deniability when a single message in a group chat is missed. When an email is sent to the team with a change in procedure you can have some expectations that it will be seen and it also provides a one-one or one-many channel for clarification. I'm not familiar with how the sales world works but I use email every day with clients, vendors, the team, my boss(es), and many other intra-company relationships. I think you have a lack of imagination in this regard :)
- scarface_74 1y ago
  > various distribution lists (which I read in full). Add in server notifications, automated reports from data processing scripts, And all of those can just as easily be sent to a Slack channel without everyone bothering to create email rules since they are automatically sent to the correct Slack channel where if it’s an actionable alert, a responsible party can add an “ack” reaction that kicks off a workflow that says this person is handling it. This can also be integrated into your CRM or wherever you call something like ServiceNow. We have all sorts of workflows and integrations with Slack. > You have plausible deniability when a single message in a group chat is missed. When an email is sent to the team with a change in procedure you can have some expectations that it will be seen and it also provides a one-one or one-many channel for clarification How are you any less likely to miss an email than miss a channel set aside for leadership announcements that only certain people can send a message too? Then you also have the “reply all” issue that I’ve seen blow up email servers. Messages allow threading etc in Slack and it’s a lot easier to ignore a thread that doesn’t pertain to you and follow those that do. Everyone at our 1000 person company communicates through Slack up to an including our CEO for announcements and updates. I don’t think I’ve emailed someone internally in over 8 years except to forward an external email and during that time, I’ve worked for startups and the second largest employer in the US.
jolmg 1y ago
> In my personal life, email is only for one way transactions. Where some company is sending email to me or spam. In my experience, email seems common for customer support.
- scarface_74 1y ago
  From a personal use standpoint, I’m looking at all of my credit card companies, hotel apps, flight apps etc and they all either have in app messaging or integrate with iMessage. Now I’m seeing more companies that want to integrate with messaging platforms for customer support - one of my specialties is implementing call centers with Amazon Connect. I’ve never been asked in 5 years to integrate customer support with inbound email.

isaachinman 1y ago

Actually, the complete opposite. We're building this app because we need it ourselves. Turns out a lot of other people do too.

scarface_74 1y ago
What’s the sales pitch for using email in 2025 for communication aside from sales?
- isaachinman 1y ago
  No sales pitch at all. USPs are on our homepage. If it doesn't appeal to you I get it. Different people have different needs. There's been a massive influx of "new gen" email clients in the past year or so. That said, we're not an "AI product".
  - scarface_74 1y ago
    [flagged]
    - jamiek88 1y ago
      [flagged]
      - scarface_74 1y ago
        This is a site run by a firm that encourages startups. What company has no idea how to pitch their product?
    - isaachinman 1y ago
      You are indeed quite rude, but I'll give you an answer. The selling point is that it's IMAP primitive, as the blog post mentions. Thunderbird is nice, but it's not cross-platform. Superhuman and Notion Mail are nice, but they only support Google and Outlook. Apple Mail is truly awful. There's a gap in the market, and as I said we're building it for ourselves.
      - scarface_74 1y ago
        Yes, because as a business you shouldn’t have a sales pitch ready for people when they ask you why they should spend money on your product. It’s the first thing you do if you are trying to make a product that you plan to monetize is ask - who is the ideal user and how will we market it. If it’s just a hobby project to learn a new to you technology, that’s fine or if you just wanted to scratch an itch.

zenoprax 1y ago

> email heavy workflow What do you mean by this? I send 5-15 emails a day at a minimum throughout the day and receive just as many directly with another 2-3x as cc in various distribution lists (which I read in full). Add in server notifications, automated reports from data processing scripts, and the generic info@company.com inbox and it's probably close to 100 in a day with ease. Lots of skimming and Ctrl-Q'ing and it's hardly a burden. The lasting power of email is that it's one of the few federated communication channels that has a global network effect. Email and chat are two different media for different purposes. You have plausible deniability when a single message in a group chat is missed. When an email is sent to the team with a change in procedure you can have some expectations that it will be seen and it also provides a one-one or one-many channel for clarification. I'm not familiar with how the sales world works but I use email every day with clients, vendors, the team, my boss(es), and many other intra-company relationships. I think you have a lack of imagination in this regard :)

scarface_74 1y ago
> various distribution lists (which I read in full). Add in server notifications, automated reports from data processing scripts, And all of those can just as easily be sent to a Slack channel without everyone bothering to create email rules since they are automatically sent to the correct Slack channel where if it’s an actionable alert, a responsible party can add an “ack” reaction that kicks off a workflow that says this person is handling it. This can also be integrated into your CRM or wherever you call something like ServiceNow. We have all sorts of workflows and integrations with Slack. > You have plausible deniability when a single message in a group chat is missed. When an email is sent to the team with a change in procedure you can have some expectations that it will be seen and it also provides a one-one or one-many channel for clarification How are you any less likely to miss an email than miss a channel set aside for leadership announcements that only certain people can send a message too? Then you also have the “reply all” issue that I’ve seen blow up email servers. Messages allow threading etc in Slack and it’s a lot easier to ignore a thread that doesn’t pertain to you and follow those that do. Everyone at our 1000 person company communicates through Slack up to an including our CEO for announcements and updates. I don’t think I’ve emailed someone internally in over 8 years except to forward an external email and during that time, I’ve worked for startups and the second largest employer in the US.

jolmg 1y ago

> In my personal life, email is only for one way transactions. Where some company is sending email to me or spam. In my experience, email seems common for customer support.

scarface_74 1y ago
From a personal use standpoint, I’m looking at all of my credit card companies, hotel apps, flight apps etc and they all either have in app messaging or integrate with iMessage. Now I’m seeing more companies that want to integrate with messaging platforms for customer support - one of my specialties is implementing call centers with Amazon Connect. I’ve never been asked in 5 years to integrate customer support with inbound email.