building-sales-team

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill building-sales-team
0 commentsdiscussion
summary

Framework-based guidance for hiring and scaling sales teams from zero to repeatable revenue.

  • Emphasizes proving founder-led repeatability (50-100 at-bats at 15-25% win rate) before hiring any salespeople
  • Recommends always hiring sales reps in pairs to validate process and create performance baselines, not single hires
  • Matches sales archetypes (hunters for outbound, growers for inbound/PLG) to your specific motion and buyer profile
  • Delays VP of Sales hires until you have two reps c
skill.md

Building Sales Team

Help the user build and scale a high-performing sales organization using frameworks from 14 product leaders who have built sales teams from zero to scale.

How to Help

When the user asks for help with building a sales team:

  1. Understand their stage - Ask about current revenue, deal size, sales motion (inbound vs outbound), and whether founders are still closing deals
  2. Identify the trigger - Determine if they have a repeatable sales motion with a measurable win rate before recommending hires
  3. Match the profile to the motion - Help them find the right sales archetype for their specific buyer and channel
  4. Structure for validation - Guide them on hiring in pairs, compensation structures, and when to add management

Core Principles

Prove repeatability before hiring

Pete Kazanjy: "You can reliably, at a pretty okay win rate, so maybe 15% or 20% or 25%, turn first meetings into eventual customers." Wait until founders achieve a statistically significant win rate (50-100 at-bats) before hiring salespeople.

Always hire in pairs

Jason Lemkin: "You need to hire one rep and you've got to hire two because otherwise, there's no A-B test. You have to A-B test humans." Hiring two reps simultaneously creates a baseline for performance and validates that your process works regardless of individual talent.

Delay sales hires until Series A

Jen Abel: "Seed is all about experimentation and proving out that experiment, and then obviously series A is about exploiting that learning." The founder must close deals personally to learn the market before delegating.

Match profiles to your motion

Annie Pearl: "In those early days, it's more inbound in nature, and so the type of sales reps you might need are not necessarily going to be outbound, heavy hunting sales reps." Hire "grower" profiles for PLG/inbound, "hunter" profiles for outbound.

Look for founder-like sellers

Jen Abel: "I always say you need people that can cosplay a founder, which is selling the vision, getting through walls to get the deal done." Early sales hires should be product-obsessed "pirates and romantics" who can adapt deal structures.

Sales hires must pass the PM test

Jeanne Grosser: "If you are an account executive in my org and I put you in front of 10 engineers at our company, it should take them 10 minutes to figure out you aren't a product manager." In technical companies, sales must have deep product knowledge.

Don't hire a VP too early

Jason Lemkin: "You need two sales reps hitting quota closing deals before you're ready to hire a manager for them. Almost all VPs of sales, their job is to take you from rep three to 300."

Pilot PLS separately from quota pressure

Elena Verna: "Attach to yourself a pilot AE, so account executive, or an SDR and see how that works... not under pressure of top-down quota relief." Experiment with product-led sales outside the traditional sales engine.

Questions to Help Users

  • "What's your current win rate from first meeting to closed deal?"
  • "Are you selling to arms-length prospects or mostly warm intros?"
  • "What's your average deal size and sales cycle length?"
  • "Is your motion primarily inbound or outbound?"
  • "Do you have two reps hitting quota consistently?"
  • "Who is your target buyer persona - department head or C-level?"

Common Mistakes to Flag

  • Hiring sales before founder-led repeatability - If the founder can't close deals consistently, salespeople won't either
  • Hiring a VP of Sales first - Start with two pioneer AEs, not a manager who hasn't sold in years
  • Mismatching sales profile to motion - Oracle reps selling to CIOs won't work if you're selling to RevOps managers
  • Single-point-of-failure hiring - One rep succeeding could be luck; two reps validates the process
  • Ignoring the 50% failure rate - Half of early sales hires don't work out, so plan accordingly

Deep Dive

For all 22 insights from 14 guests, see references/guest-insights.md

Related Skills

  • Founder Sales
  • Enterprise Sales
  • Partnership & BD
  • Product-Led Sales Strategy
how to use building-sales-team

How to use building-sales-team on Cursor

AI-first code editor with Composer

1

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 building-sales-team
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill building-sales-team

The skills CLI fetches building-sales-team from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/building-sales-team

Reload or restart Cursor to activate building-sales-team. Access the skill through slash commands (e.g., /building-sales-team) 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

GET_STARTED →

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. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 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

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.658 reviews
  • Kaira Farah· Dec 28, 2024

    I recommend building-sales-team for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Noah Bhatia· Dec 28, 2024

    We added building-sales-team from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Layla Jackson· Dec 12, 2024

    building-sales-team reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Dec 4, 2024

    Solid pick for teams standardizing on skills: building-sales-team is focused, and the summary matches what you get after install.

  • Layla Srinivasan· Nov 19, 2024

    Keeps context tight: building-sales-team is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Noah Mehta· Nov 19, 2024

    building-sales-team reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kaira Nasser· Nov 3, 2024

    We added building-sales-team from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kaira Thompson· Oct 22, 2024

    building-sales-team fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla White· Oct 10, 2024

    building-sales-team is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Mia Zhang· Oct 10, 2024

    Registry listing for building-sales-team matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 58

1 / 6