### Fresh Start Messaging Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/channel-fallback-logic/SKILL.md

These examples illustrate a 'fresh start' approach for fallback messaging, where you don't acknowledge previous attempts and present a completely new pitch angle.

```text
Hi [Name], [New pitch angle completely
different from email sequence]
```

--------------------------------

### Example Intent-Based Content Delivery

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/attachment-media-handling/SKILL.md

Shows how a bot can offer a comparison guide when a prospect expresses uncertainty about choosing a solution.

```text
Intent: Comparing options

"I'm trying to figure out which solution is right for us"

Bot: "I have a comparison guide that might help. It shows
how we stack up on the features that matter most.
[Comparison PDF]

Any specific areas you want me to highlight?"
```

--------------------------------

### A/B Testing Channels for New Prospects Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/channel-preference-detection/SKILL.md

Sets up an A/B test to compare starting outreach with email versus SMS for new prospects lacking preference data.

```text
Test: New prospects, no preference data
A: Start with email
B: Start with SMS

Measure:
- Response rate
- Time to response
- Conversation quality
- Conversion rate
```

--------------------------------

### Example Transition: To Qualification

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversational-flow-management/SKILL.md

Phrases to use when guiding the conversation towards qualifying the user's needs or requirements.

```text
To make sure I point you to the right resource...
So I can help you efficiently...
```

--------------------------------

### Example of Maintaining Flow: Acknowledge, Respond, Guide

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversational-flow-management/SKILL.md

This pattern involves acknowledging the user's statement, providing a brief response, and then guiding the conversation to the next topic.

```text
User: "I'm frustrated with our current tool"
Bot: "I hear you—that's a common frustration we hear. What specifically isn't working for you? That'll help me point you in the right direction."
```

--------------------------------

### Few-Shot Examples for LLM Tone Matching

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/tone-matching/SKILL.md

An array of example input-output pairs demonstrating how the LLM should match different prospect tones and energy levels.

```javascript
examples = [
  {
    input: "Hey! Super interested in your product. What's the price?",
    tone: "casual, high energy",
    output: "Hey! Glad to hear it! 😊 Pricing depends on your team size—usually ranges from $X-$Y/month. What's your setup like?"
  },
  {
    input: "Good morning. I would like to inquire about your enterprise pricing structure.",
    tone: "formal, low energy",
    output: "Good morning. Thank you for your inquiry. Our enterprise pricing is customized based on several factors. I would be happy to discuss your specific requirements. Would you have time for a brief call this week?"
  },
  {
    input: "Quick q - do you integrate with Salesforce?",
    tone: "casual, brief",
    output: "Yep! Full Salesforce integration. Want details?"
  }
]
```

--------------------------------

### Metrics and Statistics Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/social-proof-injection/SKILL.md

Presents examples of aggregate data used to build credibility and support claims, ideal for analytical prospects.

```text
Aggregate data:

"Our customers average 3.2x ROI"
"92% of users see results in 30 days"
"4.8/5 satisfaction rating"

Best for:
- Building credibility
- Supporting claims
- Analytical prospects
```

--------------------------------

### Event-Triggered Acceleration Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/drip-pacing-intelligence/SKILL.md

Examples of specific prospect actions that should trigger immediate or prioritized outreach.

```text
Immediate response triggers:
- Website pricing page visit → Trigger within 1 hour
- Demo video watched >50% → Follow up same day
- Competitor comparison viewed → Priority outreach
- Multiple page views in session → Real-time engagement

"I noticed you were just checking out our pricing—
any questions I can answer?"
```

--------------------------------

### Email Delivery Best Practice Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/attachment-media-handling/SKILL.md

Provides an example message for sending formal proposals and timelines via email, suitable for longer-form content.

```text
Best for:
- PDFs and documents
- Long-form content
- Multiple attachments
- Formal proposals

"I've attached our proposal and implementation timeline.
Let me know if you'd like to walk through it together."
```

--------------------------------

### Async Handoff Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/multilingual-support/SKILL.md

