The Create New Deal feature allows users to add a new sales opportunity into a pipeline and begin tracking its lifecycle from the earliest stage to closure. A deal represents a potential revenue-generating interaction with a lead, contact, or company.
This section explains each field, behavior, and best practice in detail.
Overview
Clicking + Add Deal opens a side panel with three parts:
- A Deal Name and Link this deal to section, always visible at the top
- A collapsible Deal Details section (stage, priority, amount, currency, tags)
- A collapsible Additional section (description, documents, custom fields)
Both collapsible sections start closed, so a new deal can be created with just a name, an owner, and a linked client/lead/company — everything else is optional until you expand it.
Once created, the deal becomes visible in the pipeline board under the selected stage and can be managed through its lifecycle.
Note: the pipeline list on the left of the Sales Pipeline screen can be collapsed to a slim icon rail to give the board more room — this doesn't affect deal creation, it only changes how you switch between pipelines.
Field-Level Breakdown
A. Deal Name
Type: Text input (required)
Purpose: Identifies the deal uniquely within the pipeline.
Guidelines:
- Use clear, descriptive naming
- Recommended format:
Client Name – Service/Product – Month
Example:
- “Acme Corp – Website Redesign – May”
B. Link this deal to
Type: Tab selector — Client, Lead, or Company (required, choose exactly one)
Purpose: Connects the deal to the person or organization it's being pursued with.
Behavior:
- Switching tabs clears whatever was selected on the other tabs, so a deal is only ever linked to one client, one lead, or one company at a time
- Client: picks from existing Contacts
- Lead: picks from existing Leads
- Company: picks from existing Company accounts, useful for B2B deals not yet tied to one specific contact
- At least one of the three must be selected before the deal can be created
C. Owner & Assignee
Type: Team member selection (required)
Purpose: Assigns responsibility for managing the deal.
Behavior:
- The selected user becomes the deal owner
- Appears in reporting and performance tracking
D. Stage
Type: Dropdown (required, inside Deal Details)
Default: The stage of the pipeline column you clicked + Add Deal from, or the pipeline's first stage if none was pre-selected
Purpose: Defines the current position of the deal in the pipeline.
Behavior:
- Options are the real stages configured for the current pipeline
- Determines where the deal appears on the pipeline board
- Can be changed later via drag-and-drop or edit
E. Priority
Type: Dropdown (inside Deal Details)
Options:
- Low (default)
- Medium
- High
- Urgent
Purpose: Helps prioritize deal handling.
F. Lead Type
Type: Dropdown (inside Deal Details)
Options:
- Cold
- Warm
- Hot
Purpose: Indicates engagement level. Only shown when the deal is linked to a Lead (section B) — it doesn't apply to Client- or Company-linked deals.
G. Deal Status
Type: Dropdown (inside Deal Details)
Options:
- Open (default)
- Negotiation
- Won
- Lost
Purpose: Tracks where the deal stands independently of its pipeline stage.
H. Deal Amount
Type: Numeric input (required, inside Deal Details)
Purpose: Defines the monetary value of the deal.
Behavior:
- Used for revenue forecasting and pipeline column totals
- Can be updated as negotiations progress
I. Closing Date
Type: Date picker (inside Deal Details)
Purpose: Expected deal completion date.
Behavior:
- Used for forecasting
- Helps identify delays or overdue deals
J. Currency
Type: Dropdown (inside Deal Details)
Default: Your workspace's configured business currency
Purpose: Specifies the currency for the deal value.
Behavior:
- Can be overridden per deal
- Ensures accurate financial reporting across the pipeline
K. Tags
Type: Multi-select (inside Deal Details)
Purpose: Categorizes deals for filtering and segmentation.
Behavior:
- Pick from existing tags or type a new one to create it on the fly
L. Description
Type: Rich text editor (inside Additional)
Purpose: Stores additional deal context — requirements, client expectations, internal notes.
Behavior:
- Includes an AI-assist option to help draft the description
M. Select Documents
Type: Multi-select (inside Additional)
Purpose: Attach existing workspace documents such as proposals, contracts, or quotations to the deal.
N. Add Custom Field
Type: Dynamic input, opened from the + Add Custom Field button in the panel footer
Purpose: Extend deal data beyond the default fields (e.g. Industry, Deal Source, Competitor, Contract Duration).
Actions
A. Create Deal
- Validates all required fields
- Saves deal into the selected pipeline
- Assigns it to the chosen stage
- Triggers automation (if configured)
B. Cancel
- Discards all inputs
- No data is saved
System Behavior After Creation
Once a deal is created:
- It appears in the pipeline board under the selected stage
- It becomes accessible via the Deal Details page
- Activity tracking begins (timeline logging)
Validation Rules
- Required fields must be completed:
- Deal Name
- A linked Client, Lead, or Company (exactly one)
- Owner & Assignee
- Stage
- Deal Amount
- Invalid or missing data will prevent submission
- Numeric fields must accept valid numbers only
Best Practices
- Use consistent naming conventions for deals
- Assign deals immediately to avoid ownership gaps
- Set realistic closing dates for accurate forecasting
- Update deal amount as negotiations evolve
- Use tags for better filtering and reporting
Example Deal Creation Flow
- User clicks + Add Deal
- Enters:
- Deal Name: “ABC Ltd – Mobile App Development”
- Link this deal to: Client → ABC Ltd
- Owner & Assignee: John
- Expands Deal Details and sets:
- Stage: (defaults to the column clicked, or first stage)
- Priority: High
- Deal Amount: $5,000
- Expands Additional, adds a description and attaches a proposal document
- Clicks Create Deal
→ Deal is added to the pipeline and visible to the team