Announcing o11's backing from Y Combinator.

# AI for Gusto

## AI that runs the pay cycle inside Gusto.

- Surface anomalies before the pay run is approved.
- Onboard contractors from email and contract context.

Run Payroll · pay date 4/26/2026  
142 employees · $1.28M gross · pay run by Wed 4/24

### Summary

| Employee | Hours | Gross  | Net    | Status          |
|----------|-------|--------|--------|-----------------|
| M. Chen  | 80h   | $7,115 | $5,218 | Reviewed         |
| L. Park  | 80h   | $9,231 | $6,742 | Reviewed         |
| K. Park  | 80h   | $5,538 | $4,021 | Pending review    |
| A. Hill  | 32h   | $1,440 | $1,082 | Pending review    |
| F. Sato  | 40h   | $1,800 | $1,310 | Pending review    |
| A. Tanir | 80h   | $11,538| $8,432 | Reviewed         |

**Total:** $36,662 gross · $26,805 net

### o11 for Gusto: an AI agent layer for SMB people ops

o11 is an AI execution layer that runs inside Gusto. The agent reviews pay runs, onboards contractors, and tracks benefits changes — without sending a founder or ops lead into a side spreadsheet to retype what was already settled over Slack.

If you have searched for **AI for Gusto**, a **Gusto AI agent**, or an **alternative to Gus AI** for actual workflow execution, the difference comes down to one question: does the AI explain the pay run or actually run it.

### What teams use o11 for in Gusto

- **Pay run review.** Surface unusual amounts, missing hours, and policy edge cases before the pay run is approved.
- **Contractor onboarding.** Set up new contractors from contracts, email, and W-9 docs without retyping fields.
- **Benefits change tracking.** Apply life events, new enrollments, and waivers in flow.
- **Document and notice handling.** Read agency notices and tax letters and pull them into the right place in Gusto.

### Why o11 differs from Gusto-native AI

Gus AI focuses on chat-style answers and inline help. It can describe a deduction or explain a benefit, but the pay run, the contractor record, or the benefits change still ends with a human clicking through screens. o11 prepares and edits. The chat is the control surface, Gusto is where the work lands.

### Built for teams that live across systems

Gusto is one part of a much larger SMB stack — usually paired with QuickBooks or Xero, a contract tool, a hiring tracker, and an inbox of vendor and employee emails. o11 is positioned to act across all of them. A signed contract becomes a contractor profile, a posted bill, and a Slack handoff to the team without the operator stitching tools together by hand.

### Where Gusto teams typically start with o11

- **Founders and ops leads** with pay run review and contractor setup.
- **People ops** with onboarding, benefits, and life events.
- **Outsourced HR partners** with multi-company workflows.
- **Bookkeepers** with payroll-to-GL tie-out.

### How o11 respects Gusto permissions

The agent operates with the user’s own role and company access. Admin permissions, approval flows, and audit history apply exactly the way they do in the UI. Nothing is bypassed. That is what makes o11 deployable for SMBs and operator firms that cannot trust a tool running as a single over-privileged primary admin.

### FAQ

Does it approve pay runs?  
No. It prepares and flags; owners still approve.

Multi-company?  
Yes. Scoped per Gusto company.

### Ready to see o11 inside Gusto?

[Book a demo](/content/demo/index.html)