Deployment expertise is a full-stack role

SaaStr published a piece arguing that the scarce skill of this phase isn't building AI or prompting it — it is deploying it. The "agentic deployment expert": someone who can look at your team, name the eight ways a tool would improve it and the three ways it wouldn't, get it in, train it, and measure the output. Their framing of the eras rings true — 2023 needed engineers because raw models were wild, 2024 was the convoluted-prompt period, and now capable generalists can make agents do real work. Their proposed hiring test is pleasingly concrete: what commercial AI tool did you deploy in the last 30 days, and what measured ROI did it produce?

No labor-market data backs the scarcity claim — it is an experienced investor's opinion, and Craft Ventures was pointing 80% of its investments at AI back in 2023, so the author is talking their book. I'll co-sign anyway, with one large amendment, because the phrase will otherwise get cheapened within a quarter.

"Deployment" cannot mean installing tools quickly. That version of the role already exists in every enterprise — the person who has trialed forty tools, demos beautifully, and leaves behind forty licenses and no changed workflow. If "deployment expert" comes to mean that person, the title will be worthless by Diwali.

The version worth hiring — the version that is genuinely scarce — owns a full stack that has almost nothing to do with software installation. Workflow discovery: finding the recurring work where an agent actually pays, which requires sitting with the team, not reading the tool's website. Data readiness: knowing whether the knowledge base, permissions, and integrations can feed the tool before promising anything. Evaluation: defining what "working" means for this workflow and building the small eval that proves it — before rollout, not after complaints. Security and policy review: what the tool may read, write, and retain, cleared with the people who own those answers. Change adoption: managers enrolled, training mapped to real tasks, the first cohort coached through week three, where usage goes to die. Operating cost: the run-rate at real volume, not the pilot invoice. And sustained outcomes: still measuring at month six, when the honeymoon metrics have worn off.

That is a full-stack role — the stack just isn't technical. It is data, evaluation, workflow, risk, money, and organizational change, held by one accountable person.

At work, the client pattern that proves the scarcity: plenty of AI-aware staff, real budget, tools everywhere — and when I ask who is accountable for integration, adoption, quality evidence, operating cost, and post-launch support on their flagship deployment, five different people answer, which means nobody. The tools were all deployed, in the installation sense. Nothing was deployed in the ownership sense. The gap between those two sentences is the entire role SaaStr is naming.

My rule for hiring it: extend SaaStr's 30-day test by two questions. What did you deploy — and what did you decline to deploy, and why? The expert has a graveyard of tools they evaluated and rejected; the installer has only launches. Then: what broke in month two and what did you change? Real deployments always produce this answer. Demos never do.

Steal this scorecard for the job description: workflow discovery, data readiness, evals, security review, change adoption, cost ownership, sustained outcomes — seven lines, each needing a named example from the candidate's last two quarters. Anyone who clears five is worth a premium. Anyone who clears all seven, hire before your competitor's procurement cycle finishes.

The scarce skill isn't knowing the tools — it's owning everything around the tool that decides whether it worked.