o11 Embeds AI Directly Inside PowerPoint and Excel Because That Is Where the Work Actually Happens

The Macro: AI Tools That Live Outside Your Workflow Are Dead on Arrival

The biggest problem with most AI productivity tools is context switching. You are working in PowerPoint. You need help building a slide deck. You switch to a separate AI tool, explain what you need, get output, copy it back into PowerPoint, and format it. The round trip is friction, and friction kills adoption.

The same pattern repeats across Excel, Word, Sheets, and Docs. Knowledge workers spend their entire day inside these applications. Their data is there. Their workflows are there. Their colleagues’ expectations are built around files in these formats. Any AI tool that requires leaving these applications is fighting human behavior.

This is why standalone AI writing assistants and presentation generators have struggled with enterprise adoption despite impressive demos. They produce good output in isolation, but getting that output into the actual workflow requires manual effort. And manual effort is exactly what AI was supposed to eliminate.

o11 takes the opposite approach. Instead of building a separate AI application, o11 embeds directly inside Microsoft Office and Google Workspace. It lives as a plugin within PowerPoint, Excel, Word, Slides, Sheets, and Docs. You use it where you already work.

The Micro: From Slide Decks to Financial Models, Inside the App

The product covers three main use cases. For presentations, o11 generates complete slide decks from outlines or documents. For spreadsheets, it builds financial models, writes formulas, detects errors, and handles data analysis. For documents, it drafts long-form content with tone adjustment and citation tracking.

The pricing is transparent and accessible. Free tier for limited usage. Pro at $20 per month for higher limits and all Office add-ins. MAX at $200 per month for power users. Enterprise with custom pricing for SSO, dedicated support, and bespoke features. This is reasonable compared to competitors like Beautiful.ai ($12/month) or Tome ($16/month), especially since o11 covers multiple application types rather than just presentations.

The founding team has an unusual story. Aryah Oztanir founded a Discord bot with 10,000 users at age 14, then created a free alternative to Apollo.io with 20,000 global users at 19 before dropping out of UNC to start o11. Ajay Misra dropped out of UNC as well, having previously led AI development at Cal AI and published models at Mayo Clinic’s AI Lab at 17. They are young, but the traction suggests the product works.

Hundreds of companies globally use o11 already, and the product has a 4.8/5 rating across 150 reviews. Those are real adoption numbers for a company this early.

The integration list is extensive: OneDrive, Dropbox, Box, PitchBook, and Outlook, plus the core Office and Google apps. The breadth of integrations suggests o11 is positioning itself not as a single-purpose tool but as a horizontal AI layer across all productivity software.

Competitors include Copilot from the large software company that makes Office, plus tools like Gamma for presentations, Julius for spreadsheet analysis, and various standalone AI writing tools. The fact that o11 works across both Microsoft and Google ecosystems is an advantage, since it is vendor-neutral in a way that Copilot is not.

The Verdict

The plugin approach is smart because it eliminates the adoption barrier of switching tools. Users do not need to learn a new application. They just get AI superpowers inside the applications they already use.

At 30 days: what is the daily active usage rate among installed users? Plugin products often get installed and forgotten. The metric that matters is how often people actually invoke o11 during their workday.

At 60 days: are enterprise teams standardizing on o11 across departments, or is adoption limited to individual power users? Enterprise scale requires team-level adoption, not just individual enthusiasts.

At 90 days: what workflows are users automating that they could not do before? The most interesting signal will be novel use cases that o11 enables, not just faster versions of existing work.

I think the embedded approach is the right play. AI belongs inside the tools people already use, not in a separate tab. o11 is betting that integration beats isolation, and I think that bet is correct.