Smart Email Search Won't Save You: The Message Worth Scanning Is the One You're About to Send

The Feature Everyone Is Building

Ask any AI email startup what they are working on and you will hear a version of the same answer: search. Natural language queries over your inbox. Ask a question, get a cited answer, skip the scrolling.

It is a good feature. Gmail search really is a keyword engine wearing a question-shaped box, and every professional has lost twenty minutes to a thread they knew existed but could not name.

Presend does not build it. That is a deliberate choice, and this post explains it, because the reasoning says more about where email actually goes wrong than any feature list would.

Inbound Failures Are Cheap. Outbound Failures Are Not.

Think about the last time inbox search failed you. You could not find a thread. You scrolled, you guessed at keywords, you eventually found it, and you were annoyed. Cost: minutes, and some irritation.

Now think about the last outbound mistake you watched happen — yours or a colleague's:

• A reply-all that should have been a reply.
• An API key pasted into a message to a contractor.
• "Please see attached" with nothing attached, sent to a client.
• A pricing figure sent to the wrong customer in a lookalike thread.
• A message that read like it came out of a chatbot, sent to someone deciding whether to trust you.

None of those cost minutes. They cost a deal, a credential rotation, a compliance report, or a relationship. The IBM Cost of a Data Breach report puts the average misdirected-email incident in the millions, and that is only the category that gets counted.

Search makes the cheap half of email faster. It does nothing to the expensive half.

Presend Is a Gate, Not an Assistant

Presend does not summarize your threads, draft your replies, or sort your inbox. Plenty of good tools do. What it does is stand in the compose window and interrupt the sends you would regret.

The send button stays clickable. Presend intercepts the send gesture itself — a click, or the platform's send keystroke — in the capture phase, and shows a confirmation sheet only when something it found rises to the level of risk. Warnings and notes never block you; they sit in the panel next to the draft.

That is the whole product. One window, one decision, made before the message is irreversible.

What It Reads Instead of Your Inbox

Presend reads exactly one thing: the draft in front of you. Here is what the built-in checks look for.

Credentials and secrets. Anything shaped like an API key or token, plus anything the sentence itself labels as one — "here's the password", "the token is" — even when the value that follows matches no pattern we recognize. This one fires as a hard risk at four words, because a leaked key does not need a long message to do damage.

Sensitive numbers. Values matching SSN or payment-card formats.

Missing attachments. You wrote "attached" or "see the file" and nothing is attached.

Missing links. You wrote "see the link below" and there is no URL in the message.

External recipients. How many people outside your domain are on this message, listed by address, before you send rather than after.

AI phrasing. Openers and constructions that read as model-generated, with a suggested replacement where cutting the phrase is the better move.

Banned phrases. Language your company has ruled out, whether that is a competitor's name, an unapproved claim, or a promise legal does not want in writing.

Subject and body mismatch. A company named in the subject but never in the body, or the reverse — the fingerprint of a template that was reused without being reread.

Empty subject and missing sign-off. Small, but the checks people are most grateful for on a Friday afternoon.

Each of those resolves to an underlined span in the compose box. A score you cannot act on is a horoscope; a highlighted sentence is a decision.

Voice, Measured Against Your Own Writing

The other half of the check asks a different question: does this sound like you?

Because Presend sits at the send gate, every message you actually send is a labelled sample of your real voice, on that platform, approved by you. The profile builds itself. Nobody pastes writing samples into a settings page.

The comparison is Burrows's Delta against your own corpus — character trigrams, function-word frequencies, and style scalars like punctuation rhythm and contraction rate, each z-scored against the mean and standard deviation of your own past messages. Distance comes out in units of your own variation, which is what makes the verdict interpretable instead of decorative.

Two properties matter more than the accuracy number:

It is deterministic. The same draft and the same profile produce the same verdict every time. An earlier version of this scored with a model call and the number jittered between keystrokes, which taught users to ignore it.

It is local. Scoring runs in the content script. The corpus is never synced, never attached to a request, never sent anywhere. Quoted reply chains are stripped before storage, so it keeps what you wrote and never what was written to you.

And it abstains. Under five samples or four hundred words, Presend says it does not know yet rather than inventing a percentage.

Slop detection is separate and needs no profile at all — a deterministic catalog of model tells that works on your first day. A message can sound like you and still be slop; it can be slop-free and still not sound like you. Collapsing those into one number loses both signals.

Everywhere You Write, Not Just Gmail

The same gate runs in Gmail and Outlook Web, in Slack where it guards plain-Enter sends, in LinkedIn DMs and posts, on X, and in every other textarea and contenteditable on the web — Notion, Jira, Zendesk, HubSpot, any SaaS comment box. Surfaces are found structurally rather than by a per-site selector, so a site nobody wrote an adapter for still gets checked.

What may fire where is governed by channel. Sign-off, subject, attachment and recipient rules are email-only. Secrets, PII and slop run everywhere. Slop escalates to a hard stop on public posts, where the audience is strangers. A Google Doc is advisory: no gate, no model calls. Each channel also sets a word floor — twenty-five for chat, twelve for email — below which Presend stays quiet, because a checker that fires on "sounds good" gets muted within a day.

Your Own Checks, in Plain English

The built-ins cover what is universal. The rules that matter to your job are not universal, so you write them yourself, in plain English, and set one severity per rule:

• "Flag any message to an address outside our domain that mentions unreleased product names."
• "Warn me if I promise a delivery date without a specific day."
• "Block anything containing a customer's contract value."

Teams share a rule set across the org, and rules can call out to a webhook or your own API when the check needs data Presend does not have.

What This Costs

Free is free forever: twenty-five AI checks a day, with the local rule engine and voice scoring unlimited, since those run on your machine. Pro is three dollars a month for unlimited checks, custom rules, voice-preserving rewrites, the send-guard, and personal analytics. Teams are twenty-nine dollars per user per month for org-wide rules, the Custom Actions pipeline, webhooks, and the shared dashboard.

On privacy: Presend does not store your message bodies. What is kept is a one-way hash, which is enough to deduplicate and count and not enough to reconstruct what you wrote. The voice corpus never leaves your device at all. Full detail is in the privacy policy, written as numbered clauses rather than reassurance.

If You Want Search, Buy Search

This is not an argument that inbox search is worthless. If reading email is the bottleneck in your day, buy a tool built for reading email — Shortwave and Superhuman both do it well, and Presend runs alongside either of them without conflict.

But notice which tool you would miss more. Inbox search saves you minutes on a bad day. A send gate saves you the one email a year you would have spent a quarter apologizing for.

Add Presend to Chrome — Free →