The founder fundraising audit: 20 questions before your next wave

What founders do between waves

Between waves, most founders do one of two things. They either pause and polish the deck again, or they scrape another 50 names and resend a near-identical email. Both feel like progress. Neither uses the information the first wave produced.

The first wave generates four kinds of signal, and almost no one harvests them. Reply rate tells you whether your targeting and subject line work. Which investors replied tells you which thesis you actually fit. The objections raised in calls tell you where the narrative is thin. The threads that went quiet tell you where your follow-up is leaking. All of that is sitting in your sent folder and your meeting notes, unread as data.

So founders send wave two blind. Same email, fresh strangers, and they are surprised when the reply rate does not move. The round does not improve because nothing was learned between the two sends. The audit forces the read before the resend.

The six places a round leaks

A founder-led round leaks in six specific places, and your first wave has already shown you which ones are leaking. Each question is binary. Answer from your actual records, not from how you remember it going.

Targets (did you aim at the right people)

1. Of everyone who replied, can you name the single thesis or sector pattern they share? If your replies are random, your targeting is.
2. Did your top-10 most-wanted investors get a personalized email, or did they get the same template as everyone else?
3. Can you point to at least three names in your next wave who have publicly backed something adjacent to what you do?

Paths (did you use the warm routes you had)

1. Of the investors you most wanted, how many did you reach cold when a warm intro existed in your network and you did not find it?
2. For every warm intro you requested, did the introducer get a forwardable blurb, or did you make them write it?
3. Did any intro request sit unsent for more than a week because you were "still polishing" the ask?

Outreach (did the email do its job)

1. Is your reply rate above 20%? Below that, the email or the list is the problem, not the volume.
2. Does your cold email answer "why you, why this investor" in the first two lines, or does it open with a company description?
3. Did you send any follow-up to non-responders, or did one unanswered email count as "I reached out"?

Meetings (did the calls move anything)

1. After each first call, do you have a written record of the single objection that investor raised?
2. Can you name the most common objection across all your calls so far? If three investors raised the same doubt, that is your narrative gap.
3. Did you leave any meeting without a clear, mutually understood next step and a date?

Follow-up (did momentum survive the meeting)

1. Right now, is there any investor who is waiting on something from you that you have not sent?
2. For every "keep me posted," did a next touch get scheduled, or did it evaporate into goodwill?
3. Can you reconstruct, in under a minute, the full history of any single investor conversation from your records?

Proof (did you have the evidence the calls demanded)

1. When investors asked for a specific number, did you have it ready, or did you promise to "follow up with that"?
2. Did any call surface a question you could not answer and still have not built an answer for?
3. Do you have one concrete piece of traction or proof that is newer than your first wave, that the next wave should lead with?
4. Are your three headline claims each backed by a number you can defend in two sentences?
5. Has anything in the first wave changed your story enough that the deck wave two sees should be different?

Scoring the audit

Score one point for every honest "yes." The questions are written so that yes is the healthy answer.

The total matters less than the shape. Score each domain separately and find your lowest. A round that scores 3/3 on targets and 0/3 on follow-up does not need better names. It needs a follow-up system, and adding names makes the leak bigger.

Reading the shape, not the score

The point of scoring by domain is that each leak has a different repair, and the wrong repair wastes the wave.

A low targets score means your next wave should be half the size and twice as researched. The fix is not more names, it is better-chosen ones. Pull the thesis pattern out of who replied and aim at it.

A low paths score is the cheapest one to fix and the most commonly ignored. You reached people cold who were two degrees away warm. Before wave two, run your wanted-list against your network and convert every cold shot you can into a warm one.

A low meetings or proof score is a narrative problem wearing a targeting costume. If three investors raised the same objection, wave two is not the move. Rewriting the part of the story that keeps drawing that objection is the move. Then the next wave gets a story that has already survived contact.

A low follow-up score is the quiet killer, because it does not show up as a dramatic failure. It shows up as threads that just went cold, deals you cannot trace losing. If question 13 is a yes right now, there is a live deal you are leaking today, and it outranks anything in the next wave.

