The follow-up email is the most overworked, lowest-yielding move in founder-led sales. "Just checking in." "Bumping this to the top." "Wanted to make sure this didn't get buried." Every one of those sentences is asking the prospect to do unpaid cognitive work for you, and offering nothing in return.

The fix is not to write better follow-ups. The fix is to stop sending follow-ups at all. Send updates instead.

Why "just checking in" stopped working

Inboxes are a zero-sum attention market. The cost to read your message is roughly 3 to 6 seconds of the prospect's day. The benefit to them has to be greater than that cost or they archive without thinking. A bump email contains zero new information. The benefit is literally nothing. The math collapses on the first line.

Worse: the bump email actively trains the prospect to ignore your future messages. Their brain pattern-matches your name to "person who interrupts me with nothing." After three of those, you're filtered out before you reach the inbox. You burned the relationship to send a message you knew would underperform.

The bump was invented by sales teams who needed to hit activity quotas. Founders don't have activity quotas. We have meeting quotas. The bump optimizes for the wrong number.

Every "are you the right person to talk to?" message I've ever sent has been ignored. Every message I've sent that opened with "I saw your VP of Engineering just posted about onboarding pain on LinkedIn" has been replied to. The difference is not tone or copywriting. The difference is whether the message contains new information for the reader.

An update is a follow-up that earns its place in the inbox

An update is the same kind of message as a follow-up — same prospect, same thread, same eventual ask — except the first line of the message is a fresh fact about them, not a reminder about you.

Examples of facts that count as updates:

Each of these takes 30 seconds to find using free tools — Google Alerts, LinkedIn's "creator alerts," Reddit's RSS feeds, the prospect's company changelog, or the "watching for this competitor" report PostBuild generates for you.

The discipline is simple: no signal, no message. If nothing happened in their world this week, you don't write anything. Silence is better than another bump.

The format that works

Three short paragraphs. Under 80 words total. The first line carries the entire weight of getting the email opened.

Subject: Re: [original subject]

[Their first name] —

Saw [specific thing] yesterday. Reminded me of
what you said about [the exact pain they mentioned].

Did the [related concern] ever get resolved on
your end? Curious if it changed your timeline.

— [Your first name]

Three things this format does that a bump doesn't:

  1. It quotes them back to themselves. "What you said about onboarding taking 4 weeks" is more powerful than any clever subject line. It proves you remember the conversation as a person, not as a Salesforce contact record.
  2. It introduces a new fact. "Saw [their competitor] just raised $12M." That single line is the entire reason the message gets read. The brain rewards new information.
  3. It asks one open question. Not "are you ready to buy." Not "should we talk." A question about their situation that they can answer in 6 words. Low friction, high reply rate.

Notice what's not there. No "circling back." No "wanted to make sure." No re-pitching the product. No calendar link. No "let me know if it makes sense to chat." All of that is bump language. None of it survives in an update.

Three real updates, decoded

Examples from founders who run this play. Identifying details changed.

Update 1 — funding signal:

Maya —

Saw Acme just raised their Series B on Monday.
You'd mentioned in Feb that you were holding off
on tooling decisions until your funding closed.

Is now the moment, or are you still pre-board-
approval on the budget?

— Sarah

Why it works: the funding round is fresh, public, and directly addresses the objection Maya gave in February. Maya replies because she actually has news to share now.

Update 2 — competitor moved:

Dev —

Notion just announced AI-native databases this
morning. Last we talked you were comparing us
against them — figured you'd want a heads up
before the press hits your inbox.

Does this change anything for you?

— Jordan

Why it works: Jordan is bringing news Dev hasn't seen yet. The favor is asymmetric. Dev replies because he wants to know if Jordan's product is still the right call given the move.

Update 3 — their own person posted:

Priya —

Your new Head of CX, Marcus, posted on LinkedIn
yesterday about how their first 90 days will
focus on response time. That's exactly the
problem we'd talked about in March.

Worth a 15-min intro between him and us, or
should I message him directly?

— Alex

Why it works: Alex did the homework, found a new internal stakeholder, and gave Priya optionality (warm intro vs cold reach). Priya replies because she's the gatekeeper and now she has a reason to act.

PostBuild watches your prospects' funding rounds, hires, LinkedIn posts, and competitor moves, then drops the update messages into your dumb CRM as drafts you only need to send. Try it free.

Cadence: the part everyone gets wrong

Founders ask "how often should I send updates?" and the honest answer is: as often as a real signal happens, and not one day sooner.

Some prospects will earn three updates in two weeks because their world is moving fast. Others will earn one update in 60 days. A few will earn zero, and you'll mark them dormant without ever sending another message. That is correct. A prospect with no signal is not a prospect — they're a name in a spreadsheet.

The wrong cadence is the automated one: day 3, day 7, day 14, day 30. That fixed pattern is what taught the entire B2B world to ignore follow-ups in the first place. The moment your messages look like they came out of a sequencer, you've lost.

What to do when there really is no signal

Sometimes a prospect goes silent and nothing happens in their world for weeks. You have two correct moves and one wrong one.

Right move one: Move them to "dormant" in your CRM. Set a 60-day reminder to check again. Spend the time you would have spent bumping them on someone whose world is actively moving.

Right move two: Send them a "breakup" message — but make it real, not the fake breakup that's just another bump. "Closing the loop on this — I'll stop reaching out unless something changes on either end. If your situation does shift, I'm happy to pick it back up." Then actually stop. The breakup that works is the one that's followed by silence.

Wrong move: Send another bump. "Just wanted to make sure this didn't get lost." It will get lost. That's the answer the inbox has been giving you for years. Listen to it.

What you actually gain by switching

Founders who replace bumps with updates report three changes within the first month:

That last shift is the whole game. Stop being a bump. Start being the person in their inbox who always knows what just happened.