Deal and Lead Qualification
Workflows creating deals from intake forms and managing lead qualification stages
| Metric | Value |
|---|---|
| Workflows | 6 |
| Priority | high |
| Grouping Confidence | 90% — All workflows manage lead progression and qualification stages with overlapping business logic |
| Consolidation | Integrate intake processing, SQL qualification, and meeting milestone tracking into unified lead-to-opportunity process |
Workflows in this Group
| Workflow | Trigger | Outcome | Type | Complexity |
|---|---|---|---|---|
| Augmented AI Intake Form WF | Contact submits Augmented AI intake form with project details | Create qualified deal with contact's form data and assign to specific owner | StateChange | high |
| Deal > SQL > Sheet | Contact becomes a Sales Qualified Lead through deal association | Mark contact as SQL and sync to external reporting sheet | StateChange | medium |
| AE Assignment - Outbound - Positive Signals | Contact exhibits positive buying signals requiring AE assignment | Qualified prospect is assigned to appropriate Account Executive for outbound follow-up | Routing | medium |
| AE Assignment - Outbound - Meeting Booked | A meeting is booked through outbound prospecting efforts | Update contact and company records to reflect successful meeting booking and mark outbound status as active | StateChange | medium |
| Set first meeting booked date | Contact books their first meeting and this milestone needs to be tracked | First meeting booked date is stamped on the contact record for reporting and lifecycle tracking | StateChange | medium |
| Inbound lead -> book meeting (cloned) | Inbound lead converts to meeting booking | Process inbound lead conversion to scheduled meeting | StateChange | low |
Key fields: deal_name_ai, languages_ai, channels_ai, team_size_ai, deal_description_ai, locations_ai, sql, first_meeting_booked_date, hs_createdate, last_positive_outbound_status_activity, outbound_status
Dependencies: External reporting sheets, Sales qualification criteria
Domain Summary
This group manages the conversion of leads to opportunities through intake form processing, sales qualification, and meeting milestone tracking. The current implementation has fragmented workflows handling different aspects of the same business process - lead qualification and opportunity creation.
Current Problems
- Multiple workflows handling similar qualification logic without coordination
- Cloned workflow (103171716) indicates poor version control and potential conflicts
- External sheet dependency (42204473) creates integration complexity for simple SQL marking
- Heavy use of UNSUPPORTED_ACTION suggests workarounds for HubSpot limitations
- No clear unified lead scoring or qualification framework
- Meeting booking tracked in multiple places without coordination
Rearchitecture Approach
Consolidate into a unified lead-to-opportunity conversion process with clear qualification stages. Replace fragmented workflows with a coordinated system that handles intake processing, qualification scoring, territory assignment, and opportunity creation as a single business process. Eliminate external sheet dependency and HubSpot workarounds.
Recommended Automations
Lead Qualification and Scoring
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
Purpose: Unified lead qualification system that evaluates leads across multiple signals and assigns qualification scores
Trigger: Contact record changes (form submissions, engagement updates, property changes)
Entry Criteria Formula: N/A
Logic Overview: Evaluate lead based on intake form data, engagement signals, and behavioral indicators. Calculate qualification score and set appropriate lifecycle stage. Route to territory assignment if qualified.
Replaces: AE Assignment - Outbound - Positive Signals, Inbound lead -> book meeting (cloned)
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| lead_qualification_score | Numerical score representing lead quality based on multiple factors | write | N/A | Yes | Replace binary SQL field with scoring system |
| qualification_criteria_met | Multi-select field tracking which qualification criteria this lead has met | write | N/A | Yes | Provides visibility into qualification reasoning |
| sql_date | Date when lead achieved SQL status | write | sql | No | Convert binary sql field to date stamp for better tracking |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Opportunity Creation from Intake Forms
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
Purpose: Creates qualified opportunities from intake form submissions with proper data mapping and assignment
Trigger: Contact completes intake form (form submission or intake fields populated)
Entry Criteria Formula: N/A
Logic Overview: Validate intake form completeness, create opportunity with mapped data, assign to appropriate owner based on service type and territory rules, set appropriate pipeline and stage based on intake type.
Replaces: Augmented AI Intake Form WF
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| intake_form_type | Identifies which intake form was submitted to drive proper opportunity creation | read | N/A | Yes | Needed to handle multiple intake form types consistently |
| project_languages | Languages required for the project | read | languages_ai | No | Map from contact to opportunity |
| service_channels | Delivery channels for the service | read | channels_ai | No | Map from contact to opportunity |
| client_team_size | Size of client team for scoping purposes | read | team_size_ai | No | Map from contact to opportunity |
| project_locations | Geographic locations for service delivery | read | locations_ai | No | Map from contact to opportunity |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Meeting Milestone Tracking
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | medium |
| Reusable | Yes |
Purpose: Tracks key meeting milestones and updates outbound status based on meeting outcomes
Trigger: Meeting is booked, completed, or status changes
Entry Criteria Formula: N/A
Logic Overview: When first meeting is booked, stamp the date. When meetings are completed through outbound efforts, update outbound status and last activity date. Coordinate with lead qualification scoring.
Replaces: Set first meeting booked date, AE Assignment - Outbound - Meeting Booked
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| first_meeting_booked_date | Date when prospect's first meeting was booked | write | first_meeting_booked_date | No | Preserve existing field and logic |
| last_meeting_activity_date | Most recent meeting-related activity date for outbound tracking | write | last_positive_outbound_status_activity | No | Rename for clarity and remove HubSpot workaround |
| outbound_engagement_active | Boolean indicating active outbound engagement based on meeting outcomes | write | outbound_status | No | Convert to proper boolean field |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Sales Qualified Lead Promotion
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | medium |
| Reusable | Yes |
Purpose: Promotes qualified leads to SQL status and triggers necessary downstream processes
Trigger: Lead qualification score reaches SQL threshold or manual promotion
Entry Criteria Formula: N/A
Logic Overview: Set SQL date, update lifecycle stage, trigger territory assignment, and sync to reporting systems. Replace external sheet integration with native Salesforce reporting.
Replaces: Deal > SQL > Sheet
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| sql_promotion_date | Date when lead was promoted to SQL status | write | sql | No | Replace binary field with date for better tracking and reporting |
| sql_promotion_reason | Reason why lead was promoted to SQL (automatic scoring vs manual) | write | N/A | Yes | Provides audit trail for SQL promotions |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Cross-Flow Interaction Model
Interaction handoffs were not provided. Add flowInteractionModel entries so build sequencing and contracts are explicit.
Migration Sequence
- Lead Qualification and Scoring - establishes foundation for qualification logic
- Sales Qualified Lead Promotion - depends on qualification scoring
- Opportunity Creation from Intake Forms - can run parallel to qualification
- Meeting Milestone Tracking - integrates with qualification scoring for complete picture
Architecture Diagram
graph TD
A[Lead Generated] --> B[Lead Qualification and Scoring]
B --> C{Qualification Score >= SQL Threshold?}
C -->|Yes| D[Sales Qualified Lead Promotion]
C -->|No| E[Continue Nurturing]
F[Intake Form Submitted] --> G[Opportunity Creation from Intake Forms]
G --> H[Opportunity Created with Mapped Data]
I[Meeting Booked/Completed] --> J[Meeting Milestone Tracking]
J --> K[Update Meeting Dates and Outbound Status]
D --> L[Territory Assignment]
L --> M[AE Assignment]
B --> N[Update Qualification Criteria]
J --> B
D --> O[Salesforce Reporting]
H --> O
K --> O
style D fill:#e1f5fe
style G fill:#f3e5f5
style J fill:#fff3e0
style O fill:#e8f5e8</code></pre>