Capacity.
Capability.
Promise.
The biggest talent transition of a career. Compete on capacity, not headcount.
This briefing tells you what the talent transition looks like in vertical software as AI rewrites the firm-worker promise. Read it before someone else writes it for you.
The 10-page briefing. Worth 20 minutes.
One email. One PDF. Worth twenty minutes of your week.
We send it once. Work emails only.
Every CHRO at a mid-sized European vertical software firm has had the same Monday, 9:14 a.m. Three things in the inbox. Your VP Engineering forwarded Friday's resignation note from your principal engineer who joined eight years ago, the one who carries the why-this-data-model decisions across three of your largest customer segments. He is going to a Series A AI-native competitor in your exact vertical. Your CFO attached the engagement-survey report to the GMT calendar invite. Your CTO forwarded a thread from the architecture channel where two senior engineers are debating whether to ignore the firm's Cursor-restriction policy.
You do not have a recruiting problem. You have an encoding problem. Your firm's workforce strategy is being written every week in decisions you were not invited to. The question is not whether to have one. It is whose handwriting the one you already have is in.
Your moat was never the code. The moat was the accumulated understanding of the domain. It lives in three heads, and the three heads are taking calls.
This is the question your CEO is already asking. The briefing below is what you want in your hand before the next GMT.
Talent Gravity. Capability Compounding. Succession Readiness.
Three questions every CHRO is tracking. None of them used to be the same question. They are now.
Are your senior engineers staying because of you, or despite you?
Your principal engineer resigned on Friday to an AI-native competitor in your vertical. Your best lateral recruit last quarter came from the same place. A-players watch which way you lean the first time something goes wrong. The ones who start looking quietly have already decided.
Is your median engineer's output materially higher in December than January?
The top decile is using agents daily and shipping features in days that used to take sprints. The rest are practicing the workflow they were hired for in 2022. Your L&D budget funds compliance modules and Cursor enablement videos. Neither moves the median.
Of your six senior names, how many have a successor who carries the why?
At least three of the six came through code-review work agents have already absorbed. The external senior hire in 2030 costs a thirty to forty percent premium and brings the previous firm's context.
What you get when you download
An 11-page report for Chief Human Resources Officers at mid-market European vertical software firms. Designed to be read in one sitting before your next GMT.
Your industry, your people function, and why they are one problem
The technical barrier to building a competing product collapsed in 2024. AI-native entrants reaching feature parity in twelve to eighteen months. Your senior engineers reading every tooling decision as a signal. The works council decoding shadow Cursor use. The intersection most CHROs have not named yet: you do not have two problems, you have one.
Four moves across talent, L&D, succession, and trust
Publish the encoding answer the CEO and CTO co-sign in your first 100 days. Ship one architectural role redesigned as a triad unit. Assemble six senior engineers as the authoring council before any firm-wide announcement. Publish three rules, one escalation, one red line for what engineers can do with agents without asking.
Five questions for your next GMT
What your three best engineers would say privately about whether the firm's AI-tooling policy is being designed for them or to them. The role redesigned at task level in the last twelve months. The single-point-of-failure list and which pathways still exist. The deployment fragments you authored versus the ones you decoded after they shipped. The senior engineers asked to author.
Calibrated for each seat at the table.