Every few months a new email app launches with a fresh coat of paint and a claim to have "reinvented email." Install it, connect an account, and you get a list of messages sorted newest first, with search, swipe actions, and maybe a dark mode. That's not reinvention. That's an IMAP reader with better fonts.
We think there's a real distinction between an email client and a triage layer, and almost nobody in the App Store is building the second thing.
What a client does
A client's job, historically, is narrow: connect to a mail server, download messages, render them, let you send new ones. Apple Mail does this. Outlook does this. Every third-party app that's launched in the last decade does this, with variations in speed, design, and which protocols it speaks.
A client answers "what's in my mailbox." It does this well. Modern clients are fast, sync reliably, and handle attachments and threading without much fuss. The infrastructure problem of email, moving bytes reliably between servers and screens, is basically solved.
What a client doesn't do
A client does not answer "what should I do about my mailbox." It shows you everything, in arrival order, and leaves the decision-making entirely to you. Every message gets equal visual weight until you read it. A password reset and a client emergency look the same in the list, differing only in sender name and subject line, both requiring you to open them to find out which is which.
This is fine at 20 emails a day. It breaks completely at 200. The client scales its reading and sending. It does not scale your ability to figure out what matters, because it was never built to.
Defining the triage layer
A triage layer sits on top of the reading-and-sending mechanics and answers a different question entirely: given everything that landed, what needs a human today, and in what order. It doesn't replace the client's plumbing. It replaces the client's default sort order, which is the part that was never actually useful.
The distinction in practice:
- A client shows you 200 messages. A triage layer tells you which 7 need you.
- A client treats "unread" as the primary signal. A triage layer treats urgency as the primary signal.
- A client is judged by sync speed and search quality. A triage layer is judged by whether it got the ranking right.
- A client requires you to build the mental model of "what matters" fresh every session. A triage layer carries that model for you.
Why most "new" email clients skip this
Building a fast, reliable client is a hard, well-understood engineering problem. Building a triage layer requires understanding what makes an email urgent, which means classification, which means either a lot of manual rules or a model that can read a thread and reason about it. That's a different kind of hard, and it's why most redesigns settle for the safer bet: reskin the list, ship a dark mode, call it done.
We wrote more on this pattern in why most redesigns change the paint, not the problem. The short version: a new coat of paint is shippable in a quarter. A real triage layer is a multi-year bet on getting classification right.
If your "new" email app's core screen is still a flat list sorted by time, you didn't build a triage layer. You built a client with a new icon.
How STAMP tries to be the second thing
STAMP is a client, technically, in that it connects to Gmail, Google Workspace, Outlook, Microsoft 365, iCloud, Fastmail, Proton Bridge, and plain IMAP/SMTP, and it renders and sends mail like any other app. But the part we actually built the product around is the layer above that: classification that runs fully on your Mac, ranking every incoming thread by urgency before you ever see the list.
The client part was table stakes. We had to get sync right or nothing else matters. But the reason to switch isn't sync speed, everyone's sync is fast now. The reason to switch is that the first thing you see isn't a wall of 200 messages, it's the handful that actually need you.
How to tell which one you're using
A simple test: open your current email app and ask if it could tell you, in one sentence, what today is about. If the answer requires you to scroll and read subject lines yourself, you're using a client. If the app already knows and says so before you scroll, you're using a triage layer.
Most people have never used the second kind, because until recently it barely existed. See what a real triage layer looks like on the changelog, or just try it against your own inbox for a week.
A client reads mail. A triage layer tells you what matters. hello@stamp.email