UNBOUND 2026: 10 takeaways from our Founder for HubSpot portal owners

Our founder, Lewis has just returned from Boston having attended this years HubSpot's Fall Spotlight; UNBOUND. With more than 200 sessions and a meeting with the CEO (insert Lewis fangirling here!!)

Here are Lewis’s ten takeaways from three days at the event:

What changed at UNBOUND 2026?

HubSpot now describes itself in three layers. A context layer holding the Smart CRM and Context Home, an action layer holding the Hubs and the agents, and a coordination layer holding Agent Hub and governance. Growth Context is HubSpot's name for what the platform knows about your business, your customers and your process. Context Home is the screen where you read that back and correct it.

“The biggest shift I noticed when speaking with HubSpot, Partners and customers was unanimously how Context Home is the keystone for managing agents within HubSpot.”

1. Context Home is your first stop

The main thing about Context Home is it says what HubSpot believes your ICP is. Most portal owners will find the answer thin, because it was assembled from records nobody maintained for this purpose, or is from an initial domain scrape. We’ve ensured we set ours based on data from existing customers, prospects, and the stakeholders we spend the most time speaking with.

HubSpot presented outcome multipliers comparing customers using AI with well-configured context against customers using no AI at all and the data pointed heavily towards a portal with weak definitions will scale its existing problems rather than fix them. The underlying point from all the sessions attended was every agent announced this week reads the context layer before acting.

We recommend you writing your ICP, your positioning and your stage definitions into Context Home before you switch a single agent on. This is an afternoon of work with a longer tail than anything else in the release.

2. Contract-based revenue reporting has major changes

We’ve seen great adoption with Revenue Hub, and it was welcoming hearing contract management, price books and quote rules are available in the portal, and reports MRR, TCV, NRR and GRR from contracts rather than from deal amounts. A Revenue Agent chases collections.

For finance teams reconciling HubSpot against a billing system every month, this is the most useful thing in the release. The condition is willingness to move billing detail into HubSpot properly. We recommend mapping your contract terms to objects and properties first, then build the reports.

3. Pipeline hygiene is becoming the job of AI (finally)

This update is something sales reps have dreamt of since CRMs first hit the market. I know I’d have loved it. Deal Progression suggests next steps and property updates from logged activity (calls, meetings, emails). Deal Plans share milestone plans with buyers.

Assuming every user has connected their inbox and calendar, they’ll be good to go. Reps who log by exception will get suggestions built on a fraction of what happened. We recommend fixing connection coverage first, then turn the beta on and compare the suggested updates against what your best rep does by hand.

Forecast quality is downstream of this. We set out the benchmark in what good forecast accuracy looks like.

4. Merging has levelled up in Data Hub

We saw Data Hub gaining primary record merge rules, a merge preview, similarity scores and higher duplicate limits, alongside a data model health check and new sources including Snowflake, BigQuery, S3 and Google Sheets. All requested by various clients of ours.

Primary record rules decide which values survive a merge, so review them against your own source-of-truth decisions before switching them on. Run the preview across a sample of a few hundred records and check what happens to lifecycle stage, owner and original source. Deduplication at volume is a one-way door.

5. Buyer intent is reaching further than ever

The announcement of twenty new intent signals was a welcome one, with Bombora Company Surge topics, UserGems job changes, a churn risk signal and custom signals you describe in plain language.

Most portals we audit have not configured the intent signals they already pay for. Start there. Pick two signals, route them to a named owner with a defined action, and measure whether anything happens as an experimental campaign. Widening the signal set before you have an owner produces a longer list nobody ends up working.

6. Prospecting Agent setup

Prospecting Agent now sources contacts from data providers on demand, writes in a brand voice set per play, and improves its emails from rep edits. This will save everyone a bunch of manual and automated prospecting time.

Sourcing changes the risk, however. An agent choosing its own contacts will email your existing customers, your churned accounts and your competitors unless your exclusion lists and ICP definitions are current. Audit suppression lists, confirm your customer and partner records are correctly typed, and approve the brand voice before the first play runs.

7. CRM redesign

We’ve now all seen index pages and record redesigns, with cross-object filtering, column filtering, custom task stages, personalised navigation and faster custom reports.

The reporting speed is welcome. The redesigned views are the risk we’ve identified for the average HubSpot user. Every rep opens the same screen every morning, and a changed screen with no warning produces a week of workarounds and a dip in logging discipline. Book thirty minutes of retraining and rebuild your saved views before the change reaches your team.

8. Renewals can drop the spreadsheets

Customer Success gained GRR, NRR, renewal pipeline and book-of-business reporting, plus product usage tracking, all in Service Hub.

If your renewals live in a spreadsheet as you don’t ‘trust the data’, this is the quarter to model them as a pipeline with stages, owners and dated close records. Renewal forecasting built on the same objects as new business forecasting gives you one revenue number instead of two that disagree.

9. How do credits change your AI budget?

We’re all familiar with credits as the unit of AI spend, and every agent consumes them. Breeze Assistant itself consumes none, though the agents it calls do.

Budget per pilot rather than per portal. Run one agent against one process for two weeks, record consumption next to the outcome it produced, and decide from there. Teams who switch on six agents at once get a finance conversation and reduce trust with the CFO. We’re ensuring our clients don’t end up in this situation.

10. What does the open platform release mean for your integrations?

HubSpot moved to date-based API versioning starting at 2026.09, updated its MCP server, added third-party MCP components, an Agent CLI, HubSQL and a Lovable connector. The cheers from these announcements, and the excited conversations we had with developers means this list probably isn’t in a total priority order.

Date-based versioning is the item to action. Record which version each of your integrations targets, put the number in your integration documentation, and set a review date before HubSpot's next release. Custom integrations built by a contractor two years ago are where this will likely creep up. The build-order argument for lean teams is in RevOps automation in 2026.

What should you do first?

We think sequence beats enthusiasm here. You should configure Context Home, connect every user’s inbox and calendar, review your merge rules, then pilot one agent with a credit budget attached.

Our RevOps Audit gives you that sequence against your own portal, with a prioritised roadmap of what to build this quarter and what to leave until your data supports it. Get in touch below and we will start with your Context Home score.

FAQs