HubSpot's spring announcements raised useful questions about agent costs, data preparation and custom apps. I would evaluate them against a task your team already needs to complete.
This article was first published in April and reviewed on 22 October 2026. The sections below distinguish the spring announcements from current documentation. The August developer deadline has passed; the classic CRM card migration still needs attention.
Breeze pricing: distinguish the announcement from your account cost
In April, HubSpot announced outcome-based pricing for Customer Agent and Prospecting Agent, paid through HubSpot Credits. The announcement tied charges to resolved conversations and leads recommended for outreach.
That billing event does not establish the quality of every answer or recommendation. I would include corrections, repeat contacts and human review when evaluating the result.
For a new pilot, check current access, credit rates, included allowance and overage settings in your account. HubSpot's credit guide explains the usage model. The Breeze guide covers practical checks for the individual use cases.
Agents in workflows: define what happens after the output
The current Run Agent documentation describes choosing an agent already added to the account, providing inputs and using its output in later workflow actions. It requires an eligible Professional or Enterprise subscription and HubSpot Credits. Do not assume every Breeze product can be invoked through this action.
Start with narrow enrollment criteria and review the result before allowing it to update important fields or trigger customer communication. Test missing data, repeat enrollment and failure handling. Assign someone to investigate unexpected output and check the current execution limits before expanding.
Data Hub: focus on the dataset you need
Data Hub replaced Operations Hub in September 2025. Its launch predates Spring 2026.
Data Studio combines data from HubSpot and external sources in a spreadsheet-style interface. It is available with Data Hub Professional and Enterprise; activating data outside the studio can consume credits.
I would begin with one question your current reports cannot answer reliably. Define the join keys, source refresh and calculation, then compare the dataset with a known sample. Check supported connectors and activation costs for that use case. A visual interface still needs clear rules for what each row and value means.
Quoting: test the answers and the human handover
Closing Agent can answer buyer questions on a quote using the knowledge supplied to it. The current setup guide labels it beta and lists Revenue Hub Professional or Enterprise, with seat requirements. Older material refers to Commerce Hub.
Test questions about scope, pricing and terms against approved information. Include questions that need the quote owner or another team, then verify the configured handover. For any AI-drafted quote content, review the line items, totals and promises before sending it to a buyer.
I would evaluate this on a controlled set of quotes before making it part of the normal sales process.
Custom apps: keep the interface as small as the task
The spring developer release expanded App Homes into multi-page App Pages and described sharing code across UI extensions with npm workspaces. A full app page can suit a task that spans records; a focused app card may be enough for information needed on one record.
Platform 2026.03 also restored HubSpot-hosted serverless functions. Hosted app functions require Enterprise access or a developer test account; public endpoints require Content Hub Enterprise and are not available in developer test accounts. Check the current migration path and limits for your app before choosing its hosting approach.
My renewal-status card is an example of keeping a record interface focused on one decision.
Developer dates: August has passed, and card guidance differs
The spring developer release set 1 August 2026 as the end of support for Projects 2025.1, with builds on that version failing. That date is now in the past. If a project still uses 2025.1, have its owner confirm the migration status, build and deployment path before the next change.
For classic CRM cards, the spring release lists 31 October 2026. The current migration guide instead says cards are removed from customer views on 2 November, with migration tooling available until 1 December. The tooling window does not mean old cards remain visible through November.
I would plan to finish before 31 October and confirm the guidance with the app owner. The classic CRM card migration guide compares the sources and covers testing and view replacement. Sidebar placement alone does not identify a legacy card.
What I would prioritize
- Check maintenance first. Confirm who owns custom apps, their supported version and any legacy-card replacement.
- Choose one pilot. Test an agent or dataset against a defined task, with an owner, review criteria and usage limits.
- Expand after review. Use the observed corrections, handovers and costs to decide what is worth keeping.
Questions about how these changes fit your setup? You're welcome to compare notes.