pre-client

What this skill does

# Pre-Client Identity Skill

## Overview

The Pre-Client Identity Skill is the **incoming lead intelligence engine**. It:
- Ingests and analyzes incoming emails automatically
- Extracts sender company, role, and background
- Clusters related messages into conversation threads
- Detects buying signals and business problems
- Builds relationship timelines for each prospect
- Surfaces high-potential opportunities for follow-up

Think of it as an AI that watches your inbox and alerts you when someone valuable walks in the door.

## Core Capabilities

### 1. Email Ingestion & Analysis

**What it captures:**
```
FROM SENDER:
- Name and email address
- Company name (extracted from email domain or signature)
- Job title/role
- Reporting to (if mentioned)
- Company size (estimated)
- Phone number (if provided)
- LinkedIn URL (if signature includes)
- Location/timezone

FROM EMAIL CONTENT:
- Subject line (intent signal)
- Body text (problem statement)
- Attachments (RFP, proposal, documentation)
- Links clicked (if tracking enabled)
- Email tone (formal, casual, urgent, desperate)

FROM EMAIL METADATA:
- Date received
- Time of day sent (weekend? off-hours?)
- Reply time (how quickly they respond)
- Response rate (how many emails before reply)
- Thread history (how long have they been in conversation)

EXAMPLE EMAIL ANALYSIS:

From: [email protected]
Subject: "Looking for better project management solution"

SENDER PROFILE:
- Name: Sarah Chen
- Company: TechStartup Inc (estimated 25-50 people)
- Role: Operations Manager
- Location: San Francisco, CA (timezone: PST)
- LinkedIn: linkedin.com/in/sarahchen
- Phone: Not provided

EMAIL CONTENT:
- Intent: Looking for solution (high intent signal)
- Problem: Current project management tool isn't meeting needs
- Pain points: Visibility, team collaboration, reporting
- Budget indicator: Not mentioned
- Timeline: "Looking to migrate Q1 2026"
- Current solution: Using Monday.com
- Dissatisfaction level: MODERATE (considering switch)

EMAIL TONE:
- Professional, respectful
- Not urgent or desperate
- Exploratory (gathering information)
- Open to solutions (receptive)

CONTEXT:
- Email sent Tuesday 9 AM (business hours)
- Took 2 hours to respond (attentive)
- First email in thread
- No attachments

SCORING:
- Fit score: 8/10 (perfect ICP match)
- Intent score: 7/10 (genuine interest, not urgent)
- Budget score: 5/10 (not mentioned, mid-market likely)
- Timeline score: 8/10 (Q1 2026 is soon)
- Response likelihood: 85% (warm prospect)
```

### 2. Thread Clustering & Organization

**Automatic conversation grouping:**

```
CLUSTERING ALGORITHM:
Groups emails into conversations based on:
1. Same sender + same company
2. Same topic/problem domain
3. Time proximity (within 2 weeks suggests related)
4. Reply-to-reply chains (email threading)

EXAMPLE CLUSTERED THREAD:
Conversation ID: SARAH_CHEN_PROJECT_MGMT_001

Email 1 (Nov 15, 9:02 AM):
From: [email protected]
Subject: "Looking for better project management solution"
[Initial inquiry]

Email 2 (Nov 15, 2:15 PM):
From: [email protected]
Subject: "RE: Looking for better project management solution"
[Follow-up with more details]

Email 3 (Nov 16, 10:30 AM):
From: [email protected]
Subject: "RE: Pricing and implementation timeline?"
[Asking about pricing and timeline]

Email 4 (Nov 18, 3:45 PM):
From: [email protected] (copied from email 3)
Subject: "RE: Pricing and implementation timeline?"
[CTO added to conversation - buying committee expanding]

THREAD SUMMARY:
- Duration: 3 days (active conversation)
- Participants: 2 (Sarah + John)
- Message count: 4
- Response time avg: 18 hours
- Engagement level: HIGH
- Buying committee growing: YES (CTO added)

OPPORTUNITY ASSESSMENT:
- This is a REAL opportunity (not just browsing)
- Buying committee forming (good sign)
- Timeline moving fast (3 days)
- Next step probability: 65%
```

### 3. Buying Signals Detection

**Identifies high-intent indicators:**