An example of an asynchronous handoff when a human agent is not immediately available. It informs the prospect about the delay and offers assistance in English while waiting.

```text
"Thank you for reaching out! I noticed you're more
comfortable in Spanish.

Our Spanish-speaking team member will reach out within
[timeframe]. In the meantime, is there anything I can
help with in English?

Gracias por contactarnos. He notado que prefiere
comunicarse en español. Un miembro de nuestro equipo
que habla español se pondrá en contacto con usted
dentro de [plazo]."
```

--------------------------------

### Example Trigger-Based Cold Email

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/copywriting/SKILL.md

A practical example of a trigger-based cold email, demonstrating personalization and value proposition.

```email
Subject: Your Austin expansion

Hi Sarah,

Congrats on opening the Austin office—saw the announcement on LinkedIn.

When sales teams expand that fast, getting new reps productive quickly becomes critical. Ramp time can make or break the quarter.

We helped Segment cut new rep ramp time from 5 months to 6 weeks during their scale-up. Happy to share what worked.

Worth 15 minutes this week?

Mike
```

--------------------------------

### Acknowledging Channel Switch Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/channel-fallback-logic/SKILL.md

These examples show how to transparently acknowledge a channel switch when falling back to a new communication method.

```text
Trying a different channel—not sure if my
emails are getting through.
```

```text
Wanted to reach you another way since I
haven't heard back via email.
```

```text
Email not the best way? Happy to connect
here instead.
```

--------------------------------

### SMS/Chat Delivery Best Practice Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/attachment-media-handling/SKILL.md

Offers an example message for sending short videos or quick references via SMS/Chat, emphasizing mobile-friendly content.

```text
Best for:
- Short videos (<2 min)
- Single links
- Quick references
- Mobile-friendly content

"Here's a 90-second video showing exactly how that works: [link]"

Avoid:
- Large file attachments
- Multiple links
- Complex documents
```

--------------------------------

### Reschedule Request Response Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/meeting-confirmation-reminder-logic/SKILL.md

Provides an example of how the bot should respond to a prospect's request to reschedule, offering alternative times.

```text
No problem! Here are some alternative times:
• [Option 1]
• [Option 2]
• [Option 3]

Or reply with what works better for you.
```

--------------------------------

### Graceful Channel Switching Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/channel-preference-detection/SKILL.md

Examples of how to transition communication to a different channel when the primary channel is not effective or a change is requested. These messages acknowledge the previous channel and suggest the new one.

```text
SMS → Email:
"Hi [Name], I've been trying to reach you by text.
Sending this email in case that works better for you."

Email → SMS:
"Hi [Name], just sent you an email with the details.
Texting in case you see this first—let me know if you have questions!"

Email → Phone:
"Hi [Name], I've sent a couple of emails about [topic].
Would it be easier to jump on a quick call? I can explain in 5 minutes."
```

--------------------------------

### Value Assessment Tool Flow Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/sales-enablement-tools/SKILL.md

An example flow for a value assessment tool, including assessment questions, benchmark comparisons, gap analysis, and quantifying improvement opportunities.

```text
ASSESSMENT QUESTIONS:
1. How many [X] do you process monthly?
2. What's your current [metric] rate?
3. How many hours spent on [task]?
4. What's the cost when [problem] occurs?

BENCHMARK COMPARISON:
- Your rate: X%
- Industry average: Y%
- Top performers: Z%

GAP ANALYSIS:
- Current performance: [value]
- Benchmark performance: [value]
- Improvement opportunity: [value]
- Value of closing gap: $[amount]
```

--------------------------------

### Hedge + Value Pattern Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/response-confidence-scoring/SKILL.md

Demonstrates how to add value while hedging, rather than just stating uncertainty.

```text
Don't just hedge—add value:

Weak:
"I'm not sure about that. Let me find out."

Strong:
"I want to make sure I give you accurate info
on that. While I confirm the details, can you
tell me more about your use case? That'll help
me get you the most relevant answer."

Hedge + advance conversation.
```

--------------------------------

### ROI Calculator Structure Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/sales-enablement-tools/SKILL.md

An example structure for an ROI calculator, outlining typical inputs, calculations, and outputs to quantify financial value and justify a purchase.

```text
INPUTS:
- Number of [users/transactions/units]
- Current cost per [unit]
- Time spent on [task]
- Error/failure rate

CALCULATIONS:
- Current annual cost: [formula]
- Projected cost with solution: [formula]
- Annual savings: [difference]
- Implementation cost: [one-time]
- Payback period: [months]

OUTPUTS:
- Year 1 net savings
- 3-year total value
- ROI percentage
- Payback timeline
```

--------------------------------

### Sales Test Documentation Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/ab-message-testing/SKILL.md

An example of how to document a sales A/B test, including hypothesis, variants, metrics, and status. This format helps track test progress and learnings.

```text
Test Name: Opening Message Greeting Style
Test ID: T-2024-001
Status: Running

Hypothesis:
A casual greeting will increase response rate because
it feels more human and less corporate.

Variants:
- Control (50%): "Hello! Thanks for reaching out..."
- Variant A (50%): "Hey there! Great to hear from you..."

Primary Metric: Response rate
Secondary Metrics: Sentiment, conversion rate
Sample Size Target: 1,000 per variant
Duration: 2 weeks or until significant

Results:
[To be completed]
```

--------------------------------

### Material Engagement Tracking Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/post-meeting-follow-up-automation/SKILL.md

Describes how to track prospect engagement with sent materials. Provides examples of engagement metrics and a sample follow-up question based on observed engagement.

```text
Track engagement with sent materials:

- Did they open the email?
- Did they click the links?
- How long on case study?
- Did they download proposal?
- Did they share with others?

Use to prioritize follow-ups:
"I noticed you spent time on the security
whitepaper. Any questions about our security
practices?"
```

--------------------------------

### Prospect State Management Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/drip-pacing-intelligence/SKILL.md

An example JSON object representing the state of a prospect within a sequence, including IDs, current step, engagement score, pacing status, and last engagement details.

```json
{
  "prospect_id": "12345",
  "sequence_id": "enterprise_outbound",
  "current_step": 3,
  "engagement_score": 65,
  "pacing_status": "accelerated",
  "next_touch_at": "2024-01-16T10:00:00Z",
  "last_engagement": {
    "type": "email_click",
    "timestamp": "2024-01-15T14:30:00Z",
    "content": "pricing_link"
  },
  "pacing_history": [
    {"step": 1, "interval_days": 0, "actual_days": 0},
    {"step": 2, "interval_days": 3, "actual_days": 2},
    {"step": 3, "interval_days": 3, "actual_days": 2}
  ]
}
```

--------------------------------

### Smart Content Recommendations Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/attachment-media-handling/SKILL.md

Shows how to suggest content based on what similar prospects found helpful, aiding in smart recommendations.

```text
"Prospects in [industry] often find these helpful:
1. [Industry] Case Study
2. ROI Calculator
3. Integration Guide

Want me to send any of these?"
```

--------------------------------

### Example Opening Strategy: Direct and Efficient

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversational-flow-management/SKILL.md

Employ this strategy for a concise opening when a quick decision or choice is needed.

```text
Hi there! Quick question: are you looking for [option A] or [option B]?
```

--------------------------------

### Handling 'What's your cheapest option?'

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/pricing-discussion-logic/SKILL.md

Present the cheapest option but immediately pivot to understanding the user's needs to ensure it's a suitable fit.

```text
"Our starter plan is $X/month. But let me make sure
that's actually the right fit—what are you mainly
trying to accomplish? Sometimes the starter plan
is missing key features that matter."
```

--------------------------------

### Priority Handling Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversation-branching/SKILL.md

Illustrates how to handle multiple matching branches by prioritizing them based on urgency and type, such as objections over general questions.

