🎙️ Session: 17 10:09 CDT - Notes by Gemini

Here’s an analysis of the meeting transcript, structured as requested:

Executive Summary

The Daily Huddle on June 17, 2026, primarily focused on establishing a robust architecture for automated email workflows within HubSpot for the “Conscious Leadership Foundations” learning paths. The core challenge addressed was implementing time-based email delivery and content access that accurately accounts for pauses and resumptions of a learning path (i.e., “on hold” status).

The team finalized a “dual date model” architecture, where an immutable original start date is maintained for reporting, and a new LP adjusted start date custom property dynamically manages scheduling offsets based on time spent on hold. Key decisions included defining workflow logic for pausing and reactivating sequences, configuring custom properties (e.g., coach Zoom link), and establishing a comprehensive testing protocol. Initial technical builds were initiated, leveraging automation scripts for property creation and integrating new architectural changes into project documentation.

Key Architectural Frameworks & Core Principles

• Dual Date Model for Scheduling: This principle dictates the use of two distinct date properties for learning paths:
  • Start Date: An immutable property preserving the original commencement date for historical and reporting purposes.
  • Adjusted Start Date (originally LP adjusted start date): A dynamic custom property that is programmatically shifted forward by the duration a learning path spends in an “on hold” status. All time-based email triggers and content access are calculated relative to this adjusted start date.
• Pipeline Stage-Driven Workflow Logic: Workflow behavior is directly controlled by the learning path’s pipeline stage (e.g., “on hold,” “in progress”). Transitions between these stages trigger specific calculations and workflow re-enrollment logic, rather than attempting to pause running sequences.
• Dynamic Unenrollment/Re-enrollment (Modular Workflow Design): When a contact’s learning path enters an “on hold” stage, they are automatically unenrolled from active nurture workflows. Upon transitioning back to “in progress,” a master router workflow re-enrolls them into the appropriate weekly workflow based on their current milestone, ensuring relevant content delivery.
• Leveraging Native HubSpot Properties: The solution integrates HubSpot’s default properties such as “date entered on hold” and “latest time on hold” for calculating hold durations and applying offsets.
• Dynamic Contact Ownership: The system ensures that automated emails are consistently sent from the appropriate contact owner (coach). This requires a underlying principle that contact ownership dynamically updates based on key object ownership (e.g., deal owner, learning path owner).
• Automated Property Creation & Management: Utilizing Python scripts and the HubSpot API to programmatically create and configure custom properties, streamlining the technical build process.

Flight Plan Action Items

• [Brenn Almario] Draft Workflow: Create an automated workflow in HubSpot for the Conscious Leadership Foundations learning path. Include email triggers and logic to handle on-hold status for delayed schedules.
• [Kevin Dockman] Share Briefing: Provide the summary brief of project objectives and challenges in the daily huddle. Ensure the team can access the document for implementation.
• [Brenn Almario] Test Workflow: Validate the HubSpot logic in a development environment. Verify accurate scheduling and email delivery for learning path participants.
• [Ali] Track Sessions: Build fields for the name and date of the next session in the portal.
• [Brenn] Build Zoom Property: Create a custom user property to store the Zoom link.
• [Brenn] Rename Start Date: Update the LP adjusted start date property name to adjusted start date.
• [Kevin Dockman] Inquire Session Dates: Ask the client for the next session dates to verify scheduling information.
• [Kevin Dockman] Review Subscription: Evaluate the Mermaid subscription status after the 6-day trial period.
• [Kevin Dockman] Write Documentation: Prepare project documentation for the ongoing development.
• [Brenn Almario] Execute Build: Perform the technical build process for the project components.
• [Brenn Almario] Pull Specifications: Retrieve the final project specification from the repository.
• [Kevin Dockman] Update Vault: Upload the necessary files to the vault system.
• [Brenn Almario] Create Checklist: Add a list of all team names to the project documentation.

Key Structural Sections of the Discussion

1. Problem Definition: Automated Email Workflow for Learning Paths

