Lead follow up for a small firm: how many touches to make, when to stop, and a weekly Slack sweep

For a lead who has answered once and gone quiet, plan on three to five touches in total over about two weeks, with the follow-ups at roughly day 1, day 4 and day 11 of silence, and then stop or park the lead. LeadsApp gives that range for inbound leads at professional-service firms, and Belkins found in 7,530,489 cold emails that steps 2 through 6 produced 58.6 percent of all replies, so a sequence that stops after one email leaves most of its replies uncollected.
At a 10 to 60 person firm, touches two to five usually have no named owner, so each one is sent from memory or not at all, and the owner cannot tell from the CRM which leads have gone stale. Below are a cadence table you can copy, a stop rule that says who may close a lead, and a weekly sweep that a Slack thread can run. The first reply is a separate job, covered in keeping new leads from going cold. This article starts after the first answer.
How many times should you follow up with a lead?
Three to five touches is the best-supported range for a warm lead at a small service firm, and about fourteen is the outlier, written for a firm with people on the phone. The sources disagree because they are counting different things.
| Source | What it counts | Number it gives | Who it is written for |
|---|---|---|---|
| Belkins | Steps in a cold email sequence | 3 to 5 steps is the practical sweet spot; step 6 shows minimal added value at 0.28 percent | Cold B2B email outreach |
| LeadsApp | Touches including your first reply | 3 to 5 touches over about two weeks, with an optional touch at day 20 to 30 for high-value leads | Inbound leads at professional-service firms |
| CaptaFlow | Calls, texts and emails together | About 14 touches in 14 days, 6 of them calls, for a new inbound lead; 3 to 5 emails for a cold prospect | Owners of high-ticket service businesses with a calling and texting setup |
Read across a row before you compare down a column. Belkins counts emails to strangers. LeadsApp counts the first reply as touch one. CaptaFlow counts every call and text, and says the often repeated claims that "80% of sales need five follow-ups" and "44% of reps give up after one" have no primary study behind them that it could find. Do not put those two figures in your process document unless you find the study.
Compare follow-up counts only after you decide what counts as a touch, because the published numbers count different things. For a firm that does not text and does not run a calling campaign, a touch is an email or a call that someone logs on the deal. Under that definition the 3 to 5 range is the one that matches your situation, and the 14-touch plan is a different job.
Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.
Which cadence should a firm without a sales team use?
Use three follow-ups after your first reply, touches 2 to 4, spaced by days of silence, with a fifth touch only for leads the owner marks as high value. This is a recommendation built on the LeadsApp spacing, not a sourced number. Change the days to fit your sales cycle.
Count days of silence from the lead's last reply, not from the day they first inquired, because every reply restarts the clock. LeadsApp makes the same point about its own sequence: any reply, even "not right now", resets the count. A lead who wrote back on day 9 is at day 0 of a new silence, not at day 9 of an old one.
| Touch | When (days of silence) | Channel | Who drafts | Who approves and sends | What it must contain |
|---|---|---|---|---|---|
| 1 | First reply, covered elsewhere | Deal owner | Deal owner | The answer and a booking link | |
| 2 | Day 1 | Agent drafts | Deal owner | A short nudge that confirms the message landed and repeats the booking link | |
| 3 | Day 4 | Email or a call | Agent drafts, or the owner calls | Deal owner | Something new: a relevant case, or an answer to the likeliest objection |
| 4 | Day 11 | Agent drafts | Deal owner | An easy way out: "reply not now and I will stop" | |
| 5 (optional) | Day 20 to 30 | Agent drafts | Deal owner | A check-in, only for leads marked high value |
Three rules keep the table honest. Each touch has to give the lead a reason to answer: a time, an answer or a question, never "just checking in". Every touch is logged on the deal, including a call. And the deal owner, a named person, sends it. The table has a "who" column because in most firms nobody holds touches two to five.
When should you stop following up with a lead?
Stop when a person decides to, for one of four reasons, and write the reason on the deal. CaptaFlow's own stop list and LeadsApp's exit criteria agree on most of these, and the day limit is yours to choose.
- The lead said no or asked you to stop. Stop immediately on every channel. An opt-out is not a lead to nurture.
- The lead no longer fits. Wrong size, wrong budget or wrong timing for what you sell. Close it with that reason.
- The lead replied. A reply restarts the count and a person takes over. HubSpot builds the same idea into its sequences tool: a contact who replies to a sequence email or books a meeting is automatically unenrolled, so a person takes over. Your cadence can work the same way without sequences.
- The day limit passed with no reply. LeadsApp stops at 30 days of silence for a lead that was not high-scored. Pick your own limit from your own history, as the verification section below explains, and treat the number as a recommendation.
Silence alone is not a no, so call the lead "parked" rather than "lost". CaptaFlow moves a lead that finishes the cadence into a monthly nurture instead of deleting it, and LeadsApp advises marking the lead with a status and a date so a "no for now" is not confused with a "no forever". A note on the deal costs nothing and keeps the lead findable when their situation changes.
Keep the decision to stop with a person. An agent that reads the CRM can tell you a lead has had four touches and 30 days of silence. It cannot know that the owner had a coffee with that contact last week. The sweep proposes and a person disposes.
How do you run a weekly lead follow up sweep in Slack?
Ask the Kipwise agent once, in your #sales channel, to list every open deal in an early or middle stage with no logged activity for a set number of days, and have it post the result every week. The agent reads HubSpot or Pipedrive using the access of the person who asked, so it only sees what that person can see. See per-user permissions for how that works.
The setup in order:
- Write the cadence table and stop rule into one pinned message in #sales, with the day limit you chose.
- Connect your CRM (Pipedrive or HubSpot) and, if you want drafts, Gmail, each with your own account.
- Ask for the sweep on a schedule. In plain language: "Every Monday at 9, list open deals in the first three stages with no logged activity in 3 days. For each, show the contact, the owner, the last logged touch, how many touches are logged and the days of silence." The agent can run a request on a schedule and post the result in the channel, and creating a scheduled task needs your approval once. See scheduling recurring jobs.
- Have the agent name the next step. Against the pinned table it can say which touch is due and which deals have reached the stop rule.
- Reply in the thread to ask for a draft. The agent writes the message into the asker's Gmail Drafts and shows the recipient, subject and a preview on an Approve or Deny card. Nothing is sent unless that person approves, and the card expires after 30 minutes. This is the same control described in human approval for agent workflows.
- Record the outcome. When you explicitly ask, the agent can log a note or add a task on the deal, and in Pipedrive schedule an activity, each behind its own approval.
Here is a made-up example, labelled as such, of what a Monday post and one reply could look like in a 25 person design studio.
> Quiet leads, Monday (example) > Brightwater Dental, owner Priya, 3 logged touches, last touch 12 days ago, silence 12 days. Next due: touch 4, the easy-out message. > Harbor Lane Cafe, owner Marcus, 1 logged touch, last touch 4 days ago. Next due: touch 3. > Northfield Surveys, owner Priya, 4 logged touches, silence 31 days. At the 30 day limit: stop or park? > > Priya, in the thread: "Draft touch 4 for Brightwater. Park Northfield, no budget this year."
The agent drafts touch 4 for Priya's approval, and on her explicit ask logs the Northfield note. Priya made both decisions, and the agent did the reading, the counting and the typing.
What does the sweep miss, and what stays with a person?
The sweep sees logged activity only, and that is its main limit. A call, a text or a LinkedIn message that nobody logged is invisible to it. Texting, phone calling and HubSpot sequences are not among the agent's documented capabilities, so touches made outside the CRM and your mailbox never appear.
A weekly sweep counts only logged activity, so make logging a call a condition of owning a deal, and treat a stale flag as a question to the owner rather than a reason to send. This is a recommendation, not a measured result. The risk is concrete: an owner who called a lead on Thursday and did not log it will get a stale flag on Monday, and a draft sent on top of a live conversation looks careless to a prospect who is about to sign.
Other failures to plan for:
- Wrong stage or wrong owner on the deal. The sweep is only as accurate as the CRM. A deal with no owner has nobody to ask, which is itself a finding.
- A reply that never reached the CRM. If the lead answered from a personal address or a different thread, the count is wrong. Ask owners to log replies the same way they log calls.
- Two people chasing one lead. Keep one owner per deal and have drafts go to that owner only.
- Opt-outs. If a lead says stop, the owner records it and closes the lead, so it no longer counts as an open deal. The agent does not decide who is contacted.
If your firm already has HubSpot Sales Hub or Service Hub at Professional or Enterprise with a seat, HubSpot's sequences already send timed email steps, assign the task steps to the user who enrolled the contact and unenroll on a reply. In that case the sweep is a check on the sequences, not a replacement. The Slack route is for firms on Pipedrive, on a lower HubSpot plan, or without anyone configuring sequences.
How do you check that the follow up process works?
Run it for four weeks on one owner's deals, then look at your own numbers. Do not borrow anyone else's reply rates.
- Coverage. Every open early-stage deal has an owner and a logged touch in the last two weeks, or a recorded reason it does not.
- Stop reasons. Every closed or parked lead carries one of the four reasons and a date.
- Where replies arrive. From your own closed-won deals, note which touch number the lead answered, and how many days of silence there were before they did. That gives you the day limit for your own sales cycle, which is better than 30 because it is yours.
- Complaints. Count unsubscribes or unhappy replies. If they rise after you add touch 4, tighten the spacing or cut it.
Belkins' cold email data shows returns falling quickly after step 5, and CaptaFlow advises measuring your own close rate by touch number. Your own CRM is the only source that knows your buyers.
What to do next
Today, open your last ten won deals and write down, for each, the number of days of silence before the lead answered. Take the longest sensible gap as your day limit, put the cadence table and that limit in a pinned message in #sales, and ask the agent in that channel for the first Monday sweep. To try it, add the Kipwise agent to Slack and connect your CRM: it costs $10 per user per month with a minimum of 3 users, and each user gets $5 of personal credit a month.



