Problem-first guide
How to follow up with leads consistently without a CRM
Last updated September 3, 2026
Use a small lead table with one row per opportunity and only the fields that drive action: person, request, fit, last contact, next action, next date, and status. Every conversation must end with a dated next step or a closed status.
Review the table at the same time each workday and send follow-ups from the original thread. This gives a solo business CRM discipline without the setup and maintenance of a full CRM.
Or hand it to Pally
Free to start. No app to install.
A practical approach
What to do.
- 01
Create the lead table
Make one table in a spreadsheet, task app, or notes database. Add columns for contact, company, request, source, fit, last contact, next action, next date, status, and source-thread link. Resist adding fields for information you never use in a decision. The table requires manual updates and offers fewer controls than a CRM. Its advantage is that you can understand every active opportunity on one screen and change the process without administering a larger system.
- 02
End with a next step
After every lead conversation, write the next action and its date before leaving the thread. Use actions such as send estimate, ask for dimensions, check after budget review, or close as no fit. “Follow up” is too vague because it does not tell you what the next message needs. This habit adds a small pause after each exchange, but it prevents the common state where a promising conversation looks active while nobody knows who should move it.
- 03
Review on a cadence
Filter the table to next dates due today or earlier and review it at one fixed time every workday. Handle quick messages immediately, schedule deeper work, and change stale leads to a truthful status. Then look ahead for proposals or decisions that need preparation. A daily review can feel unnecessary when the list is short, yet consistency is what makes a small system dependable. Skip weekends or closed hours according to the response promise you publish.
- 04
Write contextual follow-ups
Open the source thread and refer to the lead's request, your last agreed step, and one easy response. Send the missing document, ask the unresolved question, or offer a clear time to talk. Avoid “just checking in” when you can add useful information. Personalized notes take longer than a generic sequence, so keep a few structural templates. Change the details and call to action each time, and stop when the person declines or asks you to.
The Pally option
The short version: text Pally
Pally is one option for checking connected Gmail and iMessage for people who have not replied to a question, request, or proposal. It can name the open loop, draft a contextual nudge, and keep reminders in your text conversation. You review and approve each outgoing message.
Follow-up chaser
You asked, they went quiet. Pally notices who owes you a reply and drafts the nudge.
See the recipeA memory for your people
Where they moved, what they're into, what they're going through: pally keeps it all, and hands it back right when you need it.
See the recipeThe friendly nag
Hand pally the thing you keep putting off. It won't forget, and it won't let you either.
See the recipeOptions
Other tools people use
Fair alternatives, including ones that overlap with Pally.
HubSpot
HubSpot fits founders who want a CRM for lead follow-up.
It adds a separate CRM to the follow-up process.
Carly
Carly fits lead threads that need an AI agent with its own email address to reply and book meetings.
It works by adding an agent email address to the thread.
Fyxer
Fyxer fits founders who want follow-up replies prepared as drafts inside Gmail or Outlook.
Fyxer prepares drafts and leaves every send to the user.
Superhuman
Superhuman fits founders who want an email client with AI triage and drafting for lead follow-up.
Its focus is email rather than CRM pipeline tracking.
Folk
Folk fits founders who want a relationship CRM for lead context and follow-ups.
Its focus is relationship management rather than a dedicated sales pipeline.
Questions
Frequently asked questions.
When do I actually need a CRM?+
Move to a CRM when several people touch the same leads, permissions matter, reporting drives decisions, or manual updates regularly create missed or duplicate contact.
How long should I keep following up?+
Base the sequence on the lead's stated timing and the value you can add. Stop after a clear no, an unsubscribe request, or enough unanswered attempts that another message would add no new information.
What statuses should I use?+
Start with active, waiting, won, lost, and no fit. Add a status only when it changes what you do in the next review.
Keep reading
