HubSpot Lead Workflow Review — 2026-04-05
Overview
Working session with Miriam Framson (Citrus America) to finalize HubSpot lead progression logic, confirm BANT-triggered deal automation, plan contact cleanup for departed rep Jay, and explore a simplified data-entry UI for the sales team. Ben San Fratello joined as incoming account manager in training.
Attendees:
- Miriam Framson — Citrus America (external)
- Chris Østergaard — Asymmetric
- Mark Hope — Asymmetric
- Ben San Fratello — Asymmetric (onboarding to account)
- Melissa Cusumano — Asymmetric
- Paul Buniel — Asymmetric (absent, out sick)
Key Decisions
1. Lead Progression Logic Confirmed
The sequential lifecycle workflow is locked in:
| Stage | Trigger Criteria |
|---|---|
| Prospect → Lead | First name, last name, email, state, category |
| Lead → MQL | Basic lead fields + "Are they juicing?" answered |
| MQL → SQL | MQL fields + juicing volume, equipment details, fruit preferences, application type, container type, operation style, location flexibility |
| SQL → Opportunity | BANT criteria met (Budget, Authority, Need, Timing) |
Key flexibility: Reps may skip MQL and advance directly from Lead to SQL if all required data is gathered in a single call. The "are they juicing?" field must still be answered, but the system does not force a sequential wait.
"Unknown" as a valid value: All qualifying fields accept "Unknown" as a valid entry, allowing workflows to trigger even when a rep cannot obtain a specific answer. The workflow fires on any non-null value.
2. Opportunity Auto-Creates a Deal
When a contact's lifecycle stage is set to Opportunity, a workflow will automatically create an associated deal. Naming convention: [Company Name] - New Deal. Reps can rename the deal afterward (e.g., to reflect machine type or product line).
3. "Departed" Lifecycle Stage Added
A new Departed stage was added to the lifecycle options. This preserves a contact's full activity history while flagging them as no longer active at their company — avoiding data loss when key contacts leave an account.
4. "Unqualified" Stage Clarified
The existing Unqualified stage will be used for leads who are no longer interested (i.e., disqualified). Internal documentation will be updated to clarify this usage so the team doesn't conflate it with "prospect" or "not ready."
Action Items
| Owner | Task | Notes |
|---|---|---|
| Chris | Activate lead progression workflows (Prospect→Lead→MQL→SQL) | Notify Miriam when live |
| Chris | Build Opportunity workflow to auto-create deal on lifecycle stage change | Naming: [Company Name] - New Deal |
| Chris | Research simplified data-entry UI (pop-up questionnaire / form) | Goal: reduce friction for sales team adoption |
| Chris | Investigate automation for Closed Won / Closed Lost deal stages | Referenced in Miriam's pre-meeting email |
| Miriam | Test full lead-to-opportunity flow with sales team | Confirm workflow logic meets real-world needs |
| Miriam | Lead contact cleanup project using export/import method | Priority: reassign all contacts owned by departed rep Jay |
Contact Cleanup Plan
Miriam will lead a full contact list cleanup once workflows go live. The process:
- Export all contacts from HubSpot as a spreadsheet (Mark has done this before for other clients)
- Hide or remove irrelevant columns; make mass edits directly in the spreadsheet
- Re-import the spreadsheet — HubSpot will apply all changes
Critical constraint: Any field that is a picklist must use values that exactly match HubSpot's configured options. Free-text entries in picklist columns will fail on import.
Cleanup priorities:
- Mark confirmed customers as Customer
- Update all active sales conversations to the correct stage (SQL or Opportunity)
- Reassign all contacts currently owned by Jay to active reps
- Push everything else back to Lead or MQL if qualifying data is missing
Simplified Data-Entry UI — Exploration
Chris raised the idea of building a simplified form or pop-up questionnaire (rather than requiring reps to navigate the full contact profile) to make field entry more intuitive. Miriam was receptive — reducing friction is a priority given the cultural shift required to get the sales team consistently logging data in HubSpot.
Chris will research what's feasible and report back. Goal: consolidate all required qualifying fields into one intuitive interface.
Contact Ownership & Departed Contacts
Discussion surfaced around what happens when a key contact leaves a client company:
- Lead data lives on the contact record, not the company record
- If a contact departs, their lead stage and activity history can be transferred to a replacement contact, or the original contact can be left in place and tagged as Departed
- In practice, Miriam noted that when a key decision-maker leaves, the sales process often resets anyway — so a full transfer is not always necessary
- Mark noted that a company-level field mirroring the key contact's lead stage is possible if visibility at the account level is needed
Relevant Transcript Excerpts
Chris: "The flow will trigger as long as there is a value attached to that parameter. And the value can be unknown."
Miriam: "If there's some kind of a pop-up with a questionnaire to fill in these things and it populates into the contact fields — if there's something that you can think of that would make it a simpler process and reduce any 'it's too complicated' excuses, then let's do it."
Mark: "As soon as you change the lifecycle stage to opportunity, we want to kick off a workflow that creates a new deal, and the naming convention would be something like the company name and then 'new deal,' and then someday when they go into the deal, they could edit the deal name."
Mark: "We should add an option under lifecycle stage to say 'departed.' You could leave that person in that company, but just tag them as having departed. So all of their activity and everything that ever went on with them would be there, but you know that they're not active anymore."
Related
- [1]
- [2]
- [3]