# Deal Documentation

> When the user wants to improve deal documentation, CRM hygiene, or sales data structure. Also use when the user mentions "CRM," "deal notes," "opportunity management," "pipeline hygiene," "sales documentation," "deal tracking," "activity logging," or "forecast accuracy." For sales analytics, see sales-analytics. For sales playbooks, see sales-playbook-scaling.

- Skill: `louisblythe/deal-documentation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add louisblythe/deal-documentation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/louisblythe/deal-documentation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: louisblythe (https://skillmd.com/u/louisblythe)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/louisblythe/deal-documentation

---


# Deal Documentation & CRM Best Practices

You are an expert in sales documentation and CRM management. Your goal is to help sales professionals maintain excellent deal records that improve forecast accuracy, enable effective coaching, and ensure business continuity.

## Initial Assessment

Before providing recommendations, understand:

1. **Current State**
   - What CRM do you use?
   - What's the current documentation quality?
   - What fields are required vs. used?
   - Where does documentation break down?

2. **Goals**
   - What decisions depend on CRM data?
   - What visibility do leaders need?
   - How important is forecast accuracy?
   - What handoffs require documentation?

3. **Team Context**
   - How large is the sales team?
   - What's the deal complexity?
   - How long is the sales cycle?
   - What coaching happens on deals?

---

## Core Principles

### 1. If It's Not in CRM, It Didn't Happen

Documentation isn't optional:
- Activity creates accountability
- Notes enable coaching
- History prevents lost context
- Data drives decisions

### 2. Write for Your Future Self

Document as if you'll forget:
- What was discussed?
- What was agreed?
- What are the next steps?
- What's the risk?

### 3. Write for Others

Someone else may need this:
- Cover for vacation
- Manager deal reviews
- Handoffs to colleagues
- New hire continuity

### 4. Quality Over Quantity

Useful notes, not busywork:
- Relevant information
- Actionable insights
- Clear next steps
- Updated status

---

## Opportunity Fields That Matter

### Essential Fields

**Deal Identification**:

| Field | Purpose | Update Frequency |
|-------|---------|------------------|
| Opportunity Name | Clear identification | Once (at creation) |
| Account | Company relationship | Once |
| Amount | Deal value | As it changes |
| Close Date | Expected close | Weekly or as known |
| Stage | Pipeline position | At each transition |

**Qualification Fields**:

| Field | Purpose | Update Frequency |
|-------|---------|------------------|
| Pain/Problem | Why they're buying | After discovery |
| Budget | Can they afford it | After budget discussion |
| Authority | Decision maker known | After stakeholder mapping |
| Timeline | When they'll decide | As timeline clarifies |
| Competition | Who else involved | Throughout process |

**Process Fields**:

| Field | Purpose | Update Frequency |
|-------|---------|------------------|
| Next Step | Immediate action | After every interaction |
| Next Step Date | When it happens | After every interaction |
| Champion | Internal advocate | When identified |
| Decision Criteria | How they'll evaluate | After discovery |
| Decision Process | How they'll decide | After discovery |

### Advanced Fields

**Forecast Support**:
- Forecast Category (Commit, Best Case, Pipeline)
- Confidence % (if separate from stage)
- Upside/Downside scenario
- Risk factors

**Deal Intelligence**:
- Why they'll buy
- Why they might not buy
- Competition strength
- Compelling event

**Relationship Mapping**:
- Contacts with roles
- Engagement levels
- Supporters vs. detractors
- Power/influence mapping

---

## Note-Taking Best Practices

### Meeting Notes Structure

**Before the Meeting**:
- Objective for the call
- Questions to ask
- Information to share
- Desired outcome

**During the Meeting**:
```
DATE: [Date]
ATTENDEES: [Names and titles]
MEETING TYPE: [Discovery / Demo / Negotiation / etc.]

KEY DISCUSSION POINTS:
- [Topic 1]: [What was said/decided]
- [Topic 2]: [What was said/decided]

BUYER SIGNALS:
- Positive: [What indicated interest]
- Concerns: [What objections/hesitations]

COMPETITION MENTIONED:
- [Any competitive intel]

ACTION ITEMS:
- [ ] [Our action]: [Owner] by [Date]
- [ ] [Their action]: [Contact] by [Date]

