Hubsessed Office Hours - Unified Revenue View - Nov 12, 2026
- Chris CarolanHost
- Ryan GinsbergHost
Thursday, November 12, 2026
Sign in to watch the full replay and read the transcript.
Chris Carolan plays today's Will It Breeze: Casey Hawkins asks Breeze to show the work behind the number with Shopify, and says finance asked. With Ryan Ginsberg: agree with finance before installing anything, finance owns the view, and the view has to be seen.
Clips from this session
8 short cuts from this conversation.
Key takeaways
When a request arrives without the context behind it, say so. Telling Breeze the admin did not know, and that finance asked for the number, brought clarifying questions instead of a guessed answer.
Agree with finance on what to measure and how to prove it before installing an integration. An install button in the chat is not the first step.
Most integrations do not work the way anyone thinks. Decide what an integration between Shopify and HubSpot should mean before connecting it.
A few starting numbers, such as net sales, refunds and payment disputes, cash deposited and gross profit, let an admin with no finance background open the conversation with finance.
Once a view touches accounting, it belongs to finance. Sales does not own a unified revenue view.
Showing the work for a number means its definition and calculation, the source system and transaction references, the date range, time zone and currency, exclusions and adjustments, and who resolves differences.
Let each system be the source for what it holds: commerce activity from Shopify, cash movement from the payment provider and bank, finance-approved figures from the accounting system, with HubSpot supporting customer reporting.
Every team needs a different version of the unified view, and a view people can see makes a shift in priorities visible.
Intent signals show real activity from real people and can become contact records quickly, which makes paying for third-party data hard to justify.
Keeping commands in GitHub means every commit can be traced into a timeline of how they evolved.
Questions answered
- 00:00The best Will It Breeze so far, and why AI is mandatory on the way to a unified revenue viewTopic
- 01:13Running the morning show's command: Claude in Chrome and five background agentsTopic
- 11:57Why GitHub is the base: commit history as the story of your commandsTopic
- 13:36Repos for developers, an application and MCP for the front linesTopic
- 14:18Operating systems, and platforms as harnessesTopic
- 15:30Will It Breeze: show the work behind the number across every integration, with ShopifyTopic
- 22:17How do you quickly come to the conclusion that this is the best Will It Breeze we've ever done?Question
- 28:43The first job is to agree with finance on what to measure and how to prove itTopic
- 30:03What does an integration with Shopify and HubSpot even mean?Topic
- 32:58Four numbers to start a conversation with financeTopic
- 34:54What are your thoughts on RevOps reporting to finance?Question
- 35:41The three org model, and front office and back office seatsTopic
- 37:29What showing the work should mean for each numberTopic
- 38:00Is finance part of the conversation when a company buys HubSpot, or just approving budget?Question
- 39:01Who owns product, price, place and position, and why financial acumen mattersTopic
- 41:41Shopify, the bank and the accounting system, each the source for its own figuresTopic
- 43:14First, research other portals that have connected ShopifyTopic
- 43:42Breeze research, and showing up differently to financeTopic
- 46:18Workshops with Breeze in the room, and whose unified view?Topic
- 47:42Unified Revenue View is visualTopic
- 50:37Intent signals instead of paying for third-party dataTopic
- 52:38From a key account plan to HubSpot's agents and invoice historyTopic
