building-sales-team
This skill guides founders and hiring managers through building a sales organization from scratch using frameworks from experienced product leaders. Use it when deciding whether to hire salespeople, determining the right sales roles and profiles for your business model, structuring compensation and hiring processes, or managing the transition from founder-led sales to a dedicated team. It emphasizes validating repeatable sales motions before hiring and matching sales archetypes to specific business conditions.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/building-sales-team && cp -r /tmp/building-sales-team/skills/building-sales-team ~/.claude/skills/building-sales-teamSKILL.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
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 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.
Help users build effective AI applications. Use when someone is building with LLMs, writing prompts, designing AI features, implementing RAG, creating agents, running evals, or trying to improve AI output quality.