The Larridin Benchmark puts the median billed AI coding spend at $213 per engineer per week. Our CTO, Ameya Kanitkar, shared that number on LinkedIn with an important catch: more spend doesn't automatically mean more output.
He explained his thinking on LinkedIn:
Ameya Kanitkar, co-founder and CTO of Larridin, on LinkedIn:
The Larridin Benchmark data indicates that the median billed spend for AI coding is $213 per engineer per week (approximately $920 per month), reaching ~$3640 per month at the 90th percentile.
And more spend does not always correlate with more engineering output but it does once, you bring in AI Fluency in the picture!
AI coding is a real line item now, and sooner or later finance will ask whether your number is high or low. A benchmark helps you answer that. What it can't do on its own is tell you whether the money is buying anything.
Here's where billed AI coding spend lands in the Larridin Benchmark:
The original LinkedIn post above used approximately $3,640 per month. The published benchmark now lists $911 per week at the 90th percentile, or approximately $3,900 per month; the figures here follow that benchmark.
The post Ameya reshared from Jason Saltzman digs into why. The two AI-native groups came from the same company, using the same tools and prices. The difference in output was associated with AI fluency.
A few findings stand out:
Today the gap between AI-native engineers and everyone else is about 2x at equal spend, and the data suggests it isn't done widening.
A single spend target won't get you far. A few more useful moves:
Spend is an input. An engineer spending $213 a week could be one of your most productive people or one of your least, and the number alone can't tell you which. If you pair spend with output and fluency, it starts to mean something.
Ameya shares this kind of practical, numbers-first stuff on LinkedIn pretty regularly. If you want more of it in your feed, follow Ameya Kanitkar on LinkedIn. He's co-founder and CTO of Larridin.
On larridin.com: