The round retro: how to learn from every pass
A single pass is noise. A classified set of passes is the market telling you what to fix next.
Forty conversations, zero memory
By week six of a raise, most founders are sitting on a graveyard of passes they cannot reconstruct. Someone said "too early." Someone said "not our space." A partner you'd chased for weeks said "love the team, the timing is just off for us." You nodded, thanked them, felt the specific sting of each one, and moved to the next name on the list. The reasons are gone now, scattered across email replies, a few terse calendar declines, and three lines you half-typed into a notes app at 11pm.
So when a friend asks "what are investors telling you," the honest answer is a shrug and a vibe. It feels bad out there. They keep saying it's early. You cannot say more than that, because you never wrote it down in a form you could count.
This is the single most expensive thing founders drop on the floor during a raise. Every pass is a data point produced by a professional who looks at companies like yours all day, and you are getting dozens of them, and you are treating each one as a small private failure to be forgotten instead of a row in a dataset you are building whether you mean to or not.
Why you cannot trust any single pass reason
Here is the trap. The reason an investor gives you is a social object, not an analytical one. It is optimized to end the conversation politely, protect the relationship, and avoid an argument. It is almost never the real reason, and even when it is real, it is one person's read on one day.
"Too early" can mean your traction is thin. It can also mean the partner liked it but could not get a second partner excited, or the fund just deployed into something adjacent, or you caught them in a quarter where they are not writing new checks. Four completely different problems wearing the same three-word coat. If you act on the literal words of any one pass, you will chase the wrong fix and tell yourself a story that happens to match your worst fear that week.
The founders who panic are the ones who over-index on the most recent or most painful pass. The investor you respected most said "market feels small," so now the whole deck is getting torn up to chase a bigger TAM, on the strength of one opinion. That is not learning. That is being whipped around by whoever rejected you last.
The move is the opposite. Treat every individual pass as too noisy to act on, and treat the aggregate as the only thing worth listening to. One "too early" is an opinion. Eight "too early" out of twelve passes is a fact about your narrative, and it tells you exactly what to fix.
The framework: separate the excuse from the signal, then count
A pass has two layers. The surface is the excuse, the thing they said. Underneath is the signal, the actual reason they did not invest. Your job in the retro is to log the excuse honestly, infer the most likely signal, and then stop interpreting and start counting.
To count, you need everyone using the same labels. Free-text notes do not aggregate. A fixed taxonomy does. Here is the nine-category set every pass falls into, with what each one usually means underneath.
PASS-REASON TAXONOMY
1. TOO EARLY Stage mismatch. "Come back at $50k MRR."
Signal: you are below their entry bar, or they
want de-risking you have not done yet.
2. MARKET SIZE They do not believe the outcome is fund-sized.
Signal: your TAM story or expansion path is unconvincing,
OR this fund needs a bigger swing than you are.
3. CATEGORY FIT Not a space they invest in or have conviction on.
Signal: targeting error. Often not about you at all.
4. GEOGRAPHY Outside where they fund or can support a board seat.
Signal: targeting error. Filter these out earlier.
5. TRACTION Numbers too thin or growth too flat for the ask.
Signal: real, and the most actionable on this list.
6. TEAM A gap they can name: missing technical cofounder,
domain, prior scale.
Signal: real and slow to fix; affects framing now.
7. VALUATION Price or terms do not clear their model.
Signal: market feedback on your ask, not your company.
8. FUND TIMING Out of capital, end of fund, just did an adjacent deal.
Signal: not about you. Do not change anything.
9. UNCLEAR THESIS They could not repeat back why you win.
Signal: the most dangerous one. Your story is not landing.Two categories matter more than the rest because they are the only ones fully inside your control this week. Unclear thesis means the pitch is not transmitting. If an investor cannot paraphrase your wedge back to you, no amount of traction will save the meeting, and this shows up disguised as "too early" or "market size" all the time. Traction means the gap is real and the fix is operational, not narrative. Everything else is either a targeting error you should have caught before the meeting (category, geography), a pricing conversation (valuation), or not about you at all (fund timing).
The discipline is to resist the comforting reasons and hunt for the uncomfortable one. "Fund timing" and "category fit" feel great because they are not your fault. If your retro is mostly those, you are either mis-targeting badly or flinching away from the real signal. The pass you least want to be true, usually unclear thesis or traction, is the one worth the most.
A worked retro: twelve passes, one pattern
Say you log twelve passes by the end of week five. Raw, they feel like twelve different rejections and a generally bad market. Classified, they look like this.
| # | Investor (anon) | Excuse given | Inferred signal | Category |
|---|---|---|---|---|
| 1 | Seed fund A | "Too early for us" | Below entry bar | Too early |
| 2 | Angel B | "Not sure on the market" | TAM unconvincing | Market size |
| 3 | Seed fund C | "Couldn't get conviction" | Did not understand wedge | Unclear thesis |
| 4 | Multistage D | "Wrong stage for our new fund" | Genuinely fund timing | Fund timing |
| 5 | Seed fund E | "Need to see more growth" | Real, MoM flat | Traction |
| 6 | Angel F | "Not my area" | Targeting error | Category fit |
| 7 | Seed fund G | "What makes you different?" | Wedge not landing | Unclear thesis |
| 8 | Seed fund H | "Come back post-launch" | Below bar | Too early |
| 9 | Seed fund I | "Hard to size the outcome" | TAM unconvincing | Market size |
| 10 | Seed fund J | "Crowded category" | Wedge not landing | Unclear thesis |
| 11 | Angel K | "Timing's off for me" | Fund timing | Fund timing |
| 12 | Seed fund L | "Don't see the moat" | Wedge not landing | Unclear thesis |
Now tally. Unclear thesis: 4. Market size: 2. Too early: 2. Fund timing: 2. Traction: 1. Category fit: 1.
A founder reading these one at a time would walk away believing the market is too small, because "market size" and "crowded category" and "hard to size the outcome" all felt like the same gut-punch about TAM. But the count says something different. The dominant pattern is unclear thesis, four hits, and three of those four were dressed as something else. "Crowded category" and "don't see the moat" are not market-size problems. They are you-failed-to-explain-the-wedge problems. The market is probably fine. Your fifth slide is not.
That is the whole point of the retro. The pattern was invisible at the level of individual passes and obvious the moment you forced every pass into the same nine buckets and added them up.
What you actually do with the pattern
Counting is worthless if it does not change next week's behavior. Each dominant category maps to exactly one kind of action. Do not do all of them. Do the one your top bucket points to.
PATTERN -> NEXT MOVE
Unclear thesis is top -> Fix the pitch, not the company.
Rewrite the one sentence that names your wedge.
Test it: can a friend repeat it after one read?
Move it earlier in the deck and the meeting.
Traction is top -> Stop pitching for 2-3 weeks if you can.
Go get the number. A flat chart will not
out-argue itself in a meeting.
Market size is top -> Two sub-cases. If thesis is also high, it is
really a thesis problem (see above). If thesis
is clean, you may be pitching the wrong funds:
re-target to funds whose model fits your outcome.
Too early is top -> Re-target down a stage, or build a relationship
track: short monthly updates to the "come back
later" names instead of re-pitching now.
Category / geography -> A targeting error. Tighten your list. These
passes should mostly disappear with better
filtering before the meeting.
Valuation is top -> Market is telling you the ask. Pressure-test
your price against the round structure before
the next ten meetings, not after.
Fund timing is top -> Do nothing to the company. Note these names for
the next raise. They are warm, not cold.The retro also resets your target list. Every category and geography pass is a name that should not have been on the list, which means your sourcing filter is leaking. Every fund-timing pass is a name to re-approach next time, not a loss. The same review that fixes your narrative also cleans your pipeline, because both problems were hiding in the pile of passes you were about to forget.
Run it weekly, in fifteen minutes
This is not a project. It is a standing fifteen-minute block, ideally Friday, while the conversations are still warm.
Pull every pass from the week. For each one, write the exact words they used, your honest guess at the real signal, and the single taxonomy label. Add it to the running table. Then re-tally the whole raise, not just this week, and look at one number: which category is largest, and is it one you can act on. If the top bucket shifted from last week, ask why. If it did not, ask whether you executed last week's move or just nodded at it.
The output of the retro is one sentence you say out loud: "The pattern is X, so this week I am doing Y." If you cannot finish that sentence, you have not done the retro, you have just re-read your rejections.
Where RoundOS fits
The reason founders skip this is that the raw material is scattered. The pass reasons live inside email replies, declined calendar invites, meeting notes, and the half-sentences you typed after a call. Reconstructing them by hand at week six, when you most need the pattern, is exactly when you have the least time to do it.
RoundOS runs the round as a structured workflow over the sources where it already lives, so the passes do not have to be remembered. It pulls the rejection from the email thread, ties it to the investor who sent it, and keeps it next to the meeting notes from that conversation, so each pass arrives already attached to its context. With every pass in one place, the weekly tally stops being archaeology. You classify against the taxonomy, watch which category climbs, and see your target list re-sort itself as category and geography passes flag the names that never fit. The retro becomes a fifteen-minute read instead of an hour of digging.
Run the first round retro.
Pull the last ten passes, give each one a single label from the taxonomy, and count. Whatever bucket is largest is the thing the market has been telling you while the rejections felt unrelated.