## Executive SummaryThe meeting focused on the strategic initiative to automate the commission and revenue allocation process, moving away from manual spreadsheets to an integrated HubSpot system. Key discussions revolved around current challenges with data integrity (e.g., HubSpot close date manual overrides), the existing half-month revenue recognition logic, and complexities in multi-invoice deal management. A critical decision was made to transition to a more accurate per-day allocation methodology for revenue and commission, necessitating a one-time "true-up" adjustment. The team outlined a future system architecture utilizing new 'Contract,' 'Earnings,' and 'Payout' objects in HubSpot, emphasizing flexibility to allow manual overrides while maintaining automation benefits. A project timeline was set for scenario collection (1 week) and development/testing (30 days starting mid-August).## Key Architectural Frameworks & Core Principles* **Data Model Enhancement:** * Introduction of a new `Contract` object in HubSpot to define deal terms, automate date-related logic (e.g., start/end dates, close date validation), and bridge the gap between deals, invoices, and subscriptions. * Creation of dedicated `Earnings` and `Payout` objects within HubSpot to track the full lifecycle of a deal's commission, replacing manual spreadsheet calculations.* **Recognition Methodology Transition:** * Shift from current "half-month revenue recognition logic" to a "per-day allocation" for both revenue and commission. This aims for higher accuracy and alignment with GAAP standards (00:27:39, 00:33:05). * Requires a "one-time true-up process" to adjust discrepancies during the transition (00:40:06).* **Commission Payout Logic:** * Commissions are recognized (earned) upon service performance, not booking date (00:19:26, 00:20:34). * Payouts are authorized *only* after corresponding invoice payments are confirmed (00:11:06, 00:18:03). * End-of-month dates serve as primary checkpoints for payout eligibility (00:18:03, 00:25:07).* **HubSpot Automation Strategy:** * Focus on managing "simple change orders" involving 'who,' 'what,' 'when,' and 'amount' variables (01:02:18). * Design for flexibility, allowing "manual overrides to HubSpot automated entries" (01:00:52, 01:03:09). * System architecture aims to "emulate spreadsheet control while maintaining automation benefits" (01:02:48, 01:03:09). * Future dashboards will support aggregated views of deals and invoices.## Flight Plan Action Items* **[Jessica Colley] Investigate Close Date:** Verify if the HubSpot deal close date field can be automated or locked to prevent manual changes. Report findings regarding this automation possibility.* **[The group] Review Contract Integration:** Evaluate how the new contract object can integrate with existing revenue and commission reporting systems. Prepare to review this implementation strategy during the follow-up meeting on Wednesday or Thursday.* **[Jessica Colley] Document Scenarios:** Record and document special situations or scenarios requiring manual adjustments to CRM data.* **[Jessica Colley] Send Scenarios:** Send the recorded audio or transcribed text files containing special scenarios to Kevin Dockman.## Key Structural Sections of the Discussion### The team reviewed commission spreadsheet logic and finalized plans for migrating to an automated daily allocation model.* The existing system relies on a "deals master tab" consolidating HubSpot data (booking date, opportunity ID, customer info) and an "XREF" tab for cross-references, along with an "RO defaults" tab for commission rates (00:09:38).* The "deals commission" tab pivots this data to calculate commission amounts for each resource/coach (00:57:13, 00:58:36).* The overarching goal is to replace this manual spreadsheet logic with an automated system in HubSpot.### Commission and revenue reporting framework* **Recognition Trigger:** Commission and revenue are recognized upon service performance, rather than the booking date (00:19:26). A deal closed in February but starting in September means earnings begin in September (00:20:34).* **Current Recognition Logic:** The current process for long-term deals utilizes a "half-month revenue recognition logic" for the first and last periods of service to simplify calculations, assuming rarely anything starts on the 1st of the month (00:26:14).* **Payout Condition:** Commission payouts are only authorized after corresponding invoice payments are confirmed (00:11:06). There's typically a one-month delay (e.g., June accrual, July 31st payout) (00:11:06).* **Checkpoint Dates:** End-of-month dates serve as primary checkpoints for processing payouts (00:18:03, 00:25:07).### HubSpot process automation and data integrity* **Close Date Inconsistency:** The HubSpot deal close date currently allows manual overrides, leading to data inconsistency and impacting tracking (00:13:55). Jessica expressed a desire for a more rigid, automated system (00:13:55).* **Proposed Solution - Contract Object:** Kevin proposed integrating a new `Contract` object in HubSpot. This object could capture key details like signatures and dates, providing a stable foundation to influence the close date and automate reporting (00:14:54). This object would act as "glue" between deals, invoices, and subscriptions.### Methodology transition for calculation* **Transition to Per-Day Allocation:** There's a consensus to transition to a "per-day allocation" for revenue and commission recognition. This approach, though more complex, improves alignment with Generally Accepted Accounting Principles (GAAP) (00:27:39, 00:33:05).* **True-Up Process:** Anticipating a "1-time true-up process" will be necessary to accommodate the methodology transition and correct any discrepancies in recognized revenue and commission expenses (00:40:06).### Complex deal and invoice management* **Multi-Invoice Deals:** Multi-invoice deals are currently managed by creating multiple line items on the spreadsheet (e.g., two $30,000 line items for a $60,000 deal, with only invoice information differing) (00:44:27).* **Impact on Payout Timing:** This current approach can potentially delay coach payout timing if commissions are tied to specific invoice payments, as the second invoice might not be paid until later, even if the service is being earned (00:45:45).* **HubSpot Dashboard Capability:** The future HubSpot architecture is envisioned to support "aggregated views of deals and invoices," and eventually "earnings and payouts," through dedicated objects and dashboards (00:50:11, 00:51:10).### HubSpot automation strategy* **Focus on Change Orders:** The automation strategy will focus on simple change orders involving 'who,' 'what,' 'when,' and 'amount' variables, allowing for targeted adjustments (01:02:18).* **Flexibility and Overrides:** The design prioritizes flexibility, allowing manual overrides to HubSpot automated entries (e.g., using "hidden" columns or property fields for manual adjustments that overwrite formulas) (01:00:52).* **System Architecture Goal:** The system aims to "emulate spreadsheet control while maintaining automation benefits," ensuring users have the same level of control as they would in a spreadsheet (01:02:48, 01:03:09).### Project planning and implementation timeline* **Scenario Collection:** Deadline for scenario collection is set for "1 week from current date" (01:03:58). Jessica is requested to document special situations requiring manual adjustments.* **Development & Testing:** A "30-day window" for development and testing is targeted, starting "mid-August" (01:04:08).* **Fallback Options:** Manual fallback options are confirmed for any automation features that fail during testing, ensuring system functionality (01:04:14).