fundraising▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Strategic guidance for founders navigating capital raises and investor relationships.
- ›Emphasizes leading with your strongest proof point on the first slide, whether that's traction, team insight, or market opportunity, since investors form impressions within the first minute
- ›Challenges the assumption that venture capital is the right path by exploring alternatives like bootstrapping and assessing alignment with your goals and business model
- ›Prepares founders for the psychological rea
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:
- 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
- Understand their stage - Ask what round they're raising, how much traction they have, and what their strongest proof point is
- Help craft the pitch - Focus on leading with their strongest point and building a compelling narrative
- 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
How to use fundraising on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add fundraising
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches fundraising from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate fundraising. Access the skill through slash commands (e.g., /fundraising) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★65 reviews- ★★★★★Arya Martinez· Dec 20, 2024
fundraising reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Mia Sethi· Dec 16, 2024
fundraising has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ganesh Mohane· Dec 12, 2024
Registry listing for fundraising matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Shikha Mishra· Dec 8, 2024
We added fundraising from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Nov 27, 2024
fundraising fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Valentina Abebe· Nov 11, 2024
fundraising has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Meera Park· Nov 7, 2024
fundraising reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Charlotte Huang· Oct 26, 2024
I recommend fundraising for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Oct 18, 2024
fundraising is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hiroshi Thomas· Oct 2, 2024
Useful defaults in fundraising — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 65