founder-sales
Help founders close their first customers and build repeatable sales processes. Use when someone is doing founder-led sales, trying to get their first customers, writing cold outreach, running early sales calls, or asking when to hire their first salesperson.
What this skill does
# Founder Sales Help the user close early customers and codify a repeatable sales process using insights from 16 product leaders. ## How to Help When the user asks for help with founder sales: 1. **Understand their stage** - Ask how many customers they have, whether they have a repeatable ICP, and whether they're pre-product or have something to demo 2. **Diagnose the bottleneck** - Determine if the problem is lead generation, qualification, discovery, closing, or implementation 3. **Guide the approach** - Help them craft outreach, prepare for discovery calls, or design their sales process based on their specific situation 4. **Document for repeatability** - Encourage them to capture what works so they can eventually hand it off ## Core Principles ### The founder IS the product in early sales Jen Abel: "Founder led sales is really that first milestone... the founder is the product." In early stages, the founder's novel insight and subject matter expertise are the primary drivers of interest. Leverage your status as founder to gain market access. Use your ability to see "budding moments" in conversations to refine the product vision. ### Your biggest competitor is indecision, not other vendors April Dunford: "40 to 60% of B2B purchase processes end in no decision... they couldn't figure out how to make a choice confidently." Focus on helping buyers make a choice confidently rather than just pitching features. Act as a guide to help them navigate the market. "No decision" is the safest path for overwhelmed buyers. ### You cannot outsource early sales Pete Kazanjy: "The founder's got to do that stuff... it's going to be way easier for you to get minimally viable good at selling." Don't hire a VP of Sales until you've closed the first couple dozen customers yourself. Use early sales calls as customer development. Focus on becoming "minimally viable" at selling, not a master. ### Sell it before you build it Todd Jackson: "I want to sell it before I build it, because I really want the signal from customers to be the guide and the oxygen that drives what I'm building." Use Figma mock-ups to secure the first 5-10 customers before writing extensive code. Determine the fidelity required for a demo based on the product type. ### Close the laptop and diagnose first Geoffrey Moore: "Shut the laptop. Just don't open it... 'We understand there's this really serious problem and we believe your company might have it, is that true?'" Early sales to pragmatists should be diagnostic and focused entirely on the customer's pain. Use a physical pen and paper so customers can see you capturing their specific words. ### The "Collison Install" - don't leave until it's implemented Dalton Caldwell: "They would just install Stripe into the customer's website... they basically would not go away until you finish the implementation." Don't consider a sale finished until the product is fully implemented. Offer to manually install or set up the software. Be persistent through the "last mile." ### Founder-led sales is about learning, not revenue Jen Abel: "Founder led sales is not about revenue on day one. It is about learning as fast as humanly possible to get to that pulse." Treat early sales calls as research sessions. Be vulnerable about being early-stage to elicit more honest feedback. The goal is to find the repeatable pattern. ### Qualify ruthlessly - it's never a bottom-of-funnel problem Jen Abel: "If you spend your time on the wrong leads, that equates to a zero. It's never a bottom of funnel problem. It's always qualification." Verify if the prospect is measuring or managing the problem today. Stop chasing leads that are "just being nice" but have no intent to buy. ### Manual outreach beats AI tools for high-value deals Jen Abel: "AI tools are all pulling from the same databases. I want to email someone not in the database... I want to take a back door in." Manual, highly personalized outreach is more effective for enterprise deals than automated tools using saturated databases. Keep emails to 3-4 sentences max. Focus on shock value and relevance over generic personalization. ### Book the next meeting while you're still on this one Jen Abel: "Get the second call booked on the first call. Pull up calendars. Look at calendars. Who else should be invited?" Maintain momentum by securing the next meeting while still on the current call. Identify other stakeholders who should be included. ### Stay in founder-led sales until you have repeatability Jeanne Grosser: "Wait until you're around a million in ARR. When you have a repeatable process... there's some repeatability there." Don't hand over sales until you can define an ICP and have documented the discovery questions, objection handling, and demo flow that work. ### Design the process around how they buy, not how you sell Bob Moesta: "Instead of trying to base the sales process on how we want to sell, we need to actually design the sales process on how they want to buy." Map the buyer's timeline through six phases: first thought, passive looking, active looking, deciding, first use, and ongoing use. Tailor your approach to their phase. ## Questions to Help Users - "How many customers have you closed personally? What's your ICP?" - "Where in the funnel are you losing deals - outreach, discovery, closing, or implementation?" - "Are you talking to people who are actively trying to solve this problem, or just 'interested'?" - "Can you describe the last deal you lost? What happened?" - "What does your current outreach message say? What response rate are you getting?" - "Have you documented what works so someone else could run this process?" ## Common Mistakes to Flag - **Hiring sales too early** - Don't hire a salesperson to fix messaging that isn't landing. Founders must prove the motion works first, typically to ~$1M ARR - **Defaulting to product demos** - Discovery should focus on the customer's pain, not your features. Keep the laptop closed in early meetings - **Treating "yes" as the finish line** - A deal isn't closed until implementation is complete. Follow the Collison Install approach - **Using generic AI outreach** - Automated tools pull from the same databases everyone else uses. Manual, personalized outreach wins for high-value deals - **Chasing polite leads** - "That sounds interesting" is not buying intent. Qualify for active problem-solving, not politeness ## Deep Dive For all 28 insights from 16 guests, see `references/guest-insights.md` ## Related Skills - Building Sales Team - Enterprise Sales - Partnership & BD - Product-Led Sales Strategy
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.