```text
Priority order:
1. Safety/compliance (always first)
2. Explicit requests ("call me back")
3. Objections (must address)
4. Questions (should answer)
5. Conversation flow (can wait)

Example:
Prospect: "This sounds expensive, and can you email me info?"

Matches:
- Budget objection (priority 3)
- Email request (priority 2)

Handle request first:
"Absolutely, I'll email you detailed info. Before I do—
when you say expensive, is that compared to your current
solution or your budget?"
```

--------------------------------

### Example Opening Strategy: Context-Aware Opening

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversational-flow-management/SKILL.md

Leverage user context, such as recent page views, to personalize the opening and offer relevant assistance.

```text
Hey [Name]! I see you've been looking at our pricing page. Happy to answer any questions—what would be most helpful?
```

--------------------------------

### Parallel Paths Handling Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversation-branching/SKILL.md

Shows how to address multiple distinct questions or threads within a single user turn. Provides a structured response addressing both integration and pricing.

```text
Prospect: "What's the price, and does it integrate with Salesforce?"

Branch: Both questions need answers

Response:
"Great questions—let me address both.

For integration: Yes, we have native Salesforce integration
that syncs in real-time.

For pricing: It depends on team size. Roughly how many
people would be using it?"
```

--------------------------------

### Track Conversation Events

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/performance-analytics/SKILL.md

Provides examples of tracking key events within a conversation lifecycle, such as starting a conversation, receiving a message, and booking a meeting. Includes event type, conversation ID, timestamps, and relevant properties.

```javascript
// Track all meaningful events
trackEvent({
  event_type: "conversation_started",
  conversation_id: "abc123",
  channel: "sms",
  timestamp: now(),
  properties: {
    source: "website_form",
    lead_score: 72
  }
})

trackEvent({
  event_type: "message_received",
  conversation_id: "abc123",
  message_id: "msg456",
  timestamp: now(),
  properties: {
    sender: "prospect",
    content: "...",
    intent: "interested",
    intent_confidence: 0.87,
    sentiment: 0.3
  }
})

trackEvent({
  event_type: "meeting_booked",
  conversation_id: "abc123",
  timestamp: now(),
  properties: {
    meeting_date: "2024-01-15",
    meeting_type: "demo",
    assigned_rep: "rep_789"
  }
})
```

--------------------------------

### Install All Skills via CLI

Source: https://github.com/louisblythe/sales-skills/blob/main/README.md

Use the add-skill CLI to install all available skills from the repository. This is the recommended installation method.

```bash
npx add-skill louisblythe/salesskills
```

--------------------------------

### Preference Documentation Logging Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/channel-preference-detection/SKILL.md

Lists essential information to log regarding customer channel preferences, including consent and opt-out requests.

```text
Always log:
- How preference was determined
- When preference was set
- Explicit consent given
- Opt-out requests
```

--------------------------------

### Handling 'Can I get a discount?' - No Discount Available

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/pricing-discussion-logic/SKILL.md

If no discount is possible, pivot to exploring alternative packages that might better fit the user's budget.

```text
No discount available:
"Our pricing is set, but I can explore if there's a
different package that fits your budget better."
```

--------------------------------

### Install Specific Skills via CLI

Source: https://github.com/louisblythe/sales-skills/blob/main/README.md

Use the add-skill CLI to install only specific skills by name. This allows for a more targeted installation.

```bash
npx add-skill louisblythe/salesskills --skill pricing-negotiation competitor-alternatives
```

--------------------------------

### Time-Buying Hedges Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/response-confidence-scoring/SKILL.md

Examples of phrases to use when needing to verify information before responding.

```text
When you need to verify:

"Great question. Let me confirm the specifics
and get back to you within [timeframe]. In
the meantime, [continue conversation]..."

"I want to give you precise numbers on that.
Mind if I follow up with details after we
chat about [next topic]?"

"That's a detailed technical question—I'll
have our solutions team send over documentation.
What's the best email for that?"
```

--------------------------------

### Multi-Channel Coordination Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/drip-pacing-intelligence/SKILL.md

