What Is The 10-20-70 Rule For AI ROI? BCG Framework Guide

Written by: Mark Hull, Co-Founder and CEO, Exceeds AI

Key Takeaways

1. BCG’s 10-20-70 rule shows AI value comes from 10% algorithms, 20% infrastructure, and 70% people and processes, which explains why many investments miss ROI targets.
2. Teams should establish pre-AI baselines with DORA metrics and track tool-specific performance across Cursor, Claude Code, and GitHub Copilot for accurate ROI.
3. Leaders can map adoption patterns and quantify outcomes like cycle time reductions and rework rates to spot high performers and coaching needs.
4. Coaching systems and longitudinal tracking help sustain productivity gains while managing technical debt in the agentic AI era.
5. Exceeds AI provides commit-level analytics to prove ROI and scale adoption, so get your free AI report for team benchmarks today.

Why BCG’s 10-20-70 Rule Matters for Engineering Teams

AI results come from 10% algorithms, 20% technology and data, and 70% people and process change. This breakdown explains why organizations often overinvest in the 10% algorithms despite this distribution.

The framework fits engineering teams because AI adoption functions as a business transformation that emphasizes people and processes over technology. With 84% of developers planning AI adoption, the 70% component becomes the lever that converts scattered experiments into consistent organizational value.

7 Practical Ways to Drive AI ROI with the 10-20-70 Framework

1. Baseline Pre-AI Metrics for Clear ROI (10% Focus)

Teams need measurable pre-AI baselines before they evaluate algorithms. Use DORA metrics plus AI-specific indicators. Track cycle time, deployment frequency, lead time for changes, and change failure rate alongside rework rates and code survival percentages.

The core ROI formula is ROI = (Gain – Cost) / Cost × 100. Comprehensive ROI measurement includes efficiency gains, revenue generation, risk mitigation, and business agility. For engineering teams, this means time savings multiplied by fully loaded hourly costs, plus quality improvements and reduced technical debt.

2. Compare Algorithm Performance Across AI Tools (10%)

Teams should compare outcomes across AI tools instead of tracking adoption alone. AI coding assistants deliver 11-minute daily productivity gains, yet effectiveness varies widely by tool and use case.

Track tool-specific metrics such as Cursor for complex refactoring, Claude Code for architectural changes, and GitHub Copilot for autocomplete. Exceeds AI’s tool-agnostic detection (Tool-by-Tool Comparison in beta) highlights which tools create the strongest outcomes for your codebase and team patterns.

3. Build Scalable AI Infrastructure and Governance (20%)

Engineering leaders should build multi-tool access and governance frameworks. Gartner predicts 40% of enterprise applications will embed AI agents by the end of 2026, which requires solid infrastructure for agent orchestration and cross-tool collaboration.

Monitor uptime, API reliability, and integration health across the AI toolchain. Track infrastructure costs against productivity gains so the 20% investment amplifies the 70% people and process component instead of becoming overhead.

4. Map AI Adoption and Usage Patterns Across Teams (70% Focus)

The largest ROI component depends on granular visibility into who uses AI effectively and who struggles. Research shows that 70% of AI implementation challenges come from people and process issues.

Get my free AI report to view your team’s adoption map and pinpoint coaching opportunities.

5. Tie AI Usage to Business Outcomes (70% Focus)

Time saved on repetitive tasks, code survival rate, cycle time, bug rates, and deployment frequency drive the most meaningful metrics. Track immediate outcomes such as review iterations and merge time, then follow longitudinal results like incident rates 30 or more days later.

Consider this example. A mid-market team saw 58% Copilot adoption and an 18% cycle time improvement, yet rework rates climbed. Exceeds AI showed that rapid AI-driven commits created disruptive context switching. Targeted coaching then preserved productivity gains while improving code stability.

6. Turn Insights into Coaching Systems (70% Focus)

Teams convert analytics into prescriptive guidance through four steps. First, map current adoption with the Exceeds AI Adoption Map. Second, compare tool effectiveness. Third, surface coaching opportunities. Fourth, track technical debt patterns. BCG reports that 98% of upskilled employees generate new AI use cases, and 85% increase AI usage.