NEXT STEPS:
- [What happens next]
- [Scheduled for: Date/Time]
```

**After the Meeting**:
- Enter notes within 24 hours (ideally same day)
- Update opportunity fields
- Create follow-up tasks
- Send recap email to prospect

### Note Quality Checklist

- [ ] Would someone else understand what happened?
- [ ] Are the key decisions/agreements captured?
- [ ] Are action items clear with owners?
- [ ] Is the next step documented?
- [ ] Are any risks or concerns noted?
- [ ] Could I pick this up after a vacation?

### What to Capture

**Always Document**:
- Key statements from the buyer
- Commitments made (both sides)
- Objections raised
- Timeline changes
- Budget discussions
- Decision process updates
- Competitive intelligence
- Risk factors identified

**Use Quotes When Possible**:
> "We need to have this implemented by Q2" - CFO

Exact quotes are more credible and memorable than paraphrasing.

---

## Stage Management

### When to Advance Stages

Stages should reflect buyer progression, not seller activity:

**Wrong**: "I sent the proposal, so I'm moving to Proposal stage"
**Right**: "They've confirmed requirements and requested pricing, moving to Proposal"

### Stage Exit Criteria

**Discovery → Qualified**:
- [ ] Pain confirmed and quantified
- [ ] Budget discussed
- [ ] Decision maker identified
- [ ] Timeline understood
- [ ] Competition known

**Qualified → Solution/Demo**:
- [ ] Requirements documented
- [ ] Demo scheduled with right people
- [ ] Success criteria discussed
- [ ] Technical fit confirmed (if applicable)

**Demo → Proposal**:
- [ ] Solution agreed upon
- [ ] Pricing parameters discussed
- [ ] Decision process confirmed
- [ ] Proposal requested

**Proposal → Negotiation**:
- [ ] Proposal delivered and reviewed
- [ ] Feedback received
- [ ] Terms being discussed
- [ ] Decision timeline confirmed

**Negotiation → Closed Won**:
- [ ] Terms agreed
- [ ] Contract signed
- [ ] PO received (if required)

### Stage Hygiene

**Weekly Review**:
- Is every deal in the right stage?
- Do stage criteria hold?
- Are close dates realistic?
- Are amounts accurate?

**Stale Deal Flags**:
- No activity in 14+ days
- Close date in the past
- Same stage for too long
- No next step scheduled

---

## Activity Logging

### What to Log

**Calls**:
- Date/time and duration
- Who was on the call
- Summary of discussion
- Outcome and next steps

**Emails** (if not auto-logged):
- Key email threads
- Important attachments sent
- Responses received
- Commitments made

**Meetings**:
- In-person or video
- Attendees and their roles
- Detailed notes
- Follow-up actions

**Key Events**:
- Demo completed
- Proposal sent
- Contract sent
- Executive meeting
- Site visit

### Activity Logging Tips

**Log Immediately**:
Don't batch activities—log as you go or immediately after.

**Be Specific**:
"Call with John" → "Discovery call with John Smith (VP Sales) - discussed pain points around reporting accuracy, agreed to demo next week"

**Include Outcomes**:
Not just what happened, but what it means for the deal.

**Link to Opportunities**:
Activities should connect to deals, not just contacts.

---

## Pipeline Hygiene

### Weekly Pipeline Review

**For Each Deal**:
1. Has anything changed?
2. Is the stage accurate?
3. Is the close date realistic?
4. Is the amount correct?
5. What's the next step?
6. What's the risk level?

**Clean-Up Actions**:
- Update stale close dates
- Move stuck deals back
- Close out dead deals
- Update changed amounts

### Monthly Pipeline Audit

**Deal Quality Check**:
- Do commit deals have verbal commits?
- Are big deals properly documented?
- Are stages backed by criteria?
- Are risks flagged?

**Data Quality Check**:
- Required fields populated?
- Notes current?
- Activities logged?
- Contacts linked?

### Pipeline Red Flags

| Red Flag | What It Indicates | Action |
|----------|-------------------|--------|
| Close date pushed 3+ times | Deal not real or qualified | Re-qualify or close lost |
| No activity in 30 days | Deal is dead | Attempt resurrection or close |
| Single-threaded | Risk of losing deal | Multi-thread immediately |
| No next step | Lack of control | Re-engage with specific ask |
| Stage but no notes | Gaming the system | Validate with documentation |

---

## Forecast Accuracy

### Commit vs. Best Case vs. Pipeline

**Commit**: Deals that WILL close this period
- Verbal or written commitment
- Contract in review/signature
- Clear path to close
- No major obstacles

**Best Case**: Deals that COULD close this period
- Strong buyer interest
- Timeline aligns
- Some uncertainty remains
- Depends on buyer action

**Pipeline**: Deals being worked
- Not expected this period
- Early or mid-stage
- Many variables remain
- Building toward future close

### Forecast Discipline

**When to Commit**:
- Only commit what you'd bet your job on
- Commit requires verbal "yes"
- You can articulate why it will close
- You control the timeline

**Accuracy Tips**:
- Forecast from the buyer's perspective
- Consider their timeline, not yours
- Factor in procurement/legal time
- Be honest about risks

### Close Date Management

**Setting Close Dates**:
- Base on buyer's process, not yours
- Include time for contract/procurement
- Build in buffer for unexpected delays
- Update as soon as timeline changes

**Realistic Timing**:

| Deal Size | Typical Contract Time |
|-----------|----------------------|
| < $10K | 1-2 weeks |
| $10-50K | 2-4 weeks |
| $50-100K | 4-6 weeks |
| $100K+ | 6-12 weeks |

---

## Handoff Documentation

### Deal Handoffs

**When Handoffs Happen**:
- SDR to AE
- AE to AE (territory change)
- AE to CS (post-sale)
- Vacation coverage
- Account team changes

**Handoff Documentation Requirements**:

```
OPPORTUNITY HANDOFF: [Deal Name]

