Most companies choose contract-to-hire for reasons that have little to do with their evaluation of the candidate. A contract budget clears in a week. A permanent requisition takes three months of headcount justification and finance sign-off. Hiring leaders with work sitting in front of them tend to use whichever channel moves.
I've spent 14 years in tech recruiting across Philadelphia, Chicago, and DC, running a full desk, which means I'm the same person talking to the hiring leader and the candidate on every engagement. When a contract-to-hire is structured as one from the first conversation, my team converts well over 90% of those people into permanent roles.
These arrangements account for a substantial share of how U.S. companies staff. Staffing firms employed 9.5 million temporary and contract workers over the course of 2025. Below is how the model works, how it compares to permanent hiring on cost and risk, which roles suit each, and why most teams should run both.
Contract-to-hire is a hiring arrangement in which a company brings someone on through a staffing agency for a defined period, typically three to six months, with the stated intent of moving them into a permanent role at the end of it. The mechanics are consistent across most engagements:
That structure is why the model gets described as “try before you buy.” The description is accurate as far as the mechanics go, but it skips past the reason most of my clients reach for it.
Budgeting for a contract is easier than budgeting for a permanent requisition by a significant margin. Opening a permanent role at a large company means headcount justification, finance sign-off, and several layers of approval, and it can be months before anyone posts anything. Approving a contractor means moving money a hiring leader often already controls.
The play I see most often looks like this: a client calls needing a six-month contract-to-hire, interviews one or two people through me, and starts someone within weeks. Meanwhile, they begin the permanent requisition approval, knowing it will clear in roughly six months. When it clears, they already have a trained contractor in the seat.
The two models differ in who employs the worker, how quickly the role gets filled, and where the risk sits if the hire doesn't work out. Cost is where the comparison gets misread most often. An hourly bill rate looks expensive next to a salary, but the bill rate already carries costs that a permanent hire carries too. Benefits alone accounted for 30.1% of total compensation for private industry workers in March 2026, and that's before payroll taxes, recruiting spend, or the cost of a role sitting open.
|
Contract-to-hire |
Permanent hiring |
|
|
Employer of record during the engagement |
Staffing partner |
Your company, from day one |
|
Typical time to start |
Days to a few weeks |
Weeks to months, after requisition approval |
|
How you pay |
Hourly bill rate covering wages, payroll taxes, benefits, and agency margin |
Salary, benefits, and employer payroll taxes |
|
Cost at hire |
Conversion fee, often prorated against hours already billed |
Internal recruiting and interview costs, plus a one-time placement fee if you use a recruiting partner |
|
If it doesn't work out |
Assignment ends and the agency handles offboarding and unemployment |
Performance management, severance exposure, COBRA, and replacement costs |
|
Strongest fit |
Defined-duration work, roadmaps that could shift, roles where on-the-job performance is difficult to assess through interviews alone |
Multi-year needs, roles tied to internal growth, functions that require deep institutional knowledge |
My test is simple. If you can't say with confidence that you'll want this work done by this person two years from now, you're probably looking at a contract.
That bar is higher than it seems. Median tenure for workers ages 25 to 34 is 3 years. Setting a two-year horizon asks the work to hold someone for most of the time they’re likely to stay with an employer. What makes the test useful is that it forces you to examine the work itself: whether the function or project still exists in two years, and whether it changes enough over that span to keep someone interested in staying.
The threshold sits that high because the exit costs are lopsided. Ending a contract means reaching an end date. Ending a permanent hire means performance management, severance exposure, COBRA, unemployment claims, and then paying to recruit a replacement. The employer carries all of it, and none of it shows up in the salary figure that got the requisition approved in the first place.
When a role clears that test, permanent hiring is the right model. From there the difficulty moves to execution, because a direct placement search gets lost more often in scoping and speed than in sourcing.
Some functions fail the two-year test structurally. The work has an end state built into it, and hiring permanently produces turnover you could have predicted at the scoping stage.
The clearest case is a role whose purpose is to make itself unnecessary. A DevOps engineer arrives when deployments break, pipelines are manual, and systems go down at night. Eighteen months later deployments are clean, the pipeline runs itself, and nothing goes down. I watch those engineers leave at almost exactly that point. Nothing went wrong. They finished the interesting work, and no one had lined up what came next.
A few patterns hold across most of my clients:
But the right model for a role can change as the work changes. A role that warranted a contractor during a migration can warrant permanent headcount a year later, and the reverse happens just as often. Before you open a requisition, run the two-year test against the work sitting in front of that role now, not the work that justified it when you first scoped it.
The outcome is usually determined in the first conversation with the hiring leader, before anyone looks at a resume. A client who tells me that this is a real permanent need with a slow-moving requisition already knows they'll want the work done for years. A client who tells me not to call it a contract-to-hire, that there's budget and work but no certainty past that, is saying something different. Both are legitimate, but the distinction matters enormously to the person being asked to take the job.
Candidates sometimes read a contract offer as a lesser opportunity, but in most large organizations it reflects how procurement runs rather than how the company values the role. Saying that plainly is part of my job. What I won't do is let someone believe a permanent role is waiting when the hiring leader never said so. Trust is thin enough already, and an agency that spends it to close one placement costs its client the next five.
Once the contract starts, the failures I see have almost nothing to do with capability. The top reason new hires leave early, regardless of contract type, is mismatched expectations, followed by lack of connection. A manager tells me a contractor isn't taking initiative. I ask whether they've said so directly, and the answer is usually “not really.” In one case a contractor had spent weeks waiting to hear from a colleague who'd been reassigned without anyone mentioning it. Thirty minutes of direct conversation early on is the cheapest retention tool in the arrangement, and it's the one most often skipped.
The decision comes down to what you know about the work: how long it runs, whether it has an end state, and whether it changes enough to hold someone for two years. Most teams answer that once, at the beginning, and never revisit it as the roadmap moves.
Kelly has spent 80 years matching hiring models to business needs, across contract, contract-to-hire, and direct placement. If you're planning a build, a migration, or a team expansion and want a second opinion on how to staff it, my team is glad to talk it through.