fundraising
This Claude Code skill guides founders through the fundraising process by first challenging whether venture capital is actually necessary, then helping them understand their current stage and craft a compelling pitch narrative. Use it when preparing pitch decks, evaluating fundraising strategy, preparing for investor meetings, or deciding whether to pursue venture capital versus alternative funding paths.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/fundraising && cp -r /tmp/fundraising/skills/fundraising ~/.claude/skills/fundraisingSKILL.md
# Fundraising Strategy Help the user navigate the fundraising process using insights from 2 product leaders. ## How to Help When the user asks for help with fundraising: 1. **Question the assumption** - Before diving into tactics, ask whether they should raise at all. Understand their goals and whether venture capital is the right path 2. **Understand their stage** - Ask what round they're raising, how much traction they have, and what their strongest proof point is 3. **Help craft the pitch** - Focus on leading with their strongest point and building a compelling narrative 4. **Prepare for the process** - Set expectations about rejection rates and help them build resilience for the "dance of 100 nos" ## Core Principles ### Lead with your strongest point on slide one Uri Levine: "Most people are missing the most important slide of their presentation is the first slide... This is the place that you're going to put your strongest point." Investors form impressions in the first minute. Don't bury your best evidence. If you have incredible traction, lead with it. If you have a unique insight, lead with that. ### Challenge whether you should raise at all Ryan Hoover: "I do spend time challenging founders sometimes when they're thinking about raising... to not raise." The venture path creates a "treadmill" of growth expectations. Before optimizing your pitch, honestly assess whether venture capital aligns with your goals, timeline, and the nature of your business. ### Prepare for the "dance of 100 nos" Fundraising is a numbers game. Most investors will say no, and that's normal. The psychology of repeated rejection requires preparation and resilience. Don't take early nos as signal about your company's viability. ## Questions to Help Users - "What's your strongest proof point right now - traction, team, insight, or market?" - "Why are you raising venture capital specifically? Have you considered alternatives?" - "What's on your first slide? Is it your strongest point?" - "How many investors have you talked to? What patterns are you seeing in their feedback?" - "What's your target raise and how did you arrive at that number?" ## Common Mistakes to Flag - **Burying the lede** - Putting your strongest evidence on slide 5 instead of slide 1. Investors decide early - **Raising by default** - Assuming venture capital is the only path without considering bootstrapping or alternative funding - **Underestimating rejection** - Not preparing psychologically for 50-100 nos before getting a yes - **Weak opening** - Starting with problem/solution when you have strong traction that would be more compelling ## Deep Dive For all 2 insights from 2 guests, see `references/guest-insights.md` ## Related Skills - Giving Presentations - Founder Sales - Negotiating Offers - Startup Ideation
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.