CoreWise Academy

Practice · Layer V / Broad

Why a few people get far more from AI

Andrej Karpathy names three causes for the gap between casual and heavy AI use: the size of the problem, the kind of work, and access. Act on each, starting with one problem.

Nº 069 · Vol. I·7 min read· Updated November 2026

Most people who use AI get a better search engine. A much smaller group gets weeks of work finished from one request. Andrej Karpathy names three causes for the difference, and you can act on each.

Karpathy is an AI researcher who led AI at Tesla and helped found OpenAI. In a post on October 11, 2026 he sorted the world into four groups by how they use AI. The numbers are his own rough estimates.

GroupKarpathy’s estimateWhat AI looks like from there
Have barely used AIAbout 6 billion people, 75% of the worldNothing yet
Use a free chatbot now and then1 to 2 billion, about 20%A better search engine or a writing aid
Use the best paid models at work, for code and mathAbout 20 million, 0.2%Projects that took weeks or months, finished by AI agents from one request
Work inside an AI lab, on systems not yet releasedAbout 5,000Thousands of agents working together for weeks on one project

An agent is AI software that carries out a task over many steps without a person directing each one.

Austin Marchese, who makes videos about building with Claude, turns the three causes into steps in How To Prompt Claude Like The Top 1% (Karpathy’s Method).

The video calls the third group 2% of the population; Karpathy’s figure is 0.2%. It includes a paid segment for Viktor, an AI assistant that works inside Slack, with Marchese’s referral link and discount code.

01Three causes of the gap

Here are the three causes in Karpathy’s words, with what you can change about each.

CauseIn Karpathy’s wordsWhat you change
Problem size”The impact scales with ambition, problem size, and horizon.”Bring a bigger problem that you care about
Kind of work”Capability peaks in domains that are digital, verifiable and economically valuable.”Give AI the parts of your job that happen on a computer and can be checked
Access”Access. Free-tier, paid-tier, internal.”Find out whether your plan’s usage limit changes how you work

02Bring a bigger problem

Small questions use almost none of what the models can do. Karpathy’s line: “A question with a paragraph answer barely stresses the system.” His advice is to keep a supply of big, hard problems you care about.

The first attempt at a big problem often fails. Marchese says a person with no stake in the problem quits at that point and decides AI cannot do the job.

To find a problem you have a stake in, he asks two questions:

What do you keep putting off? A task you avoid is one to hand to AI completely.

What takes hours without your noticing? That is work you like. Keep doing it, and use AI to do more of it or do it better.

Five questions before you build with AI covers choosing the first thing to build from your answers.

Pick a problem in a field you know. Anthropic studied sessions in Claude Code, its tool that lets Claude work on your files and run programs. It had Claude rate each person’s expertise at the task in front of them, based on how precisely the person gave directions, what they asked Claude to check, and who corrected whom. Job title played no part. Sessions rated expert got more from each prompt:

For each promptNovice-rated sessionExpert-rated session
Actions Claude takesAbout 512
Words Claude writesAbout 6003,200

The study found that knowing the problem counted for more than knowing how to code. It observed sessions and ran no experiment, so it shows that expertise and output rise together and leaves open which causes which.

Then ask for more than you normally would. Marchese says the heaviest users assume AI can do more than seems possible, and that the limit is what you think to ask for.

“Can I use AI for this?”

