liveBook · Manning

Rebound effect

As explained in Vibe Engineering

The rebound effect is the increase in use of a service after efficiency reduces its per-use cost, offsetting part of the expected total savings.

The rebound effect occurs when lowering AI's per-interaction cost increases usage, offsetting part of the expected total savings. Cheaper assistance expands into code review preparation, documentation, commit messages, test data, and exploratory work. section 9.5.6

A cost reduction that falls short

Per-interaction cost fell 85%, while daily interactions rose 54%, from 65 to over 100 per developer. The monthly bill still fell from $8,754 to $1,407, but not by the full expected proportion. section 9.5.6

Manage the effect with organizational guardrails:

  • Set per-team or per-developer budgets to prioritize valuable workflows. section 9.5.6
  • Expose individual monthly costs on team dashboards to encourage self-correction. section 9.5.6
  • Review team-level return on investment quarterly to identify low-value workflow proliferation. section 9.5.6

How Vibe Engineering covers it

How deep it goes
Quantifies usage and billing changes, then recommends budgets, visibility, and quarterly ROI reviews.
Examples
Uses expanded developer workflows and an 85% per-interaction reduction alongside a 54% usage increase.
What it assumes
Assumes familiarity with AI usage costs and teaches why per-interaction savings do not predict total spending.
What you can do after
Operate/configure AI spending with budgets, cost dashboards, and quarterly value reviews.
How it connects
Connects AI assistance with cost optimization, usage visibility, budgets, and 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.