5 min readTomas Rekola

Updated on

Build, buy or borrow before you open the req

A third of open roles should never have been opened.

Build, buy or borrow before you open the req

Recruiting teams are measured on filling roles, which means they are structurally disinclined to ask whether the role should exist. Someone has to ask, and it may as well be you, because it buys enormous credibility later.

The four options

Build. Someone internal can do this with three months of support. Cheaper, faster, and it visibly rewards people who stayed.

Buy. A permanent external hire. The default, and the right answer when the capability is genuinely new and durable.

Borrow. Contract, agency or fractional. Correct when the work has an end date, when you are unsure the need is permanent, or when you need a specialist for a phase rather than a career.

Bin. The work is a symptom of a process problem. Two more support agents versus fixing the onboarding flow that generates the tickets.

The triage conversation

Fifteen minutes with the hiring manager, before intake proper. Three questions.

What breaks if this role does not exist for six months? If the answer is vague, the trigger has not fired yet.

Who inside the company is closest to being able to do this? If a name comes back quickly, you have an internal mobility conversation, not a hiring one.

Is the work steady or a project? Projects that get filled permanently create the awkward conversation eighteen months later when the project ends.

Track what the triage saves

Log the outcome of every triage. When a quarter of asks resolve into internal moves, contractors or process fixes, you now have a defensible number showing that the recruiting function reduces cost as well as adding it. That number is what protects your team in a downturn.

None of this makes you slower. A quarter hour of triage against six weeks of search is a good trade even when the answer is always buy.

Sources

  1. 01Future of jobs reportWorld Economic Forum
  2. 02Skills outlookOECD
  3. 03Research on talent, learning and HR technologyJosh Bersin Company
  4. 04People and organizational performance insightsMcKinsey and Company
ShareLinkedInXEmail

Read next in internal mobility

  • The Two-Speed Workforce Plan: Separating Core Capacity From Elastic Talent

    Traditional headcount planning fails when market volatility collides with multi-year business goals. A two-speed workforce model splits predictable core operations from elastic talent networks to protect capacity while controlling fixed employment costs.

  • Modeling Headcount for AI-Augmented Roles

    Traditional headcount planning relies on fixed output ratios per employee. When artificial intelligence alters task completion speed, workforce planners must rebuild capacity models using task-level decomposition.

  • Scaling Skills-Based Architecture Beyond the Pilot Phase

    Moving from an opt-in talent marketplace to a skill-based enterprise requires re-engineering job architectures, navigating European co-determination laws, and aligning with US pay transparency rules. Here is how forward-looking organizations are executing the transition.

  • Why headcount planning fails without structural design

    When you automatically backfill roles, you bake in the inefficiencies of the past. Learn how to identify structural debt, balance global jurisdictions, and design reporting lines that drive actual revenue.

  • Sequencing workforce reductions when headcount targets drop

    As boards mandate margin preservation next quarter, talent leaders must execute phased reductions across external spend, flexible labor, and permanent staff without triggering compliance failures in North America or Europe.

The newsletter

One edition roughly every two weeks: new articles, and what changed in hiring that is worth your time.

Back to all articles