94% of Developers Report AI Productivity Gains, but Governance Maturity Lags Behind Adoption, Finds New Study From Info-Tech Research Group

The market’s mistake would be to read this as a simple labor-efficiency headline. The more durable P&L effect is budget migration: faster code creation tends to pull spend toward testing, security review, governance, and observability, which is a better setup for control-plane vendors than for pure code-generation tools. In other words, the ROI accrues less to the developer seat and more to the software sitting between the IDE and production.

A second-order implication is that legacy-code-heavy enterprises will realize the least benefit first, so the adoption curve will be uneven and probably show up as more output per engineer rather than fewer engineers. That argues against a near-term broad margin expansion story for software; higher velocity can also mean more feature backlog burn-in and more QA/security workload. The real winners are names with attachable security and compliance workflows rather than point tools that depend on frictionless adoption.

Contrarian view: consensus is too bullish on "AI productivity" and not bullish enough on the governance tax. The next 1-3 earnings cycles matter more than the survey itself; what matters is whether cycle-time gains survive the added testing and review burden without raising defect escape rates. Falsification would be clear evidence that release throughput improves while QA/security spend stays flat; if not, this is a usage trend, not an earnings catalyst. No direct equity read-through to FCD.UN.TO or TCHC from the data provided.