GTM Strategy

    Anthropic's Labour Market Report Isn't a Jobs Story. It's a Management Story.

    The interesting number is not what the models can do. It is the gap between that and what companies have actually built into how they operate. That gap is an org-design problem, not a talent problem.

    Chart from Anthropic's labour market impact report with commentary on organisational design
    March 6, 2026
    5 min read
    Share:

    Anthropic's Labour Market Report Isn't a Jobs Story

    Anthropic published its labour market impact research, and most of the commentary treated it as a story about employment.

    I read it differently. I think it is a management story.

    The Gap Is The Finding

    When you look at a chart of what AI can do across task categories, the striking thing is not the capability line. It is the distance between that line and what companies have actually changed about how they operate.

    That distance is not explained by technology access. Every company in the B2B world can buy the same models this week. It is explained by organisational inertia, which is a much more tractable problem and a much more uncomfortable one, because it belongs to management rather than to the market.

    The gap between work still assigned to expensive people and work only people can do

    What Most Businesses Are Still Paying For

    Look at where good people spend their weeks in a typical B2B company.

    Manual research on target accounts. Manual list building. First drafts of everything. Admin and CRM upkeep. Follow-up that should already be systemised. Assembling the same report every Monday.

    All of that is work that is becoming less valuable by the month. Not worthless, but declining, and declining fast enough that paying senior salaries for it is a compounding error.

    This is not a talent issue. The people doing that work are usually capable of much more. It is an org-design issue: the roles were shaped for a world where that work had to be done by a human, and nobody has revisited the shape.

    The Prediction

    The B2B companies that win over the next few years probably will not win because they hired slightly better reps or slightly better marketers.

    They will win because they redesigned the work itself.

    Humans spending more time on judgment, relationships, and closing. Systems taking more of the repetitive workflow that slows everything down.

    Not "replace everyone." Just stop asking expensive people to do cheap, repeatable work.

    Why This Is Harder Than It Sounds

    Three reasons redesign lags capability, all of them organisational.

    Job descriptions are contracts. Telling a team that half their weekly work is moving to software is a difficult conversation regardless of whether the remaining half is more interesting. People reasonably hear it as a threat, and the natural response is to defend the work rather than redesign it.

    The savings are diffuse and the costs are concentrated. Automating list building saves twenty people two hours a week each. Building it costs one identifiable person six weeks. Budget processes are not good at that shape.

    Nobody owns the redesign. Sales owns quota. Marketing owns pipeline. Engineering owns the product. The work of restructuring how go-to-market operates sits between them, which usually means it sits nowhere.

    What A Redesign Actually Looks Like

    Start by auditing where senior time goes, honestly. Not what the job description says, what the calendar and the tooling logs show.

    Then sort that inventory into two columns: work that requires judgment about your specific market, and work that follows rules. The second column is your roadmap.

    Move one item at a time, and move the person up rather than out. The rep who spent half their week building lists should be spending it on conversations, not looking for a new role. That is the difference between a redesign that works and one that produces a morale problem and a hiring freeze.

    The Part Worth Being Honest About

    Redesigning the work does displace some roles, particularly entry-level ones where the job is mostly the repetitive layer. Pretending otherwise is not useful.

    The mitigating factor is that the same shift creates a need for people who can operate these systems, and that role is currently very hard to hire for. Teams that retrain internally will fill it faster than teams that go to the market.

    The Actual Shift

    We are building this into our own go-to-market systems in real time, and the difference is noticeable once the workflows tighten up. Not because output doubled overnight, but because the work that only happened when someone found an afternoon now happens on a schedule.

    That is the real change here. Capability was never the constraint. Attention was.

    Frequently Asked Questions

    Why do companies lag so far behind what the technology can do?

    Organisational inertia, not technology access. Every company can buy the same models this week. What they cannot do quickly is renegotiate job descriptions, reallocate budget from headcount to systems, and find someone willing to own a redesign that sits between sales, marketing, and engineering.

    Who should own the redesign?

    Someone with authority across functions, which usually means a revenue leader or a founder rather than a functional head. The work spans sales, marketing, and operations, so anyone owning only one of those will optimise their slice and leave the handoffs untouched.

    Does redesigning the work mean cutting roles?

    Some, particularly entry-level positions where the job is mostly the repetitive layer. Pretending otherwise is not useful. The mitigating factor is that the same shift creates demand for people who can operate these systems, and that role is currently very hard to hire externally.

    How do I have this conversation with a team without causing panic?

    Lead with what they get rather than what they lose, and mean it. If half of someone's week moves to software and the other half becomes more of the work they enjoy, that is a good deal. If it is a prelude to a cut, they will find out and the next change will be harder.

    Where should a redesign start?

    Audit where senior time actually goes, using calendars and tooling logs rather than job descriptions. Sort the inventory into work requiring judgment about your market and work that follows rules. The second column is the roadmap, and you move one item at a time.

    We build AI-native pipeline systems and you pay per qualified meeting, not a retainer. No paying for activity. You only pay when we book you a qualified sales meeting. See if you qualify.

    Commentary on Anthropic's published labour market impact research.

    AI StrategyOrg DesignGTM StrategySales AutomationAnthropic
    Byline

    About the author.

    Ben Carden

    Co-Founder & CRO of RevenueFlow. Former Gartner sales professional. Building predictable pipeline for B2B companies.

    Ben Carden

    Your next move

    Ready to scale your outreach?

    We build GTM engines that book real meetings. See the receipts.