B2B companies are spending significant money on AI in 2026 — seats for ChatGPT and Claude, metered token bills for coding agents, and growing line items for always-on agents. Much of that spend is fragmented across invoices, corporate cards, and personal subscriptions, leaving finance and engineering leaders unable to see whether dollars translate to useful output. Larridin connects AI spend to engineering telemetry to answer that question.
Larridin split engineers into cohorts by the share of shipped output that was AI-attributed. All cohorts started with roughly the same baseline spend, which lets the findings isolate skill and fluency effects. Results:
- Deep AI-native engineers (79% AI-attributed) reached 11.8x output at around $1,300 per week and had not hit a ceiling. At equal spend, they shipped about twice the output of partial adopters.
- Partially AI-native engineers (37% AI-attributed) saw real returns, but marginal payoff dropped sharply after roughly $600 per week.
- Low-AI engineers (15% or less AI-attributed) plateaued around 1.9x output and did not improve despite up to a 20x range in spend.
Practical takeaway: more budget only converts to more output when AI fluency exists. Larridin recommends tracking each team's marginal ROI curve and placing review triggers where returns level off.
Larridin scores merged pull requests using model-assessed complexity across five levels, adjusts for low-quality output and missing tests, and scales by code churn. The company is explicit that its relationships are associational: high-output engineers may both ship more and spend more. Larridin flags that its metrics estimate AI-equivalent work and are not direct measures of cash saved or headcount reduction.
- AI Impact: connects team-level spend to estimated human-equivalent hours returned, comparing adoption, fluency, and cost per AI hour to guide where to invest and train.
- Developer Intelligence: links engineering output, quality, and delivery to AI spend and identifies where coding agents help or where teams need support.
- Larridin Router: scores coding requests and routes lower-cost models for appropriate tasks while tracking routed sessions against output, quality, defect rate, and cost per task.
Larridin's initial benchmark provides concrete numbers to start conversations inside engineering and finance. The most useful next steps are running the same linkage on your organization's billing and telemetry, and comparing marginal output per dollar across cohorts to set targeted training and spend policies.