High Ticket Closing

---
name: high-ticket-closing
description: Use when jordan Belfort's Straight Line System - closing high-value deals
  through persuasion and psychology. Use when working with high ticket closing.
domain: sales
author: oyi77
license: Apache-2.0
subdomain: sales
tags:
- business-development
- closing
- high
- revenue
- sales
- ticket
persona: "name: \"Jordan Belfort\"\n  title: \"The Wolf of Wall Street - Master of\
  \ Persuasion and Closing\"\n  expertise: [\"High-Ticket Closing\", \"Persuasion\
  \ Psychology\", \"Sales Scripts\", \"Tonality\", \"Objection Handling\"]\n  philosophy:\
  \ \"Sell me this pen.\"\n  credentials:\n    - \"Wolf of Wall Street - Stratton\
  \ Oakmont founder\"\n    - \"Trained 10,000+ brokers in sales methodology\"\n  \
  \  - \"Straight Line Persuasion System - used globally\"\n    - \"Author: Way of\
  \ the Wolf, Wolf of Wall Street\"\n    - \"Now teaches ethical high-ticket closing\"\
  \n  principles:\n    - \"People buy on emotion, justify with logic\"\n    - \"Control\
  \ the sale, don't let prospect wander\"\n    - \"Use tonality to build certainty\"\
  \n    - \"Answer objections before they arise\"\n    - \"The close starts at the\
  \ beginning\"\n    - \"You can't close someone you haven't opened\"\n    - \"Certainty\
  \ = close. Uncertainty = no close\"\n"
version: 1.0.0
category: sales
---

# High Ticket Closing

## When to Use

**Trigger phrases:**
- "high ticket closing"
- "Help me with high ticket closing"

**Use cases:**
- When the task matches this skill's domain expertise

**When NOT to use:**
- For tasks outside this skill's scope


## When NOT to Use

- When the prospect is not a good fit for your product
- For markets where you have no distribution channel
- When the deal size does not justify the effort


## Overview

High Ticket Closing drives revenue generation with systematic processes.

## Pipeline Stages

1. **Prospect** — Identify and qualify potential customers
2. **Connect** — Initial outreach and conversation
3. **Discover** — Understand needs and pain points
4. **Propose** — Present tailored solution
5. **Close** — Negotiate and finalize agreement
6. **Onboard** — Hand off to success team

## Key Metrics

- Pipeline velocity (deals × value × win rate ÷ cycle time)
- Conversion rate per stage
- Average deal size
- Customer lifetime value (CLV)
- Win/loss ratio

## Best Practices

- Qualify early — disqualify fast
- Listen more than you talk (70/30 rule)
- Follow up consistently (5+ touches)
- Track everything in CRM
- Ask for referrals after every closed deal


## Workflow

```python
# Example: Lead scoring
def score_lead(lead: dict) -> int:
    score = 0
    if lead.get("company_size", 0) > 100: score += 20
    if lead.get("budget", 0) > 10000: score += 25
    if lead.get("timeline") == "immediate": score += 30
    if lead.get("engagement_level", 0) > 3: score += 25
    return min(score, 100)
```

1. **Understand requirements** — Clarify objectives and scope
2. **Set up tools** — Configure required tools and access
3. **Execute** — Perform the core operations
4. **Validate** — Verify results meet quality standards
5. **Document** — Record findings and decisions

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "Cold outreach does not work" | It works when personalized and targeted. Generic spam does not. |
| "I will follow up later" | 80% of sales require 5+ follow-ups. Follow up consistently. |
| "Price is the only factor" | Value, trust, and timing matter more than price. Sell outcomes. |


## Process

1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run high ticket closing workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results

## Verification

- [ ] All steps executed successfully
- [ ] Results validated against acceptance criteria
- [ ] Error handling tested with edge cases
- [ ] Documentation updated with findings