Announcing o11's backing from Y Combinator.
AI for Salesforce
AI that runs in the CRM.
- Update records and follow-ups closer to the CRM.
- Cut the gap between conversation and clean data.
Opportunities
My Open Opportunities
5 items · Sorted by Close Date · Updated a few seconds ago
| Opportunity Name | Account Name | Amount | Stage | Close Date | Owner |
|---|---|---|---|---|---|
| Helix renewal — FY26 | Helix Capital | $184,000 | Negotiation | 4/28/2026 | MCM. Chen |
| Northwind expansion | Northwind Logistics | $92,000 | Qualification | 5/14/2026 | PSP. Singh |
| Vanta annual | Vanta Foods | $64,000 | Proposal | 5/02/2026 | LPL. Park |
| Bridgewater pilot | Bridgewater Partners | $220,000 | Negotiation | 4/22/2026 | MCM. Chen |
| Skyline land+expand | Skyline Holdings | $145,000 | Proposal | 5/10/2026 | ARA. Rivera |
o11 for Salesforce: an AI agent layer for the CRM
o11 is an AI execution layer that runs inside Salesforce. The agent updates records, moves deals, drafts follow-ups, and keeps the system of record clean — without sending a rep into another tab to retype what they already said in a call.
If you have searched for AI for Salesforce, a Salesforce AI agent, or an alternative to Einstein for actual workflow execution, the difference comes down to one question: does the AI describe the work or do the work?
What teams use o11 for in Salesforce
- Pipeline hygiene. Move opportunities through stages, log activities, fix stale next steps, and keep amounts and close dates aligned with what was said in the call.
- Account research at scale. Pull recent news, signals, and product usage into account briefs without the rep doing the search-and-paste loop.
- Forecast cleanup. Reconcile what the AE believes against what the system shows, and surface the diffs to RevOps.
- Cross-system handoffs. Push qualified deals into HubSpot for marketing follow-up, or into Slides and Docs for IC and exec review.
Why o11 differs from Einstein and CRM-native AI
Einstein and most CRM-native AI features are scoped to the platform that ships them. They generate drafts, suggest next steps, and summarize records, but the workflow execution still ends with a human clicking through screens. o11 is built to drive the screens. The chat is the control surface, the CRM is where the work lands.
Built for teams that live across systems
Salesforce is one part of a much larger stack — usually paired with Outreach, Slack, HubSpot, AWS, Excel, and a deck. o11 is positioned to act across all of them. A discovery call summary can become a Salesforce activity, a HubSpot enrollment, a Slack handoff, and the next page of an account plan in Docs without the rep stitching the tools together by hand.
Where Salesforce teams typically start with o11
- AEs and SDRs with call follow-ups and deal updates.
- RevOps with pipeline hygiene, forecast cleanup, and field standardization.
- Customer success with renewal workflows and account health notes.
- Sales leadership with rolling forecasts and exec briefs.
How o11 respects Salesforce permissions
The agent operates with the user’s own profile. Sharing rules, field-level security, and validation rules apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 deployable in regulated revenue orgs that cannot trust a tool that runs as an over-privileged service account.