Published September 6, 2026 · GitHub
Copilot model retirement on September 10
Find affected workflows and test the suggested alternative before the cutoff.
Read the migration checklistWorthd Insights
Software is changing shape. Your buying process should too.
AI agents are moving from answering questions to carrying work across tools. Platforms are reaching into neighboring categories. The bill is getting harder to understand. Worthd follows the changes that reopen a real decision: what to buy, what to keep, and what deserves a second look.
New in the decision record
Recent deadlines worth checking.
Published September 5, 2026 · Zapier + Zendesk
Check legacy Zendesk token connections
Identify old connections and prepare a tested move to the current integration.
Read the connection checksThe shift worth understanding
The next software layer does not just answer. It acts.
Two major releases show the split taking shape. ChatGPT wants to work across your stack. Asana wants people and agents to coordinate inside a governed work system. That creates a more useful question than which demo looks smarter: where should context, permissions, approval, and accountability live?
ChatGPT Work turns an AI seat into a workflow decision.
It can work across connected apps, local files, and longer-running tasks. That is meaningful only when it removes a real handoff without creating a larger review and repair burden.
Watch: connection scope, action permissions, review time, and whether the workflow can recover cleanly when the agent is wrong.
Read the ChatGPT Work SignalAsana is becoming more than a project manager.
AI Teammates and AI Studio expand the buying question from task tracking to agent coordination. Several new Asana applications are still arriving in phases, so availability and ambition should not be confused.
Watch: what is live in the account, how permissions are enforced, and whether broader platform scope replaces a specialist tool or merely adds another layer.
Read the Asana SignalWhat else is moving
Three buying assumptions are starting to break.
The important changes are not isolated release notes. They alter how categories are compared, how consolidation is valued, and how cost should be modeled.
Platforms want to own more of the workflow.
Shopify is pulling AI shopping channels into commerce operations. HubSpot is bringing quote-to-cash closer to the CRM record. Consolidation can remove handoffs, but it also deepens platform dependency.
Decision test: name the system this replaces, the data it will own, and the cost of leaving later.
Software cost increasingly depends on usage, workflow design, and model choice.
Zapier's AI model tiers show how one workflow can consume very different amounts of capacity. A base allowance cannot tell you the cost of retries, human review, or an expensive model choice.
Decision test: price the completed workflow, including failed runs and repair work.
Renewal and retirement dates create leverage before urgency.
Slack's legacy plan retirements and Microsoft 365's commercial price change matter as planning triggers. Neither is a recommendation by itself. Their value is in forcing a review while there is still time to measure use, overlap, and migration effort.
Decision test: begin with actual adoption and replacement cost, not the new quote alone.
Decision record
Selected changes worth keeping on file.
This is a curated selection. Browse every Signal for the complete publication list. Each Signal starts with a primary source, separates what is available now from what is promised, and ends with a practical decision. Worthd excludes routine release notes and minor page changes.
ChatGPT Work turns the AI seat into a workflow decision
Test whether the agent removes a real handoff after review and repair work are counted.
Open SignalAsana widens the comparison beyond project management
Separate live account capability from phased products, then test one governed workflow.
Open SignalShopify makes AI shopping channels operational
Agentic commerce matters when catalog reach, attribution, and storefront control work together.
Open SignalHubSpot pulls quote-to-cash closer to the CRM
Consolidation earns its place only if it removes handoffs without weakening billing or contract control.
Open SignalZapier AI steps make task allowances harder to read
Model cost using the actual AI tier and the full completed workflow.
Open SignalSlack legacy plan retirements create a decision date
Audit history, apps, guests, and suite overlap before the migration window becomes an emergency.
Open SignalMicrosoft 365 pricing makes overlap harder to ignore
Use the new quote to inspect adoption and duplicate tools. A price change is context, not the conclusion.
Open SignalHow the writing earns trust
Evidence first. Judgment second.
Worthd does not publish an announcement just because it is new. It publishes when the change can alter cost, access, migration, risk, or what belongs in a software stack.
01
Confirm the change
Use the company announcement, documentation, pricing page, or another primary record. Clearly label staged rollouts and uncertain account access.
02
Find the decision
Explain who should care, what the change does not prove, and which existing assumption should be reconsidered.
03
Make the next move useful
End with a bounded action a buyer can take now, plus the evidence that would strengthen or reverse the call later.
Worthd Briefing
Join the Briefing launch listKeep the useful changes. Skip the release-note pile.
Preparing to launch: one concise monthly email about software changes that can alter what to buy, renew, replace, or question. Read new Signals on the site now.