How to write follow-ups that add momentum
A fundraising follow-up should deliver one new input to an investor's decision, not ask for attention.
It's Thursday. You had a good call with a partner nine days ago. She said "let me discuss internally," you said great, and since then: silence. You've drafted the same email four times in your head. It always comes out as some version of "Hi Sarah, just following up on our conversation, wanted to see if you had any thoughts or next steps on your end. Happy to answer any questions!" You hate it. You send it anyway, because the alternative is letting the thread die. She doesn't reply, and now you've made it worse, because the last thing in her inbox from you is a content-free nudge.
The problem isn't that you followed up. The problem is what the follow-up contained, which was nothing. "Just checking in" asks the investor to generate the next step. It puts the work on the busiest, least-invested person in the conversation and gives them no new reason to spend that work on you. A follow-up that carries no new information is indistinguishable from pressure, and pressure with nothing behind it reads as weakness. You're telling her the most interesting thing that's happened to your company in nine days is that you're anxious about her reply.
Why "did you see my email" follow-ups fail
A founder-led raise runs on the investor's attention, and attention is allocated to the threads that keep changing. An investor's mental model of your company is a snapshot from your last contact. The day after your call, that snapshot is fresh. Nine days later it's stale, and a stale snapshot loses to every newer, shinier thing in her pipeline. The job of a follow-up is to update the snapshot, to give her a more recent, more compelling version of your company than the one she's holding.
"Just checking in" updates nothing. It carries zero new data, so the snapshot doesn't move, and worse, it spends one of your limited touches without buying anything. You only get a handful of follow-ups before you tip from "persistent founder" into "annoying founder," and a check-in burns one of those touches on a message that advances nothing. It also tells the investor that you have no momentum. If something good had happened, you'd have led with it. The absence of news in a follow-up is itself news, and it's bad news.
The deeper trap is that the check-in feels productive. You did a thing. The thread has your name in it again. But a touch that adds no input is not progress, it's noise that costs you a touch. The founders whose threads stay warm are not the ones who follow up most often. They're the ones whose every follow-up hands the investor a new reason to lean in.
The fix: a follow-up is a delivery, not a request
Reframe the unit. A follow-up is not "a reminder that I exist." A follow-up is a delivery of one new input into the investor's decision. Before you write a single line, you answer one question: what new thing am I putting in front of her that wasn't there last time?
If you can name the new input, you have a follow-up. If you can't, you don't have a follow-up yet. You have an urge to be reassured, and that urge is not a reason to email an investor. The discipline is brutal and simple: no new input, no send.
There are five inputs worth delivering. Every good fundraising follow-up is one of these five, and naming them turns "I should follow up" into a specific, writable message.
The 5 follow-up types
| # | Follow-up type | The new input it delivers | When it's the right move |
|---|---|---|---|
| 1 | Proof update | A concrete metric, milestone, or signal since you last spoke | You have real new traction, a launch, a hire, or a logo |
| 2 | Objection answer | Evidence or reasoning against the specific doubt they raised | They named a concern on a call and left it hanging |
| 3 | Intro loop | Social proof: another investor moving, or a respected name engaged | A second investor is now active and creates timing pressure |
| 4 | Timeline prompt | A real deadline or process update that forces a decision | Your round has a closing date, a lead, or allocation filling |
| 5 | Diligence response | The exact data, doc, or reference they asked for | They requested something specific and it's open |
Five types. Every follow-up you ever send in a raise is one of these. None of them is "checking in," because none of them asks the investor to generate the next step. Each one hands her something and, in handing it over, creates the natural next step on its own.
Five follow-ups, written out
The types are useless as abstractions. Here is what each one looks like as an actual email you could send Thursday morning. Keep them short. An investor reads the first two lines and decides whether to keep going.
1. Proof update
Subject: Quick update — crossed [X] since we spoke Sarah — Since our call two weeks ago we [shipped X / signed [logo] / hit [metric]]. [One sentence on why it matters: e.g. "that's our third enterprise logo this quarter and the first inbound one."] Wanted you to have the current number as you discuss internally. Happy to walk through the detail whenever useful. [Name]
The new input is the metric. The internal discussion she mentioned now has fresher data to discuss, and you supplied it without asking her for anything.
2. Objection answer
Subject: The [retention / CAC / market size] question from our call Sarah — You flagged that [month-3 retention] was the thing you'd want to see hold. We just pulled the [March] cohort at month 3: [number], [up/flat] from [prior]. Chart attached, raw cut behind it. You raised the right concern, so I wanted to close the loop with data rather than a claim. [Name]
The new input is the evidence against her stated doubt. This is the highest-value follow-up in a raise, because it shows you listen, you execute, and you're not afraid of the hard number. A founder who answers the objection head-on is rarer than one with good metrics.
3. Intro loop
Subject: Quick timing note Sarah — Wanted to flag where things stand: [Fund B] has moved to [terms / partner meeting / verbal], and we're starting to firm up the round. I'd much rather have you in this, so if it's worth a follow-up conversation to keep you in the loop, I can make time this week. [Name]
The new input is social proof and motion. You are not pressuring her. You are reporting a fact that changes her calculus: the round is moving with or without her. State it plainly, never invent the other fund.
4. Timeline prompt
Subject: Round timing — closing [date] Sarah — We're aiming to close the round by [date], and allocation is [filling / committed at X of $Y]. I don't want to rush your process, but I also don't want you to find out the window closed. If a [partner meeting / second call] would help you decide in that window, tell me what you'd need and I'll set it up. [Name]
The new input is a real deadline. A timeline prompt only works if the timeline is true. A fake deadline an investor calls and you can't honor ends the conversation permanently.
5. Diligence response
Subject: The [cohort data / customer references / model] you asked for Sarah — Attached is [the thing she asked for]. [One line orienting her: "Tab 2 is the cohort retention by month, tab 3 is the CAC build."] [Reference name] has also agreed to a call. Let me know and I'll connect you. Anything else you need to move this forward, send it over. [Name]
The new input is the exact thing she requested. An open diligence ask is the clearest buy signal in a raise, and the only correct follow-up is delivery, fast and complete. Speed here is itself a data point about how you operate.
The follow-up selection tree
When a thread goes quiet and you feel the urge to "check in," run this instead. It resolves to one of the five types, and if it resolves to none, it tells you not to send.
FOLLOW-UP SELECTION TREE (run per thread, top to bottom, stop at first YES)
START: Did they ASK for something specific that's still open?
(data, doc, reference, a model)
YES -> Type 5: diligence response — send it, fast [TOP PRIORITY]
NO v
Did they raise an OBJECTION on our last contact that I can now answer
with evidence?
YES -> Type 2: objection answer
NO v
Has something REAL changed in the round?
(another investor moved, a lead firmed up, allocation filling)
YES -> Type 3: intro loop / Type 4: timeline prompt
NO v
Do I have a NEW proof point since we last spoke?
(metric, launch, logo, hire)
YES -> Type 1: proof update
NO v
Is there genuinely NO new input I can deliver?
YES -> DO NOT SEND A CHECK-IN.
Go create an input instead:
- line up a reference call
- pull the cohort cut they'll want
- or park the thread on a timer and re-touch when news landsThe tree's whole point is the last branch. The reason founders send check-ins is that they reach for the keyboard before they have anything to say. The tree forces the question in the right order: not "should I follow up?" but "what do I have to deliver?" If the answer is nothing, the move is to go manufacture an input, not to spend a touch announcing you have none.
Before / after: the Thursday follow-up
BEFORE (the check-in) Subject: Following up "Hi Sarah, just following up on our last conversation. Wanted to see if you had any thoughts or next steps on your end. Happy to answer any questions!" -> new input: none -> asks her to generate the next step -> signals: nothing has happened in nine days -> likely outcome: no reply, and the thread is now colder AFTER (the objection answer) Subject: The month-3 retention question from our call "You flagged month-3 retention as the thing you'd want to see hold. We pulled the March cohort: 71%, up from 64%. Chart attached. You raised the right concern, so I wanted to close it with data." -> new input: the exact metric she doubted -> the next step is implied (she reads, she replies, or she shares it internally) -> signals: you listen, you execute, you're not afraid of the number -> likely outcome: the snapshot updates, the thread warms
Same founder, same thread, same nine days of silence. One email asks for attention and gets none. The other delivers the one thing she said she needed and earns the reply. The difference is not tone or persistence. It's whether the message carried an input.
Where RoundOS fits
You can run this by hand, and you should start there. Next time you're about to type "just checking in," stop and run the tree. Find the open ask, the unanswered objection, the new proof point. Pull the relevant template above and fill it. That alone will change what lands in investors' inboxes.
Where the manual version breaks is knowing, across thirty live threads, what each investor is waiting on and what new input you have for them. The objection Sarah raised lives in a call transcript. The metric that answers it lives in your analytics. The diligence ask from another investor lives in an email from three weeks ago. The fact that you just signed a logo worth flagging lives in your head. To write the right follow-up to each thread, you have to reconstruct, per investor, what they last asked, what doubt they left open, and what's changed on your side since. That reconstruction is the real work, and it's why the follow-up defaults to a content-free check-in: it's the only message you can write without doing the reconstruction.
RoundOS reads the thread state from the sources where the round already lives, your email, calendar, meeting notes, and investor spreadsheet, and watches for new company signals on your side. It knows Sarah raised a retention objection on Tuesday's call and never got an answer, that a diligence ask from another fund has been open eleven days, that you just crossed a milestone worth sending as a proof update. It maps each quiet thread to the follow-up type that fits and drafts the message from the actual context, so what you review is not a blank "following up" box but a proof update, an objection answer, or a diligence response already populated with the real input. The job is one thing: turn the urge to check in into a follow-up that delivers something, by matching what each investor is waiting on to what has changed on your side.
Do this today
Open your three quietest live threads. For each, run the selection tree and find the one new input you can deliver, the open ask, the unanswered objection, the proof point you haven't sent. Write one of the five follow-ups using the templates above. If a thread resolves to "no new input," do not send a check-in. Instead, write down the one thing you'd need to manufacture before re-touching it, a reference call, a cohort cut, a milestone, and go get it. The rule that fixes follow-ups in a raise: you never send a message that asks for attention. You only send messages that deliver an input.
When you want each quiet thread matched to its follow-up type and drafted from the context you already have, connect the sources that hold your round and let RoundOS build the follow-ups.
Follow-up system
THE 5 FOLLOW-UP TYPES (each delivers one new input)
1. Proof update — new metric / launch / logo / hire
2. Objection answer — evidence against the doubt they raised
3. Intro loop — another investor moving, social proof + timing
4. Timeline prompt — a real deadline that forces a decision
5. Diligence response — the exact data / doc / reference they asked for
SELECTION TREE (run per quiet thread, stop at first YES)
Open ask still unfulfilled? -> Type 5 [top priority, send fast]
Objection I can now answer? -> Type 2
Something real changed in the round? -> Type 3 / Type 4
New proof point since last contact? -> Type 1
No new input at all?
-> DO NOT send a check-in. Go create an input, or park on a timer.
THE TEST (apply before every send)
"What new thing am I putting in front of them that wasn't there
last time?"
Can name it -> you have a follow-up, write it.
Can't name it -> you have anxiety, not a follow-up. Don't send.
THE RULE: never send a message that asks for attention.
only send messages that deliver an input.Deliver an input, not a check-in.
Run the selection tree on your three quietest threads today and send one real follow-up instead of a check-in. When you want each quiet thread matched to its follow-up type and drafted from the context you already have, connect the sources that hold your round and let RoundOS build them.