What Is HubSpot Work and How Does It Change Team Operations?

HubSpot Work is an AI-first workspace built natively on your CRM, where people and AI agents run projects together in one place. It combines three things most teams keep in separate tools: structured tables for tracking work, documents for the unstructured detail, and agents that act on both. Because it sits on the CRM, every task already carries its related contacts, companies, deals, and tickets. This guide covers what the workspace does, how its pieces fit, and what you can build with it. 

What Is HubSpot Work?

HubSpot Work is a shared workspace where teams and AI agents organize, accomplish, and automate business work together. It is built on the CRM rather than beside it, so contacts, deals, companies, and tickets are present in the work itself instead of being copied into a separate tool.

Two capabilities define it. Smart Creation builds project tables, documents, custom forms, and agent automations from plain-language prompts. CRM Context means every task is powered by live records, not a stale export. The result is a workspace that understands the business it is tracking.

You can grab a template from a use case library, and it scaffolds the project, the table, the columns, and the agents you need in one step. That is the fastest way to see the model in action.

How Do Tables, Documents, and Agents Fit Together?

The workspace has three building blocks, and the power is in chaining them. Tables hold structured work, with columns you can link to any CRM object, assignees, comments, and saved views. Documents hold the unstructured detail, drafted and edited inline and linked back to the row they belong to.

Agents are the third block. You give an agent a task, and it runs on a schedule or a trigger, using the language model to search CRM activity, do web research, make judgment calls, and fill in information on your behalf. Ask the assistant to build a document and it researches, drafts, and links it to the task without you leaving the view.

You can run several of these conversations in parallel. Start one task, let an agent work, switch to another, and move between the threads as they progress.

What Can You Build in the Workspace?

The use case library shows the range, from post-sale operations to marketing production to internal request handling. Each template is a table, a set of linked documents, and one or more agents wired to the work.

Representative use cases from the beta library include:

• Client onboarding: a Closed Won deal creates an onboarding row, drafts a sales-to-CS handoff from CRM history, and scaffolds kickoff tasks.
• Deal desk routing: a flagged deal property opens a routed request with an owner, an SLA, and a days-to-breach counter.
• Content pipeline: a board from idea to published, with a linked draft per piece and a reviewer pinged at the review stage.
• Webinar event prep: a marketing event provisions a folder, a three-week task table, and starter docs dated back from the event.
• Internal request inbox: one intake form that an agent classifies, routes with an SLA, and escalates when a request runs late.

How Do Agents Do Work While You Are Away?

The agents are scheduled or event-driven, so the process keeps moving when nobody is watching it. Assign an agent a weekly review at nine on Monday, and it creates that status document every week inside the project. Assign it a daily priorities report, and it generates one each morning from your open tasks.

Because the agent reads CRM activity, it can do more than remind. It can summarize prior notes into a handoff, match an account against a case study library, or draft outreach grounded in the record. When a status changes, it can stamp a date, move a card, or notify the right person, so the table reflects reality without manual upkeep.

You decide how much autonomy each agent gets. Keep a human in the loop to approve every write, or, once you trust an agent, let it run in the background within the guardrails you set.

Who Is It For, and What Do You Need To Run It?

The workspace fits any team that runs recurring, structured work against CRM records: customer success, sales and revenue operations, marketing production, and internal operations teams like IT and HR. If your process currently lives across a project tool, a doc tool, and Slack, this is built to collapse those into one place with the CRM already attached.

Getting value still depends on the data underneath. An agent that reads a messy portal makes messy decisions, so clean records and clear properties matter as much here as the templates do. The workspace also pairs naturally with custom agents built in Agent Builder, which extends what these automations can do across objects.

Treat it as an operating layer, not a to-do list. Our view on AI Services for GTM covers how to stand that layer up.

Frequently Asked Questions About HubSpot Work

Q: Is the workspace the same as HubSpot projects or tasks?

A: No. It combines structured tables, linked documents, and AI agents on top of the CRM, so work is tracked, written, and automated in one place. Ordinary tasks record what to do, while agents here can do parts of the work themselves.

Q: Does it connect to CRM records automatically?

A: Yes. It is built natively on the CRM, so contacts, companies, deals, and tickets are available inside tables and documents, and changes surface on the linked records on the other side.

Q: Can agents run without me approving each action?

A: You choose per agent. You can require human approval for every write, or let an agent run in the background once you trust it, within the caps and guardrails you configure.

Q: What plan do I need to use it?

A: At launch it is in private beta and requires a Core Seat, available starting on Starter. Confirm current plan and seat requirements in your portal before you plan a rollout.

Q: How is this different from building the same thing in workflows?

A: Workflows automate deterministic steps against CRM objects. This workspace adds tables and documents for humans, plus agents that reason and make judgment calls, so it suits collaborative work that mixes structured and unstructured pieces.

What This Means for Your Team: Work Moves Onto the CRM

The quiet shift here is location. Work that used to live in tools disconnected from the CRM now happens on top of it, with the records already attached and agents able to act. That removes the copy-paste handoffs where context usually leaks out of the business.

The teams that benefit most are the ones that first get their data and process in order, then let the workspace and its agents carry the routine. That sequence, clean system first and automation second, is the same architecture discipline the whole launch rewards. Our take on AI Services for GTM shows how to put it in place.

Ready to move your recurring work onto the CRM? Talk with our team about building agent-run operations in HubSpot.