Skip to content
, , ,

Dear Coding Agent Builders and Corporate Leaders Funding These Tools: Just Give Me the Best Model

An open letter to the companies building AI coding tools and the leaders paying for them. You built something that made software fun again. Now stop making me think about which model I am on.

·

Executive DeckListen

Let your agent read this

Executive briefClick to expand

In any given value stream, optimizing for input cost over output value creates friction.

Treat AI as an investment, not an expense to minimize.

  • The cost of engineering labor significantly outweighs the fully-loaded cost of development tooling, including AI assistance. Prioritizing small cost savings on AI tool access over engineer productivity yields a net negative return.
  • Flow state is a critical determinant of engineering throughput and quality. Interrupting developer flow through performance degradation or access restrictions introduces disproportionate friction, negating potential cost savings.
  • Access to high-performance AI models should be treated as a capability investment. Restricting access or introducing tiered usage models trains users to underutilize the most effective tools, fostering learned helplessness rather than maximizing output.
  • Measuring AI tool efficacy requires focusing on the value generated, such as accelerated delivery or improved quality, rather than solely on direct token consumption. Cost-centric governance often overlooks broader economic impacts.

The decision for AI tooling is whether the organization seeks to audit an expense or invest in a capability.

Read the full executive package →

Engineer building elaborate structures from a monitor while a giant hand with price-tagged scissors cuts the creative flow

5 min read

In any given value stream, optimizing for input cost over output value creates friction.

Treat AI as an investment, not an expense to minimize.

  • The cost of engineering labor significantly outweighs the fully-loaded cost of development tooling, including AI assistance. Prioritizing small cost savings on AI tool access over engineer productivity yields a net negative return.
  • Flow state is a critical determinant of engineering throughput and quality. Interrupting developer flow through performance degradation or access restrictions introduces disproportionate friction, negating potential cost savings.
  • Access to high-performance AI models should be treated as a capability investment. Restricting access or introducing tiered usage models trains users to underutilize the most effective tools, fostering learned helplessness rather than maximizing output.
  • Measuring AI tool efficacy requires focusing on the value generated, such as accelerated delivery or improved quality, rather than solely on direct token consumption. Cost-centric governance often overlooks broader economic impacts.

The decision for AI tooling is whether the organization seeks to audit an expense or invest in a capability.

Companion

Most readers also read: The Engineers Who Can’t Use AI Agents Don’t Have a Tools Problem

Written by

The views and opinions expressed in this article are the author’s own and do not represent the positions of any employer, client, or affiliated organization.

Every article, narrated. Listen while you ship.
From the Author

Essential or Ornamental

Three companies. Three choices. One satisfactory ending.

One does nothing. One maps the waste. One bets everything on twelve people in a warehouse.

Read free online →

Listen

6 min listenDownload

One useful note a week

Get one good email a week.

Short notes on AI-native software leadership. No launch sequence. No funnel theater.