What code-running chat tools actually change for business reporting
The code-execution modes that landed in the major paid chat assistants this year let the model write and execute Python in a sandboxed environment instead of just describing what code would do. Upload a spreadsheet, ask a question, and the model writes pandas, runs it, and shows you the result, sometimes a chart, sometimes a cleaned-up table. For a certain kind of ad hoc analysis, it's the first AI tool that feels less like a chatbot and more like a analyst you can hand a CSV to.
Where it's genuinely good
- Exploratory analysis, 'what's odd about this dataset' is a question it answers well, because it can actually run the numbers instead of guessing from a description.
- One-off cleaning, deduping a messy export, fixing inconsistent date formats, pivoting a table, without writing the script yourself.
- Quick charts, a scatter plot or a trend line for a meeting in five minutes, when the alternative was opening a notebook.
Where it stops being the right tool
It's a sandbox, and it's built for a single session with a human watching. It doesn't run on a schedule, it doesn't have access to your live systems, and it doesn't persist state between conversations. Every time you want the same analysis again, you're re-uploading the file and re-running the chat. That's fine for exploration. It's a poor substitute for a report your team needs every Monday morning, which is a scheduling and reliability problem, not an analysis problem.
We've had a few clients ask us to 'wire up' one of these chat sandboxes as their reporting pipeline. The honest answer is that the interesting part, reading a live data source, running consistent logic against it, and delivering the result somewhere people will actually see it, has to be built outside the chat interface regardless of which model is doing the analysis. A chat sandbox is a fast way to figure out what that logic should be. It isn't the thing that runs it every day.
The actual takeaway
Use it the way you'd use a very fast analyst sitting next to you: ask it to explore, sanity-check assumptions, and rough out a chart before a meeting. Then build the recurring version, the scheduled job that pulls the same data and applies the same logic automatically, as a proper pipeline. The two aren't in competition; one prototypes what the other should do every day without anyone opening a chat window.
Related reading
Approval workflows in Google Forms and Sheets, without an add-on
A request comes in, the right person approves it with one click, nobody has to chase, and there is a record. You can build that inside Google Workspace with a Form, a Sheet and Apps Script. Here is the design, and the five things that break once real volume arrives.
Google Form → Apps Script → Approver → Decision → Sheet
AI shopping agents can now buy from your store. Is your data ready?
In September Shopify switched checkout on for AI shopping agents. An agent does not see your homepage; it reads your product data and believes it. Here is what changed, where stores lose the sale, and the four checks to run before your first agent order.
Buyer asks → Agent → Product data → Checkout → Buyer approves → Your fulfilment
What changed in Google Workspace this September, and what it means for your automations
Workspace Studio flows can now run your own Apps Script steps and call webhooks, Sheets doubled its cell limit to 20 million, Apps Script data regions went GA, and Gemini connects to QuickBooks, HubSpot and Salesforce. A working read of 4 announcements.
Studio flows → Sheets → Apps Script → Gemini
Continues · Got a workflow like this?