You've decided you need an IT person. The next question is how to bring them on: contract, contract-to-hire, or direct hire. Staffing firms will happily sell you whichever one pays them best, so it's worth understanding how each actually works before anyone quotes you a rate.
The three models, plainly
Contract. The tech is employed by the staffing firm and assigned to you for a defined period, usually three to twelve months. You pay an hourly bill rate that covers their pay, payroll taxes, workers' comp, and the firm's margin. When the engagement ends, it ends. No severance, no unemployment claim against you, no COBRA paperwork.
Contract-to-hire. Same as contract, but with a stated intent to convert to your payroll after a trial period, commonly three to six months. Either the conversion is free after enough hours, or you pay a reduced fee. You get a working interview measured in months instead of an hour in a conference room.
Direct hire. The person joins your payroll on day one. The staffing firm recruits and screens, and you pay a one-time placement fee, typically a percentage of first-year salary, often somewhere between 15 and 25 percent. After that, the relationship is entirely between you and your employee.
The decision tree
Here's how we walk clients through it:
- Is the work a project with an end? An office move, a cloud migration, a system rollout. Contract. Hiring a permanent employee for temporary work is how you end up with a layoff in eight months.
- Is the need ongoing but the budget uncertain? Maybe you just landed a big client and don't know if the volume holds. Contract now, convert later if it sticks. That's what contract-to-hire is for.
- Are you unsure the role justifies a full hire? Same answer. Run it as a contract for six months and let reality tell you.
- Is this a core, permanent role? The sysadmin who owns your infrastructure, the developer maintaining your product. Direct hire. Good people know the difference between a job and an assignment, and the best candidates for permanent roles often won't consider contract work at all.
- Is the skill rare and the market tight? Direct hire, and move fast. Asking a senior network engineer with three offers to take a contract-to-hire "tryout" usually means you get the person nobody else wanted.
Honest math on cost
Contract hourly rates look expensive next to a salary. A tech earning $30 an hour on the staffing firm's payroll might bill to you at $45 or more. Before you flinch, price the alternative honestly. An employee's real cost isn't their salary. Add the employer half of Social Security and Medicare (about 7.65 percent), unemployment insurance, workers' comp, benefits if you offer them, paid time off, equipment, and the recruiting cost to find them in the first place. Loaded cost for a full-time employee commonly runs 1.25 to 1.4 times base salary. Suddenly the contract markup is mostly just those same costs, made visible on one invoice.
Contract still costs more per productive hour over the long run. That's the trade: you're paying for flexibility. You can end the engagement with a phone call, scale up for a project, and skip the hiring risk. For a role you know you'll need for years, direct hire is cheaper. For anything shorter or less certain, the contract premium is usually worth it.
One thing to watch in contract-to-hire agreements: the conversion terms. Know exactly what it costs to hire the person after 90 days versus 180, and get it in writing before the assignment starts. A firm that's vague about conversion fees is planning to negotiate when you have no leverage.
What the tech side looks like
It helps to know how candidates see these options, because it affects who you can get. Contract roles attract people who like variety, are between permanent jobs, or charge a premium for short commitments. Contract-to-hire attracts solid mid-level people willing to prove themselves, but it filters out candidates who already have permanent offers in hand. Direct hire opens the whole market. If you've been running a search as contract-to-hire and the candidates all seem mediocre, the model might be the problem, not the market.
How to know you chose right
Six months in, the answer is obvious. If a contractor rolled off and nothing broke, contract was correct. If your contract-to-hire converted and they're thriving, the trial did its job. If your direct hire is still there and glad they took a real job instead of an assignment, same. The failure modes are just as obvious: a "contractor" you've renewed four times who's clearly a permanent employee in disguise, or a direct hire you knew was wrong by week three and now have to manage out. Match the model to how certain you actually are about the role, and most of this sorts itself out.
Stuck on this, or want it done for you? That's the job.
Email us →