Provides a sample schedule for coordinating outreach across different channels to avoid overwhelming the prospect.

```text
Don't pile on. Coordinate across channels:

Day 1: Email
Day 3: Email (if opened Day 1)
Day 3: LinkedIn (if no open on Day 1)
Day 6: SMS (if engagement on either)
Day 8: Call (if high engagement)

Never:
- Email + SMS + Call same day
- Multiple touches in same channel < 48h apart
```

--------------------------------

### Static vs. Dynamic Script Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/dynamic-script-generation/SKILL.md

Illustrates the limitations of static templates and the benefits of dynamic message generation.

```text
Static templates:
"Hi {first_name}, I noticed you work at {company}..."

Every prospect gets same structure.
Experienced prospects recognize templates.
No adaptation to context or signals.
```

```text
Dynamic Generation
Each message built from:
- Prospect attributes
- Conversation context
- Previous interactions
- Current signals
- Optimal patterns

Result: Unique, relevant messages
that feel personally crafted.
```

--------------------------------

### Linguistic Hedges Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/response-confidence-scoring/SKILL.md

Examples of linguistic phrases used to communicate uncertainty in responses.

```text
Phrases that communicate uncertainty:

Soft hedges:
- "Typically..."
- "In most cases..."
- "Generally speaking..."
- "From what I understand..."

Stronger hedges:
- "I'd need to verify, but..."
- "Let me confirm this, however..."
- "I want to double-check, but my understanding is..."

Explicit uncertainty:
- "I'm not certain about that specific case..."
- "That's outside my direct knowledge..."
- "I'd need to connect you with someone who specializes in..."
```

--------------------------------

### Framework/Approach Content Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/social-selling/SKILL.md

Content that explains your methodology or approach to solving a problem, showcasing your solution's strategy.

```text
"How we help [companies] achieve [outcome]..."
```

--------------------------------

### Example of a 'Pitch-Slap' Outreach

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/social-selling/SKILL.md

This is an example of what NOT to do when reaching out. It's a direct pitch without context or personalization.

```text
❌ "Hi [Name], I'd love to show you how [Company] can help you [outcome].
Do you have 15 minutes this week for a demo?"
```

--------------------------------

### Enriched Profile Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/prospect-research-integration/SKILL.md

Shows an example of a prospect profile after data enrichment, demonstrating the value for personalization.

```text
Auto-enriched profile:
- Title: VP of Engineering
- Reports to: CTO
- Team size: 45 engineers
- Recent: Announced series B
- Tech: AWS, React, Python
- Hiring: 12 open roles
- Trigger: New product launch

Now you can personalize.
```

--------------------------------

### Customer Testimonial Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/social-proof-injection/SKILL.md

Provides an example of a direct customer quote, highlighting its suitability for emotional resonance and credibility.

```text
Direct quotes from customers:

"We cut our sales cycle by 30%."
- Sarah Chen, VP Sales at TechCorp

Best for:
- Emotional resonance
- Credibility from real person
- Quick impact
```

--------------------------------

### Example Transition: Between Topics

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversational-flow-management/SKILL.md

Use these phrases to smoothly transition from one conversational topic to another.

```text
Great, that helps. Now let me ask...
Thanks for sharing. Related to that...
Got it. One more quick question...
```

--------------------------------

### Event-Based Referral Triggers and Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/referral-request-timing/SKILL.md

Provides examples of natural moments or events that trigger opportune referral requests.

```text
Natural moments for referral asks:

Just closed deal:
"Who else at [company] should know about this?"
(Warm intro within same company)

After success milestone:
"Now that [result], any colleagues facing same challenge?"

After renewal:
"You've renewed—clearly seeing value. Who else would?"

After positive review/feedback:
"Thanks for the kind words! Anyone come to mind
who'd benefit similarly?"

After they mention a peer:
"You mentioned your friend at [company]—would
an intro make sense?"
```

--------------------------------

### User Activity Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/social-proof-injection/SKILL.md

Shows real-time social proof like sign-ups or active users, effective for creating FOMO and reducing risk perception.

