A useful UNBOUND plan starts with the decisions your team needs to make. Prepare the questions, current portal details and evaluation criteria that will help you decide which changes deserve your time.
TLDR: Before UNBOUND, document your portal baseline, name the business questions you want answered and agree on a release-review process. Separate confirmed availability from an announcement. Prepare a test plan before anyone enables a new feature.
As checked on September 7, 2026, HubSpot's official UNBOUND site lists the event for September 16-18, 2026, in Boston. This preparation guide does not predict announcements or describe unreleased features. Recheck the official schedule before making attendance plans. Official UNBOUND 2026 site
Start with a one-page preparation sheet that your team can use during sessions, demos and follow-up conversations. Give each question a business owner and an expected piece of evidence. You should be able to explain why an answer would change your priorities.
Use these fields: current problem, affected team, relevant HubSpot product, question to ask, source to collect, next action and decision owner. Add a separate space for unknowns. This keeps an interesting idea from becoming an implementation commitment before anyone has checked the details.
Ask how the proposed change affects the entire customer experience. For example, faster lead capture may create more work for sales if routing remains unclear. A customer service answer may be accurate but still leave the customer without a reliable handoff.
Bring the affected teams into preparation. Revenue operations can help connect the definitions, dependencies and reporting needs across those teams. The aim is to understand the operational tradeoff before discussing software settings.
Choose a task you can describe and evaluate. “Explore AI agents” is a topic. “Evaluate whether approved service answers can be retrieved with a reliable human escalation” is a testable question.
Write down the data foundations the task needs. If the source material is conflicting or ownership is unresolved, fixing that problem may be the next step. An event demo cannot resolve an internal disagreement about what the correct answer should be.
Use the official UNBOUND agenda to check current session details. It includes Main Stage presentations, education sessions and other formats, with reservation requirements for limited-capacity sessions. Registered attendees should verify their own reservations and access rather than treating a saved link as a confirmed seat.
Pick a primary session and a backup for each priority question. Give yourself time to move between rooms, compare notes and follow up on a useful conversation. A full schedule is not necessarily a useful schedule.
Featured speakers and broad strategy presentations can help your team rethink a business problem. A product session may provide more detail about how a capability works. Record which kind of evidence you have collected.
A story about growth or brand building is not a specification for your HubSpot account. Capture the idea, then identify the documentation, entitlement check or controlled test needed before you act on it.
If several people attend, assign different questions rather than sending everyone to identical sessions by default. A marketing leader might investigate audience and measurement questions while an administrator investigates permissions, integration behavior and release management.
Agree on a shared note format before arriving in Boston. Include the session name, source link and who attended. A colleague should be able to follow the evidence without relying on your memory of a fast-moving presentation.
HubSpot's official ecosystem guide describes the Builder Bar as a place to bring implementation questions and connect with the product team. Check the current guide for availability and timing. Do not bring confidential customer records or production credentials into an informal troubleshooting conversation.
Prepare a short description of the problem, the expected behavior and a sanitized example. Explain the systems involved and the point where the process stops behaving as intended.
For a disconnected systems problem, sketch the source, destination, record type and expected update. State which system should own the field. If you have not confirmed the sync direction or error-handling behavior, make that part of the question.
For an automation question, describe the trigger, allowed action and exception. Ask how to observe a failed run and how to stop further activity. These details make a conversation more useful than asking whether a tool can automate everything.
When discussing a connected app, ask who maintains the connection, where failures appear and what happens if access expires. Include the cost and responsibility for support in the follow-up.
Keep a clear record of what the partner demonstrated and what still needs testing in your environment. A working demonstration with sample records does not establish that every required field, permission or historical record will behave the same way after installation.
Networking can help you compare approaches with people facing similar questions. Prepare a short explanation of your role, the process you are investigating and the kind of experience you want to learn from.
HubSpot's ecosystem guide lists peer meetups and Braindates among the ways to connect at UNBOUND. Use the current event schedule to find relevant conversations. Availability and session reservations can change, so confirm the details in your attendee account.
If someone describes a successful AI or CRM project, ask what data, ownership, team capacity and review process made it possible. Ask what failed during the pilot and what they would change next time.
Treat that conversation as a lead for further research. You can learn from another team's experience without presenting its result as a prediction for your business. Get permission before attributing a private conversation publicly.
Record what each person agreed to share or discuss next. A useful follow-up might be a public documentation link, a sanitized workflow diagram or a focused technical call.
Do not turn a networking conversation into an automatic marketing enrollment. Respect the person's stated communication preferences and your organization's approved contact-handling process.
The following is a fictional preparation record, not a HubSpot announcement or an executed customer project. It shows how to convert an interesting capability into a bounded question.
| Preparation field | Illustrative entry |
|---|---|
| Business problem | Staff repeatedly answer the same public service question. |
| Proposed use | Evaluate answers against one approved public source. |
| Evidence needed | Current product documentation, account eligibility and observed test results. |
| Excluded actions | Sending messages or changing customer records without authorization. |
| Acceptance condition | The answer is supported by the approved source, and out-of-scope questions reach a person. |
| Decision owner | The named service owner, with administrator and budget input. |
| Current decision | Investigate. No production activation approved. |
Use the same fields for an integration, reporting feature or content tool. Change the test to match the use case. Do not force unrelated capabilities into identical success criteria.
Agree in advance on reasons to defer: no accountable owner, unclear commercial terms, missing documentation, unreliable source data or an action that cannot be safely bounded.
A deferral should state the missing evidence and the next review condition. That makes it possible to revisit the idea without repeatedly reopening the same unresolved discussion.
Your whole team does not need to attend the same event to participate in evaluation. Assign a colleague to collect official product documentation and reconcile it with the notes from attendees.
The official ecosystem guide says HubSpot Spotlight will be livestreamed on HubSpot Live's YouTube channel. Verify the current broadcast link and schedule through that guide. Do not assume every education session or workshop will have a public recording.
Keep a shared list of confirmed announcements, unanswered questions and proposed tests. Mark secondhand summaries separately until an official source supports the claim.
HubSpot presents UNBOUND as the new name for its annual event previously called INBOUND. Use the current UNBOUND name when searching the agenda and official event information. Old INBOUND planning material may still be useful for general travel ideas, but its session and access details may be outdated.
Bring a current portal summary, a prioritized question list, sanitized examples and a way to capture source links. Do not share account credentials, private customer data or confidential screenshots as part of casual event troubleshooting.
Only if the action is within your organization's approved scope and you understand its effects. Otherwise, record the next evaluation step. Review permissions, data access, messaging, record changes and credit use before activation.
Bring a short decision list with evidence, ownership and next steps. Separate ideas worth investigating from pilots that have actually been approved. The result should fit your team's capacity after the event.
We recommend a short baseline that makes new claims easier to evaluate. Record the products and tiers you actually have, the teams using them and the operational issues already waiting for attention.
Include the integrations and sensitive data boundaries that could affect a test. Mark anything you have not confirmed as unknown. A product name in your contract does not establish that every beta, seat or action is available to every user.
The HubSpot portal audit checklist can organize the baseline. Keep it focused on decisions you might make after the event rather than turning preparation into an unrelated portal rebuild.
We recommend asking stakeholders which task is slow, error-prone or difficult to measure. Capture the current process and what would count as a useful improvement.
These are examples of questions, not findings about your organization. Ask each team to nominate a problem owner who can review an eventual proposal.
Use a consistent record for each item worth investigating: official source URL, announcement timestamp, availability status, eligible products, required permissions, data access, credit or cost implications and unresolved questions.
Leave unconfirmed fields blank and label them “not yet verified.” Do not convert a demo or a roadmap statement into a claim of general availability.
We recommend a clear decision vocabulary: investigate, pilot, defer or reject. Each decision should include a reason and owner. Those are your review categories, not official HubSpot release statuses.
This synthetic preparation exercise uses a currently documented capability rather than an imagined UNBOUND release. HubSpot already documents building and previewing a customer agent, with deployment addressed separately. HubSpot customer-agent setup, customer-agent deployment
For the exercise, propose answering approved public service questions. Record the intended source documents, excluded subjects, human reviewer and evidence required for a pilot decision. Keep the channel undeployed while the evaluation is incomplete.
Ask what you would test: an answer supported by the sources, a question outside scope, conflicting information and a request that needs a person. The same review structure can later be applied to a genuinely new feature once its details are confirmed.
We recommend separating an enthusiastic sponsor from the people responsible for access, cost and customer impact. A proposal should have a business owner, an administrator, a budget owner where relevant and an appropriate data or privacy reviewer.
Define the acceptable test environment and the action boundary. “We are only testing” does not by itself mean no external messages, record changes or charges can occur.
For AI-related proposals, review the actual agent tools and current credit rules before running them. HubSpot's current documentation for the agent builder warns that configured MCP tools may execute during simulations, even though the simulation itself does not consume credits or change CRM data directly. Do not assume every preview surface has the same behavior. HubSpot agent simulation limits
Schedule an internal review in your team's planning process, not an automatic feature activation. Bring the evidence, the relevant business problem and a bounded test proposal. Defer items that lack availability or permission details.
If existing portal issues are more urgent, the HubSpot troubleshooting guide can help keep priorities grounded. For help evaluating changes against your current operating model, explore HubSpot operations support or request a scoped review.