Announcing o11's backing from Y Combinator.

# AI for Dynamics 365

## AI that runs the Dynamics 365 model-driven app.

- Update records and run Power Automate flows from one prompt.
- Stay in the model-driven app instead of a side chat.

# Open Opportunities

(My Open Opportunities)

| Topic                        | Account                    | Est. Revenue | Sales Stage | Est. Close Date | Owner         | Status | Probability |
|------------------------------|---------------------------|---------------|-------------|-----------------|---------------|--------|-------------|
| [North Atlantic Renewal](/content/solutions/index.html) | [Northwind Logistics](/content/solutions/index.html)  | $185,000      | Develop     | 4/28/2026       | MCM. Chen     | Open   | 70%         |
| [Helix Capital expansion](/content/solutions/index.html) | [Helix Capital](/content/solutions/index.html)      | $142,000      | Propose     | 5/06/2026       | PSP. Singh    | Open   | 60%         |
| [Bridgewater pilot](/content/solutions/index.html)      | [Bridgewater Partners](/content/solutions/index.html) | $220,000      | Close       | 4/22/2026       | MCM. Chen     | Open   | 85%         |
| [Skyline land+expand](/content/solutions/index.html)    | [Skyline Holdings](/content/solutions/index.html)    | $98,000       | Qualify     | 5/10/2026       | ARA. Rivera    | Open   | 30%         |
| [Atlas Robotics MSA](/content/solutions/index.html)    | [Atlas Robotics](/content/solutions/index.html)      | $310,000      | Develop     | 5/18/2026       | LPL. Park     | Open   | 55%         |
| [Kepler Industries renewal](/content/solutions/index.html)| [Kepler Industries](/content/solutions/index.html)   | $76,000       | Develop     | 5/01/2026       | KPK. Park     | Open   | 65%         |
| [Vega Logistics LOI](/content/solutions/index.html)      | [Vega Logistics](/content/solutions/index.html)      | $44,000       | Qualify     | 5/22/2026       | ARA. Rivera    | Open   | 25%         |

## o11 for Dynamics 365: an AI agent layer inside the model-driven app

o11 is an AI execution layer that runs inside Dynamics 365. The agent updates records, runs Power Automate flows, drafts replies in Customer Service, and keeps the pipeline aligned with what reps and agents say in the field — without sending anyone into a separate window to retype it.

If you have searched for **AI for Dynamics 365**, a **Copilot for Sales alternative**, or a **D365 AI agent** that can actually move work across the Power Platform, the difference is the same one every CRM team is now asking about: does the AI describe the work or do the work?

## What teams use o11 for in Dynamics 365

- **Pipeline updates in Sales.** Move opportunities, log activities, fix stale next steps, and reconcile estimated revenue with what the AE just heard.
- **Case triage in Customer Service.** Classify incoming cases, draft first responses, route to the correct queue, and link related knowledge articles.
- **Field Service dispatch.** Adjust work orders, slot technicians, and update bookable resources from one prompt.
- **Power Automate orchestration.** Trigger and parameterize existing flows so the same automation runs on demand from natural language.

## Why o11 differs from Copilot for Sales and D365-native AI

Copilot for Sales, Copilot for Service, and most D365-native AI features summarize records, draft emails, and surface insights. The execution still ends with a human clicking through screens. o11 is built to drive the screens. The chat is the control surface, the model-driven app is where the work lands. It also reaches outside the Microsoft estate, which Copilot is not designed to do well.

## Built for teams that live across systems

Dynamics is rarely the only system in the room. Most accounts pair it with Outlook, Teams, SharePoint, Excel, Azure DevOps, and a long tail of line-of-business apps. o11 is positioned to act across all of them. A discovery call can become a D365 opportunity update, a Power Automate flow run, a Teams handoff, and a SharePoint folder of supporting docs without the rep stitching the systems together by hand.

## Where Dynamics 365 teams typically start with o11

- **AEs and BDRs** with deal updates, activity logging, and account research.
- **Customer service agents** with case triage, response drafts, and knowledge linking.
- **Operations and CRM admins** with bulk cleanup, field standardization, and validation rule enforcement.
- **Service managers** with rolling forecasts, SLA reporting, and exec briefs.

## How o11 respects Dynamics 365 permissions

The agent operates with the user’s own security role. Business unit scoping, field-level security, and form-level rules apply exactly the way they do for that user in the Unified Interface. Nothing is bypassed. That is what makes o11 deployable in regulated orgs that cannot trust a tool that runs as an over-privileged service account.

## FAQ

**How is this different from Copilot for Sales?**
Copilot for Sales summarizes and suggests. o11 executes the next step across D365 and the systems around it.

**How does it fit the Power Platform?**
It calls Power Automate flows and Dataverse like any other system, alongside non-Microsoft apps in the same workflow.