```text
Real-time social proof:

"15 companies signed up this week"
"Sarah from TechCorp is also exploring this"
"Most popular choice for teams your size"

Best for:
- FOMO creation
- Validating popularity
- Reducing risk perception
```

--------------------------------

### Smart Routing Response Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/out-of-scope-request-handling/SKILL.md

Example of a response that detects a request type and provides specific routing information.

```text
Detect request type → Pull appropriate routing

"For [billing questions], our billing team is the best
resource: billing@company.com or call 1-800-XXX-XXXX.

They're available [hours] and usually respond within
[timeframe]."
```

--------------------------------

### Handling 'Can I get a discount?' - Explore First

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/pricing-discussion-logic/SKILL.md

Avoid immediate discounting; first, understand the reason for the discount request and explore options.

```text
"I may be able to help with that. Can you share more
about what you're working with? Is it a budget constraint,
or are you comparing to another option?"
```

--------------------------------

### Cancellation Request Response Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/meeting-confirmation-reminder-logic/SKILL.md

Example response to a cancellation request, focusing on offering rescheduling options without pressure.

```text
Understood. Would you like to reschedule for
a better time, or should I follow up in a few
weeks when things settle down?
```

--------------------------------

### LinkedIn First Message Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/copywriting/SKILL.md

An example of a first LinkedIn message after connecting, focusing on a relevant observation and offering value.

```text
Hey Sarah,

Thanks for connecting.

Noticed you're scaling the SDR team at Acme. Curious how you're thinking about outbound in the current environment?

We've been seeing interesting patterns with teams your size—happy to share if useful.

Mike
```

--------------------------------

### Example Entity-Centric Memory Structure

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/multi-turn-context-retention/SKILL.md

Shows how to organize memory around key entities like prospects, companies, and deals, storing relevant attributes and details for each.

```text
PROSPECT: John Smith
├── Role: VP Sales
├── Authority: Up to $30k
├── Communication: Prefers email
└── Personality: Direct, time-conscious

COMPANY: Acme Corp
├── Size: 200 employees
├── Industry: SaaS
├── Current tool: Spreadsheets
└── Pain: Manual reporting

DEAL: Opportunity_123
├── Budget: $30k
├── Timeline: Q2
├── Stage: Demo scheduled
└── Blockers: CFO approval needed
```

--------------------------------

### Multi-Channel Revival Sequence Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/conversation-resurrection/SKILL.md

An example of coordinating outreach across different channels over a 21-day period for a revival sequence.

```text
Day 0: Email (primary revival message)
Day 3: LinkedIn (if no response, different angle)
Day 7: Email follow-up
Day 14: SMS (if opted in, brief check-in)
Day 21: Final email (break-up)

Don't use all channels at once—escalate gradually.
```

--------------------------------

### Example Structure for Pricing/Investment Slide

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/sales-presentations/SKILL.md

Present pricing clearly by leading with value and providing context like ROI. This structure helps justify the investment.

```markdown
Your Investment

Based on [scope], we recommend:

[Solution Package]
- [What's included]
- [What's included]
- [What's included]

Investment: $[Amount]
Expected ROI: [X]x in [timeframe]
```

--------------------------------

### Timeline Reinforcement Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/buying-signal-amplification/SKILL.md

Example of responding to a timeline-related buying signal by confirming feasibility and proposing a concrete next step.

```text
Signal: "We need to solve this before Q2."

Response:
"That's tight but doable. For Q2 readiness, we'd
want to kick off by mid-February. I've seen similar
timelines work when we do a focused pilot first.
Want me to sketch out what a February start
would look like?"

→ Confirms timeline is possible
→ Creates slight urgency
→ Proposes concrete next step
```

--------------------------------

### Example Structure for Social Proof/Case Study Slides

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/sales-presentations/SKILL.md

Use this structure to build credibility by showcasing customer success. Focus on a similar industry or use case with specific, quantified results.

