Intro.
#Classifying Rejection Reasons — Four Types
| Rejection type | Signal | Follow-up value |
|---|
| Wrong Stage | Stage mismatch — too early for seed, too small for Series A | ★★★ Very likely to work in 12 months |
| Wrong Thesis | Doesn't fit their industry or geographic focus | ★ Rarely works, viable only once they raise a new fund |
| Wrong Metric | Current metrics fall short — PMF, revenue, growth rate | ★★★ Strong odds once metrics improve |
| Wrong Team / Trust | Lack of confidence in the team or founder | ★ Hard to recover, usually needs new team members |
TIP
When you get a pass, 'Wrong Stage' and 'Wrong Metric' are worth revisiting in 12 months. Deprioritize follow-up for 'Wrong Thesis' and 'Wrong Team.'
02
#The Standard Reply Right After a Rejection
Send a short reply within 24 hours of receiving a pass. The standard format packs three things into 3-5 lines: thanks, a brief acknowledgment of the feedback you received, and a promise of future updates.
- Thanks — appreciation for their time
- Acknowledge the feedback — sum up their concern in one line
- Action — how you plan to address that feedback
- Promise of updates — commit to sending a short update every quarter
주의
A reply that argues back or tries to change their mind backfires. Don't close the door on following up in the next round.
03
#The Standard Monthly/Quarterly Update Email
Keep sending monthly or quarterly update emails even to investors who passed. Subject line: '[Company Name] Update — 2026 Q3 (1 page).' Keep the body to one page or less.
- TL;DR — the single biggest change this quarter, in one line
- KPI snapshot — one table with your North Star metric plus supporting metrics, quarter-over-quarter
- Wins — three pieces of good news
- Asks — one or two specific requests (intros, advice, hiring help)
- Cash and runway — three lines (cash on hand, monthly burn, runway)
TIP
It genuinely happens often: an investor who passed last quarter reads your next update and suddenly sends over a term sheet. Companies that stop sending updates get forgotten.
04
#Triggers for Requesting a New Meeting — Four Signals
Beyond a routine update, it's appropriate to directly ask for another meeting when one of these four signals occurs.
- You've clearly improved the metric that was the reason for the pass (e.g., crossing ₩100M in MRR)
- A significant team change has happened — a key hire or a new co-founder
- A meaningful deal, contract, or partnership has closed
- Your next fundraising round is about to kick off
05
#The Standard Format for a Re-Meeting Request Email
A request for another meeting should be short and specific. Packing these four elements into one email raises your reply rate.
- One line referencing your last meeting (date, key feedback)
- One line on what's changed since that feedback (a specific metric or event)
- One line on why you want to meet now (a routine update, or the start of your next raise)
- One line on your preferred meeting format (30-minute Zoom, 30-minute coffee, or a materials review)
주의
In the follow-up meeting, address the original reason for the pass within the first five minutes, with a clear change to point to — 'Wrong Metric → crossed ₩100M in MRR,' for example.
Summary.
#Self-Check Checklist
- Have you classified each investor's rejection reason into one of the four types?
- Did you reply within 24 hours of receiving the pass?
- Do you send update emails on a regular quarterly cadence?
- Does the update stay to one page and include all five sections — TL;DR, KPIs, Wins, Asks, and Runway?
- Do you only request a re-meeting when one of the four trigger signals has actually occurred?
- Does your re-meeting email address the original rejection reason in the first line?
CTA
OpenSeed's VC and strategy agent automatically checks your rejection classification, update email structure, and whether your re-meeting triggers are well timed. Free during the current beta.
Automatically Validate Your Post-Rejection Follow-up
Our VC and strategy agent analyzes your rejection classification, update structure, and re-meeting triggers.
🔒 Free during beta · your submission isn't saved
Start Free AI Feedback →