The Archive · 2013 — Now
AI archive.
135 posts in this category
135 essays in the archive · 13 languages · 45 categories
What stays in-house vs agency in the AI era
In the AI era the in-house-versus-agency decision is no longer mainly about cost. Keep the layers that compound — brand judgement, first-party data, and the client memory that makes AI improve — and use agencies for elastic production and specialist execution. The deciding question moved from price to compounding.
Read the analysis
The One Question That Killed an Entire Curriculum Architecture in a Week
The product I shipped in April was right about the engine. The product I settled on in June was right about the spine. In between: two complete curriculum rewrites, a framework that killed an architecture in a week, and the question I wish I had been asking since March.
How many people does an AI-native agency need?
An AI-native agency needs fewer people than a traditional one for the same output, and the number is set by review capacity rather than production volume. The shape is a small, senior pod carrying what used to take a much larger team. Fewer, more senior, and accountable is the whole design.
The Full Index
Earlier entries
Sort: Newest
How to price AI agency services
No. 05AIOffline Mode for My AI App Didn't Need AI. It Needed Boring.
No. 06AIIs an AI-native agency cheaper than a traditional one?
No. 07AINative Isn't a Skin: Rebuilding DIALØGUE's iOS App
No. 08AIWhat should an agency stop selling in the AI era?
No. 09AII Rebuilt My Site With Two AI Models: Opus for Design, Codex for Execution
No. 10AIHow to start an AI-native agency
No. 11MarketingWhat Publicis Is Really Buying for $2.2B: Notes on the LiveRamp Deal
No. 12AIHow to govern marketing data for AI
Subscribe
Get the next useful note when there is something to say
I write about AI, work, expat life, and building products. Pick the topics you care about, and I'll send the next one when it's worth your time.