Smithery Logo
MCPsSkillsDocsPricing
Login
Smithery Logo

Give agents more agency

Resources

DocumentationPrivacy PolicySystem Status

Company

PricingAboutBlog

Connect

© 2026 Smithery. All rights reserved.

    samarv

    founder-led-sales-playbook

    samarv/founder-led-sales-playbook
    Business
    11

    About

    SKILL.md

    Install

    • Telegram
      Telegram
    • Slack
      Slack
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    • Download skill
    ├─
    ├─
    └─

    About

    A tactical framework for early-stage founders to transition from cold outreach to signed contracts...

    SKILL.md

    Founder-Led Sales Playbook

    Founder-led sales is not about revenue on day one; it is about learning as fast as humanly possible to earn the right to sell. This framework leverages the founder's unique position as a visionary and subject matter expert to turn "non-consumers" into customers.

    Phase 1: High-Relevancy Outreach

    Before automating with tools, manually identify 30 prospects. Focus on relevancy over personalization. If an email is read on a mobile device, the recipient should not have to scroll.

    The 4-Part Outreach Structure

    1. Relevancy: State why you are reaching out to them specifically right now (e.g., a recent role change, a specific team expansion, or a technical shift in their industry).
    2. Counterintuitive Insight: Lead with a "Novel Insight" that challenges the status quo. Avoid saying you are "better"; say you are "different."
    3. Problem Focus: Describe the problem you are solving, not the features of your product.
    4. Conciseness: Keep the total length to 3-4 sentences.

    The "Audio Test": Highlight your draft in Gmail and use the "speak" function. If it sounds passive-aggressive or overly wordy when read aloud, rewrite it.

    Phase 2: The Vulnerable Discovery Call

    The goal of the first call is to validate the problem, not to demo the product.

    Execution Steps

    • Lead with Vulnerability: Say: "I'm an early-stage founder. We are deeply passionate about [Problem], but we have a lot to learn. Can we gain your insight into how this manifests on your side?"
    • Identify Priority: Ask questions to determine if the problem is widening:
      • "Are you currently measuring or managing this problem?"
      • "How have you tried to solve for it previously (headcount, tools, manual workarounds)?"
    • The No-Demo Rule: Avoid showing the product on call one. If you show the product too early, the "dreaminess" fades and the prospect stops visualizing how it fits their specific needs.
    • The Close: Never end a call without the next one on the calendar. If they say "Email me," it is usually a polite "No."

    Phase 3: Co-Authoring and the "Service Bridge"

    In the early stages, 40-50% of B2B SaaS deals require a service component to "bridge" the gap to a technology purchase.

    The Co-Authoring Process

    1. Ask for Guidance: Invite the prospect to co-author the Scope of Work (SOW). This turns them from a "buyer" into a "guide."
    2. Sell the Education: If the prospect doesn't have a process in place to use your tool, sell a 90-day consulting engagement or "service contract" to design that process.
    3. Time-Box Services: Limit service engagements to 90-day increments. This earns the logo and the revenue while setting the stage for the technology contract.

    Phase 4: Navigating Enterprise Procurement

    Procurement professionals are professional buyers. Your job is to make their job easy so your small deal doesn't get sidelined.

    Procurement Tactics

    • Early Identification: Ask the business lead early: "Who is the final signatory and how long does IT due diligence usually take?"
    • The "Queue" Strategy: Ask for their internal forms and fill them out yourself. Don't wait for them to do the paperwork.
    • Truncate Contracts: If IT due diligence is backed up 90 days, split the contract into a "Service/Prep Contract" (which can start immediately) and a "Technology Contract" (which goes through the long queue).
    • The CFO Bullet Points: When the contract reaches the CFO, provide 3 bullet points explaining exactly what the company is buying and why. If they have to ask "What am I signing?", you lose your spot in the queue.

    Examples

    Example 1: Cold Outreach (Novel Insight)

    • Context: Reaching out to a VP of Sales after a Seed round.
    • Input: Founder of a sales training platform.
    • Application:
      • Subject: Zero-to-one sales talent
      • Body: "I noticed you just raised your Seed and are hiring your first reps. At [Company], we've found that 'zero-to-one' sales talent actually doesn't exist in the traditional market—it has to be built. We're solving the problem of founder-to-first-rep knowledge transfer. Would you be open to sharing how you're planning to handle that transition?"
    • Output: High response rate due to the counterintuitive hook and relevancy.

    Example 2: Closing the First Call

    • Context: Ending a 30-minute discovery session where the prospect showed high interest.
    • Input: Prospect mentioned they struggle with data silos.
    • Application: "It sounds like the data silo between marketing and sales is your biggest bottleneck. Based on what you said, I want to show you how we visualize that on a second call. Does next Tuesday at 2:00 PM work to walk through that specifically? Also, who else on the marketing side should see this so it becomes a team win?"
    • Output: Meeting booked with additional stakeholders included.

    Common Pitfalls

    • Using "Better" instead of "Different": "Better" requires a long, measurable proof of concept. "Different" or "Counterintuitive" sparks curiosity and bypasses comparison with existing vendors.
    • Asking Generic Questions: Never ask "What keeps you up at night?" or "If you had a magic wand..." These questions signal that you haven't done your research.
    • Negotiating with Yourself: Don't offer a discount just to get a deal done. If you offer a 30% discount, ask to remove 30% of the value/scope in return.
    • Over-Engineering Tools Too Early: Founders often spend weeks setting up Clay, Apollo, and automated sequences before they have a message that resonates. Manually write 30 notes first.
    Recommended Servers
    DataForB2B
    DataForB2B
    abm.dev
    abm.dev
    Attio
    Attio
    Repository
    samarv/shanon
    Files