Upskill or Hire? Using Skills Data to Make the Cheaper Choice
The decision most HR teams make before they have enough information
A department head sends the message on a Tuesday afternoon: "We need someone who knows [X]. Can we post the job?" By Thursday you're reviewing a job description. By the following week the vacancy is live.
It's a familiar sequence. And it often skips the question that would have saved the most time and money: Does someone here already have most of this skill?
The answer is usually unknown — not because no one cared to ask, but because the information doesn't exist in a usable form. Skills are scattered across CVs filed at hire, performance notes, LinkedIn profiles, and the mental model the manager carries around in their head. There's no single place to look.
So the default is to hire. Hiring is visible, has a clear process, and produces a new person with the credential on their résumé. Upskilling an existing employee can feel slower, harder to justify, and harder to track.
But hiring is also expensive, slow, and not always the right answer — especially when a current employee is already at a 3 out of 5 on the skill you need and could reach a working 4 in a focused six-week stretch.
This article gives you a practical framework for making the upskill-or-hire call with actual data instead of instinct. It covers how to read the skills gap, what the cost signals look like on each side, and how to structure the decision so you can defend it to a department head on a Thursday afternoon.
Why the default to hiring is expensive
Hiring is not free, and it is rarely fast. The average cost-per-hire for a non-executive role runs approximately $5,475, based on SHRM 2025 benchmarking data (reported via Pin, 2025). An older SHRM Human Capital Benchmarking Report puts the figure at $4,129, with an average time-to-fill of 42 days (SHRM, 2017). Both figures cover direct costs — advertising, recruiter time, assessment, onboarding — and neither captures the productivity ramp for a new hire learning the role, or the institutional knowledge that doesn't transfer from an external candidate.
When a hire doesn't work out, the cost multiplies. A bad hire is widely estimated at approximately 30% of that employee's annual salary (SHRM-derived benchmark, via Pin, 2026). For a role paying $60,000, that's $18,000 in sunk cost before you start over.
None of this means hiring is wrong. Sometimes the gap is too large, the skill is too specialized, or the timeline is too short for internal development. But those are specific conditions — not a default. The upskill-vs-hire decision deserves a real analysis, and that analysis starts with your skills data.
For a closer look at how to run a formal gap analysis, see our skills gap analysis guide.
What "skills data" actually means in this context
Skills data is the structured record of what your employees can do and at what level of proficiency — ideally rated on a consistent scale (a 1–5 proficiency scale is common, where 1 is awareness and 5 is the ability to teach) across a defined set of skills, updated regularly, and accessible without emailing five managers.
Most organizations don't have this. What they have is a spreadsheet someone built two years ago, last updated before two rounds of turnover, covering maybe a third of the workforce. That's not skills data — it's a snapshot of a past state. We've written about the real cost of relying on an outdated skills spreadsheet if you want to understand what that maintenance burden actually adds up to.
Usable skills data for an upskill-vs-hire decision has three properties:
- Coverage. It covers the relevant employees, not just the ones who filled out a form voluntarily.
- Currency. It reflects current proficiency, not hire-date qualifications.
- Comparability. Ratings use a consistent scale, so you can actually compare a 3 in data analysis from the ops team with a 3 from the finance team.
When those three properties exist, you can run a real decision. When they don't, you're guessing — and guessing usually defaults to hiring because a new hire comes with a credential that's legible.
Reading the gap: the three scenarios that matter
Not all skill gaps are the same size, and size drives the upskill-vs-hire call more than almost any other factor. Here's how to read the gap against the decision:
Scenario 1: Small gap (proficiency 3 → 4, or 2 → 3 in a supporting skill). One or two levels on a skill someone already uses regularly. This is the clearest upskilling case. The employee has the foundation; they need structured practice, a targeted course, or a stretch assignment. Direct learning expenditure averaged $1,283 per employee in 2023 (ATD 2024 State of the Industry). Even a focused external course or a coaching engagement rarely approaches the cost of a full hire at $4,000–$5,000+.
Scenario 2: Medium gap (proficiency 1 → 3, or a skill cluster missing across a role). The employee has adjacent skills but needs material development — six months to a year of intentional learning, mentoring, or a formal program. This is a judgment call. Run the numbers: estimated development cost versus cost-per-hire, plus the institutional knowledge the employee brings. Often the development path wins, especially if the skill is in a domain where your existing employee's context (your systems, your customers, your processes) is itself valuable. Check the training needs analysis guide for how to structure a development plan once you've made the call.
Scenario 3: Large gap (skill is entirely absent, or the role requires deep seniority the timeline can't accommodate). Sometimes no current employee is close enough. The skill is highly specialized, the need is immediate, or the required proficiency level (a genuine 5 — someone who leads others in this domain) isn't achievable internally in the window you have. This is a legitimate hire scenario. The discipline is in confirming it with data rather than assuming it.
A complete skills inventory also shows you a fourth scenario many teams miss: the employee who is already at a 4 or 5 on the skill in question, just in a different department. That's not an upskilling case — it's a redeployment or cross-training case, and it's often faster than either hiring or development. Read more in our guide on single points of failure and skills coverage.
Building the cost comparison (a worked model)
Here's a simple model to run with your own numbers. The inputs are illustrative — substitute your actual figures.
Upskilling path — illustrative inputs:
- Targeted course or external program: $1,000–$3,000
- Manager coaching time: ~$500–$1,500 (estimated loaded hourly rate × hours)
- Productivity ramp during development: partial, over 6–12 weeks
- Employee retains institutional knowledge, existing relationships, culture fit
Hiring path — illustrative inputs:
- Cost-per-hire: ~$4,129–$5,475 (SHRM 2017; SHRM 2025 via Pin)
- Time-to-fill: ~42 days (SHRM 2017)
- Onboarding and ramp time: 30–90 days additional before full productivity
- Risk of bad hire: ~30% of annual salary if the hire doesn't work out (SHRM-derived benchmark, via Pin 2026)
In a scenario where the gap is small-to-medium and the employee is already embedded in your systems, the upskilling path can cost 20–50% of the total hiring cost — sometimes less. The model only works when you have current proficiency data to anchor it on. Without that, you can't put the employee's starting point in the left column.
Run the numbers for your own situation using our ROI calculator.
Why this decision keeps defaulting to hire (and how to break the pattern)
The structural reason hiring wins by default isn't cost — it's visibility. A hire produces evidence: a signed offer letter, a start date, a new name in the org chart. An upskilling investment produces a development plan that may or may not pan out, tracked in a spreadsheet no one updates.
That asymmetry goes away when skills data is current and accessible. When a manager asks "can we post this job?" and you can pull up a heat-map showing three employees within one proficiency level of the requirement, the conversation changes. The question becomes "which of these three do we develop?" instead of "what's the job title?"
The upskill-vs-hire decision is only as good as the skills data underneath it. If the data is six months old or covers half the workforce, the decision defaults to hire — not because hire is right, but because it's the only option you can see.
This is the practical case for maintaining a live skills inventory. Not as an HR compliance exercise, but as a decision-support tool that makes a recurring, expensive call easier to get right. The skills inventory complete guide covers how to build and maintain one.
Proactive upskilling vs reactive hiring: the compounding difference
There's a longer-run version of this argument worth naming. When organizations wait for a gap to become a vacancy before addressing it, they pay the full hiring premium every time. When they track skills proactively and close small gaps before they become large ones, the gaps rarely become vacancies.
The math compounds. Sixty-three percent of employers cite skills gaps as the top barrier to business transformation over the next five years (WEF Future of Jobs Report 2025). Eighty-seven percent of executives report current or expected skill gaps, and fewer than half know how to address them (McKinsey Global Survey, 2020). The organizations that know — because they track — are in a structurally different position: they can upskill at the margin, continuously, rather than recruit at the peak, reactively.
That's not an abstract workforce-strategy argument. At the SMB scale of 50–500 employees, a proactive approach to skills data can shift the ratio of upskilling to hiring meaningfully — and the cost difference on even a few roles per year is real.
Making the call with a system that supports it
The upskill-vs-hire framework above requires one underlying capability: a current, complete, and comparable record of what your people can do. Without that, every answer to "should we hire or develop?" is a guess dressed up as a decision.
Skills Inventory Manager is built specifically for this. It gives HR teams at 50–500-employee organizations a visual skills matrix — employees on one axis, skills on the other, proficiency ratings on a 1–5 scale — seeded from the start with a 270+ skill taxonomy drawn from O*NET (the US Department of Labor's Occupational Information Network, used and adapted under CC BY 4.0; see onetcenter.org). You don't build the taxonomy from scratch; you start with a working matrix on Day 1 and refine it to your roles.
The gap analysis runs automatically against your role profiles. When a vacancy opens, you can see immediately which current employees are closest to the requirement and how large each gap is — before you decide whether to post.
Pricing is flat-rate by organization size, not per seat: $199–$1,199/month depending on employee count, with a 14-day free trial and no credit card required to start.
If you're making the upskill-or-hire call on gut feel right now, the trial is the fastest way to see what the decision looks like with data underneath it.