startup-ideation-kit 1.0.0 → 2.0.0
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/README.md +46 -34
- package/bin/cli.js +7 -1
- package/package.json +7 -3
- package/skills/sk-competitors/SKILL.md +284 -0
- package/skills/sk-competitors/references/honesty-protocol.md +72 -0
- package/skills/sk-competitors/references/research-principles.md +54 -0
- package/skills/sk-competitors/references/research-scaling.md +106 -0
- package/skills/sk-competitors/references/research-synthesis.md +237 -0
- package/skills/sk-competitors/references/research-wave-1-profiles-pricing.md +186 -0
- package/skills/sk-competitors/references/research-wave-2-sentiment-mining.md +189 -0
- package/skills/sk-competitors/references/research-wave-3-gtm-signals.md +192 -0
- package/skills/sk-competitors/references/verification-agent.md +126 -0
- package/skills/sk-export/SKILL.md +36 -12
- package/skills/sk-leads/SKILL.md +9 -8
- package/skills/sk-money/SKILL.md +7 -6
- package/skills/sk-niche/SKILL.md +3 -3
- package/skills/sk-offer/SKILL.md +15 -6
- package/skills/sk-pitch/SKILL.md +461 -0
- package/skills/sk-pitch/references/honesty-protocol.md +62 -0
- package/skills/sk-pitch/references/pitch-frameworks.md +261 -0
- package/skills/sk-pitch/references/research-principles.md +64 -0
- package/skills/sk-pitch/references/research-scaling.md +96 -0
- package/skills/sk-pitch/references/research-synthesis.md +423 -0
- package/skills/sk-pitch/references/research-wave-1-audience-narrative.md +164 -0
- package/skills/sk-pitch/references/research-wave-2-competitive-framing.md +159 -0
- package/skills/sk-pitch/references/verification-agent.md +129 -0
- package/skills/sk-positioning/SKILL.md +318 -0
- package/skills/sk-positioning/references/frameworks.md +132 -0
- package/skills/sk-positioning/references/honesty-protocol.md +72 -0
- package/skills/sk-positioning/references/research-principles.md +64 -0
- package/skills/sk-positioning/references/research-scaling.md +96 -0
- package/skills/sk-positioning/references/research-synthesis.md +419 -0
- package/skills/sk-positioning/references/research-wave-1-alternatives.md +236 -0
- package/skills/sk-positioning/references/research-wave-2-market-frame.md +208 -0
- package/skills/sk-positioning/references/verification-agent.md +128 -0
- package/skills/sk-skills/SKILL.md +9 -8
- package/skills/sk-validate/SKILL.md +8 -6
- package/skills/startupkit/SKILL.md +39 -17
- package/templates/competitors-template.md +43 -0
- package/templates/pitch-template.md +48 -0
- package/templates/positioning-template.md +51 -0
- package/templates/session-template.md +26 -7
|
@@ -0,0 +1,423 @@
|
|
|
1
|
+
# Pitch Research Synthesis Protocol
|
|
2
|
+
|
|
3
|
+
## Before Writing
|
|
4
|
+
|
|
5
|
+
1. Read ALL raw files in `{project-name}/raw/` before writing anything
|
|
6
|
+
2. Read ALL prior session files (from startup-design, startup-competitors, startup-positioning) if they exist
|
|
7
|
+
3. Identify the strongest pitch elements — what's most impressive about this company?
|
|
8
|
+
4. Determine the optimal pitch order based on strengths
|
|
9
|
+
5. Check if the pitch was built with or without validated research data — this affects the scorecard
|
|
10
|
+
|
|
11
|
+
## Cross-Source Connections to Look For
|
|
12
|
+
|
|
13
|
+
These are pitch-specific patterns that emerge when you combine research with founder data:
|
|
14
|
+
|
|
15
|
+
- **Strong traction + weak insight = lead with traction** — the numbers speak for themselves
|
|
16
|
+
- **Weak traction + strong insight = lead with insight** — reframe the conversation around the thesis
|
|
17
|
+
- **Strong team + emerging market = lead with team** — investors bet on people in uncertain markets
|
|
18
|
+
- **Large market + clear model = lead with opportunity** — the math is compelling
|
|
19
|
+
- **Comparable success story + similar approach = use the analogy** — investors love pattern-matching
|
|
20
|
+
- **Investor fatigue in space + unique angle = differentiate the narrative** — show you're different
|
|
21
|
+
- **Strong "why now" + weak traction = lead with timing** — the wave is more impressive than the surfer
|
|
22
|
+
- **Competitive gaps + unique attributes = frame against competitors** — show the opening
|
|
23
|
+
|
|
24
|
+
## Confidence Rating
|
|
25
|
+
|
|
26
|
+
Apply to every major claim in the pitch materials:
|
|
27
|
+
|
|
28
|
+
- **High:** Multiple sources agree, data is recent, verifiable
|
|
29
|
+
- **Medium:** Some evidence but gaps, or data partially disagree
|
|
30
|
+
- **Low:** Limited data, mostly inferred, or data older than 12 months
|
|
31
|
+
|
|
32
|
+
In the pitch itself, only use High and Medium confidence claims. Low confidence items go in the appendix as "areas to strengthen."
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## Pitch Construction Process
|
|
37
|
+
|
|
38
|
+
### Step 1: Identify Pitch DNA
|
|
39
|
+
|
|
40
|
+
Before writing anything, answer these questions:
|
|
41
|
+
|
|
42
|
+
1. **What's the single most impressive thing about this company?** (This determines pitch order)
|
|
43
|
+
2. **What's the 2-sentence description?** (This is non-negotiable — must be crystal clear)
|
|
44
|
+
3. **What's the unique insight?** (This separates a pitch from a product description)
|
|
45
|
+
4. **What's the "why now"?** (Timing thesis — what makes this moment right)
|
|
46
|
+
5. **What's the biggest weakness?** (Must have a prepared answer)
|
|
47
|
+
|
|
48
|
+
### Step 2: Assemble the Building Blocks
|
|
49
|
+
|
|
50
|
+
Map available data to the 8 pitch elements:
|
|
51
|
+
|
|
52
|
+
| Element | Source | Strength | Notes |
|
|
53
|
+
|---------|--------|----------|-------|
|
|
54
|
+
| What You Do | Intake / positioning-statement.md | | |
|
|
55
|
+
| Traction | Intake / scorecard.md | | |
|
|
56
|
+
| Unique Insight | Intake / research | | |
|
|
57
|
+
| Business Model | lean-canvas.md / revenue-model.md | | |
|
|
58
|
+
| Market Size | market-analysis.md / intake | | |
|
|
59
|
+
| Team | Intake | | |
|
|
60
|
+
| The Ask | Intake | | |
|
|
61
|
+
| Why Now | Wave 2 research / intake | | |
|
|
62
|
+
|
|
63
|
+
Strength ratings: Strong / Adequate / Weak / Missing
|
|
64
|
+
|
|
65
|
+
**Data Foundation Check:** Note whether each element is backed by validated research (from prior startup skills) or self-reported data (from intake only). This affects the scorecard in Phase 4.
|
|
66
|
+
|
|
67
|
+
### Step 3: Determine Pitch Order
|
|
68
|
+
|
|
69
|
+
Based on element strengths, select the template from `pitch-frameworks.md`:
|
|
70
|
+
- Strongest element is Traction → Traction-Led
|
|
71
|
+
- Strongest element is Team → Team-Led
|
|
72
|
+
- Strongest element is Insight → Insight-Led
|
|
73
|
+
- No clear standout → Pre-Traction (default)
|
|
74
|
+
|
|
75
|
+
### Step 4: Write the Narrative
|
|
76
|
+
|
|
77
|
+
Construct the pitch as a continuous story, not a collection of sections. Each element should flow naturally into the next. The narrative should feel like:
|
|
78
|
+
|
|
79
|
+
"Here's what we do. [Here's why it's working / Here's what we know / Here's who we are.] Here's the problem we're solving. Here's our solution. Here's how big this can get. Here's how we make money. Here's why we're the team to do it. Here's what we need."
|
|
80
|
+
|
|
81
|
+
### Step 5: Generate All Requested Formats
|
|
82
|
+
|
|
83
|
+
From the full narrative, derive each format by compression — not by rewriting from scratch. Each shorter format is a subset of the full pitch.
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
87
|
+
## Output File Templates
|
|
88
|
+
|
|
89
|
+
### pitch-full.md
|
|
90
|
+
|
|
91
|
+
```markdown
|
|
92
|
+
# Full Pitch Narrative: {product}
|
|
93
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
94
|
+
|
|
95
|
+
## Pitch DNA
|
|
96
|
+
- **Lead element:** {traction/team/insight/market}
|
|
97
|
+
- **2-sentence opener:** {the opener}
|
|
98
|
+
- **Unique insight:** {one sentence}
|
|
99
|
+
- **Why now:** {timing thesis}
|
|
100
|
+
- **The ask:** {amount + milestones}
|
|
101
|
+
- **Data foundation:** {Validated (prior startup skills) / Self-reported (intake only)}
|
|
102
|
+
|
|
103
|
+
## Full Narrative (~10 minutes)
|
|
104
|
+
|
|
105
|
+
### Opening — What We Do
|
|
106
|
+
{2 sentences + specific example}
|
|
107
|
+
|
|
108
|
+
> **Speaker notes:** {delivery guidance — pace, emphasis, pauses}
|
|
109
|
+
> **Timing:** 0:00 - 0:45
|
|
110
|
+
|
|
111
|
+
### {Lead Element — varies by pitch type}
|
|
112
|
+
{Content}
|
|
113
|
+
|
|
114
|
+
> **Speaker notes:** {delivery guidance}
|
|
115
|
+
> **Timing:** 0:45 - 2:00
|
|
116
|
+
|
|
117
|
+
### Problem
|
|
118
|
+
{Problem description — severity, consequences, who suffers}
|
|
119
|
+
|
|
120
|
+
> **Speaker notes:** {delivery guidance}
|
|
121
|
+
> **Timing:** 2:00 - 3:00
|
|
122
|
+
|
|
123
|
+
### Solution
|
|
124
|
+
{How it works — describe the concrete user experience. What does the user SEE and DO? Not abstract features — the specific interaction that solves the problem. If the product exists, describe it as if showing a demo. If pre-launch, describe the intended experience vividly enough that the investor can picture it.}
|
|
125
|
+
|
|
126
|
+
> **Speaker notes:** {delivery guidance}
|
|
127
|
+
> **Timing:** 3:00 - 4:00
|
|
128
|
+
|
|
129
|
+
### Traction
|
|
130
|
+
{Metrics with timeframes — growth story. If no traction: skip this section, don't fake it.}
|
|
131
|
+
|
|
132
|
+
> **Speaker notes:** {delivery guidance}
|
|
133
|
+
> **Timing:** 4:00 - 5:00
|
|
134
|
+
|
|
135
|
+
### Market Size
|
|
136
|
+
{Bottom-up calculation — show the math: number of customers × price = addressable market. Beachhead + expansion path.}
|
|
137
|
+
|
|
138
|
+
> **Speaker notes:** {delivery guidance}
|
|
139
|
+
> **Timing:** 5:00 - 6:00
|
|
140
|
+
|
|
141
|
+
### Business Model
|
|
142
|
+
{One clear model — pricing, unit economics if available}
|
|
143
|
+
|
|
144
|
+
> **Speaker notes:** {delivery guidance}
|
|
145
|
+
> **Timing:** 6:00 - 6:30
|
|
146
|
+
|
|
147
|
+
### Why Now
|
|
148
|
+
{Timing thesis from Wave 2 research. Technology shift, behavioral change, regulatory move. If timing isn't strong, keep this brief or fold into another section.}
|
|
149
|
+
|
|
150
|
+
> **Speaker notes:** {delivery guidance}
|
|
151
|
+
> **Timing:** 6:30 - 7:00
|
|
152
|
+
|
|
153
|
+
### Team
|
|
154
|
+
{Accomplishments, not titles. For each person: name, role, most impressive specific result.}
|
|
155
|
+
|
|
156
|
+
> **Speaker notes:** {delivery guidance}
|
|
157
|
+
> **Timing:** 7:00 - 7:30
|
|
158
|
+
|
|
159
|
+
### The Ask
|
|
160
|
+
{Amount + milestones + timeframe. Be direct and confident.}
|
|
161
|
+
|
|
162
|
+
> **Speaker notes:** {delivery guidance}
|
|
163
|
+
> **Timing:** 7:30 - 8:00
|
|
164
|
+
|
|
165
|
+
### Close
|
|
166
|
+
{Final sentence — memorable, forward-looking. Leave them wanting to talk more.}
|
|
167
|
+
|
|
168
|
+
## Transition Sentences
|
|
169
|
+
{How each section flows into the next — so the pitch feels like a story, not a checklist}
|
|
170
|
+
|
|
171
|
+
## Red Flags
|
|
172
|
+
- {issues investors might raise}
|
|
173
|
+
|
|
174
|
+
## Yellow Flags
|
|
175
|
+
- {concerns to prepare for}
|
|
176
|
+
|
|
177
|
+
## Sources
|
|
178
|
+
- {key data sources used in the pitch}
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
### pitch-5min.md
|
|
182
|
+
|
|
183
|
+
```markdown
|
|
184
|
+
# Five-Minute Pitch: {product}
|
|
185
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
186
|
+
|
|
187
|
+
## The Narrative (~5 minutes)
|
|
188
|
+
|
|
189
|
+
{Each element trimmed to its core claim + one supporting proof point. No secondary arguments — just the strongest version of each element.}
|
|
190
|
+
|
|
191
|
+
### Opening — What We Do (0:00 - 0:30)
|
|
192
|
+
{2 sentences + example}
|
|
193
|
+
|
|
194
|
+
### {Lead Element} (0:30 - 1:15)
|
|
195
|
+
{Core claim + proof}
|
|
196
|
+
|
|
197
|
+
### Problem + Solution (1:15 - 2:30)
|
|
198
|
+
{Problem in 2 sentences → solution as concrete experience}
|
|
199
|
+
|
|
200
|
+
### Market + Business Model (2:30 - 3:30)
|
|
201
|
+
{Bottom-up math + one-sentence model}
|
|
202
|
+
|
|
203
|
+
### Why Now + Team (3:30 - 4:30)
|
|
204
|
+
{Timing thesis + team accomplishments}
|
|
205
|
+
|
|
206
|
+
### The Ask (4:30 - 5:00)
|
|
207
|
+
{Amount + milestones + timeframe}
|
|
208
|
+
|
|
209
|
+
## Speaker Notes
|
|
210
|
+
{Pacing guidance — where to breathe, where to let silence work}
|
|
211
|
+
|
|
212
|
+
## Red Flags
|
|
213
|
+
- {concerns}
|
|
214
|
+
|
|
215
|
+
## Sources
|
|
216
|
+
- {key sources}
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
### pitch-2min.md
|
|
220
|
+
|
|
221
|
+
```markdown
|
|
222
|
+
# Two-Minute Pitch: {product}
|
|
223
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
224
|
+
|
|
225
|
+
## The Script (~300 words)
|
|
226
|
+
|
|
227
|
+
{Word-for-word script, broken into natural paragraphs. Each paragraph = one element.}
|
|
228
|
+
|
|
229
|
+
## Delivery Notes
|
|
230
|
+
- **Opener pace:** Slow and clear — this is where understanding happens
|
|
231
|
+
- **Emphasis points:** {words/phrases to stress}
|
|
232
|
+
- **Natural pauses:** {where to breathe and let it sink in}
|
|
233
|
+
- **Energy peak:** {which sentence should have the most energy}
|
|
234
|
+
- **Close:** Confident, direct, unhurried
|
|
235
|
+
|
|
236
|
+
## Structure Breakdown
|
|
237
|
+
- **0:00 - 0:20:** What we do (2 sentences + example)
|
|
238
|
+
- **0:20 - 0:40:** Strongest signal (traction/insight/team)
|
|
239
|
+
- **0:40 - 1:00:** Problem + solution
|
|
240
|
+
- **1:00 - 1:20:** Market + business model
|
|
241
|
+
- **1:20 - 1:40:** Why us + why now
|
|
242
|
+
- **1:40 - 2:00:** The ask
|
|
243
|
+
|
|
244
|
+
## The Email Test
|
|
245
|
+
{Paraphrase of the pitch in one paragraph — what someone should be able to repeat after hearing it once}
|
|
246
|
+
|
|
247
|
+
## Red Flags
|
|
248
|
+
- {concerns}
|
|
249
|
+
|
|
250
|
+
## Sources
|
|
251
|
+
- {key sources}
|
|
252
|
+
```
|
|
253
|
+
|
|
254
|
+
### pitch-1min.md
|
|
255
|
+
|
|
256
|
+
```markdown
|
|
257
|
+
# Elevator Pitch: {product}
|
|
258
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
259
|
+
|
|
260
|
+
## Formal Version (~150 words)
|
|
261
|
+
{For investor events, demo days, formal introductions. Structured: What We Do → Insight → Ask.}
|
|
262
|
+
|
|
263
|
+
## Casual Version (~100 words)
|
|
264
|
+
{For networking, dinner parties, hallway conversations. Conversational tone, no pitch structure visible. Sounds like you're telling a friend about your company.}
|
|
265
|
+
|
|
266
|
+
## When Someone Asks "So What Do You Do?"
|
|
267
|
+
{The 2-sentence answer + example that leads to "tell me more"}
|
|
268
|
+
|
|
269
|
+
## Delivery Notes
|
|
270
|
+
- Don't rush. 1 minute is longer than it feels.
|
|
271
|
+
- End with a question, not a statement — "Would that be useful for [your company]?" invites conversation.
|
|
272
|
+
- Match energy to context. Formal events: crisp, confident. Casual: relaxed, curious.
|
|
273
|
+
|
|
274
|
+
## Red Flags
|
|
275
|
+
- {concerns}
|
|
276
|
+
```
|
|
277
|
+
|
|
278
|
+
### pitch-email.md
|
|
279
|
+
|
|
280
|
+
```markdown
|
|
281
|
+
# Investor Email Pitch: {product}
|
|
282
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
283
|
+
|
|
284
|
+
## Subject Line Candidates
|
|
285
|
+
| Subject Line | Angle | Best For |
|
|
286
|
+
|---|---|---|
|
|
287
|
+
| "{subject 1}" | {angle} | {investor type} |
|
|
288
|
+
| "{subject 2}" | {angle} | {investor type} |
|
|
289
|
+
| "{subject 3}" | {angle} | {investor type} |
|
|
290
|
+
|
|
291
|
+
## Cold Email (~500 words)
|
|
292
|
+
|
|
293
|
+
{Hook — one sentence that makes them read the next line}
|
|
294
|
+
|
|
295
|
+
{What we do — 2 sentences + example}
|
|
296
|
+
|
|
297
|
+
{Traction or insight — the strongest signal, with numbers}
|
|
298
|
+
|
|
299
|
+
{Why now — one sentence timing thesis}
|
|
300
|
+
|
|
301
|
+
{The ask — specific and direct}
|
|
302
|
+
|
|
303
|
+
{Close — easy next step, not "let me know your thoughts"}
|
|
304
|
+
|
|
305
|
+
## Follow-Up Email (~200 words)
|
|
306
|
+
|
|
307
|
+
{Shorter, references the first email. Adds one new data point. Clear CTA.}
|
|
308
|
+
|
|
309
|
+
## Personalization Notes
|
|
310
|
+
- **For angel investors:** Lead with the problem and your personal connection to it
|
|
311
|
+
- **For VCs:** Lead with traction or market size
|
|
312
|
+
- **For accelerators:** Lead with team and speed of execution
|
|
313
|
+
- **For strategic partners:** Lead with mutual opportunity
|
|
314
|
+
|
|
315
|
+
## Red Flags
|
|
316
|
+
- {email-specific concerns}
|
|
317
|
+
|
|
318
|
+
## Sources
|
|
319
|
+
- {key sources}
|
|
320
|
+
```
|
|
321
|
+
|
|
322
|
+
### pitch-appendix.md
|
|
323
|
+
|
|
324
|
+
```markdown
|
|
325
|
+
# Pitch Appendix: {product}
|
|
326
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
327
|
+
|
|
328
|
+
## Top 10 Investor Questions (with Prepared Answers)
|
|
329
|
+
|
|
330
|
+
### Q1: {Most likely question}
|
|
331
|
+
**Short answer:** {2-3 sentences — for verbal delivery}
|
|
332
|
+
**Detailed answer:** {full explanation with data — for follow-up emails}
|
|
333
|
+
**Source:** {where the data comes from}
|
|
334
|
+
|
|
335
|
+
[Repeat for Q2-Q10]
|
|
336
|
+
|
|
337
|
+
## Objection Handling
|
|
338
|
+
|
|
339
|
+
### "{Objection 1}"
|
|
340
|
+
**Why they ask this:** {investor's concern}
|
|
341
|
+
**Response:** {how to address it honestly}
|
|
342
|
+
**Supporting data:** {evidence}
|
|
343
|
+
|
|
344
|
+
[Repeat for each common objection]
|
|
345
|
+
|
|
346
|
+
## Known Weaknesses
|
|
347
|
+
{Honest assessment of pitch gaps — with plans to address each. Identifying weaknesses proactively is stronger than hoping investors won't notice.}
|
|
348
|
+
|
|
349
|
+
## Financial Backup
|
|
350
|
+
{Detailed numbers if available from prior sessions. If not: note "Financial projections not yet validated — consider running startup-design for detailed modeling."}
|
|
351
|
+
|
|
352
|
+
## Competitive Detail
|
|
353
|
+
{Deeper competitive analysis for Q&A — from prior sessions if available. If not: note "Competitive landscape not fully mapped — consider running startup-competitors for battle cards."}
|
|
354
|
+
|
|
355
|
+
## Red Flags
|
|
356
|
+
- {appendix-specific concerns}
|
|
357
|
+
|
|
358
|
+
## Yellow Flags
|
|
359
|
+
- {areas needing more data}
|
|
360
|
+
|
|
361
|
+
## Data Gaps & Limitations
|
|
362
|
+
- {what data is missing — every pitch has blind spots, be explicit}
|
|
363
|
+
|
|
364
|
+
## Sources
|
|
365
|
+
- {all data sources used across all deliverables, with tier ratings}
|
|
366
|
+
```
|
|
367
|
+
|
|
368
|
+
## Post-Synthesis Verification
|
|
369
|
+
|
|
370
|
+
After writing all pitch deliverables (before the scorecard/review phase), run the Verification Agent protocol. See `references/verification-agent.md` for the full process. The verification step checks all deliverables for unlabeled claims, internal contradictions, confidence rating consistency, and startup-pitch-specific coherence (pitch claims vs. source data, cross-format consistency, pitch vs. appendix alignment, honesty checks).
|
|
371
|
+
|
|
372
|
+
---
|
|
373
|
+
|
|
374
|
+
### pitch-scorecard.md
|
|
375
|
+
|
|
376
|
+
```markdown
|
|
377
|
+
# Pitch Scorecard: {product}
|
|
378
|
+
*Skill: startup-pitch | Generated: {date}*
|
|
379
|
+
|
|
380
|
+
## Data Foundation
|
|
381
|
+
**Built with:** {Validated research (startup-design/competitors/positioning) / Self-reported data (intake only)}
|
|
382
|
+
{If self-reported: "Note: This pitch was built without validated research data. Scores in Market Sizing, Traction Honesty, and competitive Q&A may improve significantly after running startup-design or startup-competitors."}
|
|
383
|
+
|
|
384
|
+
## Scoring Rubric
|
|
385
|
+
|
|
386
|
+
| Dimension | Score (1-10) | Rationale |
|
|
387
|
+
|-----------|-------------|-----------|
|
|
388
|
+
| **Clarity** | | {Can someone explain what you do after hearing 2 sentences?} |
|
|
389
|
+
| **Strength Sequencing** | | {Is the most impressive element in the first 60 seconds?} |
|
|
390
|
+
| **Traction Honesty** | | {Are numbers accurate, timeframed, and real? Or acknowledged as missing?} |
|
|
391
|
+
| **Insight Quality** | | {Is the insight genuinely non-obvious and specific?} |
|
|
392
|
+
| **Market Sizing** | | {Is the math bottom-up with clear assumptions?} |
|
|
393
|
+
| **Business Model** | | {One model, clearly stated?} |
|
|
394
|
+
| **Team Credentials** | | {Specific, verifiable accomplishments?} |
|
|
395
|
+
| **Ask Clarity** | | {Amount + milestones + timeframe, stated with confidence?} |
|
|
396
|
+
| **Overall** | | |
|
|
397
|
+
|
|
398
|
+
## Verdict
|
|
399
|
+
- **65-80:** Investor-ready. Go pitch.
|
|
400
|
+
- **50-64:** Investor-ready with caveats. Address the weak dimensions first.
|
|
401
|
+
- **35-49:** Needs work. Iterate on the weakest areas before pitching.
|
|
402
|
+
- **Below 35:** Major gaps. Consider running startup-design or startup-positioning to strengthen the foundation.
|
|
403
|
+
|
|
404
|
+
## Weak Dimensions (Score < 7)
|
|
405
|
+
For each:
|
|
406
|
+
- **Dimension:** {name}
|
|
407
|
+
- **What's weak:** {specific problem}
|
|
408
|
+
- **How to fix:** {actionable suggestion}
|
|
409
|
+
- **Data needed:** {what information would strengthen this}
|
|
410
|
+
|
|
411
|
+
## Delivery Readiness
|
|
412
|
+
- [ ] 2-sentence opener practiced until effortless
|
|
413
|
+
- [ ] All numbers memorized (not read from notes)
|
|
414
|
+
- [ ] Prepared answers for top 5 investor questions
|
|
415
|
+
- [ ] Know the biggest weakness and how to address it
|
|
416
|
+
- [ ] Practiced with at least one person (or investor roleplay)
|
|
417
|
+
|
|
418
|
+
## Red Flags
|
|
419
|
+
- {scorecard-specific concerns}
|
|
420
|
+
|
|
421
|
+
## Yellow Flags
|
|
422
|
+
- {areas to watch}
|
|
423
|
+
```
|
|
@@ -0,0 +1,164 @@
|
|
|
1
|
+
# Wave 1: Audience & Narrative Intelligence
|
|
2
|
+
|
|
3
|
+
Read `research-principles.md` first.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Agent A1: Investor & Audience Intelligence
|
|
8
|
+
|
|
9
|
+
```
|
|
10
|
+
Research task: Build investor audience profile for {product description} pitch
|
|
11
|
+
Context: {product summary from intake}
|
|
12
|
+
Target audience: {VC/angels/accelerator/demo day — from intake}
|
|
13
|
+
Stage: {pre-seed/seed/Series A — from intake}
|
|
14
|
+
|
|
15
|
+
RESEARCH PROTOCOL:
|
|
16
|
+
|
|
17
|
+
ROUND 1 — Fundraising landscape in this space (4-5 searches):
|
|
18
|
+
- "{product category} startup funding {current year}"
|
|
19
|
+
- "{product category} VC investments {current year}"
|
|
20
|
+
- "seed stage {product category} fundraise"
|
|
21
|
+
- "{product space} Series A metrics benchmarks"
|
|
22
|
+
- "what VCs look for in {product category} startups"
|
|
23
|
+
|
|
24
|
+
ROUND 2 — Specific audience research (3-4 searches):
|
|
25
|
+
If specific investors/funds are named:
|
|
26
|
+
- "{fund name} portfolio companies"
|
|
27
|
+
- "{fund name} investment thesis"
|
|
28
|
+
- "{investor name} blog pitch advice"
|
|
29
|
+
- "{fund name} demo day companies"
|
|
30
|
+
|
|
31
|
+
If no specific audience:
|
|
32
|
+
- "best investors {product category} {current year}"
|
|
33
|
+
- "{product category} angel investors"
|
|
34
|
+
- "{accelerator name} recent batch companies"
|
|
35
|
+
|
|
36
|
+
ROUND 3 — Stage-appropriate metrics (3-4 searches):
|
|
37
|
+
- "seed stage metrics investors expect {current year}"
|
|
38
|
+
- "{product category} startup benchmarks Series A"
|
|
39
|
+
- "what traction for seed round {product category}"
|
|
40
|
+
- "seed round size {product category} {current year}"
|
|
41
|
+
- "pre-seed vs seed metrics expectations"
|
|
42
|
+
|
|
43
|
+
ROUND 4 — Current climate (2-3 searches):
|
|
44
|
+
- "fundraising climate {current year} startups"
|
|
45
|
+
- "{product category} funding trends {current year}"
|
|
46
|
+
- "VC sentiment {product space} {current year}"
|
|
47
|
+
|
|
48
|
+
OUTPUT FORMAT:
|
|
49
|
+
|
|
50
|
+
## Investor Audience Profile
|
|
51
|
+
|
|
52
|
+
### Fundraising Landscape
|
|
53
|
+
- Current funding climate in {space}: {bullish/neutral/bearish}
|
|
54
|
+
- Recent notable rounds: {examples with amounts}
|
|
55
|
+
- Average round size at this stage: {range}
|
|
56
|
+
- Key metrics investors expect at this stage:
|
|
57
|
+
- {metric 1}: {benchmark}
|
|
58
|
+
- {metric 2}: {benchmark}
|
|
59
|
+
- {metric 3}: {benchmark}
|
|
60
|
+
|
|
61
|
+
### Target Investor Profile
|
|
62
|
+
- Fund/investor type: {VC/angel/accelerator}
|
|
63
|
+
- Typical check size: {range}
|
|
64
|
+
- Investment thesis alignment: {how this pitch fits}
|
|
65
|
+
- Portfolio overlap: {similar companies they've funded}
|
|
66
|
+
- Red flags for this audience: {what turns them off}
|
|
67
|
+
|
|
68
|
+
### Stage-Appropriate Expectations
|
|
69
|
+
- What "good traction" looks like at this stage: {specifics}
|
|
70
|
+
- What "great traction" looks like: {specifics}
|
|
71
|
+
- Minimum viable metrics to raise: {specifics}
|
|
72
|
+
- Common objections at this stage: {list}
|
|
73
|
+
|
|
74
|
+
### Current Climate Notes
|
|
75
|
+
- Fundraising difficulty: {easier/normal/harder than 12 months ago}
|
|
76
|
+
- Hot topics investors are interested in: {trends}
|
|
77
|
+
- Topics investors are fatigued by: {overhyped areas}
|
|
78
|
+
|
|
79
|
+
> Data labels: Mark each finding with [Data], [Estimate], [Assumption], or [Opinion]
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
## Agent A2: Comparable & Narrative Research
|
|
85
|
+
|
|
86
|
+
```
|
|
87
|
+
Research task: Find comparable pitch narratives and story hooks for {product description}
|
|
88
|
+
Context: {product summary from intake}
|
|
89
|
+
Market: {market/category from intake}
|
|
90
|
+
Competitors: {known competitors from intake}
|
|
91
|
+
|
|
92
|
+
RESEARCH PROTOCOL:
|
|
93
|
+
|
|
94
|
+
ROUND 1 — Comparable companies and their stories (4-5 searches):
|
|
95
|
+
- "{competitor 1} pitch deck" OR "{competitor 1} fundraise announcement"
|
|
96
|
+
- "{competitor 2} pitch deck" OR "{competitor 2} seed round"
|
|
97
|
+
- "{product category} startup pitch deck examples"
|
|
98
|
+
- "{product category} demo day pitch"
|
|
99
|
+
- "{product category} successful pitch story"
|
|
100
|
+
|
|
101
|
+
ROUND 2 — Narrative patterns that work (3-4 searches):
|
|
102
|
+
- "{product category} for {customer type}" startup analogy
|
|
103
|
+
- "X for Y" startup pitch examples {product category}
|
|
104
|
+
- "{problem} startup story founder"
|
|
105
|
+
- "why I built {product category}" founder story
|
|
106
|
+
|
|
107
|
+
ROUND 3 — Market narrative and trends (3-4 searches):
|
|
108
|
+
- "{product category} market trends {current year}"
|
|
109
|
+
- "why now {product category}" timing narrative
|
|
110
|
+
- "{product space} tailwinds {current year}"
|
|
111
|
+
- "{regulatory/technology/behavioral change} driving {product category}"
|
|
112
|
+
|
|
113
|
+
ROUND 4 — What doesn't work (2-3 searches):
|
|
114
|
+
- "{product category} startup failed pitch" OR "common mistakes {product category} pitch"
|
|
115
|
+
- "investor objections {product category}"
|
|
116
|
+
- "{product category} startup risk" investors worried about
|
|
117
|
+
|
|
118
|
+
OUTPUT FORMAT:
|
|
119
|
+
|
|
120
|
+
## Comparable Narratives
|
|
121
|
+
|
|
122
|
+
### Successful Pitches in This Space
|
|
123
|
+
For each comparable:
|
|
124
|
+
- **Company:** {name}
|
|
125
|
+
- **What they raised:** {amount, stage, when}
|
|
126
|
+
- **Narrative angle:** {how they framed the story}
|
|
127
|
+
- **Key hook:** {what made investors lean in}
|
|
128
|
+
- **Analogy used:** {if any "X for Y" framing}
|
|
129
|
+
- **Source:** {where this info came from}
|
|
130
|
+
|
|
131
|
+
### Narrative Hooks Available
|
|
132
|
+
Rank by strength (strongest first):
|
|
133
|
+
|
|
134
|
+
1. **{Hook name}** — {description}
|
|
135
|
+
- Why it works: {reasoning}
|
|
136
|
+
- How to use: {specific suggestion}
|
|
137
|
+
- Risk: {potential downside}
|
|
138
|
+
|
|
139
|
+
2. **{Hook name}** — {description}
|
|
140
|
+
[same structure]
|
|
141
|
+
|
|
142
|
+
### "X for Y" Candidates
|
|
143
|
+
| Analogy | Clarity | Risk | Recommendation |
|
|
144
|
+
|---------|---------|------|----------------|
|
|
145
|
+
| "{product} is like {X} for {Y}" | High/Med/Low | {what could go wrong} | Use/Avoid |
|
|
146
|
+
|
|
147
|
+
Only recommend "X for Y" if:
|
|
148
|
+
- X is widely known to the target investor audience
|
|
149
|
+
- The analogy clarifies more than it confuses
|
|
150
|
+
- It doesn't box you into the wrong category
|
|
151
|
+
|
|
152
|
+
### "Why Now" Narrative
|
|
153
|
+
- **Timing thesis:** {what makes this the right moment}
|
|
154
|
+
- **Evidence:** {trend data, regulatory change, behavioral shift}
|
|
155
|
+
- **Strength:** Strong / Moderate / Weak
|
|
156
|
+
- **Risk:** {what could undermine the timing argument}
|
|
157
|
+
|
|
158
|
+
### What NOT to Do
|
|
159
|
+
- Narratives that have been overused: {examples}
|
|
160
|
+
- Objections investors will raise: {top 3-5}
|
|
161
|
+
- Narrative traps to avoid: {specific to this space}
|
|
162
|
+
|
|
163
|
+
> Data labels: Mark each finding with [Data], [Estimate], [Assumption], or [Opinion]
|
|
164
|
+
```
|