How do I do founder-led sales follow-up without a CRM?

What the job actually is

Founder-led sales follow-up without a CRM is keeping one-to-one threads with a warm intro, a prospect, or an investor on a list you actually open, then drafting the chase a person still sends. The thread is not a pipeline, a sequence, a snooze, or a task until something else happens to it.

Founders at companies of 2 to 50 people still own those threads. Conversations live in Gmail. Follow-ups live in the founder's head. A warm intro lands, a week passes, and the thread is dead in Sent. Inbox zero does not keep it. A notes app is too far from the thread. A cadence that sends on its own is a different product.

The buying prompt collapses four jobs: a list of names you still open, a reminder you remembered to set, a draft of the chase on the silent thread, and a CRM or sequence built for a sales team. Promises you typed are a neighboring job, on how to stop forgetting emails you promised. Silence after send is on how to keep track of emails you're waiting on. The mailbox comparison is on Fyxer vs Superhuman vs an AI in Slack.

Which tool wins which job

Fund the row that matches the leak. A spreadsheet, a snooze, and a CRM are neighboring jobs.

A CRM is a different job

A CRM wins pipeline stages, a forecast, and a handoff to a hired AE. Those are team jobs. This prompt is the founder still owning the one-to-one threads, with no CRM, and no desire to spend the weekend filling fields.

A spreadsheet is the list people actually keep at this size: name, last touch, next date. It is a list you still open. It does not sit on the Gmail thread. It does not turn I'll send the deck Friday into a follow-up, and it does not notice that Sent stayed silent.

Fund a CRM when you hire the AE and need stages other people can see. Until then, the leak is the warm intro that sat in Sent. A chief of staff that tracks team promises in Slack is a neighboring job, on the chief of staff page.

A sequence is a different job

Most inbox tools watch silence after you hit send, then draft the bump. That is emails I'm waiting on a reply to. 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 and drafts. Lindy's follow-up bumps routine does the same after 1, 2, 3, 5, or 7 days.

None of those, by itself, is a cadence. A sequence that sends without a tap is a different product, built for lists. One-to-one threads with a warm intro, a prospect, or an investor are not a list. Lindy can Always allow.

Work across apps with a send gate is on Lindy vs an AI employee in Slack. An assistant that drafts follow-ups and cannot send without a tap is on the draft-only page.

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 appear as ordinary drafts and are never sent automatically. If a placeholder is still empty when you hit send, Mail alerts you. 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.

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. It does not replace a CRM.

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 warm intro goes cold in Sent.

• Name the leak. A spreadsheet, a snooze, a CRM, and a sequence are different. The sheet is a list you open. Snooze is a time you picked. A CRM is stages for a team. A sequence sends without a tap. This job is the one-to-one thread.
• Capture the intro when it lands. A warm intro has to land on a list before it ages out of Sent. Manual copy into a notes app is the step that fails. Superhuman Instant Intro thanks the introducer. The chase after that still needs an owner.
• 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 spreadsheet you open on a set day, a Superhuman returned reminder, or a morning nudge in Slack is the list. Gmail Nudges live at the top of the inbox.
• Keep Gmail and Slack on the same list. The same wait is often an email and a Slack ping. Two tools, two lists, and the intro still goes cold. One follow-up that survives both is the job.