How AI Labor Breaks the Link Between Growth & Headcount
Failed to add items
Add to basket failed.
Add to Wish List failed.
Remove from Wish List failed.
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
By:
This week I’m going solo to talk about why growth and headcount have always moved together, and why I think AI labor can finally break that link. Technology made people more productive and changed the slope of the line, but more customers still meant more work and eventually more hires.
Using a company that processes 1,000 applications a month with ten people, I walk through what happens when you redesign the work around people, AI agents, and systems instead of just giving everyone ChatGPT. I also cover the catch: AI agents don’t break the link on their own, and a badly designed business will simply move the line somewhere else. If you’re an investor or operator planning growth and headcount, this one is for you.
Episode Timeline & Highlights
[0:00] – The old link between growth and headcount: more customers, more work, more people
[1:05] – Technology changed the slope of the line but never really broke it
[1:41] – Why AI labor can break the linear relationship between growth and headcount
[2:44] – An example: 1,000 applications a month, ten people, and the old pattern of hiring as volume grows
[4:45] – Redesign the process underneath, not just give everyone ChatGPT and hope the slope improves
[5:56] – Designing responsibilities: AI agents gather and verify information, chase missing items, and hand off exceptions
[7:04] – From 1,000 to 10,000 applications: why you add a person, and why volume should not decide it
[8:39] – Volume climbs while the team stays near ten, and growth and headcount start to disconnect
[9:53] – What this does not mean: you can still hire, just not only because existing work grew
[11:00] – Capacity planning, and how AI agents can hold thousands of active contexts around the clock
[12:00] – The catch: AI agents don’t break the link on their own, and the line can reappear somewhere else
[13:42] – Why architecture matters: design the work so more volume doesn’t create new manual work downstream
[15:24] – How growth planning and workforce planning got tied together, and the cost of hiring too slowly or too fast
[17:30] – Instead of asking how many people you need, ask what actually needs to change if you grow by 50%
[18:52] – Why “do more with less” misses the point of what AI labor changes
[20:28] – Economic architecture: hire because a person makes the business better, not because a spreadsheet says so
Key Takeaways
- Growth Used to Mean Headcount: For a long time more customers meant more work and more people, and technology only changed the slope of that line.
- Redesign the Work, Don’t Just Add AI: Giving everyone ChatGPT may improve the slope, but breaking the line means redesigning the responsibilities underneath the process.
- Hire for Value, Not Volume: Headcount can still grow, but it should grow because a person makes the business better, not because volume crossed a threshold.
- The Line Can Reappear: If the architecture is badly designed, the link between growth and headcount simply moves downstream to handoffs, exceptions, and lost context.
- More With Less Misses the Point: The real change is that the amount of work your business can execute is no longer tied to the number of people the way it always was.
Links & Resources
- smrtPhone: https://www.smrtphone.io
- That Real Estate Tech Guy: https://thatrealestatetechguy.com
Before your next planning meeting, pick one growth number and ask what actually needs to change if you hit it, instead of asking how many people you need. You may find the answer is smaller, or very different, than the spreadsheet says. More high-signal conversations coming next.