📊 Full opportunity report: The Model Is Only 10%: The Real Lesson of the New SDLC on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
A recent Google whitepaper reveals that in AI-assisted software development, the core value lies in configuring and engineering the surrounding system, not the AI model itself. This shift impacts how companies should invest in AI tools and development strategies.
A new Google whitepaper published in early 2026 states that the AI model accounts for only about 10% of a system’s behavior in AI-assisted development. The paper emphasizes that the harness and context engineering are the primary factors influencing performance, shifting focus from model upgrades to system configuration and management.
The whitepaper, authored by Addy Osmani, Shubham Saboo, and Sokratis Kartakis, highlights that 85% of professional developers regularly use AI coding agents, with over half using them daily. It stresses that 41% of new code is AI-generated, yet the real challenge lies in system configuration and contextual setup.
The authors argue that the model itself is only a small part—roughly 10%—of what determines an AI agent’s behavior. The remaining 90% involves the harness, prompts, tools, and context. They cite experiments where tweaking only the harness or context improved performance significantly, without changing the model.
This perspective encourages organizations to invest more in system design, verification, and context engineering rather than solely chasing the latest AI models.
The model is only 10%
A Google whitepaper argues software’s biggest shift is from writing code to expressing intent. Its sharpest claim: the model you obsess over is the smallest part of the system — the scaffolding around it does the real work.
The clearest map yet of how serious AI development works — and mostly tool-agnostic. But it’s a Google funnel: the concepts are neutral, the on-ramps point to Gemini, Jules & the ADK. If the harness is 90% and it’s yours, your moat and your costs both live there — so own your scaffolding, route across models, and remember: AI amplifies whatever engineering culture it lands in.
Why the Focus on Harness and Context Matters
This shift redefines strategic priorities in AI development, suggesting that organizations can achieve better results by optimizing system configuration rather than constantly upgrading models. It also impacts cost management, security, and long-term maintenance, as the system setup becomes the primary driver of performance and reliability in AI tools.
MUCAR 892BT AI-Assisted Bidirectional Scan Tool, Full System OBD2 Scanner, Bi-Directional OBD2 Scanner Diagnostic Tool,ECU Coding, 35 Services, FCA Autoauth, CANFD and DOIP, Free Lifetime Updates
- Large 8-inch Display: Ultra-large touchscreen for easy use
- Powered by Android 10: Fast, responsive diagnostics with robust OS
- High-performance Hardware: 4-core processor, 4GB RAM, 64GB storage
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background on the Evolving Role of AI Models
Up to early 2026, the AI community has heavily emphasized model advancements as the key to better performance. However, recent insights from the Google whitepaper challenge this view, arguing that most failures and inefficiencies stem from poor system configuration.
Previous trends focused on acquiring the latest models like GPT-4 or Claude, but experiments show that tuning the harness and context can often yield more substantial improvements than switching models. The paper situates this as a fundamental paradigm shift in software engineering for AI.
“The model is only 10% of what determines behavior; the harness and context are the real crafts.”
— Addy Osmani
AI Prompt Engineering Bible (7 Books in 1): Beginner-to-Pro System to Master ChatGPT and Generative AI for Powerful Results and Real Income (The Generative AI Creator Series)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unclear Aspects of Implementation and Impact
It is not yet clear how organizations will scale their focus on harness and context engineering across different industries or how quickly this shift will be adopted widely. The long-term effects on AI development costs and security protocols remain to be seen.
The Agentic AI Bible: The Complete and Up-to-Date Guide to Design, Develop, and Scale Goal-Driven, LLM-Powered Agents that Think, Execute and Evolve
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Developers and Organizations
Organizations should evaluate their current AI workflows, emphasizing system configuration, prompt design, and context management. Future research and industry practices are likely to focus on developing standardized harness tools, verification frameworks, and best practices for context engineering. Monitoring how this shift influences AI performance and costs over the coming months will be crucial.
AI Use and Verification Basics: Level One General Business Training Manual
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why is the model only 10% of the system’s behavior?
The whitepaper shows that most of an AI agent’s behavior depends on how it is configured, the prompts, tools, and context provided, rather than the underlying model itself.
How can organizations improve their AI systems based on this insight?
Focus on designing better harnesses, prompts, and context management tools, and invest in verification and testing frameworks rather than solely upgrading models.
Does this mean model development is less important?
Not necessarily less important, but the strategic emphasis should shift towards system configuration and management, which have a greater impact on performance and cost-efficiency.
What are the risks of over-relying on harness and context engineering?
Potential risks include increased complexity, maintenance overhead, and security vulnerabilities if system configuration is not managed carefully.
When will this shift in focus become standard practice?
It is likely to accelerate over the next 12-24 months as organizations recognize the cost and performance benefits of system-focused engineering.
Source: ThorstenMeyerAI.com
