Pulse

What AI enablement changed in how work gets done. Ranked daily.

September 19, 202610 signals ranked

This edition's principle

7 min read

Work the overhang

The next model will not empty your queue

GPT-6 Astra already drafts inbox, follow-ups, and ticket notes. Named people still know, select, and send.

Read Work the overhang

The ranking

Top 10

September 19, 2026

#1 signal that day

Claims most teams underuse current model capability

Claims most teams underuse current model capability; cites an adoption gap

Where it lands

Fits a weekly backlog review: pick 2, 3 high-friction flows (inbox triage, follow-up drafts, ticket summaries) and ship with evals instead of waiting on newer models. You still approve scope, data access, and customer-facing sends.

@emollick

Advice to maintain a parallel portfolio of things you ship

Lands in hiring and vendor review: ask for shipped artifacts (repos, demos, invoices tied to delivery) not study credentials. For your own team, weekly 'shipped this week' note in standup. You still judge fit, IP, and client risk.

@PeterDiamandis

Long thread pitching inbox triage automation and new business models

Maps to email and ticket intake: classify junk, needs reply, and delegate. Before buying, trace one week of real messages against your SLA and CRM fields. You approve anything that sends quotes, legal text, or payment links.

@gregisenberg

Predicts agencies split cheap automated delivery and high-touch expert upsells

Use when scoping services: define which deliverables run on repeat playbooks (status updates, first-draft reports) vs which need human sign-off (strategy, custom integrations). You still set prices, SOW language, and client-visible send rules.

@EXM7777

Weekly human-curated AI notes for large engineering orgs promoted

Fits a Friday leadership skim: compare their themes to your backlog (agent policy, pilot scope, headcount). Subscribe if useful, but you still decide what becomes a ticket, pilot charter, or security review, not the curator.

@clairevo

Claim

Lands in calendar and comms policy: default async updates, tickets with owners, calls only when a decision or unblock is on the agenda. You still approve which relationships stay call-heavy (paying client, legal).

@levelsio

Rumor that major AI vendors delayed public listing timelines

Lands in vendor stability memo: note liquidity and pricing volatility when locking multi-year inference deals. You still decide contract length, prepaid credits, and whether to diversify models before renewal dates.

Finance@GaryMarcus

Skeptic-turned-believer thread on AI across the full video production stack

Map to content SOP: rough cut, b-roll, captions, and revision tickets, with AI drafts and a human final approve before publish. You still own brand voice, client sign-off, and rights on footage and music.

Marketing@businessbarista

Frontier lab brings in external firm for deep-in-house model evals and red-teaming

Maps to vendor due diligence and audit scope: define what third parties can access, what eval artifacts you must retain for incidents, and when findings become release blockers. Humans approve contract terms, data boundaries, and ship/no-ship after red-team reports, not the vendor alone.

Policy@rohanpaul_ai

Argues premium sound design makes short social clips feel higher quality

Lands in creative briefs and ad QA before publish: add a sound checklist (hook in first 3s, mix, captions). Daily use means templated audio packs per campaign, not one-off polish. You still approve final cut, claims, and music rights.

Marketing@AmirMushich