Contract, Contract-to-Hire, or Direct: A Framework for Picking the Right Engagement
One of the most expensive hiring decisions a manager can make is not the salary they offer. It is the engagement model they choose before the search even starts.
Pick direct hire for a role that needed a short-term specialist and you are carrying a salary you cannot justify once the project closes. Pick contract for an evergreen role and the person leaves for a full-time offer eight months in, taking everything they learned with them. Pick contract-to-hire when you already knew you needed a permanent employee and you will pay a conversion fee on top of the contractor premium you already absorbed for six months.
Each of these plays out regularly in Calgary. Not because hiring managers are careless, but because the model decision gets made fast, under pressure, and without a clear framework for what the choice actually implies. The role gets posted, the staffing firm gets briefed, and the engagement model defaults to whatever feels familiar or easiest to approve.
Here is a framework for making that decision deliberately.
The Four Models, Defined Clearly
Before the decision logic, it is worth being precise about what each model actually is, because the labels get used loosely and the commercial terms attached to each matter.
Contract (Pure)
You engage a specialist for a defined period, typically three to twelve months, through a staffing firm that employs or manages the contractor. The person works under your direction but is not your employee. The staffing firm handles payroll, source deductions, and compliance. At the end of the term, the engagement ends with no expectation of conversion and no conversion fee.
In the Canadian market, IT contractor hourly bill rates range from $70 to $150 per hour depending on specialization, with the staffing firm's margin typically sitting in the 25 to 40 percent range on top of the contractor's effective pay rate. That margin covers payroll taxes, benefits administration, insurance, and the firm's overhead. For specialized roles in data, cloud, or cybersecurity, bill rates in Calgary regularly run $90 to $130 per hour for intermediate to senior profiles.
Contract-to-Hire
Structured like a contract engagement at the start, with an agreed option to convert to permanent employment after a defined trial period, usually three to six months. Conversion triggers a fee, either a flat amount or a percentage of first-year salary, typically in the 15 to 20 percent range for mid-level roles. The staffing firm's economic interest is for conversion to happen, which is worth keeping in mind when you assess how they represent the role to candidates and how actively they manage the relationship during the trial period.
Direct Hire (Permanent Placement)
The staffing firm sources, screens, and presents candidates for a permanent role. You interview, select, and extend an offer. The firm earns a placement fee on the candidate's start date. According to Staffing Industry Analysts, the most commonly cited direct hire fee is around 20 percent of first-year base salary, with entry-level roles running closer to 18 percent and senior or specialized roles running 22 to 25 percent. The candidate becomes your employee immediately, with no ongoing billing relationship and no conversion mechanism.
Project-Based Staffing
A variation on contract that deserves its own category because it shifts accountability in a way individual placement cannot. Instead of a single contractor, you engage a team for a defined deliverable: a platform migration, a process redesign, an ERP implementation. The staffing or consulting firm manages the team composition and internal coordination. You manage the outcome. Cost per hour is typically higher than individual placement, but your management overhead is lower and some degree of delivery risk sits closer to the firm.
Five Questions That Determine the Right Model
Work through these in order. Each one narrows the decision.
1. Is This Role Evergreen?
An evergreen role is one the organization will need filled continuously, regardless of project cycles or budget resets. A business analyst embedded in an ongoing program, a project manager running a portfolio that will not close, a process designer supporting continuous improvement across business units. These roles do not end when a project ends. They are part of how the business runs.
If yes: direct hire is almost always the right model. Paying a contract billing premium for an evergreen role means overpaying from the first day and building turnover risk into the engagement, because a strong contractor will take a full-time offer the moment one appears. The break-even point between contractor billing and direct hire costs, accounting for the placement fee, typically sits between eight and fourteen months. For roles expected to run longer than a year, direct hire is almost always cheaper in total cost of engagement.
If the role is genuinely time-bound, move to question two.
2. How Well-Defined Is the Scope?
A well-defined scope has a clear start, a clear end, and a clear definition of done. Migrating a data warehouse to a cloud platform by Q3 is well-defined. Helping with the data platform is not. Implementing a new project delivery framework across three business units by year end is well-defined. Improving how we do project management is not.
If the scope is clear: pure contract is usually the right model. You are buying a capability for a period of time, not building a team member.
If the scope is still forming, move to question three.
3. How Confident Are You in the Role Definition Itself?
This is different from scope. Sometimes the business need is clear but the role required to address it is not. An organization knows it needs stronger business analysis capability but is not sure whether it needs a senior BA with process depth, a systems analyst with technical fluency, or a hybrid profile that sits between the two. Hiring direct into an unclear role definition is one of the most common and costly mistakes, because a wrong hire at the permanent placement level costs you a placement fee, a notice period, and the time to restart the search.
If you are uncertain about the role definition: contract-to-hire is worth considering. The trial period gives you real working evidence of what the role needs to be before you commit to a permanent structure. Used correctly, it is a genuine risk management tool. Used incorrectly, it becomes a way to defer a decision you have already made, which leads to the trap described below.
4. Is This Role Relationship-Dependent?
Some roles succeed or fail almost entirely on technical execution. A contractor brought in to document a current-state process, run a requirements workshop, or configure a platform does not need to be deeply embedded in the organizational culture. They need to be competent, reliable, and easy to work with.
Other roles depend heavily on trust, influence, and the ability to navigate organizational dynamics over time. A business architect shaping how the enterprise thinks about capability. A program manager holding senior stakeholder relationships across a two-year transformation. A process lead driving behavior change across teams that did not ask for it. These roles are where fit materially changes outcomes over a sustained period, and where the cost of a wrong hire extends well beyond the placement fee.
If the role is relationship-dependent: invest properly in the direct hire assessment process rather than treating a trial period as a substitute for rigorous hiring.
5. What Is Actually Driving the Model Choice?
This is the question most hiring managers answer first. It should be last. If the honest answer is that contract is being chosen because it avoids a headcount approval, or because the budget sits in a project code rather than a salary line, the model is being chosen for the wrong reason. This produces the evergreen-role-on-contract problem at scale: permanent organizational need funded through a mechanism designed for temporary work, generating ongoing cost and turnover that accumulates quietly over time.
If internal budget or approval dynamics are driving you toward contract for a role that should be permanent, the right answer is usually to address the approval constraint, not to paper over it with a staffing model that costs more in the long run.
The Contract-to-Hire Trap
Contract-to-hire deserves specific attention because it is both genuinely useful and frequently misused.
The model works when the uncertainty is real: you are not sure whether the role needs to be permanent, or you are not confident enough in a specific candidate to commit to a direct hire fee without working evidence. In those cases, a three to six month trial period is a legitimate risk management mechanism.
It does not work when the uncertainty is manufactured. If you already know you need a permanent employee but are using the contract period to avoid paying a placement fee, two things typically happen. First, strong candidates in the current Calgary market know the game and many will decline a contract-to-hire offer when direct hire alternatives exist, particularly for the senior BA, PM, and process roles where demand is highest. Second, if the person is excellent, you will pay the conversion fee anyway. If they are not, you will have spent three to six months finding out what a more rigorous direct hire process would have told you in three weeks.
For hard-to-fill roles in analytical, process, and program management functions, the strongest candidates are not waiting around. If the engagement model signals ambiguity about whether the organization is serious about the role, those candidates will move on to organizations that are.
When Project-Based Staffing Is the Right Answer
The project-based model is consistently underused in the Calgary market relative to how well it fits certain situations. If you have a defined initiative, a clear deliverable, and a need for a coordinated team rather than an individual, this model shifts accountability in a way individual placement cannot replicate.
A current-state process assessment across multiple business units. A requirements definition and solution design phase for a new platform. A change management program supporting a major technology rollout. In each case, engaging a firm to deliver the outcome rather than placing individuals to contribute to it reduces your coordination overhead and creates a cleaner accountability structure.
The trade-off is cost and control. Project-based engagements typically run at higher effective rates than individual placements, and you have less direct visibility into how the work is being resourced. For organizations with well-defined deliverables and limited internal project management capacity, that trade-off is usually worth making. For organizations still figuring out what they need, individual placements give you more flexibility to adjust as the picture clarifies.
A Simple Decision Guide
The role is ongoing with no defined end: Direct hire.
The scope is clear and time-bound: Contract.
The role definition is uncertain or candidate risk is real: Contract-to-hire, used genuinely.
The deliverable needs a coordinated team: Project-based staffing.
The model is being driven by budget approval dynamics: Solve the approval problem first. The staffing model is not a substitute.
The framework takes twenty minutes to work through properly. That is a small investment against the cost of getting the model wrong on a role that will take sixty days to fill, generate a placement fee or months of contractor billing, and sit at the center of something that matters to the organization's delivery capacity.
Talk to Us
ClarityArc places business analysts, project managers, process experts, and IT leadership roles across Calgary and Alberta. If you are working through a hiring plan and want a second opinion on the right engagement model for specific roles, we are happy to think it through with you.
Get in Touch