🎙️ Session: 26 12:50 EDT - Notes by Gemini

Executive Summary

The Daily Huddle on June 26, 2026, primarily focused on critical updates for upcoming program launches within HubSpot and optimizing data visualization and reporting. Key discussions centered on aligning email workflows for “Foundations June” by locking in Zoom links and enforcing brand standards for email templates. Significant effort was directed towards resolving sales dashboard visibility issues through user-specific filtering and enhancing data interaction by transitioning reports from tables to charts. Additionally, a crucial data association fix was identified for Accounts Receivable reporting, requiring the syncing of deal owner information to invoice properties to enable accurate aging summaries.

Key Architectural Frameworks & Core Principles

• User-Specific Data Views: Implementing filtering (e.g., “is any of me” or “is any of [User]”) on dashboards to ensure users only see their relevant data, enhancing privacy and personalization.
• Data Association for Reporting Integrity: Emphasizing the necessity of direct data links (e.g., syncing deal owner to invoice property) to enable comprehensive and accurate filtering in complex financial reports like Accounts Receivable aging summaries.
• Prioritizing Visual Data Interaction: Advocating for the use of interactive charts over static tables in dashboards to improve data comprehension and allow users to drill down into specific data points.
• Centralized Brand Standard Enforcement: Maintaining consistency across all external communications by adhering to a single branded template for email headers, footers, backgrounds, and text styles.
• Workflow-Driven Automation: Leveraging HubSpot’s workflow capabilities for automated email sequences and property updates, triggered by specific system events (e.g., WordPress sending a portal ID back to HubSpot).
• System Optimization & Clean-up: Proactively decommissioning outdated or unnecessary dashboards and reports to maintain a streamlined and efficient system environment.
• Dynamic vs. Static Property Management: Differentiating between dynamically pulled data (requiring robust property configuration) and temporarily locked-in static values for program-specific needs, highlighting the importance of correct property setup for scalability.

Flight Plan

Brenn Almario

• Update HubSpot Record: Change the “Foundations June” record in HubSpot to 9:00 a.m. Eastern time.
• Style Email Templates: Copy the header and footer from the branded template into all June workflow emails. Ensure the background and text styles match the branded template exactly.
• Build Email Schedule: Complete the remaining email schedule for the June workflow for all 4 sessions (Welcome 24 hours prior, Session 1 upon portal ID trigger, subsequent session emails 2 hours prior).
• Notify Status: Inform Kevin once all emails are updated and ready for review.
• Update Report Filter: Change the time filter on the Accounts Receivable aging summary to “this year so far.”

Kevin Dockman

• Associate Contacts: Link contacts from the “foundations zoom tune segment list” with the learning path record.
• Sync Deal Owner: Create a property on invoices that mirrors the associated deal owner to enable filtering in reports.
• Fix Dashboard: Resolve report visualization issues and reorganize properties on the coaching dashboard.
• Review Workflow: Send the completed June workflow with drafted emails to Emily for testing.
• Notify Jacqueline: Communicate with Jacqueline once the sales dashboard is finalized.

Key Structural Sections of the Discussion

• CLG Foundations June Hubspot Setup: Kevin Dockman initiated a discussion regarding the upcoming CLG launch, focusing on the HubSpot learning path record titled “Foundations June.” Kevin directed Brenn Almario to edit a property to 9:00 a.m. Eastern time, which triggers the email workflow (00:02:05). Kevin noted that Brenn had already built the necessary notifications and confirmed that these emails need to align with the branded template, including the header, footer, background, and specific styles (00:04:14). Kevin requested that Brenn verify these design elements match the template exactly (00:07:09).
• Foundations June Zoom Link and Contact Association: Kevin addressed the requirement for the Zoom link within the emails, stating that it should be a locked-in value rather than dynamically pulled from a coach’s profile, as the previous dynamic setup was incorrect for this program (00:08:26). Kevin instructed Brenn to ensure that contacts from the “foundations zoom tune segment list” are associated with the learning path record. Kevin noted that this association task is straightforward and could be handled by either of them (00:09:30).
• Email Workflow Schedule and Triggering: Kevin outlined the workflow schedule for the four foundation sessions in June. A “Welcome” email is to be sent 24 hours prior to Monday at 9:00 a.m (00:09:30). Once the contact is connected to the portal, WordPress sends a property back to HubSpot containing the portal ID, which then triggers the Week 1 session email (00:12:37). Kevin specified that a subsequent session email should be sent 2 hours prior to the session at 7:00 a.m (00:13:38).
• Workflow Handover to Emily: Kevin expressed the need to provide Emily with the completed workflow and drafted emails by the end of the day so that Emily can review the design and content. Kevin mentioned that Emily would send herself test emails as a contact within the segment (00:13:38). Kevin offered to manage the connections within the workflow while Brenn finishes the email updates to ensure everything is prepared for review (00:14:29).
• Coach Sales Dashboard Implementation: Brenn discussed the ongoing development of a sales dashboard for Joyce, noting challenges with reports becoming public when added to the dashboard. Kevin clarified that the issue with visibility can be resolved by using HubSpot’s filtering capabilities rather than creating separate dashboards for different users. Kevin instructed Brenn to set the filters to “is any of Joyce” for the time being, with the intention of switching the filter to “is any of me” later, so that the dashboard displays data specific to the logged-in user (00:15:12) (00:18:00). Additionally, all reports should be set to a “this year so far” time filter (00:19:58).
• Accounts Receivable Aging Summary and Data Challenges: Kevin reviewed the Accounts Receivable aging summary created by Brenn, confirming the time filter should be set to “this year so far” (00:21:24). A technical hurdle was identified regarding the association of the coach owner, as the data source does not inherently link to the deal. Kevin explained that to resolve this, the owner of the deal must be copied or synced to the invoice as a property, which will then allow the owner field to be used as a filter (00:22:47).
• Dashboard Visualization Improvements: Regarding the sales dashboard, Kevin and Brenn discussed Jacqueline’s request to clean up the existing dashboard by deleting unnecessary reports (00:24:06). Kevin advised against using tables for data visualization, noting that tables are less effective than charts, which allow users to click into specific data points, such as invoices overdue by 90 days. Kevin recommended that numerical data blocks occupy two cells and that charts should be sized at least 2x3 (00:26:04). Kevin committed to reviewing the tasks and resolving these visualization issues (00:27:10).
• CLG Process Complexity and Professional Context: Kevin remarked on the complexity of the CLG client, noting that it is one of their favorite clients due to the challenging work and the goal of fully utilizing HubSpot. Kevin also shared context regarding their work with “The Dog Wizard,” which involves pushing Google Ads data into BigQuery to filter by location, demonstrating the type of technical solutions they are pursuing. Kevin also referenced past experiences at Long Term Care as part of their professional background (00:28:02).