a16z: Don't Price AI Apps per Token, Price the Value
a16z Newsletter · rss · 2026-08-27
a16z argues that while token pricing makes sense at the model layer, importing it to the application layer is often a mistake.
Key Points:
- Don't anchor on tokens: Falling token costs make this a poor anchor for app value; it ignores data/workflow/orchestration value and makes costs unpredictable.
- Price at the value layer:
- Selling model access: Price tokens.
- Selling useful work: Price recognizable value units (often via Credits).
- Selling clear business outcomes: Price the outcome.
- Credits done right: Should map to customer-recognized work (e.g., small bug fix vs. feature), not hide tokens. Good systems abstract complexity, explain relative effort, and offer flexibility.
- Protect margins: Decouple "work value" from "delivery cost" to retain benefits from falling model costs.
More from Companies & People
- Revenge IPO goal: Turning grudges into chips in pockets — cixliv · 2026-08-28
- Missing OpenAI or Anthropic is a career-ending move for VCs — beffjezos · 2026-08-28
- Building agents is easy now; safely operating 50 at once is the real bottleneck — Many_Audience7660 · 2026-08-28
- X's link UI update changes the game: how the split view affects engagement — gefei55 · 2026-08-28
- Thomson Reuters builds in-house AI model on Alibaba's Qwen for $40M — schwarzjn_ · 2026-08-28
- Ex-Nvidia engineer on company culture and inference infrastructure — Scobleizer · 2026-08-28