Every function gets its agent

The earlier piece I wrote about agents was anchored in engineering, because that's the easiest case to see clearly. That was a narrow read of what's happening. The shelf is filling up for every function — sourcing, finance close, marketing ops, support triage, QA, design implementation, paralegal review. We are already past the “we'll have to build one” stage and into the “which one do we buy” stage, function by function. The agent for each persona is no longer a roadmap item; for most of them, it is a procurement decision this quarter.

Every department had a layer of repeatable cognitive labor sitting under a thinner layer of judgment. The repeatable layer is now a SaaS line item. Recruiter sourcing has a credible off-the-shelf agent. So does L1 support. So does invoice reconciliation, content moderation, ad-copy variant generation, contract redlining for standard terms, sales follow-up sequencing. None of these are demos — they are shipping into mid-market companies right now, and the distance between credible and good is closing in months, not years.

Some roles don't erode, they disappear. Manual QA testing is the cleanest case: an agent that reads a ticket, generates a test plan, runs it across browsers, and files the bug at higher coverage and lower cost than a human is not a research problem. It is a deployment problem, and the deployment is happening. Front-end implementation work — turning a Figma file into shipped components — is the next domino. Both of these line items will be gone from new org charts within two quarters. Not reduced. Gone from the market for good.

The skill that survives is taste, not typing. The role that survives is the one that decides what to build, not the one that adjusts the CSS or runs the regression suite. This is uncomfortable for anyone whose identity is wrapped around the doing — the test runner, the pixel-pusher, the recruiter who sources by hand, the analyst who reconciles spreadsheets line by line. The honest read is that the doing is the part automating fastest, and the people who stay employed are the ones who treat their current title as a loose costume rather than a fixed identity.

The earlier line was: managing agents is managing engineers. The update is broader. It is also managing recruiters, accountants, marketers, designers, testers, support reps. Every function with a repeatable cognitive core gets an agent on the shelf, and most of them already do. The org chart of 2027 has fewer boxes; the boxes that remain are senior, judgment-heavy, and answer the one question agents can't answer for themselves — what should we be pointed at next.