Austin Marchese, reading the note he keeps on his desk, “How To Prompt Claude Like The Top 1% (Karpathy's Method)” · 2:45

He gives three ways to ask for more:

Take a problem apart before AI solves it and Split big AI tasks into steps and checks cover working on a big problem once you have chosen it.

03Use AI where it is strongest

The models are strongest at work that happens on a computer, has a result that can be checked, and earns money. Karpathy explains that the models learn by practicing tasks where a program can check the answer, and the labs pick the tasks that can bring revenue. Code and math fit best.

Much office work is conversation. Karpathy notes that executives and many other professionals spend their days talking to people, so what AI can do stays “second-hand and a bit abstract” for them.

Marchese says to ask AI for software that does part of your job, even if you have never written code. Anthropic’s report on its own workforce looked at employees who had no record of writing code there. Their monthly sessions with coding agents grew 45-fold between August 2025 and May 2026. One sales representative in the report built a custom dashboard in three to four hours.

Marchese gives three ways to start, smallest first:

Use AI inside the apps you already work in. If your work lives in a spreadsheet, run Claude in the spreadsheet. A practical guide to Claude’s features covers where Claude can run.

Build a small tool for one annoyance. Marchese calls these micro tools. Name the annoying task and ask Claude to suggest an artifact for it. An artifact is a small working app or document that opens beside the chat. Build a personal tool with Claude covers building one from start to finish.

Save a repeated process as a skill. A skill is a set of saved instructions Claude follows for one task. Marchese sorts skills into three types so the small ones get reused by the larger ones:

Skill typeWhat it doesExample for reviewing an inbox
UtilityOne small task you repeatDecide whether an email is spam
Task completionA whole job, built from utility skillsDraft a reply to an email
OrchestrationRuns several skills in orderReview the inbox

Write a first skill as one piece. Marchese says the three types help later, once you have several skills.

When a skill gets something wrong, tell Claude what was wrong and why, and ask it to update the skill. Write smaller Claude skills that work covers writing a skill. Make skills improve after each run covers repairing one.

Expect your first tool to take longer than doing the task by hand. Marchese says many people quit there. Choose AI changes worth your time covers counting that cost before you commit.

04Check if your plan is too small

Karpathy’s third cause is access, in three tiers: free, paid, and internal. The internal tier belongs to people who work at the labs. Your choice is between a free plan and a paid plan, which comes in several sizes.

Every plan has a usage limit: a cap on how much you can use the AI before you have to wait for it to reset. Marchese’s rule is to upgrade when a usage limit changes what you do. He asks two questions:

A small plan costs less money, but Marchese also counts the time spent waiting and the work he cuts down to fit the limit. He budgets for the subscription the way he budgets for his laptop and internet connection.

His work is building software and videos with these tools. Your answers to the two questions tell you whether a larger plan is worth it for your work.

Before you pay more, get more from the plan you have:

Stop hitting your token limit covers finding where a session’s usage goes.

05Try it on one problem

Paste this prompt into a new chat. Claude interviews you and finishes with a one-page plan.

I want to get more from AI on one problem that matters to me. Interview me one question at a time and wait for each answer. This conversation produces a plan only: do not build anything yet.

1. Ask what I keep putting off at work, and what I spend hours on without noticing. Ask which of those I know best, and help me pick one problem from my answers.

2. Ask what I would normally request from you for that problem. Then describe a version 10 times more useful, and ask what would have to be true for it to work.

3. List the parts of the problem. For each part, say whether it happens on a computer or in person, and whether someone could check the result. For the parts on a computer with a result I can check, propose one small tool or one saved skill, and say which to build first.

4. Ask how often I wait for a usage limit to reset, and how often I change a request because of a limit.

Finish with a one-page plan: the problem, the bigger version, the first thing to build, how I will check that it works, and whether my plan is limiting me.

FAQ

You mostly ask AI questions that one paragraph can answer. Which of the three causes is that, and what do you change?

Problem size. Karpathy writes that a question with a paragraph answer barely stresses the system. Pick one large problem you care about, from the tasks you postpone or spend hours on without noticing, and ask for a bigger version of the result.

Your job is mostly meetings and calls. Where can AI still do strong work for you?

In the parts of the job that happen on a computer and have a result you can check. Ask Claude to build a small tool or a saved skill for one of those parts, such as the report you assemble after the calls.

How do you tell whether your plan is limiting your work?

Count how often you wait for a usage limit to reset and how often you change a request because of one. If either happens, first stay on the default model and turn repeated steps into a program. If a limit still gets in your way after that, consider a larger plan.

Sources
  1. Austin Marchese · “How To Prompt Claude Like The Top 1% (Karpathy's Method)”
    cited at 0:52 · 1:35 · 2:03 · 2:33 · 2:45 · 3:09 · 6:56 · 7:50 · 8:37 · 8:51 · 9:17 · 10:00 · 10:34 · 11:21 · 11:33 · 12:22 · 12:58 · 13:27 · 13:33 · 15:02 · 15:13
  2. Andrej Karpathy · “Post on the widening gap in AI use, October 11, 2026”
  3. Anthropic · “Agentic coding and persistent returns to expertise”
  4. Anthropic · “How employment is changing at Anthropic”