Your AI code spend is soaring, here's how leading engineering orgs are proving the ROI | Harness Blog

AI coding tools have become widely adopted, shifting engineering leaders’ focus toward demonstrating whether rising spending produces meaningful business value. A Harness panel advised measuring outcomes across the full software delivery lifecycle rather than relying on easily gamed activity metrics such as lines of code, pull requests, or token usage, while combining quantitative indicators like cycle time and defect rates with qualitative evidence from real work. Panelists emphasized granular attribution of AI costs to tickets, features, models, test runs, and workflow stages as essential for identifying waste, improving model selection, and connecting spending to production results. They also noted that reliable pre-AI baselines are difficult because development practices and AI capabilities are changing rapidly, making end-to-end measurement and bottleneck detection especially important. Model prices may decline while total costs rise as usage expands, prompting calls for deliberate budgeting, governance, and visibility tailored to team needs rather than a single universal approach. The discussion further argued that organizations should periodically reconsider whether AI should merely accelerate existing development processes or enable redesign of processes originally created for a more expensive, slower way of building software.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.