Framework-based guidance for hiring and scaling sales teams from zero to repeatable revenue.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuilding-sales-teamExecute the skills CLI command in your project's root directory to begin installation:
Fetches building-sales-team from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate building-sales-team. Access via /building-sales-team in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
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.
When the user asks for help with building a sales team:
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.
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.
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.
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.
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.
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.
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."
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.
For all 22 insights from 14 guests, see references/guest-insights.md
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
I recommend building-sales-team for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added building-sales-team from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
building-sales-team reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: building-sales-team is focused, and the summary matches what you get after install.
Keeps context tight: building-sales-team is the kind of skill you can hand to a new teammate without a long onboarding doc.
building-sales-team reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added building-sales-team from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
building-sales-team fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
building-sales-team is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for building-sales-team matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 58