What is the 10 20 70 rule for AI?

The 10-20-70 rule for AI says that roughly 10% of AI success comes from algorithms, 20% from technology and data, and 70% from people and processes. This article gives a practical, business-focused answer to the question, 'What is the 10 20 70 rule for AI?' and is written for owners, operators, marketers, and creators who want useful guidance instead of shallow AI hype. The goal is to explain the idea clearly, show where people usually misunderstand it, and give you an action plan you can use immediately.

For a small business, the best use of AI is not replacing people; it is removing friction. AI can draft first versions, summarize research, organize messy notes, answer routine questions, identify patterns, and help a small team look more prepared than its headcount suggests. The mistake is treating AI like a magic employee. The smarter approach is to treat it like a capable assistant that still needs direction, review, and boundaries. Give AI a specific job, feed it accurate context, review the output, and improve the process over time. That habit turns AI from a novelty into a repeatable workflow.

Good AI adoption also requires a simple rule: start with a business problem, not a tool. A restaurant does not need “AI” in the abstract; it may need faster review responses, better social posts, cleaner inventory forecasting, or a chatbot that answers menu questions. A contractor may need proposal templates, follow-up emails, job photos organized into case studies, or a website that answers common quote questions. Once the problem is clear, the tool choice becomes easier. ChatGPT, Gemini, Claude, AI-enabled CRM systems, design tools, transcription tools, analytics platforms, and automation builders all solve different problems. The best AI stack is the one that saves time or increases revenue without confusing the team.

The 10%: algorithms: Algorithms matter, but they are rarely the whole reason an AI project wins or fails. Many organizations can access similar models through cloud providers, open-source tools, or enterprise platforms. The model choice matters, but it is only valuable when attached to a real workflow.

The 20%: technology and data: AI needs clean data, infrastructure, integrations, security, and reliable access. This is the plumbing that makes AI usable. If customer records are messy, systems do not talk to each other, or data is locked in spreadsheets, AI outputs will be limited. Technology and data are the foundation, but not the whole house.

The 70%: people and processes: The biggest share is workforce and workflow change. People need training, permission, incentives, and clarity. Processes need redesign so AI output becomes part of real work. BCG emphasizes that people and processes carry the largest share of AI transformation value.

Why the rule matters: The rule prevents leaders from overbuying software and underinvesting in adoption. A company can spend six figures on an AI platform and still fail if employees do not know when to use it, managers do not trust it, and workflows stay unchanged.

How to apply it in a small business: For every AI project, spend time on the team and process, not just the tool. If you add an AI chatbot, define escalation rules and update FAQs. If you add AI content workflows, create review standards. If you add AI analytics, schedule meetings where insights are discussed and acted upon.

What success looks like: Success looks like a repeatable workflow, not a random prompt. Employees know the use case. Data is ready. Outputs are reviewed. Decisions improve. Time is saved. Customers get better service. The rule reminds you to measure operational change, not just tool adoption.

Common mistakes to avoid: Do not treat AI transformation as an IT purchase. Do not assume the model is the hard part. Do not skip training. Do not add AI on top of a broken process without removing old steps. Do not measure adoption by logins alone. Measure real work completed with AI support.

A practical action plan: Take your next AI idea and divide the work according to the rule. Spend 10% choosing the model or tool, 20% preparing data and integrations, and 70% designing the workflow, training users, setting review standards, and measuring results. This allocation will feel slower at first but produces more durable value.