Contract-to-hire conversions: what makes them stick

Contract-to-hire is sold on a simple premise: you get to see how someone actually works before you commit. That premise is sound. What gets less attention is that a conversion which happens is not the same as a conversion which lasts, and the gap between those two outcomes is almost entirely decided in the first month of the contract rather than at the point of offer.

What the data says

Conversion rates and twelve-month retention are the two numbers to hold a staffing partner to, and they should be quoted together. A firm converting a high proportion of contractors but losing them within the year is not running a trial period, it is running a slow permanent hire with extra paperwork.

The pattern worth understanding is that these two numbers are not independent. Engagements that convert early — before the agreed term, on the strength of visible work — retain considerably better than engagements that convert at term by default. Early conversion is a signal that the match was genuinely good. Conversion at term is often a signal that nobody wanted to restart the search.

Four things that predict a conversion sticking

1. The contractor was given real work in week one. Not documentation cleanup, not “get familiar with the codebase” for a fortnight. A scoped, shippable piece of work with a deadline. This is the single strongest predictor, because it is the only way either side learns anything during the trial. A contractor kept on the periphery for two months has been evaluated on nothing.
2. Somebody owns them. A named manager who runs a weekly one-to-one from the first week, the same as with an employee. Contractors are routinely excluded from the management rhythm on the theory that they are temporary, which guarantees the trial produces no evidence.
3. The conversion terms were agreed up front. The salary band, the target date and the fee position, written down before the contract starts. Conversions that go wrong late almost always go wrong on money that nobody wanted to discuss at the beginning.
4. They were included, not seated nearby. Access to the systems the team uses, presence in the planning meetings, a name in the team channel. The practical exclusions — no calendar access, no design review invite — read to the contractor as a decision that has already been made about their future.

The trial period is a two-way test

The framing everyone uses is that the client evaluates the contractor. In practice the contractor is running a more thorough evaluation of you, and with better information, because they see how the team behaves under normal conditions rather than under interview conditions.

They are learning whether estimates are treated as commitments, whether the on-call rotation is as described, whether the technical debt discussed in the interview is being addressed or narrated, and whether the manager’s stated approach survives contact with a bad week. By the time you offer conversion, they have formed a view, and it is more evidence-based than yours.

This is why good contractors decline conversion, and why the decline usually surprises the client. Nothing went wrong in the last week. The decision was made in week three, and there was no mechanism through which anyone would have found out.

The mechanism is straightforward: ask. A short, genuine conversation at the thirty-day mark about how the engagement is going from their side — asked by the manager, not by the agency — surfaces almost everything that would otherwise arrive as a declined offer three months later.

A checklist for month one

• Day one: access to every system they need, including the ones they will not need until week three. Nothing delays a trial like a two-week wait for a repository permission.
• Day one: a scoped first deliverable with a date. Small, real, and theirs.
• Week one: a thirty-minute one-to-one with the manager they report to, scheduled as a recurring meeting rather than a one-off.
• Week one: written conversion terms — band, target date, fee position — in the contractor’s hands. If those cannot be stated in week one, the engagement is not really contract-to-hire.
• Week two: included in planning, retro and code review as a full participant.
• Week four: the two-way conversation. What is working, what is not, and whether the role they are actually doing matches the role they were sold.
• Week four: an honest internal answer to one question — if the term ended tomorrow, would we convert? If the answer is no, say so now, while there is still time for it to change.

None of this is expensive. All of it is routinely skipped, on the grounds that the contractor is temporary — which is exactly the assumption the engagement was set up to test.