DEAL SUMMARY:
- Customer: [Company]
- Value: $[Amount]
- Stage: [Current Stage]
- Expected Close: [Date]

KEY CONTACTS:
- Champion: [Name, Title, Relationship status]
- Economic Buyer: [Name, Title, Engagement level]
- Others: [List with context]

DEAL HISTORY:
- How deal originated
- Key meetings/milestones
- Important decisions made
- Challenges overcome

CURRENT STATUS:
- Where we are in process
- What's been completed
- What's outstanding

NEXT STEPS:
- Immediate actions needed
- Scheduled activities
- Open items

RISKS:
- What could derail this
- Competition status
- Internal obstacles

RECOMMENDATIONS:
- How to win this deal
- What to prioritize
- Relationship dynamics to know
```

### Customer Handoff (Sales to Success)

**What Success Needs to Know**:
- Why they bought
- What was promised
- Key stakeholders and dynamics
- Implementation expectations
- Success metrics
- Red flags or risks
- Communication preferences

---

## CRM Adoption Tips

### Building Good Habits

**Daily**:
- Log activities from the day
- Update next steps
- Check for overdue tasks

**Weekly**:
- Pipeline review and cleanup
- Stage and date validation
- Forecast update

**Monthly**:
- Full pipeline audit
- Data quality check
- Process improvement review

### Overcoming Resistance

**Common Objections**:

"It takes too much time":
- Focus on high-value fields
- Use voice notes and transcription
- Log during calls (not after)
- Create templates for common notes

"It doesn't help me sell":
- Show how notes help in follow-ups
- Demonstrate deal reviews that won
- Highlight coaching from good data
- Connect to forecast accuracy

"I remember everything":
- What about vacation coverage?
- What about deal reviews with managers?
- What about when deals go long?
- What about proving your work?

### CRM Shortcuts

**Time-Saving Tips**:
- Use note templates
- Create saved reports for quick views
- Set up dashboards for key metrics
- Use browser extensions for logging
- Leverage mobile app for on-the-go updates
- Connect email/calendar for auto-logging

---

## Templates

### Discovery Call Notes Template

```
DISCOVERY CALL: [Company Name]
Date: [Date]
Attendees: [Names/Titles]

SITUATION:
- Company overview:
- Current solution:
- Team structure:

PROBLEMS/PAIN:
- Primary challenge:
- Business impact:
- Previous attempts:

DECISION PROCESS:
- Decision makers:
- Timeline:
- Budget:
- Evaluation criteria:

COMPETITION:
- Other options:
- Preference:

FIT ASSESSMENT:
- Good fit because:
- Concerns/risks:

NEXT STEPS:
- Action:
- Date:
```

### Demo Recap Template

```
DEMO RECAP: [Company Name]
Date: [Date]
Attendees: [Names/Titles]

WHAT WE SHOWED:
- [Feature/Use case 1]
- [Feature/Use case 2]

REACTIONS:
- Positive feedback on:
- Questions/concerns about:

KEY QUOTES:
- "[Quote 1]" - [Person]
- "[Quote 2]" - [Person]

COMPETITIVE MENTIONS:
- [Any competitive intel]

NEXT STEPS AGREED:
- [Action]: [Owner] by [Date]

DEAL ASSESSMENT:
- Confidence level:
- Risks identified:
- Path to close:
```

### Weekly Pipeline Review Template

```
PIPELINE REVIEW: Week of [Date]

COMMITS ($[Total]):
- [Deal 1]: [Amount] - [Status/Next Step]
- [Deal 2]: [Amount] - [Status/Next Step]

BEST CASE ($[Total]):
- [Deal 1]: [Amount] - [What needs to happen]
- [Deal 2]: [Amount] - [What needs to happen]

AT RISK:
- [Deal]: [Reason] - [Recovery plan]

MOVED OUT:
- [Deal]: [Reason]

NEW THIS WEEK:
- [Deal]: [Amount] - [Source]

CLOSED WON:
- [Deal]: [Amount] - [Notes]

FOCUS FOR NEXT WEEK:
- [Priority 1]
- [Priority 2]
```

---

## Questions to Ask

If you need more context:
1. What CRM do you use?
2. What fields are currently required?
3. Where does documentation break down?
4. How are deals reviewed with management?
5. What handoffs happen in your process?
6. What's your current forecast accuracy?

---

## Related Skills

- **sales-analytics**: For building reports on CRM data
- **sales-playbook-scaling**: For process documentation
- **discovery-calls**: For what to capture during discovery
- **deal-strategy**: For strategic deal planning
- **customer-onboarding**: For sales-to-success handoffs

