When to Use
Agent helps with B2B sales: prospecting, outreach, deal qualification, pipeline analysis, forecast reviews, or account strategy. Applies to founders selling enterprise, sales reps, or sales managers.
Quick Reference
| Topic |
File |
| Frameworks |
frameworks.md |
| Outreach |
outreach.md |
| Pipeline |
pipeline.md |
Core Rules
1. Research Before Outreach
- Min 3 insights per prospect: recent news, hiring signals, tech stack, funding
- Identify decision makers AND influencers (map org chart)
- Detect buying signals: leadership changes, expansion, competitor issues
- Never send generic "I noticed you work at X" messages
2. Qualify Ruthlessly (MEDDIC)
| Element |
Question |
| Metrics |
What measurable outcome do they need? |
| Economic Buyer |
Who signs the check? |
| Decision Criteria |
What will they evaluate? |
| Decision Process |
What steps before purchase? |
| Identify Pain |
What specific problem hurts? |
| Champion |
Who will sell internally for us? |
3. Multi-Thread Every Deal
- Never single-threaded (one contact = fragile deal)
- Map: Champion, Economic Buyer, Technical Evaluator, End Users
- Ask: "Who else should be involved in this decision?"
- If champion leaves, deal often dies
4. Next Step Obsession
- Every interaction MUST end with concrete next step + date
- "I'll follow up" is not a next step
- Use Mutual Action Plans for complex deals
- No next step = deal is stalled
5. Don't Trust CRM Stage
- A deal in "Negotiation" may be dead
- Validate with: recent activity, next step scheduled, champion engaged
- Time in stage matters: 60 days in Discovery = red flag
- Weighted pipeline only works with realistic probabilities
6. Build Champions, Not Just Contacts
- Champion = someone who sells internally when you're not there
- Arm them with ROI data, competitive positioning, internal pitch
- If they can't articulate value without you, not a champion yet
- Protect and nurture: their success = your success
Common Traps
| Trap |
Reality |
| Superficial personalization |
"Hi [Name], I see you work at [Company]" is not personalization |
| Talking features before pain |
Understand their problem first; demo features they need |
| Ignoring buying committee |
You need consensus, not just one excited person |
| Happy ears syndrome |
Rep says "great call!" but no commitment to next step |
| Chasing volume over ICP |
10 qualified leads > 100 random ones |
| Premature proposal |
Sending pricing before validating budget/authority |
| Forgetting the champion post-close |
Recipe for churn |
| Same message to CEO and user |
Different stakeholders need different value props |
Forecasting Red Flags
- Deal in pipeline 3x average cycle length
- No activity in 14+ days
- Single-threaded with one contact
- Verbal "yes" but no signed paperwork
- Champion "too busy" for next meeting
- Procurement/legal not engaged in late stage
- Slipped commit date more than once
1---2name: b2b3description: Close enterprise deals with qualification frameworks, prospecting research, pipeline management, and outreach personalization.4---56## When to Use78Agent helps with B2B sales: prospecting, outreach, deal qualification, pipeline analysis, forecast reviews, or account strategy. Applies to founders selling enterprise, sales reps, or sales managers.910## Quick Reference1112| Topic | File |13|-------|------|14| Frameworks | `frameworks.md` |15| Outreach | `outreach.md` |16| Pipeline | `pipeline.md` |1718## Core Rules1920### 1. Research Before Outreach21- Min 3 insights per prospect: recent news, hiring signals, tech stack, funding22- Identify decision makers AND influencers (map org chart)23- Detect buying signals: leadership changes, expansion, competitor issues24- Never send generic "I noticed you work at X" messages2526### 2. Qualify Ruthlessly (MEDDIC)27| Element | Question |28|---------|----------|29| Metrics | What measurable outcome do they need? |30| Economic Buyer | Who signs the check? |31| Decision Criteria | What will they evaluate? |32| Decision Process | What steps before purchase? |33| Identify Pain | What specific problem hurts? |34| Champion | Who will sell internally for us? |3536### 3. Multi-Thread Every Deal37- Never single-threaded (one contact = fragile deal)38- Map: Champion, Economic Buyer, Technical Evaluator, End Users39- Ask: "Who else should be involved in this decision?"40- If champion leaves, deal often dies4142### 4. Next Step Obsession43- Every interaction MUST end with concrete next step + date44- "I'll follow up" is not a next step45- Use Mutual Action Plans for complex deals46- No next step = deal is stalled4748### 5. Don't Trust CRM Stage49- A deal in "Negotiation" may be dead50- Validate with: recent activity, next step scheduled, champion engaged51- Time in stage matters: 60 days in Discovery = red flag52- Weighted pipeline only works with realistic probabilities5354### 6. Build Champions, Not Just Contacts55- Champion = someone who sells internally when you're not there56- Arm them with ROI data, competitive positioning, internal pitch57- If they can't articulate value without you, not a champion yet58- Protect and nurture: their success = your success5960## Common Traps6162| Trap | Reality |63|------|---------|64| Superficial personalization | "Hi [Name], I see you work at [Company]" is not personalization |65| Talking features before pain | Understand their problem first; demo features they need |66| Ignoring buying committee | You need consensus, not just one excited person |67| Happy ears syndrome | Rep says "great call!" but no commitment to next step |68| Chasing volume over ICP | 10 qualified leads > 100 random ones |69| Premature proposal | Sending pricing before validating budget/authority |70| Forgetting the champion post-close | Recipe for churn |71| Same message to CEO and user | Different stakeholders need different value props |7273## Forecasting Red Flags7475- Deal in pipeline 3x average cycle length76- No activity in 14+ days77- Single-threaded with one contact78- Verbal "yes" but no signed paperwork79- Champion "too busy" for next meeting80- Procurement/legal not engaged in late stage81- Slipped commit date more than once
johnalbertini14-glitch