Excel and Power Query, kept, pointed at live Azure SQL.
A lending team's models untouched; the data behind them live. Weekly exports gone.
The Athena ribbon in desktop Office. AI formulas and Sheet Queries in your existing workbooks. Attribution on every change, synced both ways.
Built because a lending team wanted its Excel and Power Query models kept exactly as they were, and pointed at live Azure SQL.
Finance runs on Excel and will keep running on it. The problem is not the spreadsheet; it is the six partner files a supply chain team receives weekly into their shared inbox, the Power Query everyone is careful with, and the 100,000-cell cleanup that is hard to do with formulas.
Replacing Excel is a three-year project nobody wants. Feeding it is a weekly inbox problem everybody has.
Do not replace the model. Connect it, and give it hands.
Install once, tenant-wide. Touchless O365 admin consent; the ribbon appears for everyone in the group. SSO through your IdP.
Connect the workbook to live data. Sheet Queries pull from Azure SQL, Snowflake, Databricks, the Athena Lakehouse, or a semantic model. Existing Power Query steps stay attached.
Ask in the cell or the panel. =ATHENA for a plain-language question. =ATHENAQUERY through the governed semantic model. The side panel for transformations that would otherwise need VBA: "normalize these 14 department tabs into one table."
Sync when it outgrows the laptop. "Copy to Athena" moves the workbook to Studios for the million-row job or multi-agent workflows; sync brings the result back with every change attributed.
A lending team's models untouched; the data behind them live. Weekly exports gone.
A transformation Excel cannot express, described in a sentence in the side panel, executed in Python inside the workbook, attributed cell by cell.
Email to Excel to notebook to Databricks: the request arrives by email, the model updates in Excel, heavy computation runs in a notebook, the result lands in Databricks and back in the workbook.
Draft a memo section from the workbook's numbers with citations back to the cells. Build the deck from the sheet in the company template, from inside PowerPoint.
The reaction from a mid-market accounting firm when they saw the ribbon. Nothing to learn.
“It's good to understand the capability of the platform. That how far, and how quickly you guys can get these things going [...] that has been impressive overall.”
“Lets us get a lot more out of our data than [...] We can sit on top of all of the data in [our data warehouse] as opposed to just, like, our little ingested, you know, three gigabytes semantic models. I think we have a lot of power here.”
“Gave Athena the spreadsheet, explained which column I was trying to figure out, and then ten secs it told me... exactly how the calculation was based on the other data.”
“He wrote the entire stuff. By itself. And I was there, and I was thinking, alright. If I had to write all this stuff, I mean, I would've spent days, days, days.”
“I send that to the programmer and he said, alright. I read your file. I copied the section of the code because he has the right interface, and it works. Wow. Just like magic.”
“One workspace. All different, let's say, avatars of their output data. Right? Suddenly, it's dashboard. Excel is here. PowerPoint is when it's all together. It's very impressive.”
“Use the Athena platform probably closer to the concept and how it was designed, like, with the spaces architecture where you've got a set of primitives and capabilities, and you bring together the right set of capabilities to solve a task.”
“Digital worker, it gets spun up, it gets given access to the toolkits that it needs. It gets given access to the data that it needs. Just exists for the period it needs to exist to perform the task. And then it gets torn back down again afterwards.”
“I like that direction, that concept of the agent is the agent. It becomes an entity in its own right with its own ownership and its own missioning, and you get rid of the gray area and the blurry lines.”
“It was PowerPoint... there was no kind of distinction between the two. So that was killer. And I literally had a meeting on it today, and people said how great it was.”
Verbatim from customer calls. Customers anonymized.
Agents answer in the cell. Workflows (Agent Operating Procedures) refresh the workbook on schedule and email it. Applications turn the finished sheet into a dashboard the rest of the company opens without Excel or a license.
Microsoft 365 with tenant-wide admin consent. Windows and Mac desktop Office. Azure SQL, Snowflake, Databricks, SharePoint-hosted workbooks. Runs against managed cloud or your VPC.
The add-in brings Athena into Excel; it does not make Excel handle a million rows. When the file outgrows the laptop, "Copy to Athena" is the answer, and the sync back is attributed so nothing is lost in the round trip.
Brings the agent into Excel, Word, and PowerPoint, working with your own files and live data.
No. Keep them and connect them to live data.
Centrally by your admins.
Records every change by a person or an agent, rolls back one contributor's edits without losing anyone else's, and keeps the model, instructions, and sources behind each agent action.
How the platform is deployed: Athena's managed cloud, your cloud on AWS, GCP, or Azure, on-prem, air-gapped, or GovCloud. Same platform in every option.
Build, Work, and Data on top; 150+ connectors and every surface in and out; one map of the whole platform.
We will connect it to the source, leave your Power Query alone, and show you the attribution.