A worked example

Suppose your audit comes back: Targets 3/3, Paths 1/3, Outreach 3/3, Meetings 1/3, Follow-up 0/3, Proof 3/5. Total 11.

The 11 is a "stop" score, but the number is not the story. The shape is. Your targeting and email work, so the leak is not at the top of the funnel. The two zeros and ones are clustered in paths, meetings, and follow-up. Translated: you are getting meetings and then losing them, and you are reaching people cold who you could reach warm.

The wrong response is to send 50 more emails, because your top of funnel is fine. The right response is a small set of moves before any new outreach. Convert the warm paths you skipped on your existing wanted-list. Pull the repeated objection out of your meeting notes and rewrite that part of the story. And close every open follow-up loop today, starting with anyone waiting on you. Only then load wave two, which is now aimed at the repaired gaps instead of widening them.

That is the difference between running the experiment again and acting on its results.

Where RoundOS fits

The audit is a manual read of data you already own, and you can run it today with your sent folder, your meeting notes, and the scorecard above. The harder part is that three of the six domains decay between waves: source context, follow-up, and the objection history that tells you what to rewrite.

RoundOS pulls the round in from where it already lives. Email, calendar, meeting notes, investor spreadsheets, decks, LinkedIn exports, founder notes. From those sources it builds the per-investor history, so question 15, reconstructing any conversation in under a minute, is a lookup instead of a memory test. It flags the threads that went quiet and surfaces who is waiting on you, which is the follow-up domain, questions 13 and 14. It keeps the objections from your calls attached to the round, so question 11, naming the most common objection, is a filter rather than a guess.

So instead of running this audit from scratch every wave and trusting your memory of how the calls went, the answers to the decaying questions are already assembled from your sources. The targeting and narrative calls are still yours to make. The system keeps the data the audit depends on from rotting between sends.

Reusable artifact: The 20-question between-waves audit

THE FOUNDER FUNDRAISING AUDIT — score 1 for each honest YES

TARGETS  (___/3)
[ ] 1. Can you name the shared thesis of everyone who replied?
[ ] 2. Did your top-10 wanted investors get personalized emails?
[ ] 3. Are 3+ names in the next wave backers of adjacent companies?

PATHS  (___/3)
[ ] 4. Did you avoid going cold where a warm intro existed?
[ ] 5. Did every introducer get a forwardable blurb?
[ ] 6. Did no intro request sit unsent over a week from polishing?

OUTREACH  (___/3)
[ ] 7. Is your reply rate above 20%?
[ ] 8. Does the email answer "why you, why this investor" in 2 lines?
[ ] 9. Did non-responders get at least one follow-up?

MEETINGS  (___/3)
[ ] 10. Is each call's main objection written down?
[ ] 11. Can you name the most common objection across all calls?
[ ] 12. Did every meeting end with a dated next step?

FOLLOW-UP  (___/3)
[ ] 13. Is no investor currently waiting on something from you?
[ ] 14. Did every "keep me posted" get a scheduled next touch?
[ ] 15. Can you reconstruct any conversation's history in <1 min?

PROOF  (___/5)
[ ] 16. Did you have every requested number ready on the call?
[ ] 17. Have you built answers to questions you couldn't answer?
[ ] 18. Is there proof newer than wave one to lead with?
[ ] 19. Are your 3 headline claims each defensible in 2 sentences?
[ ] 20. Has the first wave changed the story wave two should tell?

TOTAL ___/20

17–20  Send the next wave. Scale volume.
12–16  Fix the lowest domain before wave two.
 7–11  Stop. Repair before sending any new email.
 0–6   Not a volume problem. Rebuild the weakest domain.

Read the SHAPE, not the total. Find your lowest domain.
Each leak has a different repair:
  low targets   -> smaller, better-researched wave
  low paths     -> convert cold shots to warm intros
  low meetings  -> rewrite the repeated-objection part of the story
  low follow-up -> close every open loop today, before new outreach