growth

The Contractor-First Hiring Strategy: Test Roles Before You Commit

Last year I hired a "Head of Growth" who looked perfect on paper. Stanford MBA, 8 years at top startups, great references. Three months and $45,000 later, we parted ways.

James Heaney
James Heaney
CTO & Co-founder
|
January 3, 2026·5 min read
The Contractor-First Hiring Strategy: Test Roles Before You Commit

Last year I hired a "Head of Growth" who looked perfect on paper. Stanford MBA, 8 years at top startups, great references. Three months and $45,000 later, we parted ways. He was smart. Just wrong for our stage.

That mistake changed how I hire. Now I test every role with contractors before making it full-time. Not as a probation period or a trick - I'm upfront about it. "Let's work together for 2-3 months and see if this makes sense for both of us."

The results have been good. My next three hires started as contractors. All three converted to full-time. Zero regrets.

Why traditional interviews fail

Interviews test whether someone can talk about doing a job. Working together tests whether they can actually do it.

I've seen brilliant interviewers who couldn't execute. I've seen awkward interviewers who crushed it once they started working. The correlation between interview performance and job performance is weaker than most founders want to admit.

The contractor-first approach fixes this. You're not guessing if someone can do the work. You're watching them do it.

How to structure the trial

Be honest from the start. Tell candidates this is how you hire. Some will self-select out - that's fine. The ones who stay are confident in their abilities and comfortable being evaluated.

Set a clear timeline. I usually do 8-12 weeks. Shorter than that and you're not seeing enough work. Longer and you're stringing people along.

Define what success looks like. For a developer: ship two features end-to-end. For a marketer: run one campaign from idea to results. For a sales rep: close three deals. Pick metrics that actually matter for the role.

Pay market rate. This isn't a discount labor scheme. If you're cheap here, you'll attract desperate people, not good ones.

What I look for during the trial

Output quality matters, obviously. But I'm also watching for things you can't see in an interview:

Communication patterns. Do they flag blockers early or wait until deadlines pass? Do they ask questions when stuck or spin their wheels for days?

How they handle feedback. Nobody gets everything right the first time. What happens when you point something out? Some people get defensive. Some improve. You want the second type.

Consistency. Week one enthusiasm is easy. Week six grind is where you see the real person.

Whether they're actually interested. Are they learning the product? Asking about strategy? Or just completing tickets and collecting a check?

The conversion conversation

If it's working, make the offer before the trial ends. Waiting until the last day feels transactional. Around week 6-8, if I'm confident, I'll say "this is going well - let's talk about full-time."

If it's not working, end it early. Don't let a bad trial drag on. You're wasting their time and yours. I try to give 2 weeks notice and be direct about why it's not a fit.

Sometimes it's unclear. That's useful data too. If after 8 weeks you're not sure, you probably have your answer. A strong hire should be obvious by then.

Making the logistics work

The tricky part is managing contractor payments during the trial. You're potentially paying multiple people in different countries while figuring out who to keep.

We built Grade partly because this was painful. Adding trial contractors should be as simple as entering an email address. They pick their own payment method. I pay everyone with one click every two weeks. When someone converts to full-time, the transition is seamless - same person, different status.

More importantly, I can tie payment to verified work. Trial candidates get paid when they deliver, not just when time passes. That clarity helps both sides.

When not to use this approach

Some roles don't work as contractor trials. Anything requiring deep institutional knowledge takes too long to evaluate. C-level executives need to own strategy, which is hard to do as a contractor. Roles with heavy compliance requirements (finance, legal) have regulations that make contractor status complicated.

And some candidates will say no. Top-tier talent with multiple offers might not wait around for a trial period. You have to be willing to move fast when you find someone great. I've occasionally skipped the trial when the fit was obvious, but those are exceptions.

The real benefit

Beyond avoiding bad hires, this approach changes how you think about roles. When you're paying per deliverable instead of per seat, you start asking better questions. Do I actually need this full-time? Could two part-time specialists beat one generalist? What would this role look like if I could only afford half the hours?

Some of my "trials" never converted to full-time - not because the person was bad, but because the role didn't need to exist the way I'd imagined. That's a win too. I avoided a hire I didn't need.

The $45,000 Head of Growth mistake taught me something: hiring confidence and hiring evidence are different things. Now I get the evidence first.

#contractors#hiring#startups
James Heaney
James Heaney
CTO & Co-founder

Building Grade to make paying contractors effortless.

LinkedIn

Ready to scale your contractor payouts?

With just their email, you can track results, send payouts, and automate tax forms.

Try Grade Free →