# Sales Pipeline Pattern
## Keywords
`sales`, `deal`, `pipeline`, `opportunity`, `close`, `win`, `revenue`, `CRM`, `sales funnel`
## Overview
Manage deals from opportunity creation to close. This is the PRIMARY workflow for sales-focused workspaces, using deal-centric operations rather than company-centric tracking.
## When to Use
- Creating new sales opportunities
- Managing deal progression through stages
- Tracking deal values and close dates
- Associating companies and people with deals
- Creating follow-up tasks for sales reps
## Workflow Steps
### Step 1: Create deal from opportunity
Call `create-record` with:
```json
{
"resource_type": "deals",
"record_data": {
"name": "Q4 Enterprise Deal - Acme Inc",
"value": 50000,
"stage": "In Progress",
"associated_company": ["<company_record_id>"]
}
}
```
> **Note**: Use exact stage option titles from your workspace. Check schema skill for custom attributes.
### Step 2: Add to active deals list
Call `add-record-to-list` with:
```json
{
"listId": "<your-active-deals-list-id>",
"record_id": "<deal_record_id>",
"resource_type": "deals"
}
```
> **Note**: Get listId from your schema skill.
### Step 3: Create discovery task
Call `create-task` with:
```json
{
"content": "Schedule discovery call",
"title": "Discovery Call",
"linked_records": [
{
"target_object": "deals",
"target_record_id": "<deal_record_id>"
}
],
"dueDate": "2024-12-16T10:00:00Z"
}
```
### Step 4: Document opportunity context
Call `create-note` with markdown formatting for structured notes:
```json
{
"resource_type": "deals",
"record_id": "<deal_record_id>",
"title": "Opportunity Context",
"content": "## Source\nInbound demo request\n\n## Key Stakeholders\n- CTO\n- VP Engineering\n\n## Budget\nConfirmed: $50k",
"format": "markdown"
}
```
**Tip**: Use `\n` for line breaks, `##` for headings, and `-` for bullet points.
### Step 5: Progress through stages
Call `update-record` with:
```json
{
"resource_type": "deals",
"record_id": "<deal_record_id>",
"record_data": {
"stage": "Won",
"value": 55000
}
}
```
### Step 6: Move between lists (if using list-based pipeline)
Call `remove-record-from-list` with:
```json
{
"listId": "<discovery-list-id>",
"entryId": "<entry_id>"
}
```
Then call `add-record-to-list` with:
```json
{
"listId": "<proposal-list-id>",
"record_id": "<deal_record_id>"
}
```
## Key Points
- **Deal-centric workflow** (not company-centric)
- **Status field updates OR list movement** (depending on workspace setup)
- **Task creation** for follow-ups
- **Notes** for context and audit trail
- Always use **exact option titles** for status/stage fields
## Cross-References
- [Golden Rules](../golden-rules.md) - Error prevention, especially status field formatting
- [Tool Reference](../tool-reference.md) - `create-record`, `update-record`, `create-task`, `create-note`
- **attio-workspace-schema skill** - Your workspace's deal attributes, stage options, list IDs
