Announcing o11's backing from Y Combinator.

# AI for HubSpot

# AI that moves deals forward.

- Update deals and tasks from inside the CRM.
- Less drift between conversation and clean data.

## Sales Pipeline

### Actions

#### BoardTable

ImportCreate deal

Pipeline: SalesOwner: AllClose date: This quarter Filter

7 deals · $743K

Board synced with this quarter's sales pipeline.

Appointment1

$0

Aurora intro call

Aurora Cloud

$0LP

Close Jun 02

Qualified2

$130K

Northwind Logistics

Northwind Logistics

$92KPS

Close May 14

Mercury Edge

Mercury Edge

$38KPS

Close May 25

Presentation2

$209K

Vanta Foods

Vanta Foods

$64KLP

Close May 02

Skyline Land+Expand

Skyline Holdings

$145KAR

Close May 10

Decision2

$404K

Helix Capital — Renewal

Helix Capital

$184KMC

Close Apr 28

Bridgewater Pilot

Bridgewater Partners

$220KMC

Close Apr 22

Contract0

$0

Closed Won0

$0

Move the deals

### AT

Move Helix renewal to Closed Won at $210K and close it out today.

### Reasoning

I'll bump Helix to Closed Won, set amount to $210K, and stamp today's c

Ask anything…

## o11 for HubSpot: AI that runs the GTM workflow inside HubSpot

o11 is an AI execution layer for HubSpot. The agent updates deals, manages tasks, runs sequences, and keeps the CRM in sync with what is actually happening in the customer conversation. The system of record stays clean, and the rep stays in flow.

If you have searched for **AI for HubSpot**, a **HubSpot AI agent**, or an **alternative to Breeze** for actual revenue execution, the question is the same as in any CRM: does the AI describe the deal, or does it move the deal forward?

## What teams use o11 for in HubSpot

- **Pipeline movement.** Update deal stages, log meetings, schedule follow-ups, and clean up next steps without the rep clicking through every record.
- **Sequence and engagement management.** Enroll qualified leads, throttle outreach when context changes, and pause sequences when a real reply lands.
- **Account research and personalization.** Bring in product usage, recent news, and prior conversations as part of the next outreach instead of relying on a generic template.
- **Marketing operations.** Manage list segmentation, lifecycle stage transitions, and workflow triggers that keep marketing and sales aligned.

## Where Breeze and other CRM AI tools stop short

HubSpot’s Breeze and most CRM-native AI features are good at describing pipeline and drafting copy. They are not designed to act across the CRM and the rest of the GTM stack. o11 is built around action: it operates the CRM, the email tool, the deck, and the doc that goes with the next step.

## Built for revenue ops, not just for sellers

A clean CRM is a RevOps problem. Reps update what they remember; the system reflects what they remembered. o11 closes that gap by making the CRM update part of the conversation, not a separate task. RevOps gets cleaner data without owning the cleanup.

## Where HubSpot connects to the rest of the platform

o11 is the AI agent layer for enterprise applications. HubSpot is one surface — the agent also operates inside Salesforce, Slack, Google Docs, Slides, Sheets, Excel, PowerPoint, and SAP. A meeting summary can become a HubSpot deal update, an outreach sequence change, an account plan update in Docs, and an exec one-pager in Slides without the rep stitching the tools together.

## Where HubSpot teams typically start with o11

- **AEs** with deal updates and follow-ups after each meeting.
- **SDRs** with sequence management and personalized outreach.
- **RevOps** with pipeline hygiene and lifecycle transitions.
- **Customer success** with renewal motions and account health updates.

## How o11 respects HubSpot permissions

The agent operates with the user’s own seat. HubSpot’s user permissions, team boundaries, and partition rules apply the same way they do in the UI. There is no shared service account writing across the org. That is what makes o11 deployable in HubSpot tenants that share data with partners or external teams.

## FAQ

### How does HubSpot fit o11?

Same execution-layer idea inside GTM systems.

### Why beyond Office and Workspace?

Product is broader. Pages reflect that scope.