@opendirectory.dev/skills 0.1.33 → 0.1.35
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/registry.json +20 -0
- package/skills/gh-issue-to-demand-signal/.env.example +3 -0
- package/skills/gh-issue-to-demand-signal/README.md +118 -0
- package/skills/gh-issue-to-demand-signal/SKILL.md +638 -0
- package/skills/gh-issue-to-demand-signal/evals/evals.json +118 -0
- package/skills/gh-issue-to-demand-signal/references/demand-categories.md +181 -0
- package/skills/gh-issue-to-demand-signal/references/gtm-translation.md +211 -0
- package/skills/vc-finder/.env.example +18 -0
- package/skills/vc-finder/README.md +113 -0
- package/skills/vc-finder/SKILL.md +663 -0
- package/skills/vc-finder/evals/evals.json +125 -0
- package/skills/vc-finder/references/stage-signals.md +98 -0
- package/skills/vc-finder/references/vc-outreach-guide.md +142 -0
|
@@ -0,0 +1,125 @@
|
|
|
1
|
+
[
|
|
2
|
+
{
|
|
3
|
+
"id": "eval_001",
|
|
4
|
+
"name": "B2B SaaS product URL: full two-track output with correct stage detection",
|
|
5
|
+
"description": "A B2B SaaS developer tool with a demo CTA. Validates the full 10-step workflow, stage detection from page signals, two-track VC research, and complete output.",
|
|
6
|
+
"input": {
|
|
7
|
+
"prompt": "Find VCs for my startup: https://linear.app",
|
|
8
|
+
"env": {
|
|
9
|
+
"GEMINI_API_KEY": "set",
|
|
10
|
+
"TAVILY_API_KEY": "set",
|
|
11
|
+
"FIRECRAWL_API_KEY": "set"
|
|
12
|
+
}
|
|
13
|
+
},
|
|
14
|
+
"expected_behavior": [
|
|
15
|
+
"Fetches URL via Firecrawl",
|
|
16
|
+
"Step 4 detects 'free trial or demo CTA' signal from page content",
|
|
17
|
+
"Stage outputs 'seed' or 'series-a' with medium or high confidence",
|
|
18
|
+
"Industry taxonomy: software > developer tools > issue tracking or project management",
|
|
19
|
+
"Generates 5 comparable companies (e.g. Jira, Shortcut, Height, Plane, Asana)",
|
|
20
|
+
"Runs 5 Track A Tavily searches using quoted company names",
|
|
21
|
+
"Runs 3 Track B Tavily searches using L2 and L3 taxonomy terms",
|
|
22
|
+
"Every Track A VC in the output has evidence_company field populated",
|
|
23
|
+
"Every Track B VC in the output has thesis_source_title field populated",
|
|
24
|
+
"Self-QA step removes any VCs missing required evidence fields",
|
|
25
|
+
"Output includes exactly 5 deep dives and exactly 3 outreach hooks",
|
|
26
|
+
"Output saved to docs/vc-intel/linear-[date].md"
|
|
27
|
+
],
|
|
28
|
+
"expected_output": "Full two-track VC list with sourced Track A evidence and Track B thesis citations, 5 deep dives with product-specific outreach hooks, saved to docs/vc-intel/"
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"id": "eval_002",
|
|
32
|
+
"name": "Consumer app: different stage signals, consumer-focused VCs not B2B enterprise funds",
|
|
33
|
+
"description": "A consumer mobile app. Validates that the skill detects consumer-specific signals and returns consumer-focused investors, not enterprise SaaS funds.",
|
|
34
|
+
"input": {
|
|
35
|
+
"prompt": "Find investors for this consumer app: https://www.bereal.com",
|
|
36
|
+
"env": {
|
|
37
|
+
"GEMINI_API_KEY": "set",
|
|
38
|
+
"TAVILY_API_KEY": "set",
|
|
39
|
+
"FIRECRAWL_API_KEY": "set"
|
|
40
|
+
}
|
|
41
|
+
},
|
|
42
|
+
"expected_behavior": [
|
|
43
|
+
"Fetches URL successfully",
|
|
44
|
+
"Industry taxonomy maps to consumer or social media, not B2B SaaS",
|
|
45
|
+
"Comparable companies are consumer social apps, not enterprise tools",
|
|
46
|
+
"Track A searches target consumer social investors (who backed TikTok, Snapchat, Instagram at early stage)",
|
|
47
|
+
"Track B searches use consumer social or UGC thesis terms",
|
|
48
|
+
"VCs in output are consumer-focused funds, not B2B SaaS investors",
|
|
49
|
+
"Outreach hooks are specific to consumer social or photo product type",
|
|
50
|
+
"No B2B enterprise-only investors appear in the output"
|
|
51
|
+
],
|
|
52
|
+
"expected_output": "VC list with consumer-focused investors, stage-appropriate alignment, no B2B enterprise fund entries"
|
|
53
|
+
},
|
|
54
|
+
{
|
|
55
|
+
"id": "eval_003",
|
|
56
|
+
"name": "Description-only input: skips fetch, goes direct to Gemini analysis",
|
|
57
|
+
"description": "User pastes a product description with no URL. Validates that Steps 3 and 4 are skipped and the skill proceeds directly to Gemini analysis.",
|
|
58
|
+
"input": {
|
|
59
|
+
"prompt": "Find VCs for my startup. Here's what we do: We build an AI-powered legal contract review tool for in-house legal teams at mid-market companies. Our tool flags risky clauses and suggests standard language. We're pre-seed, 3 months post-launch, no pricing page yet. US-focused.",
|
|
60
|
+
"env": {
|
|
61
|
+
"GEMINI_API_KEY": "set",
|
|
62
|
+
"TAVILY_API_KEY": "set",
|
|
63
|
+
"FIRECRAWL_API_KEY": "not set"
|
|
64
|
+
}
|
|
65
|
+
},
|
|
66
|
+
"expected_behavior": [
|
|
67
|
+
"Detects no URL in the input",
|
|
68
|
+
"Skips Step 3: no fetch attempt is made",
|
|
69
|
+
"Skips Step 4: no regex stage detection from page",
|
|
70
|
+
"Passes the pasted description directly to Gemini in Step 5",
|
|
71
|
+
"Stage set to 'pre-seed' with high confidence (user stated it explicitly)",
|
|
72
|
+
"Industry taxonomy: software > legaltech > contract review automation",
|
|
73
|
+
"Generates 5 comparable legaltech companies",
|
|
74
|
+
"Runs full Track A and Track B searches using description-derived comparables and taxonomy",
|
|
75
|
+
"Output note: 'Stage: pre-seed (stated by user)'",
|
|
76
|
+
"data_quality_flags includes note about stage coming from user description not page signals"
|
|
77
|
+
],
|
|
78
|
+
"expected_output": "Full VC list using description-derived analysis, legaltech-specific investors, stage labeled as user-stated"
|
|
79
|
+
},
|
|
80
|
+
{
|
|
81
|
+
"id": "eval_004",
|
|
82
|
+
"name": "GEMINI_API_KEY missing: immediate stop at Step 1",
|
|
83
|
+
"description": "Validates that the skill stops at Step 1 with exact setup instructions when Gemini key is absent.",
|
|
84
|
+
"input": {
|
|
85
|
+
"prompt": "Find VCs for https://stripe.com",
|
|
86
|
+
"env": {
|
|
87
|
+
"GEMINI_API_KEY": "not set",
|
|
88
|
+
"TAVILY_API_KEY": "set",
|
|
89
|
+
"FIRECRAWL_API_KEY": "set"
|
|
90
|
+
}
|
|
91
|
+
},
|
|
92
|
+
"expected_behavior": [
|
|
93
|
+
"Step 1 detects GEMINI_API_KEY is missing",
|
|
94
|
+
"Stops immediately at Step 1",
|
|
95
|
+
"Tells the user: 'GEMINI_API_KEY is required for product analysis and VC synthesis. Get it at aistudio.google.com. Add it to your .env file.'",
|
|
96
|
+
"Does NOT fetch the URL",
|
|
97
|
+
"Does NOT run any Tavily searches",
|
|
98
|
+
"Does NOT attempt any analysis"
|
|
99
|
+
],
|
|
100
|
+
"expected_output": "Immediate stop at Step 1 with exact error message including the URL to get the key. No partial output generated."
|
|
101
|
+
},
|
|
102
|
+
{
|
|
103
|
+
"id": "eval_005",
|
|
104
|
+
"name": "TAVILY_API_KEY missing: immediate stop at Step 1, no fallback",
|
|
105
|
+
"description": "Validates that the skill stops at Step 1 when Tavily key is absent, with no fallback path suggested.",
|
|
106
|
+
"input": {
|
|
107
|
+
"prompt": "Who invests in CI/CD automation startups? https://buildkite.com",
|
|
108
|
+
"env": {
|
|
109
|
+
"GEMINI_API_KEY": "set",
|
|
110
|
+
"TAVILY_API_KEY": "not set",
|
|
111
|
+
"FIRECRAWL_API_KEY": "set"
|
|
112
|
+
}
|
|
113
|
+
},
|
|
114
|
+
"expected_behavior": [
|
|
115
|
+
"Step 1 detects GEMINI_API_KEY is set",
|
|
116
|
+
"Step 1 detects TAVILY_API_KEY is missing",
|
|
117
|
+
"Stops immediately at Step 1",
|
|
118
|
+
"Tells the user: 'TAVILY_API_KEY is required to research VC investments and theses. There is no fallback for this. Get it at app.tavily.com. Free tier: 1000 credits/month (about 125 full runs). Add it to your .env file.'",
|
|
119
|
+
"Does NOT fetch the URL",
|
|
120
|
+
"Does NOT run any Gemini analysis",
|
|
121
|
+
"Does NOT suggest any workaround"
|
|
122
|
+
],
|
|
123
|
+
"expected_output": "Immediate stop at Step 1 with exact error message. Does not proceed past setup check."
|
|
124
|
+
}
|
|
125
|
+
]
|
|
@@ -0,0 +1,98 @@
|
|
|
1
|
+
# Stage Signals Reference
|
|
2
|
+
|
|
3
|
+
Used by SKILL.md Step 4 to detect funding stage from product page content before any API call.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Signal Detection Table
|
|
8
|
+
|
|
9
|
+
| Signal Pattern (regex) | Stage Hint | Example Page Text |
|
|
10
|
+
|---|---|---|
|
|
11
|
+
| `join (the )?waitlist` | pre-seed | "Join the waitlist for early access" |
|
|
12
|
+
| `sign up for beta` | pre-seed | "Sign up for our beta program" |
|
|
13
|
+
| `early access` | pre-seed | "Request early access" |
|
|
14
|
+
| `request (an? )?invite` | pre-seed | "Request an invite" |
|
|
15
|
+
| `get notified` | pre-seed | "Get notified when we launch" |
|
|
16
|
+
| `start (your )?free trial` | seed | "Start your free 14-day trial" |
|
|
17
|
+
| `try (it )?for free` | seed | "Try for free, no credit card required" |
|
|
18
|
+
| `request a? demo` | seed | "Request a demo" |
|
|
19
|
+
| `book a? demo` | seed | "Book a demo with our team" |
|
|
20
|
+
| `schedule a? demo` | seed | "Schedule a 30-minute demo" |
|
|
21
|
+
| `contact sales` | series-a | "Contact sales for enterprise pricing" |
|
|
22
|
+
| `talk to (our )?sales` | series-a | "Talk to our sales team" |
|
|
23
|
+
| `see pricing` / `view pricing` | series-a | "See pricing" |
|
|
24
|
+
| `plans and pricing` | series-a | "Plans and Pricing" |
|
|
25
|
+
| `case stud(y\|ies)` | series-a | "Read our case studies" |
|
|
26
|
+
| `customer stor(y\|ies)` | series-a | "Customer success stories" |
|
|
27
|
+
| `trusted by \d+` | series-a | "Trusted by 2,000+ teams" |
|
|
28
|
+
| `enterprise (plan\|pricing\|tier)` | series-a-or-b | "Enterprise plan available" |
|
|
29
|
+
| `we.?re hiring` | series-a-or-b | "We're hiring -- see open roles" |
|
|
30
|
+
| `join our team` | series-a-or-b | "Join our team of 50+" |
|
|
31
|
+
| `raised \$[\d,.]+[mk]?` | announced | "We raised $8M in Series A" |
|
|
32
|
+
| `series [abc] round` | announced | "Series B round closed" |
|
|
33
|
+
| `seed round` | announced | "Seed round led by X" |
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## Signal Confidence Rules
|
|
38
|
+
|
|
39
|
+
| Signals Found | Confidence |
|
|
40
|
+
|---|---|
|
|
41
|
+
| 2 or more matching signals | high |
|
|
42
|
+
| Exactly 1 matching signal | medium |
|
|
43
|
+
| 0 signals (stage estimated from content alone) | low |
|
|
44
|
+
| Funding announcement text found directly | high (overrides other signals) |
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## Handling Conflicting Signals
|
|
49
|
+
|
|
50
|
+
Some pages show signals from multiple stages simultaneously (e.g. a pricing page AND a waitlist). Use this resolution order:
|
|
51
|
+
|
|
52
|
+
1. Funding announcement text wins over all other signals (the stage is known, not inferred)
|
|
53
|
+
2. If both "pricing page" (Series A) and "free trial" (seed) signals appear: call it seed-to-series-a transition, output `series-a` with medium confidence
|
|
54
|
+
3. If both "waitlist" (pre-seed) and "demo request" (seed) signals appear: output `seed` -- the product is likely further along than the waitlist implies
|
|
55
|
+
4. If no signals found at all: output `unknown` with low confidence, pass this to Gemini with a note to infer from product maturity and content
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Common Misdetections
|
|
60
|
+
|
|
61
|
+
**"Request demo" from a mature Series B company:** Some large companies keep demo CTAs even after raising Series B. Override signals if the page also shows: enterprise logo bars, "trusted by Fortune 500", or explicit Series B announcement.
|
|
62
|
+
|
|
63
|
+
**Open-source projects:** Often show no stage signals (no pricing, no CTA). Output `unknown`. In the Gemini analysis step, note that the product appears open-source and ask Gemini to infer whether there is a commercial entity behind it.
|
|
64
|
+
|
|
65
|
+
**Startup landing pages with no product live:** A site with only a headline, a value prop paragraph, and an email capture is almost certainly pre-seed. Even without explicit waitlist language, if the page has no product demo and no pricing, output `pre-seed` with medium confidence.
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## Stage-to-Tavily Query Modifiers
|
|
70
|
+
|
|
71
|
+
These modifiers are added to Track B search queries based on detected stage:
|
|
72
|
+
|
|
73
|
+
| Detected Stage | Query Modifier |
|
|
74
|
+
|---|---|
|
|
75
|
+
| pre-seed | "pre-seed micro VC angel" |
|
|
76
|
+
| seed | "seed fund" |
|
|
77
|
+
| series-a | "series A lead investor" |
|
|
78
|
+
| series-b | "growth stage VC" |
|
|
79
|
+
| unknown | "early stage" (default) |
|
|
80
|
+
|
|
81
|
+
Example Track B query with modifier:
|
|
82
|
+
- L3 = "CI/CD automation", stage = seed
|
|
83
|
+
- Query: `seed fund "CI/CD automation" investment thesis portfolio companies`
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
87
|
+
## Stage-to-VC-Check-Size Reference
|
|
88
|
+
|
|
89
|
+
Use this to validate stage fit scores in the synthesis step:
|
|
90
|
+
|
|
91
|
+
| Stage | Typical Check Size |
|
|
92
|
+
|---|---|
|
|
93
|
+
| Pre-seed | $25K-$500K |
|
|
94
|
+
| Seed | $500K-$3M |
|
|
95
|
+
| Series A | $3M-$15M |
|
|
96
|
+
| Series B | $15M-$50M |
|
|
97
|
+
|
|
98
|
+
A VC whose typical check size is $20M-$50M has a stage fit score of 2 or lower for a pre-seed product, regardless of how well their thesis matches.
|
|
@@ -0,0 +1,142 @@
|
|
|
1
|
+
# VC Outreach Guide
|
|
2
|
+
|
|
3
|
+
How to approach the different investor archetypes the skill surfaces. The right approach depends on the VC type, not on the founder's preference.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## 5 Investor Archetypes
|
|
8
|
+
|
|
9
|
+
### Archetype 1: Thesis-First Writers (Track B investors)
|
|
10
|
+
|
|
11
|
+
These VCs publish blog posts, newsletters, or Twitter threads about why they want to invest in a specific space. They are signaling active deal interest.
|
|
12
|
+
|
|
13
|
+
**How to approach:**
|
|
14
|
+
1. Read the article or post that surfaced them in Track B before reaching out
|
|
15
|
+
2. Open with a direct reference to their specific thesis language, not a paraphrase: "You wrote in [post title] that you believe [exact phrase from post]. We built exactly that."
|
|
16
|
+
3. Keep the first message under 100 words. The thesis reference does the work -- do not over-explain.
|
|
17
|
+
4. Cold email works here. These VCs publish specifically to attract inbound -- they expect cold emails from founders who read their work.
|
|
18
|
+
|
|
19
|
+
**What to avoid:** Do not write "I came across your firm" or "I've been following your work." These are signals that you did not actually read the thesis. Quote it or do not mention it.
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
### Archetype 2: Portfolio-Pattern Investors (Track A investors)
|
|
24
|
+
|
|
25
|
+
These VCs backed a company comparable to yours. They already understand the space, the buyer, and the risk profile.
|
|
26
|
+
|
|
27
|
+
**How to approach:**
|
|
28
|
+
1. Name the specific portfolio company in your opening: "You backed [Company X] which means you understand [specific pain]."
|
|
29
|
+
2. Do not position yourself as a competitor to their portfolio company. Instead, find the adjacent or complementary angle: "We're solving the [different part of the workflow] problem that [Company X] doesn't address."
|
|
30
|
+
3. Cold email or LinkedIn works. Warm intro from a mutual connection in the portfolio company works best.
|
|
31
|
+
|
|
32
|
+
**What to avoid:** Do not say "just like [portfolio company] but better." This forces the investor to choose between two bets and they will default to protecting the existing one.
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
### Archetype 3: Operator-Turned-Investor
|
|
37
|
+
|
|
38
|
+
Former founders or operators who moved into investing. Typically reachable via warm intro from their portfolio company founders.
|
|
39
|
+
|
|
40
|
+
**How to approach:**
|
|
41
|
+
1. Find a founder in their portfolio via LinkedIn or the fund's website
|
|
42
|
+
2. Get a warm intro from that founder: "I'm building in the same space you were in at [company] -- would you be willing to introduce me to [investor name]?"
|
|
43
|
+
3. Operator-investors respond to founder-to-founder intros at 3-5x the rate of cold outreach
|
|
44
|
+
|
|
45
|
+
**What to avoid:** Cold email works less well with this archetype. They deal-select heavily from their personal networks. Do not skip the warm path attempt.
|
|
46
|
+
|
|
47
|
+
---
|
|
48
|
+
|
|
49
|
+
### Archetype 4: Multi-Stage Generalists with Sector Coverage
|
|
50
|
+
|
|
51
|
+
Large funds with dedicated sector teams. Partners focus on different verticals. Do not email the wrong person.
|
|
52
|
+
|
|
53
|
+
**How to approach:**
|
|
54
|
+
1. Identify the specific partner who covers your sector from the fund website or LinkedIn. Look for their recent investments in your space.
|
|
55
|
+
2. Email the sector partner, not the managing partner or the fund's general inbox.
|
|
56
|
+
3. If you cannot identify the right partner, email a principal or associate first and ask who covers your space. They are more responsive and will route you correctly.
|
|
57
|
+
|
|
58
|
+
**What to avoid:** Do not cold email a managing partner at a large fund with no warm intro. Response rates are near zero. The sector partner path is 10x more effective.
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
### Archetype 5: Scout Program Participants
|
|
63
|
+
|
|
64
|
+
Many top-tier funds (a16z, First Round, Bessemer, etc.) run scout programs -- operators, founders, and angels who refer deals in exchange for carry. Scouts have much higher response rates than GPs at the same fund.
|
|
65
|
+
|
|
66
|
+
**How to approach:**
|
|
67
|
+
1. Find scouts on Twitter/X or LinkedIn (search "[fund name] scout")
|
|
68
|
+
2. Scouts are often active founders themselves -- they respond well to peer-to-peer founder outreach
|
|
69
|
+
3. A positive scout referral carries significant weight internally at the fund
|
|
70
|
+
|
|
71
|
+
**What to avoid:** Do not treat a scout as a gatekeeper to avoid. A scout intro is often more valuable than a cold email to the GP.
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## Cold Email vs Warm Intro
|
|
76
|
+
|
|
77
|
+
| Method | Typical Response Rate | When to Use |
|
|
78
|
+
|---|---|---|
|
|
79
|
+
| Cold email (generic) | 1-3% | Only if no warm path exists |
|
|
80
|
+
| Cold email (thesis-referenced) | 8-15% | Track B investors who published their thesis |
|
|
81
|
+
| Cold email (portfolio-referenced) | 5-10% | Track A investors with named portfolio evidence |
|
|
82
|
+
| Warm intro from portfolio founder | 30-50% | Always attempt first for Archetype 3 and 4 |
|
|
83
|
+
| Warm intro from mutual angel/advisor | 20-35% | Use your existing cap table to find bridge connections |
|
|
84
|
+
|
|
85
|
+
The warm intro advantage is real. Before sending a cold email to a Track A or Track B investor, spend 10 minutes on LinkedIn finding a second-degree connection through their portfolio companies. One warm intro is worth 10 cold emails.
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## Application-Form Funds
|
|
90
|
+
|
|
91
|
+
Some funds operate structured intake processes. These require filling out a form, not cold emailing.
|
|
92
|
+
|
|
93
|
+
| Fund Type | How to Engage |
|
|
94
|
+
|---|---|
|
|
95
|
+
| YC | Apply during batch cycle at ycombinator.com/apply |
|
|
96
|
+
| First Round Capital | Submit via firstround.com/funding |
|
|
97
|
+
| Andreessen Horowitz | Public application at a16z.com -- reference their exact investment criteria from their published content |
|
|
98
|
+
| Sequoia | Warm intro strongly preferred; Arc program for early stage |
|
|
99
|
+
| Techstars | Apply to accelerator program for access to their network |
|
|
100
|
+
|
|
101
|
+
For application-form funds: use the exact language from their published investment criteria in your application. They score applications against stated criteria. Generic applications score low regardless of product quality.
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
## Outreach Message Structure
|
|
106
|
+
|
|
107
|
+
For cold email (any archetype):
|
|
108
|
+
|
|
109
|
+
```
|
|
110
|
+
Subject: [Specific signal reference, under 8 words]
|
|
111
|
+
|
|
112
|
+
[Sentence about THEM -- their portfolio company, their thesis, their recent investment]
|
|
113
|
+
|
|
114
|
+
[One sentence about what you build and who it is for]
|
|
115
|
+
|
|
116
|
+
[One specific data point: metric, customer, or signal]
|
|
117
|
+
|
|
118
|
+
[One-line ask: 20-minute call, or specific question]
|
|
119
|
+
|
|
120
|
+
[Name]
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
Hard limits:
|
|
124
|
+
- Email body: under 100 words
|
|
125
|
+
- Subject line: under 8 words
|
|
126
|
+
- No attachments in first message
|
|
127
|
+
- No pitch deck link in first message (send on request only)
|
|
128
|
+
- No "I hope this finds you well" or "I wanted to reach out"
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Red Flags to Check Before Outreach
|
|
133
|
+
|
|
134
|
+
Before emailing any VC from the output list, check:
|
|
135
|
+
|
|
136
|
+
1. **Recent fund vintage:** A fund that raised in 2019 and has not announced a new fund is likely deployed and not writing new checks. Check Crunchbase or their website for their most recent fund announcement.
|
|
137
|
+
|
|
138
|
+
2. **Portfolio company failure in your space:** If a VC backed a direct competitor that failed, they may be reluctant to re-invest in the same category. Frame your differentiation clearly.
|
|
139
|
+
|
|
140
|
+
3. **Check size mismatch:** If the VC's minimum check is $5M and you are raising a $1M seed, the round economics do not work. Do not waste either side's time.
|
|
141
|
+
|
|
142
|
+
4. **Geography restriction:** Some funds explicitly invest only in US companies or only in European companies. Check their website before outreach.
|