oyi77 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
- Prospect — Identify and qualify potential customers
- Connect — Initial outreach and conversation
- Discover — Understand needs and pain points
- Propose — Present tailored solution
- Close — Negotiate and finalize agreement
- 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
# 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)
- Understand requirements — Clarify objectives and scope
- Set up tools — Configure required tools and access
- Execute — Perform the core operations
- Validate — Verify results meet quality standards
- 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
- Prepare — Gather requirements, verify prerequisites, set up environment
- Execute — Run high ticket closing workflow with configured parameters
- 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