Agents outwork staff at Anthropic, DeepSeek adds web search, and Claude heads to Canada
Anthropic published unusually detailed data on how AI agents are changing its own workforce, DeepSeek shipped an open MIT-licensed model update with a cheap web search API, and Anthropic signed its first Canadian data-centre lease. Together they show the agent economy growing on three fronts at once: how work is organised, what it costs to run, and where the compute physically sits.
Key takeaways
- Anthropic says its staff's AI agents logged about 6 times human work hours by August, while the junior share of its technical hires fell from 27% to 9%; the data is internal and not proof of cause.
- DeepSeek's V4.1-Flash-1017 brings MIT-licensed open weights, a 1-million-token context and a Search & Fetch API priced at $0.75 per 1,000 calls from 31 October.
- Anthropic has leased the first 95 MW phase of EverWind's planned C$10 billion Nova Scotia campus, due online in late 2027, with water, power and regulation still open questions.
Anthropic's own data: AI agents now log 6x staff hours as the junior share of its tech hires falls from 27% to 9%
On October 16 Anthropic published a technical report on its own workforce: agent hours overtook human hours in March 2026, and junior staff are a shrinking share of technical hiring.
Anthropic published a technical report on October 16, titled 'How employment is changing at Anthropic', written by four economists including Peter McCrory and Maxim Massenkoff. It uses the company's internal data: headcount, agent logs, code output, surveys, Slack, calendars and hiring scorecards, plus 17 employee interviews. The headline finding is that in March 2026 the combined hours its AI agents spent working passed the hours its human staff worked for the first time. By August, interactive agent hours for individual employees had reached about six times human hours.
The hiring numbers are just as striking. Anthropic says the junior share of its technical hires fell from 27% to 9%, and juniors' share of technical-department staff fell from 21% to 14% since early 2025. By April 2026, about a third of machine-learning managers and a fifth of software-engineering managers said they were hiring less because of AI. Code commits per engineer reached about five times their level six months earlier. Mentions of candidates' AI tool use in hiring assessments roughly tripled for technical roles and quadrupled for non-technical ones.
The report also describes how the work itself is changing. 'Meta-work', such as building agent tools, writing specifications and monitoring pipelines, rose from 10% to 22% of interactive Claude sessions between fall 2025 and spring 2026. Standing instructions for agents grew from a few hundred in July 2025 to about 8,500 a year later. About 80% of interactive session time is spent with the agent idle, waiting for a human. Reading every word the agents produce would take more than half of a work week, even for non-technical teams. One engineer described 'an army of Claudes, with every one asking for my attention.'
There are important caveats, and the authors list many of them. This is one fast-growing company describing itself, using tools it sells. The 6x figure measures agent runtime, not finished work, and human hours were estimated from headcount at 40 hours a week. Engineers who adopted agents were already on steeper output trajectories, and business growth is a confounder. The junior figures are shares, so they do not show that the number of junior hires fell, and the authors call the junior-employment relationship descriptive, not causal. Survey wording also changed between waves.
Even with those limits, it is the most detailed public look yet at a company that runs largely on agents. The pattern it describes, fewer junior hires, more people managing agents, and more value placed on autonomy and judgment, is likely to spread as other firms adopt the same tools. The authors argue employers should build early-warning systems for at-risk roles and move people internally, but they also say company commitments alone will not fix the slowdown in junior hiring, and that retraining and income support policy are needed too.
Why it mattersIt gives the first detailed numbers on what an agent-heavy workplace looks like, and the skills it rewards (writing instructions, reviewing output, judgment) are ones freelancers and job-seekers can learn now.
👀 What to watch
Whether other employers publish comparable data, and whether the junior-hiring squeeze shows up in broader labour statistics rather than one company's figures.
3 opportunities from this story
Agent instruction libraries for small teams
Anthropic's standing instructions for agents grew from a few hundred to about 8,500 in a year, and 'meta-work' like writing specs more than doubled as a share of sessions. Most small businesses using ChatGPT, Claude or Copilot have no shared instructions at all, so every staff member re-explains the same jobs. Offer to write, test and maintain a library of reusable instructions, project files and skills for a team's most repeated tasks. The deliverable is concrete, easy to price, and it gets better with every revision.
- Best for
- Freelance writers, virtual assistants, operations consultants and no-code builders
- First step this week
- Pick one past client and write 10 reusable instructions for their most repeated tasks, then measure the time saved on a real week of work.
Open the full playbook
Launch steps
- Interview the team about the 10–20 tasks they repeat most often
- Write instructions with clear inputs, outputs, examples and quality checks
- Test each one on real past work and fix failures
- Store them in the team's tool (Claude Projects, custom GPTs, or a shared folder) with a short guide
- Review monthly and add new instructions as the team's work changes
Tools
Risks
Clients may copy the library and cancel; the value is in testing and upkeep, so price the retainer around updates and new tasks. Avoid putting confidential client data into instructions without permission.
'AI orchestrator' bootcamp for graduates and junior developers
Anthropic says the junior share of its technical hires fell from 27% to 9%, while hiring assessments mention AI tool use three to four times more often and interviews focus more on autonomy and judgment. Graduates who can direct agents, write specs and review AI output stand out in that market. Run a short, project-based cohort that teaches exactly those skills, ending in a portfolio of agent-built projects the student can explain and defend. Universities and coding schools in Kenya and across Africa are natural partners.
- Best for
- Senior developers, tech trainers, coding schools and university tech clubs
- First step this week
- Draft a 4-week syllabus around three portfolio projects and invite 5–10 graduates to a free pilot cohort.
Open the full playbook
Launch steps
- Design three projects that need planning, agent direction and careful review
- Teach spec-writing, task breakdown, testing and reading AI-generated code
- Run a free pilot and collect before-and-after work samples
- Turn the best student projects into case studies
- Pitch sponsored seats to local tech employers
Tools
Risks
Don't promise jobs; the report shows fewer junior roles, not more. Tool costs can be high for students, so use free tiers and budget for API credits. Course content dates quickly and needs regular updates.
Agent output review desk
Anthropic says reading all of its staff's agent output would take more than half a work week, and about 80% of interactive agent time is spent waiting for a human. That bottleneck exists in any business using agents for code, content or research. Offer a managed review service that checks, summarises and flags agent output against a client's checklist, so their own staff only see what needs a decision. It suits detail-oriented freelancers and small teams in lower-cost markets serving international clients.
- Best for
- QA testers, editors, research assistants and small outsourcing teams
- First step this week
- Write a one-page review checklist for one type of agent output (for example, AI-written blog drafts or pull requests) and offer a free one-week trial to two prospects.
Open the full playbook
Launch steps
- Choose one output type you can judge well (code, articles, research summaries)
- Build a checklist and a short report template with pass, fix and escalate decisions
- Use AI to pre-screen, then apply human judgment to anything flagged
- Track error rates to show clients the value
- Add more output types once one is running smoothly
Tools
Risks
Liability if you miss a serious error, so define scope clearly and avoid guarantees on correctness. Confidentiality agreements are essential. Clients may automate review themselves over time.
DeepSeek ships V4.1-Flash-1017 with MIT-licensed weights and a web search API at $0.75 per 1,000 calls
DeepSeek released an update to its V4.1-Flash model on October 17, with open MIT-licensed weights, a 1-million-token context, higher self-reported coding scores and new Search and Fetch APIs.
Chinese AI lab DeepSeek released DeepSeek-V4.1-Flash-1017 on October 17. It is a snapshot update to the V4.1-Flash model it launched in September, and it is already live on DeepSeek's website, app and API. The company calls it a 'Pareto improvement in performance and cost': stronger on benchmarks, faster at finishing tasks and producing shorter outputs. The weights are published on Hugging Face and ModelScope, and the Hugging Face model card lists an MIT licence covering both the code and the weights, one of the most permissive licences available.
According to the model card, the model has 763 billion total parameters and a 1-million-token context window, and supports tool calling, a thinking mode with adjustable reasoning effort and image inputs. DeepSeek's own benchmark table shows Terminal-Bench 4.0 rising from 31.2 to 42.3 compared with the previous version, DeepSWE v1.1 from 74.2 to 77.0, and Humanity's Last Exam without tools from 36.8 to 42.6. The company says it trained the update with reinforcement learning to get better at building whole projects end to end, showing demos such as a web racing game.
The bigger practical news may be the new Search and Fetch APIs, which let developers give any app live web search and page reading powered by DeepSeek's in-house search engine. Each endpoint costs $0.75 per 1,000 calls. DeepSeek says calls made through server-side tools in its own DeepSeek Harness, Claude Code and Codex are currently free, with billing starting on October 31 at 16:00 UTC. The model is also optimised for Tencent's CodeBuddy and WorkBuddy tools.
Caveats apply. All benchmark scores are reported by DeepSeek and had not been independently reproduced at the time of writing. The model card's own comparisons show Anthropic's Opus 5 ahead on several tests, so this is not a clean sweep over closed frontier models. At 763 billion parameters, self-hosting needs a serious multi-GPU server, not a laptop. Rate limits and how failed search calls are billed are not yet documented, and organisations with data-sovereignty rules will need to think about routing data through a Chinese provider's API.
For builders, the combination matters more than any single score. Open weights under MIT mean the model can be hosted by third-party clouds and fine-tuned without licence worries, while cheap search makes research and monitoring agents far less expensive to run. Each release like this keeps pressure on the prices of US closed models and gives small teams more room to build agent products with thin margins. The free search window before October 31 is a low-risk chance to test whether it fits a real workflow.
Why it mattersA permissively licensed, near-frontier open model plus cheap web search lowers the cost of building research and coding agents, especially for small teams with tight budgets.
👀 What to watch
Independent benchmark reproductions, third-party hosting prices for the open weights, and how search billing and rate limits work after October 31.
3 opportunities from this story
Low-cost market and competitor monitoring agents
At $0.75 per 1,000 search calls, an agent that checks 50 sources a day costs a little over a dollar a month in search fees. That makes daily monitoring of competitors, tenders, prices or regulations affordable for small businesses that could never pay a research analyst. Build a simple agent that searches, reads pages and emails a short digest on a client's chosen topics. Kenyan and African exporters, NGOs and agencies tracking tenders are good first buyers.
- Best for
- Developers, data analysts and research freelancers
- First step this week
- Build a prototype that monitors one niche (for example, government tenders in one sector) and send a free week of digests to three potential clients.
Open the full playbook
Launch steps
- Pick one niche where people already pay for information
- Build a search → fetch → summarise → email pipeline
- Add source links to every item so readers can verify
- Run it for two weeks and fix noisy or missed results
- Price per topic and offer custom topics as an upsell
Tools
Risks
Search billing details and rate limits are not fully documented yet; budget for change. Some clients may not want their queries sent to a Chinese provider, so keep the search layer swappable. Always cite sources to avoid passing on errors.
'Should we switch models?' cost benchmarks for AI products
Every open release like this raises the same question for teams paying for closed models: could a cheaper model do our job well enough? Offer a fixed-price benchmark that runs a client's real tasks through their current model and through DeepSeek and one or two other open models, then reports quality, speed and cost side by side. Vendor benchmarks rarely match a specific business's work, so a test on their own data is genuinely useful. The report also documents a fallback model if their main provider changes prices or terms.
- Best for
- AI engineers, ML freelancers and agencies that build chatbots or AI features
- First step this week
- Build a reusable evaluation script, then test it on 50 tasks from one of your own past projects to create a sample report.
Open the full playbook
Launch steps
- Collect 50–200 real, anonymised tasks from the client
- Define pass/fail criteria with the client before testing
- Run each model through the same prompts and score the results
- Report quality, latency and monthly cost at the client's volume
- Recommend a primary and a fallback model
Tools
Risks
Results can change with each model update, so date every report. Clients' data must be anonymised or covered by an agreement. Don't overstate small differences from small test sets.
Rapid prototype builds for small clients
DeepSeek says this update was trained specifically to build whole projects end to end, and it is optimised for coding tools such as DeepSeek Harness and Tencent CodeBuddy. Freelancers can use cheaper models like this to turn around clickable prototypes, landing pages or simple web games in days rather than weeks. Package it as a fixed-price 'idea to working demo' service for founders and small businesses who need something to show investors or customers. The skill you sell is scoping and review, not typing code.
- Best for
- Freelance web developers and indie builders
- First step this week
- Build one demo prototype in a weekend with an AI coding tool and publish it with a short write-up of the time and cost.
Open the full playbook
Launch steps
- Define three fixed packages (landing page, clickable app demo, simple web game)
- Write a scoping questionnaire so every project starts with a clear spec
- Build with an AI coding agent and review every file before delivery
- Deliver with a short video walkthrough
- Offer a maintenance or upgrade path
Tools
Risks
Prototype quality depends on your review; AI-built code can hide bugs and security holes. Set clear limits so a prototype isn't sold as production software. Prices for this kind of work are falling, so compete on speed and clarity, not just cost.
Anthropic leases a 95 MW phase of a C$10 billion Nova Scotia data-centre project, its first in Canada
Anthropic has signed a long-term lease for the first 95 MW phase of EverWind's planned data-centre campus at Point Tupper, Nova Scotia, due online in late 2027.
Anthropic, the maker of Claude, has signed a long-term lease for data-centre capacity at Point Tupper, near Port Hawkesbury in Nova Scotia, Reuters reported on October 16. It is the company's first data-centre agreement in Canada. The developer, EverWind, first described its tenant only as a 'leading frontier AI developer' before Anthropic confirmed its involvement. Reuters describes the lease as covering the campus's first phase, and reports put its term at around 20 years.
According to Global News, the first phase will provide 95 megawatts of capacity starting in late 2027. EverWind plans a 325 MW expansion targeted for 2028, which would bring the campus to 420 MW, but that stage depends on commercial, technical and regulatory conditions. The total plan is about C$10 billion of private investment: roughly C$8 billion for the data centre and C$2 billion for onshore wind projects. EverWind says the campus will include several hundred megawatt-hours of battery storage, about 2,000 construction jobs and 215 permanent operating roles.
EverWind CEO Trent Vichie called it the largest private capital investment in Nova Scotia's history. Jacob Glick, Anthropic's head of Canada public policy, said Canadians are using Claude in growing numbers and that the company would meet Canada's bar for responsible data-centre development. The deal comes as AI companies race to secure power and buildings years ahead of need, and as Canada pushes for more domestic, secure computing capacity. The federal government also announced C$100 million the day before for the Wind West offshore wind project.
The project is not without controversy. Cooling is mainly air-based with a sealed water-glycol loop, but water use is still estimated at about 100,000 litres a day in the first phase and about 500,000 litres a day at full build-out; these are design estimates. EverWind says it will fund electricity and water infrastructure so costs are not passed on to local ratepayers. Premier Tim Houston says existing approval processes will apply, while opposition leader Claudia Chender has called for dedicated regulation. Other Canadian provinces and municipalities have pushed back on data centres over power, water and environmental concerns.
For the wider AI market, the deal is a reminder that the next two years of AI capability are being decided now, in leases and power contracts. Capacity in Canada could also help Anthropic serve customers who want data processed inside the country, though the companies have not said how the site will be used. For communities everywhere being pitched large data centres, including in East Africa, the Nova Scotia debate over water, power costs, tax revenue and local ownership is a useful template; EverWind is negotiating a possible ownership stake with a First Nations consortium led by Membertou Development Corporation.
Why it mattersAI capacity is being locked in years ahead through long leases and power deals, and the local fights over water, power and tax revenue are becoming part of the AI story everywhere.
👀 What to watch
Whether the 325 MW expansion wins approval, whether Nova Scotia adopts data-centre-specific rules, and whether Anthropic offers in-country data processing for Canadian customers.
3 opportunities from this story
Independent data-centre impact briefings for communities and councils
Local governments and community groups are being asked to judge huge data-centre proposals, with claims about jobs, water, power and tax revenue they have little capacity to check. Offer short, independent briefings that compare a proposal's numbers with similar projects and list the questions to ask. The Nova Scotia project gives a ready-made comparison: 95 MW, about 100,000 litres of water a day at first, 215 permanent jobs. The same need exists in Kenya and other African markets where large, renewable-powered data centres have been announced.
- Best for
- Environmental consultants, policy researchers, engineers and investigative journalists
- First step this week
- Build a one-page comparison table of 10 announced data-centre projects (MW, water, jobs, power source, investment) from public sources.
Open the full playbook
Launch steps
- Collect public data on announced data-centre projects
- Build a standard checklist covering water, power, tax, jobs and ownership
- Write a sample briefing on one public proposal
- Share it with local councils, NGOs and journalists
- Offer custom briefings for specific proposals
Tools
Risks
You must stay neutral and accurate; developers may challenge your figures. Use only cited, public data and state assumptions clearly. Grant and public-sector payments can be slow.
AI data-centre project tracker newsletter
Contractors, equipment suppliers, recruiters and investors all want early warning of new data-centre projects, but announcements are scattered across local news, regulator filings and company releases. A weekly tracker listing new projects with capacity, timeline, tenant, investment and status can become a paid newsletter or database. Projects like EverWind's, with a 2027 start, a 2028 expansion and 2,000 construction jobs, are exactly the leads suppliers want. Start with one region where you can read local sources well.
- Best for
- Researchers, business journalists and newsletter writers
- First step this week
- Publish a free first issue listing every AI data-centre project announced in one region in the last 30 days, with sources.
Open the full playbook
Launch steps
- Set up alerts for 'data centre' plus MW, lease and planning keywords
- Build a database with consistent fields and source links
- Publish a weekly issue with the top 5 new projects
- Add a paid tier with the full searchable database
- Approach equipment suppliers and recruiters for sponsorship
Tools
Risks
Existing paid trackers serve big markets, so focus on an underserved region. Announced projects often slip or get cancelled; mark status clearly and update it. Check every item against a primary source.
Data-residency maps for businesses using AI tools
As AI companies add data centres in new countries, regulated businesses need to know where their data is actually processed by each AI tool they use. Many small firms in finance, health, legal and education cannot answer that question for their auditors or regulators. Offer a short audit that lists every AI tool a business uses, where each processes and stores data, and which settings or plans keep it in-country. Kenya's Data Protection Act and similar laws elsewhere make this a real compliance need.
- Best for
- Data-protection consultants, IT consultants and compliance freelancers
- First step this week
- Create a template listing 15 common AI tools with their published data-location and retention options, sourced from each vendor's documentation.
Open the full playbook
Launch steps
- Build a vendor reference sheet from official privacy and data-residency pages
- Interview clients to list every AI tool in use, including unofficial ones
- Map each tool to data location, retention and training settings
- Recommend settings changes or alternative plans
- Deliver a short report the client can show regulators
Tools
Risks
Vendors change data locations and terms often, so date every report and re-check. Don't give legal advice unless qualified; partner with a lawyer for regulated clients. Clients may underreport tools staff use informally.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.