Technical Context
I wasn't hooked by a new release, but by a very telling user experience: a finance professional is in Excel, building a mathematical model, complaining about AI bugs, and applying fixes iteratively. It looked exactly like my own work with LLMs in development.
That's what made me pause. This is no longer just 'generate a formula'; it's a mature artificial intelligence implementation in domain-specific work where people used to either call a senior analyst or spend hours figuring it out themselves.
Looking at the tools, the picture is clear: Microsoft Copilot in Excel, Ajelix, GPTExcel, Formularizer, AI ExcelBot, and similar tools can translate natural language into formulas, VBA, summaries, forecasts, and logic explanations. Not perfectly, of course. But the pattern is what matters: prompt, review, revise, prompt again.
Essentially, Excel is starting to behave like a lightweight IDE for specialists without a traditional programming background. A finance professional isn't writing code in the conventional sense, but is already thinking like an engineer: formulating a hypothesis, getting a draft result, catching an error, clarifying context, and fixing the model.
Yes, these assistants have plenty of limitations. They provide partial answers for complex calculations, get confused by long logic chains, and sometimes eloquently explain an incorrect formula. But these are the same growing pains I see in AI coding tools every day; they've just moved into Excel and financial models.
Impact on Business and Automation
For businesses, I see three practical shifts here. First, the barrier to entry for complex modeling is dropping. Someone from FP&A or finance ops can create a working draft much faster without a lengthy back-and-forth with development.
Second, the speed of iteration is changing. When a model can be not only built but also debugged via AI integration directly in the spreadsheet, the 'idea → test → fix' cycle shrinks dramatically.
Third, demand is shifting from 'another Excel analyst' to a proper AI architecture around these processes. Because as soon as a spreadsheet starts influencing decisions, you need version control, validation, access rights, and clear review protocols.
Teams with a lot of manual analytics and repetitive models win. Those who think they can just plug AI into Excel and forget about quality lose.
At Nahornyi AI Lab, we tackle these specific bottlenecks in practice: where to keep a human in the loop, where to integrate AI automation, and where it’s better to move the logic out of spreadsheets into a more robust system. If your Excel has already become a hidden 'business engine,' let's review the process together and build an AI solution development without the hype, focusing on real-world verifiability.