周五下午你按名单打过去：「您好，看到您前几天在我们网站留了资料——」他已经想不起自己留过什么，也已经跟另外两家聊完了。那两家替他定义了「对账系统该怎么比」，你现在只能在别人的评分表里争分数。
「您刚在网站上提到对账——我先不介绍产品，想确认一下您那边现在是几个人在手工对，一个月大概多少单？」
—— 快的价值不在礼貌，在他此刻脑子里还挂着这个问题、还没被别人的框架占住。第一个到场的人不是抢单，是定义标准。
EN The most-quoted follow-up statistic in sales — "80% of deals close after the fifth follow-up" — has no traceable source and is credited to an association nobody can find. Drop it. What is measurable is speed: in an audit of 2,241 US companies, firms that responded within an hour were roughly seven times likelier to reach a real conversation with a decision maker than firms that waited just one hour longer, and over sixty times likelier than those who waited a day — while about 23% never replied at all. The count of touches is an effect, not a cause: warm deals survive long enough to be followed up seven times. Chase the count and you'll harass people you should have disqualified.
机制：快不是勤快，是接住注意力。人一离开那个页面、那场会，这件事就从「待办」变成「已归档」，重新打开要额外成本。更要命的是位次——你越晚到，越可能是第三第四个联系他的人，前面的人已经替他写好了评估标准，你只能在别人的表里得分。
速度红利只在他刚举手时存在——表单、询价、会后、他主动问了一句。冷线索上「1 小时内」不叫快，叫唐突。另外，快指的是联系快，不是报价快：发现还没做完就把价格甩过去，你只是更快地把自己变成了一张比价单（挖痛点那期讲的就是这一步）。
"You mentioned reconciliation — before I pitch anything, can I ask how it works today?" —— 快，但不推销。
"I'd rather be early and useless than late and irrelevant." —— 解释你为什么这么快回。
· 替他做了一小块活。一页排期、一版按他数字做的测算、一张对比表。成本在你，省的是他的时间。
· 他那行的新信息。同类公司怎么解的、政策变了、供应商涨价了。要求是他还不知道，不是你官网上就有。
· 补上次没答完的。「你问的那个并发数，我去问了工程，答案是 X，附带一个前提。」这条最容易做，也最少人做。
· 流程性节点。合同版本、档期、他自己定的那个时间点。这类天然合法，因为日程是他给的。
· 纯人的一条。他提过的事：上线日、搬办公室、孩子考试。只在你真记得时用——翻 CRM 演出来的关心，比不关心更伤。
「王总，就是跟您确认一下进展～方便的话回我一下？」信息量为零，成本全转给对方：他得先回忆是哪件事、再判断该怎么答、还欠你一个回复。你要的是他的时间，给的是零。第三条这样的消息之后，他不是讨厌你，是把你的名字归进了「可以稍后再说」那一栏——那一栏没有稍后。
「王总，你上次担心两个系统对账口径不一致。我拿你们给的样表跑了一遍，差异集中在退款单，附件三行结论。」（换行）「不用回，看到就行。周四我把只上对账那版的排期发你。」
—— 带了东西，免了义务，还预告了下一次。他就算这轮不动，也知道打开你的消息不亏。
EN "Just checking in" is the most expensive sentence in follow-up: zero information, and every cost transferred to them — recall which thread this is, decide how to answer, and now they owe you a reply. Pestering isn't defined by frequency, it's defined by repetition with nothing new in it. Each touch opens a small account in their head: bring something and you deposit, arrive empty-handed and you withdraw. When the balance goes negative they don't reject you — they stop seeing you. So the only test that matters before you hit send: if they deleted this message unread, would they lose anything? And where you can, remove the obligation too — "no reply needed, just so you have it" — because a follow-up that costs them nothing to receive can be sent many more times than one that demands an answer.
机制：重复本身能提升好感——熟悉让加工更省力，省力被大脑读成「这东西还行」。但这条曲线有顶：重复到不再带新信息时，熟悉转成厌倦，再叠上「被推着走」的心理逆反。决定你在顶点左边还是右边的，不是次数，是每一次有没有新东西。
「带价值」不等于「附一份行业白皮书」。判据是他删掉会不会亏，不是你花了多少工夫。群发的报告对他信息量为零，还额外证明了你没在听。真正的分水岭很朴素：这条东西是不是只对他一个人成立。
"No reply needed — just so you have it." —— 带东西且免除义务。
"I ran your sample file; the gap is all in refunds. Three lines attached." —— 有信息量的开头长这样。
"Just checking in" —— 反面教材，永远别写。
· 你先承诺。「我这边下一步是把只上对账那版的排期做出来，周三之前发你。」——先给，不先要。
· 让他承诺，时间由他说。「你那边需要跟财务对一下，对吗？大概什么时候方便？」——日期从他嘴里出来，后面才不是你在追。
· 把下一次变成预约。「如果到那天还没动静，我周四上午打个五分钟电话，可以吗？」——他说可以，这通电话就永远不是骚扰，是他批准过的日程。
EN The reason follow-up feels like nagging is that the previous conversation ended without a next one. Close every call with three sentences: what you'll deliver and by when (you commit first), what they need to do and — crucially — when they think that is (the date comes out of their mouth, not yours), and then permission for the follow-up itself: "if nothing's moved by then, can I call you Thursday morning for five minutes?" Once they say yes, that call is never pestering; it's a scheduled item they approved. Then space the touches out at widening intervals rather than clustering them. Spaced beats massed in the memory literature, and practically, widening intervals cover more of the moments when something changes on their side — the budget lands, their boss asks, a competitor raises prices.
机制两层。一是覆盖：他的决策不是均匀推进的，是被外部事件触发的；分散的接触在时间上撞到更多触发点，集中轰炸只是在同一个饱和时刻反复敲。二是外包：把「什么时间、什么情况下、做什么」事先写死，行动就不再取决于当时想不想做——这对他有用，对你自己更有用。
递减间隔的前提是这单还活着。连续三次完全无反应还去加密频率，只会更糟——那时候要修的是资格判定（追错人 / 追错层级），不是节奏。另外：约定过的跟进也会过期。他说「下周三给你答复」而下周三没来，你在周四问一句是履约；拖到第三周才问，那句约定已经不保护你了。
"If nothing's moved by then, can I call you Thursday morning for five minutes?" —— 把跟进变成预约。
"When do you think that conversation happens?" —— 让日期从他嘴里出来。
"I'll have it to you by Wednesday." —— 先承诺再要求。
「李工，我先把这件事从跟进表移到季度提醒，免得一直占你收件箱。如果今年不做，这是完全合理的决定，你不用特地回我一句解释。如果只是时机不对，年底预算那阵我再敲一次门。这期间需要那份对账口径的表随时找我，不附带任何条件。」
· 三个零件缺一不可：给台阶（不做是合理的）、免义务（不用回）、留门且无条件（东西还是给你）。
· 一个反直觉的观察：这封信的回复率常常高于前面三条催问。因为你把「拒绝你」变成了「帮你省事」——而人更愿意做后者。
EN Follow-up is a low-frequency, many-threaded task where every thread has a different next step — precisely the shape human memory handles worst. Run it from memory and you'll only stay on top of the people who are comfortable to contact: the fast repliers, the friendly ones. Five columns are enough: who, what I gave them last time, the next step written as who-by-when-does-what, the due date, and the count of consecutive non-replies. Twenty minutes on Monday morning is the only discipline the system needs. Decide the walk-away number in advance — three, four, whatever — so the question "should I chase again?" becomes a rule you set once rather than a mood you argue with daily. Then send a closing note that gives them an out, waives the reply, and leaves the door open unconditionally.
机制：跟进是低频、多线程、且每条线下一步都不同的任务——正好是人类记忆最差的形态。把「下一步」写成外部可查的条目，等于把认知负担从「记住」转成「读取」。放手线同理：事先定规则，是为了在你情绪最差的那天不必现场判断。
放手线是保护关系，不是惩罚对方。收尾信里只要漏出一点「看来你们不太重视」的味道，你就把一个「只是排不上号」的人，变成了一个永久的不。还有一条更实的：放手线该不该触发，先看你追的是不是对的人——三次无回应有时不是他不想，是你一直在跟一个既不掏钱也不拍板的人说话（找到决策链那期讲的正是这件事）。
"I'm moving this to a quarterly reminder so it stops sitting in your inbox." —— 收尾且不尴尬。
"If this isn't happening this year, that's a completely reasonable call." —— 给台阶。
"Happy to send it either way — no strings." —— 无条件留门。
打开你的收件箱和那张（大概率不存在的）跟进表。20 分钟，写纸上。