Agents reshape the work while data moves between tools

What we're tracking

• •The developer's job shifts from writing to directing GitHub framed the change plainly: the role is moving from coder to orchestrator. In its own words, "Developers are owning more of the delivery system around code, not just code itself." [1] That is a short sentence with a large implication. If agents can draft, test, and ship more of the routine work, the scarce skill stops being the typing and becomes the judgement: deciding what should be built, reviewing what an agent produced, and owning the system that moves it to production.
• •Deflection is a tempting number and the wrong one Pylon's founders used their SaaStr AI Day session to push back on a metric that a lot of support teams quote. The description of the talk is direct: "Marty Kausas and Advith Chelikani on why deflection rate is the wrong number in CX." [2] The headline fact around the session is that the team "Deflected 50% of Tickets Without Increasing Headcount" [2] — a result most buyers would want. The useful part is the caution attached to it.
• •Spreadsheets should cross tools without breaking Two of Tuesday's announcements were about something less dramatic and more immediately practical: moving data between tools without losing its shape. Google said of its Sheets update, "We're introducing two key improvements in Google Sheets that preserve formatting and linked data when converting files from Microsoft Excel." [3] The change brings Excel tables across as Sheets tables and carries linked pivot tables with them, rather than flattening the file into static values.
• •Where the AI market is actually growing Stripe published its reading of demand, and the framing is a reminder that the AI story is now a business story with geography. The company wrote, "We analyzed Stripe data to understand where global demand is the strongest, and how companies can build to best capture that demand." [5] For a business choosing tools, a payments processor's view of where money is moving is a different signal from a vendor's own growth chart. It describes the market a tool is being built for, not the tool itself.
• •A large acquisition is a signal about your vendor's stability SaaStr's look at Palo Alto Networks is a security story on its surface, but the number that matters to any software buyer is the consolidation underneath it. The company reported $11.4 billion in revenue with 60% ARR growth and 120% net revenue retention, alongside a $25 billion acquisition. On the market's response, SaaStr noted, "The stock is up roughly 100% over the past twelve months and hit an all-time high of $368.80 in July." [6]
• •The thread, pulled together The day's stories rhyme. Agents are moving the human up the stack, from doing to directing, which changes what a good tool has to support [1]. The metrics vendors lead with can flatter the wrong outcome, so a buyer has to read past them [2]. And the quiet features — importing a spreadsheet without breaking it, querying a database from a sheet — decide whether your data stays yours as you move [3][4]. For how we think about picking software that respects both your time and your data, see choose software worth using.