The Archive · 2013 — Now
AI archive.
136 posts in this category
136 essays in the archive · 13 languages · 45 categories
AI-native agency vs traditional agency
An AI-native agency and a traditional agency are not the same business with a bigger tool budget. The difference is where the default sits, how the work is staffed, and what the client is actually buying. Traditional sells a team and its hours; AI-native sells an operating model and judgement, with the machine doing the first pass.
Read the analysis
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.
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.
The Full Index
Earlier entries
Sort: Newest
How many people does an AI-native agency need?
No. 05AIHow to price AI agency services
No. 06AIOffline Mode for My AI App Didn't Need AI. It Needed Boring.
No. 07AIIs an AI-native agency cheaper than a traditional one?
No. 08AINative Isn't a Skin: Rebuilding DIALØGUE's iOS App
No. 09AIWhat should an agency stop selling in the AI era?
No. 10AII Rebuilt My Site With Two AI Models: Opus for Design, Codex for Execution
No. 11AIHow to start an AI-native agency
No. 12MarketingWhat Publicis Is Really Buying for $2.2B: Notes on the LiveRamp Deal
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.