The fastest way to build AI capability inside a company is to give a capable person a real business problem, the authority to work on it, and a deadline for getting it into use. A course can help, but a certificate cannot tell you whether the customer handoff works or the security review will pass. On October 2, Anthropic announced Claude Frontier Academy, a $100 million commitment to train 10,000 engineers by the end of 2027. The interesting part is not the size of the investment. Each participant arrives with a named project to lead at their own organization.
In brief: Do not measure your AI talent plan only in seats trained. Pick an important workflow, name the person who will own its deployment, give that person a business counterpart, and judge the work by whether the process actually changes.
The project comes before the credential
Anthropic’s program starts with a simulated enterprise deployment. Candidates work through use-case selection, security review, and handover, then complete a graded practical. Those who pass enter a 12-week residency in which they lead a real Claude project at their organization with support from Anthropic engineers. A second assessment follows. Anthropic says the first engineers to earn the final badge are expected in early 2027. These are the company’s plans and descriptions, not independently measured results from finished cohorts.
There is a useful contrast inside the same announcement. Anthropic reports more than 175,000 Claude certifications across professionals at 46,000 firms through its Partner Network, and nearly 4,000 Basecamp completions. The new program aims to train 10,000 people more deeply. These are different programs, not proof of business impact. Anthropic is distinguishing broad familiarity from the smaller group expected to take a project through deployment.
That distinction should be familiar to anyone who has paid for a company-wide AI training day and then watched the operating plan remain unchanged. Learning to use an assistant is worthwhile. It does not, by itself, decide who can approve a changed workflow, what records the system may touch, or how a mistake gets corrected. Those decisions are where a pilot becomes a service the team trusts.
Where the gap actually widens
One organization can keep sending people to workshops while waiting for a future hire who will “do AI.” Another can start with a single owner, one process, and a review date. Six months later, the second organization may have something more durable than a list of tools: a record of which permissions were needed, which exceptions blocked the work, and what employees had to change. That is the practice gap. It grows because each real deployment teaches the next one what the slide deck could not.
Anthropic’s first cohorts include engineers from Accenture, Bain, Capgemini, Commonwealth Bank of Australia, Deloitte, McKinsey, Morgan Stanley, and Novo Nordisk, according to its announcement. That list is evidence of who is participating, not evidence that their projects have already succeeded. It also makes the question urgent for a smaller organization: if a large company can afford a residency, what is the smallest version you can run with the people you have?
You do not need to copy the badge. You need to copy the assignment.
Make one person responsible for a live handoff
Suppose an operations team spends every Friday reconciling customer requests from email with records in its service system. A useful internal assignment is not “learn AI.” It is: map the Friday reconciliation, identify the repeatable decisions, and test whether an assistant can prepare a reviewable draft without changing a live customer record. The operations manager owns the process. A technically capable employee owns the proposed system. Both agree on what a successful handoff looks like before the trial begins.
That scenario is illustrative, not a report about a specific company. Its value is in the boundaries. The employee needs time with the people doing the work, access to representative cases, a security reviewer, and a place to record where the draft was wrong. The manager needs to decide who signs off on the final change. If those people are unavailable, the constraint is not a shortage of clever prompts.
Ask for a working result after a short, fixed period: a demonstrable change in the Friday process, a documented reason it cannot safely change yet, or a decision to stop. Count hours spent preparing and checking the output against the old process. Count exceptions that still require a person. Do not claim time savings because a demo ran faster once. A failed trial that identifies a permission or ownership problem is more useful than a successful-looking trial nobody can operate next month.
Training can help an engineer recognize problems sooner. It cannot supply your authority structure or make employees trust a new handoff. See From AI Pilot to Production for the wider transition.
Hire for the work you can name
If your company does need to hire, write the assignment before writing the job description. Name the process, the business owner, the systems the person will need to understand, and the decision they will not be allowed to make alone. Then ask candidates to describe a project they helped move past a demonstration, including what went wrong after the first test. The answer is more revealing than a list of AI products on a resume.
Anthropic is committing $100 million to a program that puts a real project at the center of training. Most businesses will not have that budget, and the program is nomination-based rather than a general enrollment offer. The transferable part costs less but asks more of management: protect one person’s time, put them next to the workflow owner, and hold both to a result that survives ordinary work. The talent gap starts closing when there is work to learn against.
Research and draft: Mai. Editorial direction: John Lipe.