• Automated Workflow Requirement: Kevin Dockman requested the creation of an automated email workflow for the Conscious Leadership Foundations learning path. This workflow needs to draft three time-based emails linked to the learning path start date to provide automated reminders (00:05:22).
• Core Challenge - Time-Based Delivery with Pauses: The primary difficulty identified by Kevin Dockman is managing time-based delivery when a learning path schedule is paused or delayed. This necessitates pushing back automated email reminders and rescheduling access to specific portal content modules (00:06:42).
• Start Date Property: Users will manually set the learning path start date using a time and date picker property within the CRM, signifying when project work begins (00:06:42).
• Email Content & Organization: The email workflow must include a welcome email and reminders for week one (day before and hour before), followed by subsequent weekly reminders. Emails should be simple (logo, content, footer). A new folder, “LP notifications CLF,” was established for categorizing these learning path notifications (00:10:17, 00:12:19).
• Dynamic Contact Ownership: Emails are to be sent by the coach (defined as the contact owner). Kevin Dockman emphasized that the contact owner property must dynamically update based on key objects (deal owner, learning path owner) to ensure emails consistently originate from the appropriate coach (00:14:31).

2. Proposed Solution: Managing “On Hold” Status Logic

• Workflow Suspension Logic: Kevin Dockman proposed a logic where emails are prevented from firing if the learning path project is in an “on hold” pipeline stage. The workflow requires a branching mechanism to check for this suspended status (00:17:22, 00:18:42).
• Reactivation and Looping Logic: Brenn Almario and Kevin Dockman discussed the need for the workflow to handle reactivated accounts. A looping, cascading sequence was suggested to check for suspended status and loop the contact back to the correct step once the status changes to “active” (00:19:55).
• Leveraging Pipeline Stage Properties: Kevin Dockman reviewed the learning path pipeline board, noting that existing properties associated with the “on hold” stage (e.g., “date entered on hold,” “latest time on hold”) could be used for necessary timeline adjustments (00:20:58, 00:56:56).
• Timeline Adjustment on Reactivation: The system must calculate the duration a learning path was “on hold” and add this to the original start date to establish a new timeline when it transitions back to “in progress” (00:22:30).

3. AI-Assisted Blueprinting & Architectural Decisions

• Gemini-Generated Briefing: Kevin Dockman utilized Gemini to generate a summary brief outlining the project objectives, challenges, and requirements, including sequential reminders and managing “on hold” status, for team alignment (00:25:34, 00:27:13).
• Refined Workflow Strategy: Kevin Dockman proposed splitting emails into weekly milestones per workflow to better manage user state changes. When a contact is “on hold,” they are unenrolled from active nurture workflows, and upon moving to “in progress,” a master router workflow re-enrolls them into the appropriate week’s workflow (00:56:56).
• Dual Date Model Adoption: Brenn Almario suggested using a custom property, LP adjusted start date, to handle restarts while keeping the original start date immutable to prevent reporting issues. Kevin Dockman endorsed this as an effective engineering solution. The protocol involves querying the latest time on hold, converting the duration, and applying the offset to the adjusted start date, with all dynamic emails recalculating delays relative to this adjusted date (01:24:27, 01:27:51).
• Testing Protocol Defined: Kevin Dockman established a testing protocol for a sandbox user: setting a future start date, verifying pipeline stage updates, confirming start date copies to adjusted start date, simulating a hold period to confirm offset calculation, and verifying email merge tokens (01:17:04, 01:40:25).

4. Property Configuration & Documentation

• Custom Property Creation: Identified the need for a custom user property for “Zoom link” and decided to rename the LP adjusted start date property to adjusted start date for consistency (01:40:25, 01:44:48).
• Strategic Property Storage: Kevin and Brenn determined that property fields, particularly for participants taking multiple courses, should be stored directly in the learning path object rather than as contact properties, to ensure seamless calendar synchronization (01:55:50, 01:57:37).
• Automated Property Build & Sync: Kevin demonstrated using a Python script to automatically create a “coach Zoom link” property and configured it to sync with the contact owner associated with the learning path (01:59:13, 02:08:20).
• Documentation and Diagramming: Kevin Dockman updated the project’s master document using Markdown and initiated a subscription for the Mermaid diagramming tool to embed flowcharts for visual documentation (01:30:32, 01:33:01). Finalization involved pushing updates to the repository and ensuring email templates reflected the correct Zoom link reference (02:19:23).