Staffing is the recurring decision at the heart of a services business: an engagement needs a person — who? Made well, it balances four inputs at once:
- Availability — who actually has free hours in the needed weeks, read from the forecast rather than from memory or hallway knowledge.
- Fit — skills, seniority and domain against what the slot needs; a mis-leveled assignment burns either margin (over-staffed) or the client relationship (under-staffed).
- Economics — the person's cost against the engagement's rate; staffing decisions are margin decisions wearing a scheduling mask.
- Continuity — pulling the only person who knows a system to staff something new trades one problem for two.
The classic failure at 10–50 people is staffing by loudest project manager: two PMs promise the same person, and the conflict surfaces after both clients have heard a name. The fix is structural, not heroic — one shared view of allocations that every promise gets checked against.
The second discipline is internal-first: before opening a requisition, check who is rolling off. Redeploying someone free in three weeks is faster and cheaper than hiring — and it is exactly the option that stays invisible without a forecast.
In Helia, staffing runs on the capacity matrix and the 12-week forecast; an AI fit score gauges an engineer-to-project match where enabled; and the redeployment board connects capacity to recruitment — people rolling off soon are matched to open requisitions by department and skill overlap, so internal moves get first look before external hiring.