```markdown
[Customer Logo]

Challenge: [Similar to prospect's challenge]
Solution: [How they used your product]
Result: [Specific, quantified outcome]

"Companies like [Customer] have seen [result]..."
```

--------------------------------

### Static Bot vs. Bot with Feedback Loops

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/feedback-loop-integration/SKILL.md

Illustrates the core problem of static bots and the benefits of implementing feedback loops for continuous improvement.

```text
Bot deployed with initial messages:
- Same templates forever
- No learning from results
- What worked in testing may not work at scale
- Changing market = declining performance

Result: Performance degrades over time
```

```text
Bot learns continuously:
- Tracks message → outcome correlation
- Identifies winning patterns
- Deprecates losing patterns
- Adapts to market changes

Result: Performance improves over time
```

--------------------------------

### LinkedIn Connection Request Examples

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/copywriting/SKILL.md

Examples demonstrating how to personalize a LinkedIn connection request based on shared interests or observed content.

```text
Hi Sarah, noticed we're both in the B2B sales space and I've been following your posts on outbound. Would love to connect.
```

```text
Hi John, saw your talk at SaaStr last month—great insights on scaling SDR teams. Would love to connect.
```

--------------------------------

### Handling 'That's too expensive' - Step 1

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/pricing-discussion-logic/SKILL.md

Begin addressing price objections by understanding the root cause: budget constraints or comparison to alternatives.

```text
Step 1: Understand the objection
"I hear you. Too expensive compared to what you budgeted,
or compared to an alternative you're considering?"
```

--------------------------------

### Strong Sales Hypothesis Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/ab-test-setup/SKILL.md

An example of a well-structured hypothesis that includes observation, change, effect, segment, and metrics for measurable outcomes.

```markdown
Because prospects in the CFO segment respond better to ROI messaging (per reply analysis), we believe leading with specific cost savings in our subject line will increase reply rates by 20%+ for cold outreach to finance leaders. We'll measure reply rate and meeting booked rate.
```

--------------------------------

### Examples of Variable Message Elements

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/spam-bot-detection-avoidance/SKILL.md

Use these examples of variable openers, value propositions, and calls to action to personalize messages and increase engagement.

```text
Openers:
- "I noticed [Company] is [observation]."
- "Saw that [Company] recently [event]."
- "Your [role] caught my attention because..."
- "Quick question about [topic]..."

Value props:
- "We help [similar companies] [outcome]."
- "Most [role]s struggle with [problem]. We fix that."
- "Thought of you when [trigger]."

CTAs:
- "Worth a quick chat?"
- "Open to learning more?"
- "Would it make sense to connect?"
- "Interested in seeing how it works?"
```

--------------------------------

### Handling Support vs. Sales Scenarios

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/out-of-scope-request-handling/SKILL.md

Example response for when a prospect has a support issue rather than a sales inquiry.

```text
Prospect: "I'm having trouble logging into my account"

Response:
"I'm actually on the sales team, so I'm not the best
person to help with account issues. But I can definitely
get you to someone who can!

Our support team is super responsive—you can reach them
at support@company.com or through the help button in the app.

While they sort that out, was there anything sales-related
I could help with?"
```

--------------------------------

### SMS Channel Norms and Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/response-length-calibration/SKILL.md

Defines optimal and maximum character counts for SMS messages, along with formatting guidelines and a concise example.

```text
Optimal: 50-160 characters (1 SMS segment)
Maximum: 320 characters (2 segments)
Never: 500+ characters

Format:
- Single clear ask
- No paragraphs
- Direct language
- Easy response

Example:
"Hi [Name], any questions after the demo?
Happy to clarify anything."
```

--------------------------------

### Stacked Objections Response Example

Source: https://github.com/louisblythe/sales-skills/blob/main/skills/objection-recognition/SKILL.md

Example response for handling multiple objections simultaneously. It acknowledges both, addresses the primary, and checks if the secondary remains.

```text
"I hear you on both counts—budget and timing matter. Let me address the investment question first... [response]. Does that help, or is timing still the bigger factor?"
```