Follow up before good prospects go cold

Who this is for

This is for owner-operated companies where inbound still lands in a shared inbox, a form email, or a voicemail, and the next step lives in someone’s head. If that is already the pain, use /lead-follow-up as the short doorway. This playbook is the method: stages, a next-step field, stale alerts, and draft review — without handing the relationship to an agent.

It is not for outbound machine-gun sequences, marketplace spam, or teams that want a bot to negotiate price. If your motion depends on a human relationship, keep a human on the send. Automate the remembering and the draft, not the commitment.

Symptoms

If several of these are true in the same month, this is a live operational leak — not a tooling preference.

• Website and referral inquiries wait until someone “gets through the inbox.”
• Calls and voicemails are not logged, so the owner cannot see what came in yesterday.
• Quotes sit in drafts or email sent folders with no date for the next touch.
• The CRM is a graveyard: stages that mean nothing, contacts with no next step.
• Good conversations go quiet after a strong first call because nobody owned the follow-up.
• A tool already drafts replies, and some of them have gone out without a read.
• The same prospect is worked by two people because inbound is not assigned.

What done looks like

Done is a working operating change, not a purchased seat or a dashboard nobody opens.

• Every live inquiry has a stage, an owner, a next step, and a date.
• New inbound is visible the same day, in one place, without hunting inboxes.
• Stale next steps surface as a list, not as a feeling on Sunday night.
• Outbound drafts are reviewed before send. Money terms are never auto-sent.
• Handoff into onboarding is a stage change, not a hope.
• Nobody is running a silent second pipeline in a notebook.

Speed-to-lead is not a personality trait

Fast response is a path: the inquiry lands, a person is notified, a first reply goes out, and the record exists. You can make that path short without making it reckless. A same-day reply that asks one useful question beats an instant paragraph that invents scope. Speed without a record just moves the leak into the afternoon.

Write the first-reply job. Is it confirm receipt, qualify fit, book a call, or send a packet? Pick one for inbound of a given type. A form from a pricing page and a referral from an existing client do not share a script. Keep the first reply short enough that a tired owner will actually send the draft.

Stages, then a next-step field

You need fewer stages than the CRM template offered. A working set for many service firms: new, qualified, conversation, proposed, verbal yes, signed, lost. If a stage does not change what someone does this week, delete it. “Nurture” is usually a drawer for records you are afraid to mark lost.

The next-step field is the operating system. It is a verb and a date: “send revised scope, Thursday,” “call after their board meeting, the 12th,” “mark lost if no reply, Friday.” A note that says “follow up” is not a next step. Require the field on every stage after new. If the CRM cannot require it, run a weekly list of blanks until the habit holds, then automate the nag.

Stale alerts follow the date. They should name the owner and the record, not generate a fresh pitch. The job of the alert is to reopen a human decision: send the draft, change the date, or mark lost. An agent that keeps “checking in” forever trains prospects to ignore you.

Draft review, not autonomous selling

Drafts are a good use of models: a first reply from the form fields, a recap from the call notes, a reminder that restates the last agreed next step. Constrained inputs, constrained outputs. The sender reads the draft against the record. If the record is thin, the draft will be thin, which is a gift — it tells you the CRM is empty.

Do not auto-send money terms, discounts, or “we can start Monday” language. That is how you inherit a commitment the owner never made. The same rule applies when follow-up turns into a document: read call notes to proposals and keep the proposal on a review path. When the yes is real, onboarding sequence takes over. Follow-up that tries to be onboarding in the same thread is how assets and deposits get lost.

Adjacent packet work — one-pagers, estimate shells, recap emails — lives with document workflows. Keep the CRM as the status. Keep the document as the artifact. Do not store the only copy of the quote in a chat.

Rank this against the rest of the week

Follow-up often wins the ranking because frequency and pain are high and the first DIY is small: a field, a notification, a draft. Blast radius jumps the moment you let anything send itself. Keep the first pass on capture, next step, and review. If the company also cannot produce a weekly pipeline brief, that is a reporting problem sharing the same empty CRM. Rank them together so you do not build a dashboard on missing next steps.

