liveBook · Manning

Return on investment

As explained in Vibe Engineering

Return on investment is a measure comparing the value gained from an investment with the cost of making that investment.

Return on investment compares the value produced by an investment with its cost. For AI coding tools, the tempting shortcut is to ask developers whether they feel faster. That shortcut can produce trust debt: experienced developers predicted a 24% speed gain, estimated 20% afterward, yet took 19% longer in a randomized trial. section 9.4.2

A defensible ROI assessment should:

  • Start with the full cost picture, then compare it with additional value rather than assumed productivity gains. section 9.4.2
  • Treat self-reported productivity as a hypothesis, not evidence; project complexity, morale, technical debt, and requirements clarity can distort attribution. section 9.4.2
  • Measure observable proxy metrics such as cycle time, defined as the interval from task start to merged pull request. section 9.4.2

How Vibe Engineering covers it

How deep it goes
Explains measurement hazards, self-report bias, and cycle time, but stops short of a complete ROI formula.
Examples
Uses a 2025 randomized trial involving 16 experienced developers and 246 real issues, where participants took 19% longer with AI allowed.
What you can do after
Evaluate AI coding investments with observable proxy metrics rather than developer self-reports.
How it connects
Connects return on investment with developer productivity, technical debt, project complexity, and requirements clarity.

Also explained in

Compare how 14 books explain return on investment →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.