mcpField
S
sales

sales

github.com/iankikuMarketing & growth1844 installsUpdated 13w ago
Repository

About sales

A sales skill for founders and sales teams, covering personalized outreach, demos, objection handling, and pipeline reviews. It emphasizes prospect-specific conversations and a defined follow-up process.

Key features

  1. 01Personalized cold outreach
  2. 02Demo preparation and structure
  3. 03Objection response frameworks
  4. 04Pipeline stages and weekly forecasts

Use cases

  1. 01Drafting a prospect-specific cold email
  2. 02Preparing a focused product demo
  3. 03Responding to sales objections
  4. 04Reviewing pipeline and weighted forecasts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/iankiku/forwward-teams --skill sales

After installing, type/salesin Claude Code to confirm it loaded.

Details

From the project README

Sales — Close Deals

Sell the problem you solve, not the product you built.

Outreach Principles

  1. Lead with their pain, not your product. "I noticed you're hiring 3 engineers to build internal tooling" not "We built an amazing platform."
  2. Reference something specific. Blog post, LinkedIn post, job listing, press mention. Prove you did homework.
  3. One ask per message. "Open to a 15-min call?" not "Check our demo, read our blog, and schedule a call."
  4. Follow up exactly once. Two follow-ups = spam. One = professional.

Cold Outreach Template

Subject: [Specific observation about their company]

Hi [First name],

[One sentence referencing something specific about them — proves research.]

[One sentence connecting their situation to the problem you solve.]

[One sentence on what you offer — outcome, not features.]

Worth a 15-min call this week?

[Your name]

Anti-patterns:

  • "I hope this email finds you well" — delete this from your vocabulary
  • "We're an AI-powered platform that leverages..." — nobody reads past "leverages"
  • Sending the same template to 500 people — they can tell

Demo Playbook

Before the Demo
  1. Research the prospect: company size, stack, pain points, competitors they use
  2. Prepare 2-3 specific scenarios relevant to them
  3. Have answers ready for: pricing, security, integrations, timeline
During the Demo (30 min max)
TimeWhat
0-5 minDiscovery: "What's your biggest pain with [X] today?"
5-20 minShow 2-3 workflows that solve THEIR specific pain
20-25 minPricing and next steps
25-30 minQuestions

Rules:

  • Never show features they didn't ask about
  • Let them drive: "What would you want to see next?"
  • If they're excited, shorten the demo and close
After the Demo
  • Send recap within 2 hours: what you showed, what they liked, next steps
  • Include specific pricing (not "let me get back to you")
  • One clear next step with a date

Objection Handling

ObjectionResponse Framework
"Too expensive""What's it costing you today to do this manually?" (reframe as ROI)
"We'll build it ourselves""What's the engineering cost? How long until it's production-ready?"
"Not a priority right now""When does this become urgent? Can I check back in [specific time]?"
"Need to talk to my team""Happy to join that conversation — what concerns would they have?"
"Using competitor X""What's working? What's not?" (find the gap)
"Need more features""Which specific feature would unblock you?" (scope it)

Never: Argue, dismiss, or pressure. Understand → reframe → suggest.

Pipeline Management

StageDefinitionAction
LeadShowed interest (signup, inbound, referral)Qualify within 24 hours
QualifiedHas budget, authority, need, timeline (BANT)Schedule demo
Demo'dSaw the productSend proposal within 48 hours
ProposalReviewing termsFollow up once at day 3
NegotiationDiscussing termsBe flexible on terms, firm on value
Closed WonSignedHand off to onboarding
Closed LostDeadLog reason, learn, move on

Weekly review: Pipeline value × probability by stage = weighted forecast.

Comments

Markdown supported