What the week looks like when this is working

Monday, the owner can see every live record with a next-step date this week and every inbound that landed since Friday. Nothing in that list is “need to follow up.” Each row has a verb. New form fills produced a draft the same day. The owner sent, edited, or killed those drafts in one sitting.

Midweek, stale alerts are a short list, not a mood. One record gets a new date because the buyer’s board moved. One gets marked lost because silence after two reviewed touches is enough. One draft reminder goes out restating the last agreed action — not a new offer invented to “create urgency.”

When a conversation turns into a document, the opportunity already has an owner and a next step, so the proposal work has a home. When a yes arrives, the stage change is the handoff into onboarding, not a folder named NEW in someone’s downloads. That is a revenue motion. It is still human.

Inbound types need different first replies

A pricing-page form, a referral, a voicemail, and a “just circling back” from a conference are not one script. Write a first-reply job for each type you actually get. Confirm and book. Qualify and decline. Thank the referrer and open the new record. Do not let a generic “thanks for reaching out, we’d love to learn more” become the whole system.

Declining is part of speed. A fast, clear no is better than a slow maybe that clogs the pipeline and trains the team to keep dead records warm. If fit rules exist — geography, minimum, service line — put them where the drafter can see them. If they do not exist, write them. That is ranking work, not a model problem.

Voice and chat need the same record rule as forms. If the call is not logged, it did not happen for the pipeline. A same-day note with a next step beats a perfect transcript that never becomes a task. Recorders are useful. They are not a CRM.

Failure modes that look like progress

A sequence tool starts sending because “the prospect went quiet.” Quiet after a real next step is a human decision. Quiet after you never set a next step is a capture failure. Do not treat those as the same trigger.

Two people work the same inbound because assignment is a suggestion. Make it exclusive. If coverage is required, transfer the owner. Dual ownership is how prospects get two stories and no commitment.

The CRM fills with activities and still has no next step. Activity is not motion. If you automate logging before you require the next-step field, you will get a beautiful history of a cold pipeline.

A draft mentions a price the owner never approved because an old email was in the context window. Constrain the inputs. If price is not in the opportunity fields or the rate card, the draft leaves a blank. Blanks are safer than confident fiction.

DIY vs hire

DIY the stages, the required next-step field, same-day inbound visibility, and a draft-and-send habit. Most teams can do this in the CRM and inbox they already have. The discipline is marking lost and refusing a second notebook.

Hire for routing across several inboxes, voice capture, quote systems that write back, or a bounded first-line agent that stays on drafts. Those are later builds. The $997 assessment is a consult and a written analysis that can put follow-up in the DIY now list or on the roadmap. Implementation is quoted only if you want it.

Controls before automation

Recommendations that touch customers, money, contracts, private data, or systems of record need human review, limited permissions, a log, and a fallback. Do not automate a broken path because the tool is ready.

• Humans send. Models draft.
• No auto-send of price, scope, or start dates.
• Inbound assignment is exclusive. Two owners is a bug.
• Stale alerts create a task, not a customer-facing email, until a person approves the send.
• Lost is a valid stage. Do not hide dead records in nurture to protect a forecast.
• If the CRM and the inbox disagree, stop the automation and correct the capture path.

What to leave in the notebook

Personal working notes can stay personal: color on a buyer, a reminder to yourself, a half-formed offer you have not decided to make. They should not be the only copy of a next step. If the business would be hurt when your laptop is closed, it belongs on the record.

Likewise, not every inbound deserves a long sequence. A clear no, a referral thank-you, and a “not now, ask again in a quarter” with a dated next step are complete outcomes. Automation that cannot accept those outcomes will keep talking after the commercial truth is already known.

The notebook test is simple: if you were out for two days, could someone else send the right next step from the CRM alone. If they would have to call you, the record is still a diary. Diary is allowed. It is not a pipeline.

In the fourteen asks

Follow-up is a core mid-market AI ask. It sits next to onboarding and documents, not next to “build us a salesperson.” If you want the leak ranked against reporting and knowledge on one page, start with the assessment.