Skip to main content

The New Unit of Planning: Headcount vs Tokens

 

As I work through another planning cycle, the ritual remains the same: the spreadsheet opens, the roadmap is prioritized, and we start the negotiation for more "heads." In my world, and likely yours, the engineer has always been the fundamental unit of progress. If we want to move faster, we hire more of them.

But this year, the math feels... off. I’m asking myself - do I really need a new hire for this or do I just need a larger token budget?

We are moving away from a world of Fixed Labor and into a world of Variable Compute. When you hire a Senior Engineer, you’re buying a long-term asset. You’re also buying a 6-month onboarding lag, a management overhead, and a permanent line item on the P&L. 

When you "hire" tokens you’re buying instant, fractional capacity. If your engineers are telling you they can automate 30% of the "toil" using a custom-tuned model, the traditional argument for that extra engineer disappears. We are moving from mere management to true resource orchestration, balancing human architects with pure compute power.

The Shadow COGS and the Entry-Level Gap

This transition isn't without significant risk. Depending on your organization, you might only see your HR costs; the cost of tokens may be centralized elsewhere, masking the true COGS (Cost of Goods Sold) for your team. Beyond the budget, there are two existential threats to the traditional org chart:

  • The Context Ceiling: AI is a world-class executor but a mediocre architect. You buy tokens for the "What" (the code), but you hire humans for the "Why" - the strategy, the empathy, and the organizational alignment.

  • The Junior Pipeline Crisis: If we replace all entry-level headcount with tokens, we aren’t just saving money; we are eroding our talent pipeline. If nobody is doing the "easy" work today, nobody will be qualified to do the "hard" architectural work in five years.

The New Managerial Playbook

As I’m sitting down to plan the next quarter, I’m adding three columns to my planning template to build a Hybrid Resource Plan:

  • Human FTE: Reserved for high-ambiguity, high-leverage, cross-functional and strategic architectural work.

  • Token FTE: Dedicated to repetitive, high-volume, and well-defined execution tasks.

  • The Hybrid Buffer: A "flex" budget that allows my leads to choose between hiring junior engineers, or lean into a compute-heavy automation strategy mid-quarter.



We are no longer just "People Managers." We are becoming System Architects. Our job is to orchestrate a hybrid workforce where the "org chart" includes both people with names and models with versions. The goal remains the same: to deliver on business goals effectively by leveraging every resource available to us. The next time one of my managers asks me for an extra new hire for a roadmap item, I’m going to ask them “if I gave you another $50k in API credits, could you make that roadmap item happen?”. I’m curious to see what they say, and if they’ll still give the same answer 6 months from now. 

How are you working through this? Are you further ahead in this evolution? If so, any tips to help others navigate?
Labels:

Comments

Post a Comment

Popular posts from this blog

The "Just-in-Time" Manager and the 1:1 Gemini Gem

  We’ve all been there. The calendar notification pings. You finish your previous meeting (which ran over by three minutes), and as the Zoom window for your next 1:1 pops up, you’re frantically tabbing through Google Docs and Slack. You’re trying to remember: What did we talk about last time? Did that project go okay? Wait, did they mention a vacation or a baby? You’re "prepping" while the meeting is already happening. You’re physically present, but mentally, you’re a detective trying to solve the mystery of your own calendar and trying to switch off the last meeting.  It’s a common trap for managers, especially as their direct reports grow and they now have skip level 1-1s, or skip-skip level 1-1s. Our schedules are a mosaic of context-switching, and unfortunately, the deep, reflective prep our direct reports deserve is often the first thing to get squeezed out as we are dealing with incidents or other emergencies.  From "Zero Prep" to "Instant Context" R...
Post a Comment
Read more

Prompting AI Adoption for Skeptical Engineers

We’ve all seen the headlines. "AI will replace the junior engineer”.  "The 10x engineer is now a 100x engineer." In leadership meetings almost every conversation comes back to velocity and how we could unlock efficiency with AI.  But when you talk with the team the reality can be different. Your most senior engineers - the ones who built the core of your system - are looking at Copilot or Cursor with a squint. Some see it as a toy; others see it as a threat to the craft; a few see it as a glorified Clippy that hallucinates half-baked solutions into their carefully maintained repos. As Engineering Managers and Directors, we are currently in a delicate spot. We are being asked by the business to "leverage AI," but we are being told by some of our best people that it’s "not quite there yet". How do we advocate for AI without sounding like a marketing brochure? How do we move the skeptics without losing their trust? 1. Validate the Skepticism (Because it...
Post a Comment
Read more

Prompting the org

For a decade, my job as an Engineering Leader was about clarity and predictability. I optimized for the team's velocity, coached managers on team dynamics, helped engineers maximise their impact and tried to build a "machine" where human output was the primary engine. Then the engine changed. We’ve all seen the headlines about 10x productivity and AI-native workflows. My team is early in the adoption curve. We’re still figuring out which tools are signal and which are noise. Honestly? We’re still learning how to work in a world where the "how" (the code) is becoming a commodity, and the "what" (the intent) is everything. A lot has been written about what this means for engineers, but what does this mean for engineering managers, directors, VPs and executives? I’ve realized that as we integrate AI, I’m quickly realizing my role is shifting from managing the output to refining the input - what I call the 'Org Prompt’. In AI, a system prompt sets the ...
Post a Comment
Read more