partnership-bd▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Strategic partnership and BD guidance grounded in insights from nine product leaders.
- ›Covers four core phases: understanding opportunities, assessing network vs. merit dynamics, designing pitches that show mutual benefit, and navigating negotiations with timing and leverage
- ›Emphasizes industry-specific dynamics—relationships dominate in healthcare, finance, and enterprise, while product merit matters more elsewhere
- ›Advises building scalable partner platforms rather than one-off deals
Partnership & BD
Help the user build strategic partnerships and business development deals using insights from 9 product leaders.
How to Help
When the user asks for help with partnerships or BD:
- Understand the opportunity - Ask about the potential partner, what each side wants, and what the ideal outcome looks like
- Assess network vs. merit dynamics - Determine if success depends on relationships or product quality, and plan accordingly
- Design the approach - Help them craft a pitch that shows mutual benefit, not just their own needs
- Navigate the negotiation - Guide them on timing, leverage, and when to say no
Core Principles
Partnerships are network-dependent in some industries
Ayo Omojola: "Very often the way to make things happen is network-dependent, not necessarily about the merit of the thing itself. There are companies that exist because the founders know the CEO of every major payer." In industries like healthcare, finance, or enterprise, relationships matter more than product. Determine if your business is network-dependent early.
Position yourself as a case study for the platform
Adam Grenier: "Let me into your alpha, because I have five years of experience buying mobile ads. If you get us to work, we're a killer case study for a category you want to grow." When partnering with major platforms, show how your success helps them prove their business model. Offer to be an alpha tester for new features.
Build scalable platforms, not bespoke deals
Keith Yandell: "We'll build you a product so you won't need to ask us every time. Then you'll know the parameters in which you can negotiate." Effective BD teams work with Product to create self-serve platforms for partners rather than negotiating one-off integrations. This increases velocity and reduces engineering load.
Strategic patience leads to better deals
Jason Droege: "McDonald's approached us and I said 'No.' I pushed them off for four or five months. It ended up being a net benefit because we got a great deal." Don't rush into partnerships just because of the partner's size. Initial resistance can lead to better terms or exclusivity.
Channel partners won't sell like founders
Jen Abel: "The problem with channel partnerships is there are a hundred of you on the list and you're expecting them to sell on your behalf. They're not visionaries, they're consultants." Don't expect Accenture or Deloitte to evangelize your product. They lack the founder's vision-casting ability.
Use corp dev to find internal sponsors
Julia Schottenstein: "Use that corp dev team to your advantage. Take that meeting, say you're not interested in acquisition yet, but push them for an introduction to someone who could sponsor the deal - usually someone in Product or a GM." Corp dev teams are gateways to internal sponsors even if you're not looking to sell.
Find partners at the moment of need
Meltem Kuran: "VCs ask portfolio companies 'What platform do you trust for hiring?' So people go to their VCs for that kind of question." The best partners are those your target audience already consults at the exact moment the problem arises.
Treat partnerships as iterated prisoner's dilemma
Tobi Lutke: "Being a good partner is like a corporate marshmallow test companies tend to fail. The correct way to play iterated prisoner's dilemma is coordinate for both sides - it's way more valuable over long periods." Resist pulling future profits forward at the expense of a partner. Long-term coordination always beats short-term defection.
Test with manual operations before building
Keith Yandell: "We should have tested this at one hotel with hacky operations before asking for product resources." Validate partnership hypotheses with manual operations before committing engineering time. Dream big, start small.
Questions to Help Users
- "What does the partner want from this deal? What's in it for them?"
- "Is this industry network-dependent, or will product merit win?"
- "Can you position yourself as a case study for something they want to prove?"
- "What's your leverage? Can you afford to say no?"
- "Are you building toward a scalable platform or negotiating a one-off deal?"
- "Who inside the partner organization can sponsor this internally?"
Common Mistakes to Flag
- Expecting partners to sell for you - Channel partners and consultants won't evangelize like founders. Don't outsource vision-casting
- Rushing into big-name partnerships - Strategic patience often leads to better deal terms. Don't let FOMO drive bad deals
- Building before validating - Test partnership ideas with manual operations before committing engineering resources
- Ignoring network dynamics - In some industries, relationships matter more than product. Know which game you're playing
- Short-term defection - Pulling profits forward at a partner's expense destroys long-term value. Play the long game
Deep Dive
For all 11 insights from 9 guests, see references/guest-insights.md
Related Skills
- Founder Sales
- Enterprise Sales
- Building Sales Team
- Negotiating Offers
How to use partnership-bd 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 partnership-bd
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches partnership-bd 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 partnership-bd. Access the skill through slash commands (e.g., /partnership-bd) 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▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★69 reviews- ★★★★★Mei Rao· Dec 28, 2024
partnership-bd reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakura Jain· Dec 12, 2024
I recommend partnership-bd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ganesh Mohane· Dec 8, 2024
partnership-bd reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sophia Lopez· Dec 4, 2024
Keeps context tight: partnership-bd is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakshi Patil· Nov 27, 2024
I recommend partnership-bd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★William Gill· Nov 23, 2024
partnership-bd has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Harper Ramirez· Nov 19, 2024
I recommend partnership-bd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sophia White· Nov 11, 2024
partnership-bd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hiroshi Torres· Nov 3, 2024
partnership-bd reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sophia Desai· Oct 22, 2024
Registry listing for partnership-bd matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 69