Synthesized by Clarity (Claude) from 36 sources · May contain errors — spot one? [email protected] · Methodology →
Slack and Teams Become Free AI Agent Distribution Overnight
- Sources
- 36
- Words
- 1,459
- Read
- 7min
Topics Agentic AI LLM Inference AI Regulation
◆ The signal
A buyer's team already lives in enterprise chat. They will ask the general-purpose agent to do the workflow you charge for, and it will try. You have about 90 days to ship your own agent into that surface before those workflows get absorbed. The decision is not whether to build the agent.
◆ INTELLIGENCE MAP
Intelligence map
01 Enterprise Chat = Zero-Cost AI Agent App Store
act nowSlack and Teams are now AI agent distribution platforms with zero rev-share. Perplexity's Computer agent grew 17% per week since April; Viktor hit 400+ signups in one week post-Claude Tag. Microsoft chose platform gravity over Copilot exclusivity. Anthropic's strategy: integrate, learn workflows, then build the competing product.
- Perplexity growth/wk
- Viktor best week
- Rev-share cost
- Teams MAU vs Slack
02 Agent-Readable Products: Your Next User Can't Render JavaScript
act nowAI agents are now a buyer persona hitting your product pages — and failing. ChatGPT deduplicates by domain, favors plain HTML over JS, and cites Reddit over your site. Shopify built a Global Catalog explicitly for agent buyers. Companies are shipping /pricing.md files as machine-readable endpoints. Products opaque to agents lose distribution as agent-mediated workflows become mainstream.
- ChatGPT source pref
- CTA microcopy lift
- Domain dedup
- Shopify products
- JS-rendered pages15invisible to agents
- Plain HTML/markdown85fully parseable
03 Warner AI AGENT Act: Architecture Becomes Compliance
monitorSen. Warner's AI AGENT Act (June 29) requires FTC registration, human-operator linkage, consent/revocation controls, and bot-to-bot governance. Large platforms must let users choose compliant agent providers — an interoperability mandate. Separately, Boston University proved anthropomorphizing AI as 'coworkers' causes 18% more oversight errors. Ford's $100M+ AI reversal validates the risk.
- Error increase
- Ford engineers rehired
- Ford savings
- Bill bipartisan support
04 Cost Scissors: Hardware Up 15-20%, Inference Down 35-85%
monitorMemory TAM exploding $220B→$890B forced Apple to pass 15-20% price hikes. But software-side: Devin Fusion's multi-model routing cuts costs 35-41%, DSpark open-sourced 85% inference speedup, and Sakana Fugu ships at $5/M tokens. Your on-prem costs rise while cloud inference drops — the architecture decision determines which blade cuts you.
- Apple price hike
- Memory TAM growth
- Devin routing savings
- DSpark speedup
- Memory TAM 2025$220B
- Memory TAM 2026$890B+4x
- Inference cost (routing)59% of baseline-41%
05 Voice AI: 200ms Micro-Turn Architecture Emerging
backgroundThinking Machines announced a 276B MoE model (12B active) built for 200ms continuous turns — not request-response cycles. Enables simultaneous speak/listen, proactive interjection, and video-grounded response. Research preview in months, wider release H2 2026. The scaffolded VAD→STT→LLM→TTS pipeline may hit a capability ceiling.
- Total parameters
- Active parameters
- Turn latency
- Wider release
- Pipeline stack latency800ms
- Micro-turn model200ms-75%
◆ DEEP DIVES
Deep dives
01 Enterprise Chat Is Your New App Store — Ship There or Get Absorbed
act nowThe Distribution Shift in Numbers
Three independent data points converged this week to confirm a structural change in how AI products reach enterprise users. Perplexity's Computer agent has grown enterprise Slack users 17% per week since its April 2026 launch — roughly 3x per month. Viktor, a Poland-based startup, had its best week ever (400+ new customer signups) directly after Claude Tag launched. Neither company pays Salesforce or Microsoft a dollar for that distribution.
Satya Nadella told shareholders the most exciting AI developments are plugins in Word and Excel — reading this as a decision: Microsoft values platform gravity over Copilot revenue exclusivity. Teams has several times more users than Slack. The channel is free. Microsoft will tolerate agents that compete with Copilot inside its own workspace.
The Anthropic Trap You Must Navigate
Here's where the story gets uncomfortable. A major software CEO privately drew the Facebook Like button analogy — comparing Anthropic's integrations to a data intelligence play, not a distribution partnership. Supporting evidence: In Fall 2025, an Anthropic official publicly stated they used Claude to build a Slack-like workplace chat app. Figma dropped collaboration talks because Anthropic is building design tools. Salesforce employees internally compare Claude Tag to 'letting a fox into the hen house.'
Anthropic integrates, learns the workflow, then ships the competing product. The question isn't whether to be on the platform — it's what survives when Claude can orchestrate 80% of the workflows you own today.
The 2x2 That Decides Your Strategy
Run this diagnostic before your sprint plan. Axis 1: Can Claude or Perplexity already do the core task your product charges for? Axis 2: When it does that task, does the output need revision against something durable — proprietary data, source-of-truth integration, a verification step only your system can perform?
- They can do it + output is usable: You're being disintermediated, not distributed. The agent channel is where you get replaced.
- They can do it + needs revision: That revision step IS your product. Ship it as a Slack agent immediately — it's worth more than your standalone app.
- They can't do it: Your moat holds, but ship the agent anyway for distribution before the gap closes.
Why 90 Days Is Your Window
Perplexity's agent already creates GitHub tickets and queries Snowflake databases. Claude Tag asks customers to connect it to their apps and databases with near-zero friction. AWS's $1B Forward Deployed Engineer investment confirms enterprise AI implementation remains brutally complex — which means the winning agents are winning on setup simplicity, not raw capability. The cost of entry is zero. The cost of waiting is that a general-purpose agent learns your user's workflow this quarter and automates it next quarter.
Action items
- Ship a Slack and/or Teams agent for your product's core workflow within 90 days
- Audit your product's workflow value chain against what Claude Tag + Perplexity can already orchestrate (GitHub tickets, Snowflake queries, deck generation, web research)
- Establish a formal partnership policy on Anthropic integrations — specifically document what workflow data they could extract and whether to integrate given their pattern of building competing products
- Identify your product's 'revision step' — the specific value-add that general-purpose agents can't replicate — and make it the centerpiece of your agent experience
Sources:Applied AI · The Pragmatic Engineer · ben's bites · US AI in the Enterprise · Simplifying AI
02 Your Product Needs a Machine-Readable Interface — This Sprint, Not Next Quarter
act nowThe Buyer Your Page Can't Serve
An AI agent visited a SaaS pricing page this week. It rendered the JavaScript, waited for the modal, parsed the comparison table, and gave up. The buyer got a wrong answer — not because the pricing was bad, but because the page was built for a human with a cursor, and the thing reading it was not.
This is happening at scale. ChatGPT preferentially cites third-party sources (Reddit, G2, review sites) over brand websites. It deduplicates by domain — each domain gets one shot. It favors plain HTML over JS-rendered content. If your critical product information lives behind JavaScript rendering, modals, or interactive components, AI agents literally cannot see it.
The /pricing.md Pattern
Several companies have quietly begun shipping /pricing.md files — plain markdown at a static URL with plan names, features, prices, overage costs, and billing terms. No authentication, no rendering required. Some host these without linking them anywhere, betting agents will find them the way crawlers found robots.txt. For B2B SaaS, this scopes to hours of work and determines whether an AI agent can evaluate your product at all.
Shopify's Bet: The Global Catalog for Agent Buyers
Shopify is building something more ambitious: an LLM-powered clustering layer across billions of products from millions of merchants, organized into a single searchable intelligence layer explicitly designed so AI agents can map products to buyer preferences. This isn't a feature — it's a platform architecture decision betting that agents, not humans, will be the primary 'shoppers' of the future.
Products that are opaque to agents — complex UIs with no structured APIs, unstructured data models, workflows requiring human visual interpretation — will lose distribution as agent-mediated workflows become mainstream. This is the SEO of the agent era.
The Immediate Playbook
The fix splits into two timeframes. This week: ship a /pricing.md file and ensure critical product pages render in plain HTML. This quarter: add an 'agent persona' to your user research framework, audit your information architecture for machine navigability, and prototype structured APIs that let agents complete tasks in your product.
One additional conversion signal worth noting: adding reassurance copy inside the primary CTA button (not beside it) produced a 29% conversion lift in testing. At the decision moment, attention narrows to the button — copy outside it is invisible. Test 'Start free trial — no credit card needed' as button text against your current CTA this week.
Action items
- Ship a /pricing.md file at yoursite.com/pricing.md by end of this sprint — plain text tables with plan names, features, prices, overage costs, billing terms, no login or JS required
- Audit your top 5 product pages for JS-rendering dependencies — ensure pricing, features, and comparison content is available in plain HTML
- Add an 'agent persona' to your PRD template — for every new feature, document how an AI agent would discover, navigate, and complete the task programmatically
- Run a CTA microcopy A/B test: put reassurance text inside your primary conversion button ('Start free trial — no credit card') vs. current copy
Sources:TLDR Marketing · Pointer · Applied AI · The Pragmatic Engineer
03 The AI AGENT Act: Four Architecture Requirements Landing in Your Backlog
monitorWhat the Bill Actually Requires
A product lead skimmed the headline, filed it under "consumer protection," and went back to the sprint board. That's the pitch. Here's what it does to a roadmap. Sen. Warner released the AI AGENT Act on June 29, 2026. Strip the framing and the bill imposes four concrete constraints on AI agent providers:
- FTC registration — agents taking consequential actions become registrable entities
- Human-operator linkage — every agent action must trace to a responsible human, with attribution running action → agent → operator
- Consent and revocation controls — users can stop any agent action at any point in the chain
- Third-party certification — not FTC-enforced directly, but validated by certification bodies, which creates a new compliance market
Three of these are surface features you can bolt on after launch. Human-operator linkage is not. It has to live in the data model from the first action an agent takes. Skip it now and you rewrite history later.
The Cost Gap: Build Now vs. Retrofit Later
The bill also names bot-to-bot interactions as a risk vector, so Agent A calling Agent B calling a tool needs governance checkpoints. And the part buyers will feel first: large platforms must give users the right to choose at least one compliant agent provider. That is an interoperability mandate. This is the DMA for AI agents.
Building human-operator linkage and revocation into agents that already shipped is not a sprint. It's a migration, plus a backfill of records you never captured, plus a certification pass on top. Building the same constraints before launch is a design decision that costs days.
The Research That Changes Your UX Copy
Boston University's Emma Wiles measured what happens when you call an agent a "coworker." Managers reviewing work attributed to an agentic "AI employee" caught 18% fewer errors than when the identical output was labeled a "chatbot." Microsoft, OpenAI, Anthropic, and Google are all marketing agents as digital colleagues. The research says that positioning makes the humans reviewing the work worse at reviewing it. Ford's public reversal — rehiring 350 engineers after AI quality control failed, saving hundreds of millions — is the enterprise version of the same finding.
How This Plays Out in Procurement
The FTC registry is a soft gate in law and a hard gate in deals. Enterprise procurement will treat FTC registration the way it treats SOC 2: table stakes, checked before the demo. Okta's GA of AI agent governance for FedRAMP/HIPAA environments — agents as first-class identities with least-privilege tokens, audit logging, SIEM streaming, and kill switches — now sets the floor buyers will ask for. So the forcing function, before the next agentic action ships: can you answer three questions on demand — which agent, whose authority, which version?
Action items
- Audit your AI agent data model for the human-operator-linkage field — if it doesn't exist, add it before your next agentic feature ships
- Replace 'AI teammate/colleague/coworker' language with tool-oriented framing in all product copy, and A/B test impact on user error rates
- Add FTC registry readiness and third-party certification compatibility to your compliance roadmap as Q4 2026 targets
- Submit stakeholder feedback on the AI AGENT Act through your policy/legal team, particularly on the 'large platform' interoperability definition
Sources:CyberScoop · The Download from MIT Technology Review · TLDR IT · CSO First Look · Morning Brew
◆ QUICK HITS
Quick hits
Claude 4.8 verbosity regression: outputs padded and hedged vs. 4.7 — specifying audience, tone, and format cuts bloat ~50%; route writing tasks to Sonnet 4.6, reserve Opus 4.8 for reasoning
Simplifying AI
Solo founders hit 63% of Stripe Atlas C corps in Q2 2026; top-decile vs. median revenue gap widened from 34x to 61x — AI is a force multiplier for strong operators, not a rising tide
a16z speedrun
Meta open-sourced Astryx: 150+ components, 8 years battle-tested across 13,000+ apps, with first-class AI-collaborative APIs designed for Cursor/Copilot consumption — evaluate against your current design system
TLDR Dev
Salesforce spending $300M/year on Anthropic tokens with only 1% equity stake — the most concrete enterprise AI COGS benchmark available (roughly 0.85% of revenue to a single AI vendor)
TLDR AI
Update: Inference cost deflation — DeepSeek open-sourced DSpark for 85% inference speedup via speculative decoding; Sakana Fugu Ultra hits 93.2 LiveCodeBench at $5/M input tokens
TLDR AI
Gartner warns AI coding agent token costs on track to rival developer payroll within 2 years — track per-developer AI spend per sprint before it blindsides your CFO
US AI in the Enterprise
npm v12 hard-errors on unrecognized .npmrc keys and disables install scripts by default — treat it as a migration, not an upgrade; audit all configs before it becomes CI/CD default
JavaScript Weekly
Ford rehired 350 'gray beard' engineers after AI quality control failed — saving hundreds of millions in warranty/recall costs; strongest quantified case for human-in-the-loop on high-stakes decisions
Morning Brew
GitHub restricted issue creation to write-access collaborators citing the 'agentic era' — first major platform product response to AI-generated noise; model your own UGC surfaces for 10x bot throughput
JavaScript Weekly
Update: Multi-model routing proven — Devin Fusion's dual-agent architecture achieves 35% cost reduction on FrontierCode, 41% with Fable 5 integration, without sacrificing performance
TLDR AI
◆ Bottom line
The take.
Enterprise chat platforms just became zero-cost AI agent distribution channels growing 17% weekly — and the companies shipping agents into Slack today are either capturing workflow ownership or handing it to Anthropic, who uses those integrations to learn your domain before building the competing product. Meanwhile, your product needs two interfaces (one for humans, one for agents that can't render JavaScript), the AI AGENT Act is making human-operator linkage an architecture requirement, and the scissors effect of hardware costs rising 15-20% while inference costs fall 35-85% means your P&L model from last quarter is already wrong. Ship the Slack agent and the /pricing.md file this sprint — both cost hours and determine whether you're distributed or disintermediated.
Frequently asked
- Why only 90 days to ship a Slack or Teams agent?
- Perplexity's Computer agent is growing enterprise Slack users 17% per week, and Claude Tag is onboarding customers with near-zero setup friction. Once a general-purpose agent learns a user's workflow this quarter, it will automate that workflow next quarter — closing the window for a category-specific agent to claim the surface.
- How do I tell if my product will be distributed or disintermediated by these agents?
- Run a 2x2: can Claude or Perplexity already do your core task, and does the output need revision against proprietary data or a verification step only you can perform? If they can do it and the output is usable as-is, you're being replaced. If it needs your revision step, that step is your new product — ship it as the agent.
- What's the risk of integrating with Anthropic specifically?
- Multiple sources indicate Anthropic uses integration data to build competing products — a Slack-like chat app, design tools that pushed Figma out of talks, and internal Salesforce comparisons to 'a fox in the hen house.' Treat Claude integrations as a data-exposure decision, document what workflow signal they can extract, and set a formal policy before connecting production systems.
- Why does a /pricing.md file matter if my pricing page already works?
- AI agents evaluating your product often can't render JavaScript modals or interactive comparison tables, and ChatGPT preferentially cites plain HTML and third-party sources over JS-heavy brand sites — with only one citation per domain. A plain-text /pricing.md with plans, prices, overages, and terms takes hours to ship and determines whether agent-mediated buyers can evaluate you at all.
- Which AI AGENT Act requirement can't be bolted on later?
- Human-operator linkage. FTC registration, consent controls, and third-party certification can be added post-launch, but tracing every agent action back to a responsible human has to live in the data model from the first action taken. Retrofitting it means a migration plus backfilling records you never captured plus a certification pass — versus a few days of design work if built in now.
◆ Same day, different angle
Read this day as…
◆ Recent in product
Keep reading.
Spot an error? [email protected]