When to rent the angle instead of hiring

The fraction problem

Most specialist gaps in a working engineering team are not full-time gaps.

You need somebody who has taken LLM systems to production, or built data pipelines that don't fall over, or done a serious SAP integration. What you need is that depth applied to one problem, for a few months, and then embedded in your team's understanding.

That's a genuine need and it is not a job. When it gets turned into a job, one of two things happens. Either the person is underused and leaves within a year, or the team finds work to justify the hire, and you now have a specialist steering the roadmap toward their speciality.

What hiring actually costs

Four numbers, and only one is the salary.

The search. For a genuine specialist in a European market, four to six months from opening the role to a start date is normal. If the problem is in front of you now, that's the real cost.

The salary, fully loaded. In Germany, a senior specialist in a scarce discipline sits somewhere between ninety and a hundred and forty thousand once employer costs are included. That's a public range and you'll have a better number for your own market.

Ramp-up. Three months before a senior hire is producing at full rate in an unfamiliar codebase, even a very good one.

The permanence. You're committing to a cost structure for a need you haven't yet confirmed is permanent.

What renting costs, honestly

More per day. Considerably more than the day-rate arithmetic of a salary. Anybody who tells you otherwise is either underpricing or about to.

Less continuity. The knowledge leaves unless the arrangement is explicitly designed to leave it behind. That's the thing to negotiate: documentation, two people who understand it, and a handover that's part of the work rather than an afterthought.

A ceiling on depth of context. Somebody working three days a week for four months will not know your business the way a two-year employee does. For a specific technical angle that rarely matters. For anything requiring broad judgement about your product, it does.

The question that decides it

Not cost per day. Ask: is this need permanent, and do I want the knowledge to compound in-house?

If yes to both, hire. Take the four to six months, pay the salary, and get the compounding. That's the correct answer more often than suppliers like us admit.

If the need is real but bounded, or if the four to six months is time the business doesn't have, rent it, and make the handover an explicit part of the arrangement rather than a hope.

If you can't tell whether it's permanent, rent it for three months and find out. That's the case where renting is clearly right, because you're buying information as well as work.

The tell that you've got it wrong

If you hired a specialist and the roadmap now contains projects that exist to use them, the need wasn't permanent and the arrangement is quietly steering the product.

If you rented and the same person has been extended three times without a handover plan, you have a permanent need and you're paying a premium for it. Both of those are fixable and neither fixes itself.