Commit-level visibility enables immediate coaching instead of nine-month setup cycles. Leaders can identify power users who share best practices and developers who need support within hours of implementation.

7. Track Long-Term Impact in the Agentic AI Era (70% + 2026 Trends)

Early adopters report 52% executive adoption of production AI agents and 88% positive ROI on generative AI use cases. As agentic AI spreads, long-term code quality tracking becomes essential for controlling technical debt.

Monitor AI-touched code over periods longer than 30 days for incident rates, maintainability issues, and follow-on edit patterns. This longitudinal analysis gives boards proof that AI investments deliver sustained value instead of short-lived productivity spikes that hide quality costs.

How Exceeds AI Proved ROI for a 300-Engineer Team

A 300-engineer software company used Exceeds AI’s commit-level analytics to measure AI impact. Within the first hour, they saw 58% GitHub Copilot adoption with an 18% productivity lift that correlated with AI usage. Deeper analysis with the Exceeds Assistant revealed rising rework rates from spiky AI-driven commits that signaled context switching.

Using Exceeds AI Adoption Map and Outcome Analytics, leaders separated teams using AI effectively from those struggling. Targeted coaching then preserved productivity gains while resolving quality issues. The company now reports AI ROI to its board with concrete, defensible metrics.

“Exceeds AI provides the code-level visibility we needed, outperforming metadata-only tools like LinearB with actionable insights,” said their VP of Engineering.

Master the 10-20-70 Rule and Prove AI ROI

BCG’s 10-20-70 rule clarifies why AI investments succeed or fail. The 70% people and processes component determines whether algorithm and infrastructure spending creates durable value. Nearly three-quarters of companies with advanced AI initiatives met or exceeded ROI targets by focusing on workforce development and systematic measurement.

Engineering leaders need commit-level visibility to apply this framework effectively. Traditional metadata tools cannot separate AI from human contributions, which makes ROI proof and best-practice scaling difficult. Get my free AI report to see how Exceeds AI delivers the code-level analytics required to master the 10-20-70 rule and prove AI ROI to your board.

FAQ

What is the BCG 70-20-10 rule?

The BCG 70-20-10 rule reverses the standard 10-20-70 framework. BCG’s research uses 10-20-70 for AI adoption and states that 10% of value comes from algorithms, 20% from infrastructure, and 70% from people and processes. This distribution helps organizations avoid heavy technology spending while underinvesting in the human elements that create sustainable AI ROI.

How do you calculate ROI on AI coding tools?

Teams calculate AI ROI with the formula (Benefits – Costs) / Costs × 100. Benefits include productivity gains measured as time saved multiplied by hourly cost, plus quality improvements and reduced technical debt. Costs include tool licenses, training, and implementation overhead. Establish pre-AI baselines for cycle time, defect rates, and deployment frequency, then measure improvements after rollout. Track immediate metrics such as review speed and merge time, along with incident rates 30 or more days later, for complete ROI evidence.

What is the 70-20-10 rule for AI implementation?

The 70-20-10 rule is a variant of BCG’s 10-20-70 framework, and both highlight that the largest share of value comes from people and processes rather than technology. For AI implementation, 70% of effort should focus on adoption coaching, workflow redesign, and organizational change management. The remaining 30% splits between infrastructure at 20% and algorithms at 10%, which keeps investment balanced across all components needed for sustainable AI value.

How does the 10-20-70 rule apply to agentic AI trends in 2026?

Agentic AI increases the importance of the 70% people component because autonomous agents require new governance, collaboration patterns, and risk management processes. With multi-agent orchestration becoming common, the 20% infrastructure investment must support cross-agent communication and policy enforcement. The 10% algorithm focus shifts toward agent capabilities and decision quality instead of simple code generation, which makes the 10-20-70 framework even more useful for managing complex AI ecosystems.

Why do most AI implementations fail to achieve ROI according to the 10-20-70 rule?

Many AI implementations fail because organizations overinvest in the 10% algorithms and neglect the 70% people and processes component. Companies buy advanced AI tools but skip workflow redesign, adoption coaching, and structured change management. Without addressing how people use AI and how it fits into existing processes, even strong algorithms create limited business value. The 10-20-70 rule works by keeping investment balanced across technology, infrastructure, and human factors.