Every RevOps lead I know runs a shadow ticketing system. Slack threads, a Google Form, an inbox rule, a spreadsheet nobody else can find. Requests arrive from everywhere, nobody knows what's open, and the same question gets asked every quarter because the answer lives in someone's head.
HubSpot Work, in beta as of this week, is the first HubSpot product aimed at that mess.
An AI-first workspace natively connected to the CRM, where teams and agents organise and automate work together. Describe the work in plain language and it builds project tables, documents, forms and agent automations from a single prompt. Because contacts, deals and companies are already there, agents reason over real records without you re-explaining the business. No syncs, no status requests.
Three parts: an agent you can question, assign tasks to and let run while you're away (and which suggests improvements over time); flexible tables, forms and documents built on the fly; and native links to existing CRM records so everything has full context from the start.
HubSpot has published nine patterns. In brief:
Client onboarding: Closed Won creates an onboarding row, pulls linked contacts and company, drafts a sales-to-CS handoff document from deal history, sends welcome emails, updates status when kickoff is booked, scaffolds sub-tasks.
Deal desk routing: a single queue for every review request, auto-created from deal property changes, routed by a decision matrix, with SLA deadlines and days-to-breach counters.
Personal task tracking: a Now/Next/Backlog/Done board, auto-stamped start and completion dates, a daily priorities document at 8am.
Targeted account action plans: an account table from CRM filters or CSV, sub-task plans per account, a case-study library the AI matches to each account, generated outreach documents.
Webinar event prep: a marketing event creates a folder, a three-week task table with dates worked back from the event, and starter documents for every deliverable.
Content pipeline: a board from Idea to Published with a linked document per piece, the agent creating the draft at Drafting and pinging the reviewer at Review.
Internal request inbox: one intake form for IT, HR, office and finance asks, AI classification, routing with SLAs, escalation, a weekly ops report.
Internal intake via Work Forms: capture operational request fields without syncing them to CRM properties, then push only the properties you choose back to the deal at a decision point.
HubSpot admin request management: one intake point feeding an admin request table, agent triage against your own playbooks, auto-drafted replies, weekly status and monthly roundup documents.
Deal desk routing. Today a deal needing legal, finance or technical review becomes a Slack thread with no owner and no clock. In HubSpot Work, a flagged property change on the deal creates a request, links the deal and company, and reads a decision matrix table to determine who decides, who gives input and who gets informed. Each request carries an SLA and a days-to-breach counter; the agent generates a daily document of anything near breach and a weekly summary.
The companion is Work Forms, which resolves an old dilemma. Use a HubSpot form for internal intake and every field becomes a CRM property cluttering the deal record; use an external tool and you lose the CRM link. Work Forms push submissions into a Work table without touching CRM records, keep the linked deal for context, and sync only the fields you choose (approved, denied) back when a status is reached. Your existing reporting keeps working.
Admin request management. Access changes, workflow builds, report requests, property updates arrive by Slack, email and hallway. The admin is the bottleneck. In HubSpot Work, one form or Slack integration feeds a table; an agent classifies complexity, checks the request against a Knowledge & Playbooks folder (data dictionary, process guides, approval matrix), determines whether it needs approval and from whom, flags when existing documentation already answers it, and drafts a reply in your own playbook language. Weekly status documents; a monthly roundup of request themes, which teams need coaching, and what governance should change.
That monthly roundup is the document I'd pay for. It turns the admin from ticket-taker into the person who tells leadership where the system is fighting the business.
Both produce a visible artefact within a week: a queue where there wasn't one. Both are hard for a client to build alone and easy to keep. And both expose bad data fast: if deal properties aren't reliable, the routing triggers won't fire; if nobody documented the approval matrix, the agent has nothing to look up. Fix the foundation, then automate the process on top of it.
It's a beta. Confirm availability for your plan, don't move a process your revenue depends on into it in week one, and pick one team as the pilot. The onboarding tracker or the admin queue are the safest starts.
If you want a second opinion on which process to move first, that's a conversation we're happy to have; see the pricing page for how we work.
Part of our guide to the HubSpot Unbound 2026 release: everything HubSpot announced, on one page.