agentleFS
Docat0209Docat0209/SoloForge/skills/sales-close/SKILL.md

sales-close

Skill1 starsChanged 7 months agoMITView on GitHub

Manages outbound sales and deal closing. Triggers ONLY when: user asks to plan sales outreach, write cold emails, build a pipeline, or close deals. Do NOT trigger when: doing marketing, content creation, or community engagement.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep volume under 50 emails/day per mailbox

    line 39
  2. Distinctive:

    Use in demos and sales calls (source: Neil Rackham, "SPIN Selling" — based on 35,000+ sales call study):

    line 47
  3. Distinctive:

    Keep it simple, especially as a solo founder (source: general B2B sales practice):

    line 73
  4. Distinctive:

    Weekly review: Every Friday, review pipeline.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sales Close SOP

1. Dream 100 Strategy

Identify and pursue your highest-value prospects (source: Chet Holmes, "The Ultimate Sales Machine"):

  • Build the list: Identify 100 ideal customers who would transform your business. Quality over quantity — these are companies/people who already have the exact problem you solve.
  • Deep research each: Role, company stage, recent news, tech stack, public pain points. Spend 10-15 min per prospect before any outreach.
  • Multi-channel persistence: Email + LinkedIn + events + referrals. Chet Holmes found that 95% of a market was controlled by just 167 companies — targeting them specifically doubled sales within 12-15 months.
  • Sell the meeting, not the product: First outreach goal is a conversation, not a close. Offer an educational session or insight, not a pitch.
  • Cadence: Touch each prospect every 2-4 weeks across channels. Most deals close after 5-12 touches. Most salespeople give up after 2.

2. Cold Email Formula

Structure for 2025-2026 outbound (source: Saleshandy, Autobound, Cleverly, Mailshake):

Single email structure:

  • Subject: Under 5 words, no clickbait ("Quick question", "Saw your [specific thing]")
  • Opening: Reference something specific about them — hiring post, funding round, product launch, role change. Never generic flattery.
  • Value prop: One sentence. What you do + specific result ("We help [role] at [company type] reduce [problem] by [metric]")
  • CTA: Low-friction ask. Not "book a demo" — instead "worth a 15-min chat?" or "want me to send a 2-min video walkthrough?"
  • PS line: Optional social proof ("PS: We helped [similar company] achieve [specific result]")

3-email sequence:

EmailTimingFocus
1Day 0Value prop + low-friction CTA
2Day 3-5New angle or case study, reply to thread
3Day 8-10Breakup email ("Should I close your file?")

Deliverability (non-negotiable in 2026):

  • Configure SPF, DKIM, and DMARC before sending anything — major providers reject emails without these
  • Warm up new domains for 2-4 weeks before outbound
  • Keep volume under 50 emails/day per mailbox
  • Target 95%+ deliverability rate
  • 50-125 words per email gets highest reply rates

Benchmarks: Average reply rate is 3.4%. Signal-based personalized campaigns achieve 15-25% (source: Autobound, Instantly 2026 data).

3. SPIN Questions

Use in demos and sales calls (source: Neil Rackham, "SPIN Selling" — based on 35,000+ sales call study):

  • Situation: Gather facts about their current state. "How do you currently handle [process]?" "What tools are you using for [task]?" Keep these brief — too many situation questions bore prospects.
  • Problem: Uncover pain points. "What's the biggest challenge with [current approach]?" "Where does the process break down?" These reveal implied needs.
  • Implication: Expand the pain. "What happens when [problem] occurs?" "How does that affect [team/revenue/timeline]?" "What's the cost of not solving this?" These are the most powerful questions — they make the problem feel urgent.
  • Need-payoff: Let them articulate the value. "If you could [solve problem], what would that mean for your team?" "How would [outcome] impact [metric]?" The prospect sells themselves.

Key insight from Rackham's research: Traditional closing techniques hurt large sales. The best sellers ask better questions, they don't push harder.

4. Objection Handling

Framework: Listen → Acknowledge → Reframe → Resolve (source: Cognism, HubSpot, Salesforce):

ObjectionResponse strategy
Price"What's the cost of NOT solving this? If [problem] costs you [X/month], this pays for itself in [timeframe]."
Timing"What changes in 3 months that makes it a better time? Usually the cost of waiting is [specific consequence]."
Competition"Great that you're evaluating options. Here's specifically how we differ on [their stated priority]." Don't trash competitors — differentiate.
Need"Let me show you what users in your situation discovered. [Share specific case study]."
Authority"Totally understand. What would [decision maker] need to see? I can prepare a summary for them."
Trust"Fair concern. Here's [case study / free trial / pilot program] so you can verify before committing."

The "Feel, Felt, Found" backup: "I understand how you feel. [Company X] felt the same way. What they found was [specific outcome]."

5. Pipeline Management

Keep it simple, especially as a solo founder (source: general B2B sales practice):

Stages:

  1. Lead — matches ICP, not yet contacted
  2. Contacted — outreach sent, awaiting response
  3. Conversation — replied, actively discussing
  4. Demo/Trial — experiencing the product
  5. Proposal — pricing/terms sent
  6. Closed Won / Closed Lost — track both with reason codes

Tracking: Spreadsheet is fine until ~50 active deals. Then use a free CRM (HubSpot Free, Attio, Folk). The tool matters less than the discipline of updating it.

Weekly review: Every Friday, review pipeline. Move stale deals (no response in 14+ days) to "Closed Lost — No Response." Focus energy on deals in Demo/Proposal stage.

6. Solo Founder Sales Rules

Constraints that protect your time and sanity:

  • Only sell to people who already have the problem — if you have to convince them the problem exists, walk away
  • Never hard-sell — desperate energy repels buyers. Be genuinely helpful and let them decide.
  • Time-box sales to 1 hour/day max — protect your building time. Sales won't matter if the product doesn't improve.
  • Qualify ruthlessly — ask "do you have budget and authority to buy this quarter?" early. Don't waste weeks on tire-kickers.
  • Automate the top of funnel — content, SEO, and product-led growth feed the pipeline while you sleep. Reserve outbound for Dream 100 targets only.
  • Track your numbers — emails sent, replies, demos, closes. You can't improve what you don't measure.
  • Ask for referrals — after every successful close, ask "who else do you know facing this problem?" Warm intros convert 3-5x better than cold outreach.

Next Steps

Report to user: "Pipeline: [N deals]. Stage breakdown: [summary]. Key action: [one line]"

Suggested next steps (user decides):

  • First customer → "Run support-ops"
  • Pipeline growing → "Run growth-track"
  • Need better copy → "Run copy-craft"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.