How do I stop forgetting to follow up on emails I promised?

What the job actually is

You stop forgetting to follow up on emails you promised by turning I'll send that Friday into a follow-up that still fires on Friday. The line in the thread is not a reminder, a snooze, a nudge, or a task until something else happens to it.

Founders and operators type that line in Gmail to a warm intro, a prospect, or an investor, then the thread dies. I'll send you that report by Friday is the leak. Inbox zero does not keep it. A notes app is too far from the thread. A sales cadence that sends on its own is a different product.

The buying prompt collapses four jobs: a reminder you remembered to set, a nudge when sent mail gets no reply, a draft of the chase, and a promise kept until a person still sends. Waiting on their reply is a neighboring job. Work across apps with a send gate is on Lindy vs an AI employee in Slack.

Which tool wins which job

Fund the row that matches the leak. A snooze, a no-reply nudge, and a promise you typed are neighboring jobs.

A snooze is not the promise in the email

Snooze hides a thread until a time you picked. Gmail's help is exact: the email is removed from the inbox, then comes back at the top when you want it. You still have to remember to snooze it. I'll send that Friday in the body does nothing by itself.

Superhuman's Remind Me is the same job with a keyboard: H, then a day and time. Reminders default to if no reply. If they reply before Friday, the reminder is canceled. Set regardless if the promise still needs to go out even after they write back.

Operators say Gmail snooze breaks if they reply early: the thread comes back, you handle the reply, and Friday has nothing left to fire. That is why a snooze is a time you chose, not a reading of the promise.

Waiting on a reply is a different job

Most inbox tools watch silence after you hit send. That is emails I'm waiting on a reply to, not emails I promised. Gmail Nudges suggest sent threads to follow up on. Superhuman Auto Reminders fire when the latest outgoing message has had no reply. Fyxer keeps those threads in Sent until your wait period passes, then labels them Awaiting reply or To follow up and drafts the bump. Lindy's follow-up bumps routine does the same after 1, 2, 3, 5, or 7 days.

None of those, by itself, reads I'll send you that report by Friday and keeps Friday. Lindy's Discover library has a Promise tracker template for follow-ups you promise in email. It is a template you add, not a built-in toggle. Superhuman Auto Reminders detect that a follow-up is needed from the latest outgoing message. They do not claim to parse the promise in the body.

If the leak is they never wrote back, fund the no-reply row. If the leak is you said you would send the deck and then forgot, fund the promise row.

The caveat that should decide the setup

The failure operators name first is an AI that sends the follow-up on its own. A prompt that says draft only is not a send gate: people have watched a bot email the team after they told it not to. Worst case with a draft is you delete it. Worst case with auto-send is you explaining the email on Monday.

Fyxer states that it never sends drafts automatically; you always review and approve. Superhuman Auto Drafts wait for you to hit send, and still alert if a placeholder is empty. Lindy's email-drafting and follow-up-bump routines land in your drafts folder. Anything with outside impact waits for approval, and Always allow turns that gate off. Guardrails apply in shared Slack threads only, not in the web app, Slack DMs, iMessage, or SMS. Lindy's meeting follow-ups are a different path: after a recorded meeting, an email can go out to attendees.

Concrete is an AI employee that works in existing Slack channels and reads Gmail alongside them. It keeps every promise made in a thread, and every thread waiting on a reply, as a follow-up. Each morning it nudges the owner. It drafts the follow-up as a Send / Edit / Skip card in Slack. A Gmail send needs the same tap. There is no auto-send mode. Follow-ups survive reboots. It is in design-partner preview; the longer thesis is on the vision page. It does not run sequences or cadences.

A practical setup for a 2-to-50 person shop

This is the boring version that holds when the founder still owns the one-to-one threads. Pin it before the next I'll send that Friday.

• Name the leak. A snooze, a no-reply nudge, and a promise you typed are different. Snooze covers a time you picked. Nudges cover silence after send. The promise job is the line in the email.
• Capture the line when you type it. I'll send that Friday has to become an owned follow-up before the thread ages out. Manual copy into a notes app is the step that fails. A personal snooze is a graveyard if you forget to set it.
• Keep send as a tap on the exact text. Draft the chase. Send stays a tap. Always allow, Auto, or a prompt that says draft only is a different setup. One-to-one threads with a warm intro, a prospect, or an investor are not a sequence.
• Put the morning list where you will see it. A follow-up that only lives in Sent is easy to skip. A morning nudge of what you still owe, in Slack or at the top of the inbox, is the list. Gmail Nudges and Superhuman returned reminders live in the mailbox. Concrete posts the list in Slack.
• Keep Gmail and Slack on the same list. The same promise is often typed in email and repeated in Slack. Two tools, two lists, and Friday still slips. One follow-up that survives both is the job.