```
TIER 1: HIGHEST INTENT (Act immediately)
Signal: "We need to migrate by Q1"
Signal: "We've allocated budget for this"
Signal: "We're evaluating vendors this month"
Signal: "Your solution solves problem X that's costing us $Y"
Signal: "When can you start implementation?"
Signal: "Can you do a demo tomorrow?"
Action: Schedule call immediately

TIER 2: HIGH INTENT (Respond within hours)
Signal: "We're looking for a solution like yours"
Signal: "Our current tool doesn't support feature X"
Signal: "How much does this cost?"
Signal: "Can you send pricing and case studies?"
Signal: "Tell me more about your solution"
Signal: "Does this integrate with [their tools]?"
Action: Respond with valuable information

TIER 3: MODERATE INTENT (Follow up within 24 hours)
Signal: "We might be interested in the future"
Signal: "Just exploring options"
Signal: "Can you add me to your mailing list?"
Signal: "Do you have any case studies?"
Signal: "What's your free trial period?"
Action: Provide resources, nurture

TIER 4: LOW INTENT (Add to nurture sequence)
Signal: "Just curious what you do"
Signal: "We're not looking to change right now"
Signal: "Can I learn more about your company?"
Signal: "Interesting product, thanks for sharing"
Action: Long-term nurture, stay in touch

EXAMPLE SIGNALS IN CONTEXT:

Email: "We have budget allocated for this in Q1"
Tier: 1 (HIGHEST)
Reasoning: Budget allocated = money reserved
Action: Call them before competitors do

Email: "How long is your implementation timeline?"
Tier: 1-2 (HIGH)
Reasoning: Specific implementation question = ready to execute
Action: Provide detailed timeline, case study

Email: "Can you send us pricing?"
Tier: 2 (HIGH)
Reasoning: Asking about price = considering buying
Action: Send pricing + case study showing ROI

Email: "What do you charge?"
Tier: 2-3 (MODERATE-HIGH)
Reasoning: Price question, but phrased casually
Action: Respond quickly with pricing framework

Email: "Just browsing your website"
Tier: 4 (LOW)
Reasoning: No specific problem mentioned
Action: Add to nurture, wait for signal
```

### 4. Business Problem Detection

**Identifies pain points and opportunity triggers:**

```
OPPORTUNITY TYPES:

1. TOOL REPLACEMENT
Signal: "Our current [tool] isn't meeting our needs"
Problem: Existing solution inadequate
Opportunity: Replace with your solution
Timeline: Usually 4-8 weeks
Approach: Comparison guide, migration support

Example:
"We use Monday.com but it doesn't support our workflow"
→ You have project management solution
→ Create comparison: Monday.com vs. Your tool
→ Highlight features they specifically need
→ Timeline: Could migrate in Q1

2. PROCESS PAIN
Signal: "We're struggling with [process]"
Problem: Manual process, inefficiency
Opportunity: Automate with your solution
Timeline: Depends on complexity
Approach: ROI calculator, process improvement plan

Example:
"We spend 20 hours/week on manual status reports"
→ Your solution automates reporting
→ Calculate time savings: 20 hrs/week × 50 weeks = 1,000 hrs = $50k/year
→ ROI: Huge
→ Timeline: 30-60 days

3. GROWTH BLOCKER
Signal: "We can't scale because [reason]"
Problem: Current setup can't support growth
Opportunity: Enable growth with your solution
Timeline: Urgent (growth is happening now)
Approach: Growth strategy, capacity planning

Example:
"We can't onboard more clients because we can't manage them"
→ Your solution supports unlimited clients
→ Calculate revenue impact: Each client = $10k/year
→ For every 10 clients: $100k new revenue
→ Timeline: URGENT - do this month

4. COMPETITIVE THREAT
Signal: "Competitor X has feature Y"
Problem: Falling behind in market
Opportunity: Close gap with your solution
Timeline: Medium urgency
Approach: Competitive comparison, feature roadmap

Example:
"Competitor is offering integration we don't have"
→ Your solution has that integration
→ Risk: Losing customers to competitor
→ Timeline: 6-8 weeks to close gap

5. TEAM/WORKFLOW IMPROVEMENT
Signal: "Our team would work better if [feature]"
Problem: Sub